Plugboard crashing after adding another node
Since I've added my WH1080 node to the HAH I seem to be getting plugboard crashes due to receiving data from the wrong serial ports.
Sometimes plugboard just stops, other times I do actually get an error like this...
lua: /usr/share/lua/5.1/xap/init.lua:395:
/usr/share/lua/5.1/xap/jeenode.lua:51:
invalid value (nil) at index 3 in table for 'concat' xAP Message being processed.
xap-header { uid=FF00D500 source=dbzoo.livebox.Serial hop=1 class=Serial.Comms v=12 }
serial.received { data=OK 2 41 0 19WH1080:2619:2 0 port=/dev/ttyUSB0 }
stack traceback:
[C]: in function 'error'
/usr/share/lua/5.1/xap/init.lua:395: in function 'dispatch'
/usr/share/lua/5.1/xap/init.lua:97: in function 'fun'
/usr/share/lua/5.1/pl/List.lua:444: in function 'foreach'
/usr/share/lua/5.1/xap/init.lua:96: in function 'callback'
/usr/share/lua/5.1/xap/init.lua:203: in function 'dispatch'
/usr/share/lua/5.1/xap/init.lua:117: in function 'process'
/etc_ro_fs/plugboard/plugboard.lua:77: in main chunk
[C]: ?
I thought it could be a power issue so I have now added a powered USB hub rather than stressing the HAH any more but that doesn't seem to have helped
I know nothing, but just a quick observation, why is it using the plugboard.lua from /etc_ro_fs/plugboard rather than the one in /etc/plugboard ?
The first issue looked like a recurrance of this: issue 30 whcih I fixed in release 308.
Multiple HAH's each running jeenodes would promiscuously process data from running xap-serial instances
http://code.google.com/p/livebox-hah/source/detail?r=436&path=/trunk/use...
Do have a local copy of jeenode.lua in /etc/plugboard ?
The second looks like you are opening the wrong port.
Brett
As you can see from the above post, the data that is being received is a combination of a roomnode and the code from the WH1080
data=OK 2 41 0 19WH1080:2619:2 0 port=/dev/ttyUSB0
The WH1080 is on /dev/ttyUSB2 so why does it appear here?