OpenPeripheral Energy Monitoring

battery = peripheral.wrap("back")
print(battery.getMJStored("unknown")

battery = peripheral.wrap("back")
dir = {
"north",
"west",
"east",
"south",
"up",
"down",
"unknown",
"front",
"back",
"left",
"right",
"top",
"bottom",
}

for side = 1, #dir do
print(battery.getMJStored(dir[side]))
end

0
0
0
0

0

local battery = peripheral.wrap("back")
local dir = {

local battery = peripheral.wrap("back")
local dir = {
"north",
"west",
"east",
"south",
"up",
"down",
"unknown",
"front",
"back",
"left",
"right",
"top",
"bottom",
}

for _,side in ipairs(dir) do
  print(side .. ": " .. battery.getMJStored(dir[side]))
end

Dog, on 22 August 2014 - 05:22 PM said:

FIrst, you should always localize your variables and functions like so…

local battery = peripheral.wrap("back")
local dir = {

Next, try this code and tell me what you get…

local battery = peripheral.wrap("back")
local dir = {
"north",
"west",
"east",
"south",
"up",
"down",
"unknown",
"front",
"back",
"left",
"right",
"top",
"bottom",
}

for _,side in ipairs(dir) do
  print(side .. ": " .. battery.getMJStored(dir[side]))
end

The code you were using was counting from 1 to the number of entries in the 'side' table then passing that number instead of the side.

FXgamer247, on 22 August 2014 - 08:09 PM said:

This returns: "temp: 19: Argument direction cannot be null"

So i tried changing the print to print(dir[side]), and it print absolutely nothing.

print(side)

local battery = peripheral.wrap("back")
local dir = {
"north",
"west",
"east",
"south",
"up",
"down",
"unknown",
}

for _,side in ipairs(dir) do
  print(side .. ": " .. battery.getMJStored(side))
end

Dog, on 22 August 2014 - 08:31 PM said:

FXgamer247, on 22 August 2014 - 08:09 PM said:

This returns: "temp: 19: Argument direction cannot be null"

So i tried changing the print to print(dir[side]), and it print absolutely nothing.

If you want to see it print out the sides in the list you would use

print(side)

Which points out a mistake I made in the code I asked you to run. Please run this and tell me what the results are

local battery = peripheral.wrap("back")
local dir = {
"north",
"west",
"east",
"south",
"up",
"down",
"unknown",
}

for _,side in ipairs(dir) do
  print(side .. ": " .. battery.getMJStored(side))
end

north: 0
west: 0
east: 0
south: 0
temp: 13: attempt to concatenate string and nil

Dog, on 22 August 2014 - 08:52 PM said:

Do you have the Energy Cube attached directly to the back of the computer (no peripheral proxy/modem)?

Is the output side of the Energy Cube the side that is attached the the computer?

What versions of MC, Mekanism, ComputerCraft, and Forge are you using?

local battery = peripheral.wrap("back")
local dir = {
"north",
"west",
"east",
"south",
"up",
"down",
"unknown",
}

for _,side in ipairs(dir) do
  print(side .. ": " .. battery.getEnergyStored(side))
end

Dog, on 22 August 2014 - 09:07 PM said:

Hmmm…getMJStored() doesn't work for me with the same versions, it returns "attempt to call a nil" - I have to use getEnergyStored(). Since you're directly connected and you aren't pushing or pulling items I'm pretty sure the correct direction should be "unknown".

I'm curious - what happens if you run this…

local battery = peripheral.wrap("back")
local dir = {
"north",
"west",
"east",
"south",
"up",
"down",
"unknown",
}

for _,side in ipairs(dir) do
  print(side .. ": " .. battery.getEnergyStored(side))
end

Dog, on 22 August 2014 - 09:17 PM said:

Something is amiss here and I'm not seeing it. I've tried this in both MC 1.6.4 and MC 1.7.10 and getEnergyStored() is returned as a valid method for me while getMJStored() is not. As well, the above code works for me and shows the energy stored in the cube.

Let's stick with the getMJStored() method since that's returned as a valid method for you.

Are you sure the output side of the cube (there is only one output side) is facing the back of the computer?

FXgamer247, on 22 August 2014 - 09:19 PM said:

I am 110% sure it is. Also, if we are using the same versions, why can you use getEnergyStored() and I can't? If we have the exact same build.

Dog, on 22 August 2014 - 09:31 PM said:

FXgamer247, on 22 August 2014 - 09:19 PM said:

I am 110% sure it is. Also, if we are using the same versions, why can you use getEnergyStored() and I can't? If we have the exact same build.

That is a really good question. My downloads are relatively recent, from the original sources (and work when swapped out with the files for a server I play on) so I'm relatively confident that the files on my end are as they should be. I am troubled that "up" and "unknown" caused an error for you - that makes me wonder if one of your mod files may be corrupted in some way. However corruption wouldn't explain why we have different methods available for getting the stored energy.

This may be an issue that a more experienced pro can answer, but my first suspect (based on the errors you are reporting) would be one of your mods. Are you doing this in single player or multiplayer? If multiplayer, is this an MCPC/Cauldron server?

Dog, on 22 August 2014 - 09:36 PM said:

What version of OpenModsLib (if installed) do you have?

Dog, on 22 August 2014 - 10:13 PM said:

I'm not sure what you mean by 'same peripherals' - do you mean same peripheral methods?

Did you include both OpenPeripheralCore and OpenPeripheralAddOns?

Dog, on 22 August 2014 - 10:31 PM said:

so if you try to set up an energy cube and computer and run the program now you get "attempt to call a nil" ?

Dog, on 22 August 2014 - 10:44 PM said:

Hmmm…anything unusual in your logs?

And I guess, just to double check:

Forge
ComputerCraft
Mekanism
OpenPeripheralCore
OpenPeripheralAddons
OpenModsLib

This should be what we're working with, right? Am I missing anything from this list?

Dog, on 22 August 2014 - 11:12 PM said:

I'm not sure how to proceed. It sounds like something is awry with your MC install but, again, I'm unsure as to the next steps to take. As much as it's a bummer, I think we'll need to get the help of another pro in here to resolve this.

Cranium, on 22 August 2014 - 11:27 PM said:

I made a monitoring program with the help of theoriginalbit not too long ago. Try this, and let me know if you're still having issues.
http://pastebin.com/iyPUG8XC

EDIT: Sorry, I had mine multi-purpose built for fluids and ME networks, but if I'm right, should work for your problem. If not, then yeah, bugginess ensues.

print(textutils.serialize(peripheral.getMethods("back")))
local file = fs.open("dump", "w")
file.write(textutils.serialize(peripheral.getMethods("back"))
file.close()

Cranium, on 23 August 2014 - 12:04 AM said:

I'll have to do some testing then, because my program is supposed to be universal. Thanks for inadvertantly testing a bug for me. That is strange that it's not returning proper info.

print(textutils.serialize(peripheral.getMethods("back")))
local file = fs.open("dump", "w")
file.write(textutils.serialize(peripheral.getMethods("back"))
file.close()

Try that little bugger there, then tell us the output. That should tell us the available functions for that peripheral. If it doesn't fit on the screen, it'll output a dump file you can access.

local energy = peripheral.wrap("back")
print(energy.getMaxMJStored()) --#I assume you'll have to enter "unknown" if it errors here

Cranium, on 23 August 2014 - 01:21 AM said:

Well, just to test, try this:

local energy = peripheral.wrap("back")
print(energy.getMaxMJStored()) --#I assume you'll have to enter "unknown" if it errors here

If it returns a value other than 0, then it should mean that there's no problem, and it's program related. If it returns 0 or nil, then we're in trouble.

Dog, on 23 August 2014 - 01:47 AM said:

Just for clarification - does it return nil or do you get an attempt to call nil?

And - did you call it with or without a direction (e.g. "unknown")?

Cranium, on 23 August 2014 - 01:49 AM said:

Yeah, that is a problem. It means that even though you're wrapping the peripheral, it's saying that the block is not returning a MaxMJStored amount. Now…just to make sure, you have added some power into the energy cube, correct?

EDIT: actually, Dog brings up good questions. Try his suggestions, definitely.

Dog, on 23 August 2014 - 02:02 AM said:

If you'd clarify for me a bit more - what do you mean by 'Neither worked.'? Did they return something (0 or a nil value) or did you get an error? The more data we have to work with the better idea we'll have for which direction to explore next.

Cranium, on 23 August 2014 - 02:57 AM said:

Actually, just to expand on his possible moment of enlightenment:
What other energy-producing mods do you have installed?

Dog, on 23 August 2014 - 03:13 AM said:

Buildcraft is probably why you're seeing getMJStored() while Thermal Expansion is probably why I'm seeing getEnergyStored() - without one of those mods, neither energy method is available