All messages from JeeNode =?
5 January, 2013 - 10:24
Out of the blue my JeeNode which is in my airing cupboard has stopped sending out real values when I view the messages using XFX Viewer all 3 outputs (light, temp & lowbat) all show '?' for the state and text e.g.
xap-header
{
v=12
hop=1
uid=FF00D802
class=xAPBSC.info
source=dbzoo.livebox.jeenode:immersion.temp
}
input.state
{
state=?
text=?
}
Anyone know what is wrong/how I fix?
xap-header
{
v=12
hop=1
uid=FF00D802
class=xAPBSC.info
source=dbzoo.livebox.jeenode:immersion.temp
}
input.state
{
state=?
text=?
}
Anyone know what is wrong/how I fix?
5 January, 2013 - 14:48
#2
If nothing else changed ...
... the most likely thing is that the batteries on the roomNode are drained. If your monitoring script raises an alert when the lowbat signal becomes active, you can have this act as a warning that the batteries are on their way out.
6 January, 2013 - 10:48
#4
Next thing to do
It's worth doing a manual inspection of what (if anything) is being received by the baseNode.
Telnet onto the HAH and kill off any processes that are using the serial port. Then fire up microcom and see what is coming in over the serial port.
6 January, 2013 - 11:30
#6
A few basic busybox commands
Use 'ps' to list all of the running processes. 'kill -9 <process id>' will kill a specified process. kill the plugboard and any xap-serial processes.
microcom is just a simple terminal emulator 'microcom -s 57600 /dev/USBxx' (replace xx with the number of your USB port).
use 'dmesg' to check which USB port your cable has been allocated.
6 January, 2013 - 22:04
#8
Make sure you use the correct
Make sure you use the correct baud rate you entered 57500 which is wrong its 57600.
# microcom -s 57600 /dev/ttyUSB0
In any case before you got that low I would have checked to see if xap-serial was reporting xAP packets.
JEENODE BASE ----serial---> xap-serial ---> xAP (serial class)
xAP (serial class) -----> Plugboard.lua ---> JeeNodeApplet.lua ---> xAPBSC
6 January, 2013 - 22:40
#9
other process
You should also kill the plugboard process.
Do you have any other jeenodes or is this the only one?
7 January, 2013 - 15:00
#11
Very interesting
All I can think of is that something (temperature at the location of the HAH?) caused the HAH 5V line to drop below the point at which the regulator on the baseNode was happy to keep powering the AVR micro. We do know that folks who make use of the onboard relays of the HAH PCB are better to run the PCB via an external 5V supply ... could be a similar thing.
Anyway, thanks for persevering & letting us know what fixed it for you. I've added a note to the wiki.
The ? means that nothing has been received from the node for a while. So either the node isn't transmitting any more or the HAH basenode isn't receiving.
Have you tried resetting the node? Then reset the box?