It's a standard EmonTX running the Emontx_single_CT_example_watchdog sketch, and a Emonbase (Nanode RF) running the NanodeRF_singleCT code. The CT is the blue seedstudio, and all the settings in the sketch are the defaults.
The EmonTX has a single CT plugged into the CT2 socket, and a figure is produced on the serial monitor every few seconds which matches the current usage in watts (+- 1W anyway) to a British Gas alertme monitor, so that seems to be as expected. I have now removed the Alertme transmitter (& removed the batt) in case it was causing interference.
When the Emonbase is connected , it picks up an IP correctly from the DHCP server, and is posting to my emonCMS server.
I am getting rf-fail:1 displayed every 30 seconds or so, and a steady RED led lit.
I have transferred Ian Chilton's test_rx script to the Emonbase, and the serial Monitor displays a number every few seconds, which is in perfect sync with the flash of the green LED on the EmonTX, which leads me to believe that the wireless is working. The payload which is being displayed is in the format:
Received: 213910407
Received: 213910410
Received: 213910409
Received: 213910413
Received: 213910405
I have uploaded both test_TX to the emonTX and the 2 devices count up in sync.
I was using a Philips external battery pack with USB supply out - Switching to a Kindle USB adaptor cured it for about 5 hours before the signal was lost again. I have since swapped the USB power on the EmonTX for 2 AA batteries, but that has not made any difference.
Has anyone got any more ideas?
Re: Wireless link not working
Is the Nanode receiving any data? Have you checked that the emonTx is on the correct network group, correct payload and correct frequecy for the module.
Re: Wireless link not working
Both EmonTX and NanodeRF are configured for RF_433Mhz, Group 210. The Nanode is node 35 and the emonTX is node 10.
If I use the test_rx sketch from Ian Chilton's nanode site, I recieve payloads similar to the following everytime the LED on the EmonTX flashes:
Received: 213910410
Received: 213910409
Received: 213910413
Received: 213910405
And these continue on and on if I leave them
With the Emonbase_singleCT sketch loaded, I pick up a DHCP address Ok, and then just rf_fail:1 similar to below
[webClient]
DHCP status: 1
IP: 10.10.10.122
GW: 10.10.10.1
{rf_fail:1}
0
Date: Thu, 23 Feb 2012 21:46:17 GMT
ok recieved
{rf_fail:1}
the NanodeRF is uploading OK to my emonCMS site as I can see the RF_fail input update every 30 seconds or so.
As I said, this all worked for about 4-5 hours on Sunday, before stopping again, and I got all excited!
Re: Wireless link not working
Mm that's strange. The RF is obviously working and so is the Etherent! How far are the units appart?
Re: Wireless link not working
normally about 2 metres apart seperated by a brick wall, but I have had them on the bench next to each other.
The odd thing is I got it all to work last w/e when I powered the emonTX with a Kindle usb adaptor, and it lasted for about 5 hours before failing again. Thought that the Kindle supply may have been more stable but not stable enough so am now powering from a 2 AA battery holder from Maplin and fresh duracells.
I have tried powering the Nanode from a laptop USB port, via the FTDI cable from the same laptop, even with the emonTX USB powered from the same laptop
EmonTX is using the EmonTX single CT watchdog example sketch, and the NanodeRF is using the NanodeRF singleCT example.the EmonTX sketch is unmodified apart from to ensure the wireless settings are correct, and the nanodeRF the same + my web server details.
Re: Wireless link not working
I think/hope I may have sussed this and it appears to have been one or both of two things.
after testing again with the test_rx sketch on the Nanode, I decided to flick though the other sketchs, and loaded up the emonBase_singleCT_RTCrelay_GLCDtemp sketch, and after a minute or so settling down, the Nanode started displayiing data correctly on the serial monitor
Checked my emonCMS , only to discover that it was trying to upload to the openenergyMon demo site - as soon as I put in the internal Ip address for my web server, it bombed, but if I put in the FQDN, then it uploads.
That seems kinda weird to me as it will quite happily upload rf_fail=1 to the website via the IP, but the decode seems to fail - very odd, but it has been workign now for a couple of hours, so fingers crossed!
Re: Wireless link not working
Is the code trying to do a DNS lookup against an IP address? This is likely to fail.
Can you put the NAME of your local server in the code instead?