Hi - I have been successfully running emonhub interfacing to an rfm12pi and a local copy of emoncms on a Raspberry Pi for many months.
However, I have recently needed to restart my system following some updates, and noticed that after the restart emoncms was not receiving any inputs.
If I type sudo service emonhub restart, then everything starts working again. I tried to change the config file to use debugging, but on that occasion, everything worked normally. I wonder if this is some timing issue?
Here is the log file:
2015-05-06 21:45:10,551 INFO EmonHub Pre-Release Development Version (rc1.2)
2015-05-06 21:45:10,572 INFO Opening hub...
2015-05-06 21:45:14,656 WARNING Device communication error - check settings
2015-05-06 21:48:35,044 INFO EmonHub Pre-Release Development Version (rc1.2)
2015-05-06 21:48:35,056 INFO Opening hub...
2015-05-06 22:01:31,655 INFO EmonHub Pre-Release Development Version (rc1.2)
2015-05-06 22:01:31,672 INFO Opening hub...
2015-05-06 22:01:35,718 ERROR Unable to create 'RFM2Pi' interfacer: Attempting to use a port that is not open
2015-05-06 22:04:05,536 INFO EmonHub Pre-Release Development Version (rc1.2)
2015-05-06 22:04:05,538 INFO Opening hub...
At 21:45 I rebooted the system - and got the WARNING message
At 21:48 I restarted the service and all was well.
At 22:01 I rebooted the system - and got the ERROR message (I get this message most of the time).
At 22:04 I restarted the service and all was well.
Does anyone have any ideas please?
Re: Emonhub not working on reboot [SORTED]
If a serial baud is not defined in emonhub.conf, emonhub tries to determine the correct baud, it is not a perfect solution and is currently "under review" If you know the correct baud for your system you can set "com_baud = n" in the init_settings of that interfacer in emonhub.conf.
Usually "n" is either 9600, 38400 or 57600 depending on hardware, firmware and age etc
Paul
Re: Emonhub not working on reboot [SORTED]
Hi Paul,
Thanks for the suggestion - that seems to have fixed it (although I can't explain why I suddenly had a problem). I chose com_baud = 9600 thinking that the slower the more reliable it would be, and that there is no performance hit given that I am only transferring data from two emonTxV2, each sending temperature and voltage every 20 seconds.
Nick