The above is wireless traffic from other devices and can be ignored. Your ttl looks fine The empty xAPBSC.info events occur when no valid message has been received, try moving the jeenode and basenode about 4-5 meters apart and see if that helps, we can work from there if it does. I would also suggest connecting the roomnode to the HAH and using microcom to check it's config.
Have you enabled the xap-serial daemon? Via the web gui "Automation -> Assists -> Serial SCHEMA Service" ENABLE.
Are you seeing traffic coming in from this daemon? That is with xFxViewer(Windows) or xap-snoop (HAH) do you see the traffic from the dbzoo.livebox.serial endpoint?
Do you have ANY other USB serial devices on the HAH, ie CurrentCost? Are you 100% its /dev/ttyUSB0?
Plugboard does not support the -d switch - _DEBUG is an ON/OFF switch... the output will only be visible if you are running the plugboard from the command line. Make sure you only run one at a time if the other is running kill it before starting manually.
Also you CANNOT run both xap-serial AND any microcom session to the same serial port.
Thanks to all who responded - the main problem was down to the fact that the xap-serial daemon wasn't running. Once that had been enabled things started moving.
I've re-compiled the roomnode2 code to enable the debug option (it will then output to the serial port) and also increasing the transmit rate to make it a little easier to debug this using xap-snoop. I've attached the new compiled code below and also the sketch if anyone is interested.
Thanks to all again - I'm now a happy owner of a Livebox with working Jeenodes!
Enable serial on a BATTERY operated device is a bad idea as it will increase your power consumption.
OK for power and DEBUG NOT ok for production on batteries.
By enabling SERIAL and DEBUG you have added 10sec to the main loop due to the additional delays that where added to SLOW things down for debugging. This also means that the report period is no longer once per 150sec its 160sec. I've not examined how the Arduino libraries implement these delay() operations hopefully with an interrupt timer otherwise you are doing a busy spin (re: sucking power).
As I said not a good idea when you go production to leave these things enabled esp. for battery powered units.
Wait you've drop down the reporting period to be once every 1 second and you have 10 seconds worth of delay loops (as mentioned above due to SERIAL/DEBUG enablement. So really its once every 12 seconds (as you report every 2nd cycle). You are going to chew battery. Really you need to know the temp and light readings this often? I really advise NOT to use this with batteries unless you want to replace them every few weeks.
Agree - the re-compiled version was for debugging only. Waiting 2 1/2 minutes between each transmit to see if it was being seen by xap-snoop when you are not sure if the jeenode is transmitting/receiving or even in range is a painful way to get things working. The re-compiled version allows you to check any attached devices are being seen and then, using xap-snoop, quickly check that the final position of the device will work ok.
At least then you can be sure that everything should be working whilst you wait for the transmissions.
I've tried hooking on a variety of USB attached devices. I don't know of a way to 'force' a given device to a specific USB<n> port, but I do know that for any given setup, the devices always enumerate in the same order.
So, whilst this is a bit of a pain when you are in the setup phase and devices are being added/removed, once things settle down it's a solid environment.
Member for
16 years 5 monthsJeeNode Range
> ? 18 36 216 230 116 139 102 48 20 206 172 103 247 98 27 65 26 14 75 93 77
The above is wireless traffic from other devices and can be ignored. Your ttl looks fine The empty xAPBSC.info events occur when no valid message has been received, try moving the jeenode and basenode about 4-5 meters apart and see if that helps, we can work from there if it does. I would also suggest connecting the roomnode to the HAH and using microcom to check it's config.
Karl
Member for
16 years 10 monthsDid you enable xap-serial too
Have you enabled the xap-serial daemon? Via the web gui "Automation -> Assists -> Serial SCHEMA Service" ENABLE.
Are you seeing traffic coming in from this daemon? That is with xFxViewer(Windows) or xap-snoop (HAH) do you see the traffic from the dbzoo.livebox.serial endpoint?
# xap-snoop -s dbzoo.livebox.Serial
xAP Snoop - for xAP v1.2
Copyright (C) DBzoo 2009-2010
xap-header
{
v=12
hop=1
uid=FF00D500
class=Serial.Comms
source=dbzoo.livebox.Serial
}
Serial.Received
{
port=/dev/ttyUSB0
data=OK 2 0 0 171 0
}
Do you have ANY other USB serial devices on the HAH, ie CurrentCost? Are you 100% its /dev/ttyUSB0?
Plugboard does not support the -d switch - _DEBUG is an ON/OFF switch... the output will only be visible if you are running the plugboard from the command line. Make sure you only run one at a time if the other is running kill it before starting manually.
Also you CANNOT run both xap-serial AND any microcom session to the same serial port.
Brett
Member for
17 yearsFrequency looks wrong
These modules are designed to work at 868MHz. Yours looks to be configured for 433MHz. '8b' will fix this.
Derek.
Member for
15 yearsWorking!
Thanks to all who responded - the main problem was down to the fact that the xap-serial daemon wasn't running. Once that had been enabled things started moving.
I've re-compiled the roomnode2 code to enable the debug option (it will then output to the serial port) and also increasing the transmit rate to make it a little easier to debug this using xap-snoop. I've attached the new compiled code below and also the sketch if anyone is interested.
Thanks to all again - I'm now a happy owner of a Livebox with working Jeenodes!
Andy
Member for
15 yearsThanks DerekI hadn't realised
Thanks Derek
I hadn't realised they should have been running at 433Mhz.
I've changed them over and all is well.
Andy
Member for
16 years 10 monthsDont enable serial
Enable serial on a BATTERY operated device is a bad idea as it will increase your power consumption.
OK for power and DEBUG NOT ok for production on batteries.
By enabling SERIAL and DEBUG you have added 10sec to the main loop due to the additional delays that where added to SLOW things down for debugging. This also means that the report period is no longer once per 150sec its 160sec. I've not examined how the Arduino libraries implement these delay() operations hopefully with an interrupt timer otherwise you are doing a busy spin (re: sucking power).
As I said not a good idea when you go production to leave these things enabled esp. for battery powered units.
Wait you've drop down the reporting period to be once every 1 second and you have 10 seconds worth of delay loops (as mentioned above due to SERIAL/DEBUG enablement. So really its once every 12 seconds (as you report every 2nd cycle). You are going to chew battery. Really you need to know the temp and light readings this often? I really advise NOT to use this with batteries unless you want to replace them every few weeks.
Brett
Member for
15 yearsBrett,Agree - the re-compiled
Brett,
Agree - the re-compiled version was for debugging only. Waiting 2 1/2 minutes between each transmit to see if it was being seen by xap-snoop when you are not sure if the jeenode is transmitting/receiving or even in range is a painful way to get things working. The re-compiled version allows you to check any attached devices are being seen and then, using xap-snoop, quickly check that the final position of the device will work ok.
At least then you can be sure that everything should be working whilst you wait for the transmissions.
Andy
Member for
15 yearsMultiple USB Devices - Jeenode & CurrentCost
Is there a reliable way to get the different devices to register on specific ports? i.e. Current Cost always on USB1 and Jeenode on USB0?
Andy
Member for
17 yearsEnumeration is repeatable
I've tried hooking on a variety of USB attached devices. I don't know of a way to 'force' a given device to a specific USB<n> port, but I do know that for any given setup, the devices always enumerate in the same order.
So, whilst this is a bit of a pain when you are in the setup phase and devices are being added/removed, once things settle down it's a solid environment.
Cheers,
Derek.