Well, after trying about everything I can think off I have decied I need help....
My daughter soldered up the 2 nodes a few weeks ago (she was bored in the school hols & not a bad hand with a soldering iron !) and I eventually got round to loading the scripts which went ok.
I have just picked them up again to get them working and built the room node into the airwick.
But no data is being picked up !
Member for
17 yearsbaseNode seems OK
The startup string from your baseNode looks fine.
Have you double-checked that the roomNode has an id of > 1 ?
Also, if you have a multimeter to hand, checkout the output from the regulator on your roomNode. You should see 3.3V
If you get really stuck, let me know & I'll send you out a 'known good' pair of baseNode/roomNode. I've got several sets of these things. It's rather 'chicken and egg' but it's a lot easier to debug issues on these units if you already have a setup that works!
Cheers,
Derek
Member for
14 years 7 monthsMoved a little further forward
Moved a little further forward, voltage is good from the regulator on both the base & room nodes.
Now got the base node responding fine when I connect via microcom (I think the AVR wasnt seated well).
Swapped the room node AVR back but could get no response.
Started from scratch again and loaded HAHcental, set up as node 2 etc.
Loaded roomNode2.cpp.hex.
But again no response when I try and connect via microcom
I noticed the roomNode2.cpp.hex file I had originally 'curled' did not have a capital 'N' for node, so deleted and pulled new file down on to the box (# curl -o roomnode2.hex http://livebox-hah.googlecode.com/files/roomNode2.cpp.hex), but again it saves it with only a lower case 'n'. Run through loading HAHcentral and setting up etc again but end result the same.
Looking at http://code.google.com/p/livebox-hah/downloads/list the roomNode2 file does have a capital - Could this be anything to do with the problem ?
Member for
17 yearsLowercase filename is what is specified
The command:
# curl -o roomnode2.hex http://livebox-hah.googlecode.com/files/roomNode2.cpp.hex
Gets the file roomNode2.cpp.hex from the Google repository and saves it as roomnode2.hex, (the '-o' specifies the output filename) so that's not an issue.
Note that your roomNode will never output anything on the serial port ... only the baseNode firmware does this - hence no six way connector fitted on the roomNode PCB.
If you can load up code images onto the devices and set the RF and Id parameters, it's a pretty good sign that the microcontrollers are running properly. Focus attention on the soldering of the RF module to the PCB - sometimes a pad can look to be soldered when it's actually not quite making contact.
Mad thought ... you do have the antennae connected?
Cheers,
Derek.
Member for
14 years 7 monthsNow ticking away nicely...
Thanks Derek, I have finally got back to having a look at this.
It was one of the RF module solder pads as you suspected, my Daughter soldered the nodes up (she is only 13 but has enjoyed electronics at school, shame she wasnt able to continue with a GCSE as the school dropped the subject - so much for encouraging you engineers !), will have to have a word on her quality control ;-)
Now hopefully move onto some automation !
Dave
Member for
17 yearsLearning to persevere
Good to hear that the unit is now ready for some action. Very good that you have a youngster who can actually solder ... the lesson of that one dodgy solder joint is worth a great deal.
On the RF front, I've been enjoying excellent results with the LightwaveRF series devices. Very reliable, high quality, kit.
Do keep us posted re your progress.
Derek.
Member for
14 years 7 monthsCOSM Feed frozen Help to diagnose please...
My HAHNode has been ticking away nicely but last week the HAH stopped feeding the node light level corretly to COSM.
For some reason the HAH feeds constantly a value of '1', but the correct readings are showing up on xFx Viewer from the node.
Suggestions how to diagnose greatly received.
Dave
Member for
17 yearsCheck the xap-pachube process
telnet onto the HAH & use 'ps' to see if the xap-pachube process is still running.
If it isn't restart it. If it is, try a bounce of the HAH.
Derek.
Member for
14 years 7 monthsOk found the fault I think...
I had updated the light feed to 'state' rather than 'text' by mistake, so I am fairly sure this was why I was getting a constant feed of 1 to COSM.
Pachube was running fine on the HAH, it had to be as the temp feed was working fine of the node.
I however now seem to have broken it, It wont run when I start of the command line I get the following error;
[crt][init.c:113:discoverBroadcastNetwork] errno 126 (Cannot assign requested address)
[crt][init.c:113:discoverBroadcastNetwork] Unable to query capabilities of interface eth0
Member for
16 years 10 monthsWhen running from the command
When running from the command line you need to supply "-i br0" for the correct interface to be used.
# xap-pachube -i br0
Or use xap shell script to start it for you which will determined the corrected interface from your "config_bridge" setting.
# /etc/init.d/xap restart pachube
Brett
Member for
14 years 7 monthsThanks Brett...
I have run xap-pachube -i br0 (if I had read the wiki I no dot should have found this), the command returns:
[crt][main.c:134:getDynINI] INI file missing [pachube] id5=<value>
Member for
17 yearsCheck the .ini file
Looks as if xap-pachube is having trouble parsing your ini file. Telnet in and have a look at /etc/xap-livibox.ini
Inspect the [pachube] section for any unwanted characters or other chaos.
Member for
14 years 7 months.ini file screwed up
Derek, the file was messed up in a couple of areas.
Have now corrected and all is working fine, a little more learnt with the experience !
The webserver seems to be whats messing up the file, it often locks up when saving.
thanks
Dave