Hello, i have more than a month trying to make my raspberry pi b+ work with emonhub service.
i have uploaded default firmware in my emontx and i can see from serial Monitor that Emontx is working as it should. i have also installed emonhub service in my raspberry pi but it does not send data to emoncms interface.
So as far as im using default firmware for emontx V3 can somebody upload a working configuration file (emonhub.conf) please? 433mhz,network210, nod 10. I assume that the problem is in my configuration please someone upload or write the configuration content.
this is my log file
2014-10-30 10:29:21,499 INFO EmonHub Pre-Release Development Version (rc1.0)
2014-10-30 10:29:21,514 INFO Opening hub...
2014-10-30 10:29:21,517 INFO Logging level set to DEBUG
2014-10-30 10:29:21,520 INFO Creating EmonHubEmoncmsReporter 'emonCMS'
2014-10-30 10:29:21,536 INFO Set up reporter 'emonCMS' (buffer: memory | size: 1000)
2014-10-30 10:29:21,545 INFO Creating EmonHubJeeInterfacer 'RFM2Pi'
2014-10-30 10:29:21,548 DEBUG Opening serial port: /dev/ttyAMA0
2014-10-30 10:29:21,552 INFO Opened serial port: /dev/ttyAMA0 9600 bits/s
2014-10-30 10:29:21,562 DEBUG Setting RFM2Pi frequency: 433 (4b)
2014-10-30 10:29:22,571 DEBUG Setting RFM2Pi group: 210 (210g)
2014-10-30 10:29:23,667 DEBUG Setting RFM2Pi baseid: 10 (10i)
Thank you
Re: emonhub.conf how to configure to work with emonTX discrete sampling firmware
The log you've posted looks ok. there are no errors and the RFM2Pi configuration looks correct, however there's no response to the commands and no data received. Is the serial UART available to the RFM2Pi?
The last line in /etc/inittab should read (in particular the # should of been added)
# T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
And the single line in /boot/cmdline.txt should read
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
If both are correct, is there any LED activity on the RFM2Pi board ?
The RFM2Pi's led should flash each time a packet is received, so if there's no flash when the emonTx transmits try moving it closer to eliminate a possible range issue. Can you be sure the emonTx is transmitting? do you have a usb programmer you can check the emonTX operation with?
Paul
Re: emonhub.conf how to configure to work with emonTX discrete sampling firmware
Hi ariol22,
Did you resolve this?
There are a couple of things you need to ensure:
To check the rfm2pi is receiving messages you can use minicom:
minicom -b 9600 -o -D /dev/ttyAMA0If you press 'h' it will give you the configuration commands, and it should say something like:
You can change those settings directly in minicom (press 'h' to find out how), or in the /boot/emonhub.conf file. If you do the latter, make sure you restart emonHub to see the changes – within minicom you'll see it being set up with the band, group and node ID.
If no messages are appearing in minicom you need to look at the emonTx and verify the settings there, otherwise your issue is with the emonHub config.
My nodes section in /boot/emonHub.conf is set up for an emonTx and emonTH. You need to comment out the default [[99]] entry and add the appropriate node IDs as follows:
Hope that helps, or at least serves as a reference if anyone else has problems getting set up.
Re: emonhub.conf how to configure to work with emonTX discrete sampling firmware
Hi Ryan
Just for clarity your points are mostly correct although emonhub doesn't have to be restarted to pick up the conf changes, any " [[[runtimesettings]]] " will be changed during normal running and any [[[init_settings]]] will be made by emonhub deleting and recreating the interfacer or reporter so a restart shouldn't be needed.
And the interfacers each have a default datacode (usually h) so just omitting [[10]] and [[19]] from the nodes section should have the same outcome, this was done so that emonhub would automatically function with standard "int-only" sketches without any setting modifications.
Paul