Hi all,
I've built the RPi module and downloaded the SD image.
The pi boots and I can access emoncms but am reciving the "Message: The RFM12 to PI interface script is not running, you may need to configure cron" notification.
I've killed cron and the php script as per the instructions and rebooted but the message remains.
I've removed the original raspberrypi_run.php file and replaced it with the one here - http://openenergymonitor.org/emon/node/1236 - rebooted and still no change.
A strange thing is that I have a jeenode up and running sending data. Some of that data is appearing in emoncms but not a lot of it. The node is set to send every 30 seconds but emoncms only seems to get data roughly every 20 minutes or so.
Any pointers?
Matt
Re: The RFM12 to PI interface script is not running.
Spent 4 hours trying to get it running yesterday and still no luck. :(
Re: The RFM12 to PI interface script is not running.
Have you tried running the script directly from command line? You'll need to kill it after, as doesn't have any kill code internally. Worth then checking error logs?
Re: The RFM12 to PI interface script is not running.
Is the LED blinking upon powering the board and later when a packet is received? If the LED dowsn't light up when the board is inserted, that would be an indicator for trouble. Maybe close-up pictures would shred some light
Re: The RFM12 to PI interface script is not running.
Matt,
> I've removed the original raspberrypi_run.php file and replaced it with the one here - http://openenergymonitor.org/emon/node/1236 - rebooted and still no change.
I think Martin's fix (the script you're pointing to in that other thread) was integrated, so you shouldn't have to replace raspberry_run.php.
> The pi boots and I can access emoncms but am receiving the "Message: The RFM12 to PI interface script is not running, you may need to configure cron" notification.
> I've killed cron and the php script as per the instructions and rebooted but the message remains.
The idea behind commenting the line in cron and rebooting (or manually killing the process) is to free the COM port to allow another soft to read what comes in. You could try to see if anything is coming from the serial port. For instance with minicom, as suggested in the wiki.
Anyway, if I understand correctly, in raspberry_run.php, function raspberrypi_running() is called on a regular basis, whether or not data was received. Therefore, the message you're seeing means not that you don't receive stuff on the OCM port, but that the script is dead or stuck.
Once cron line commented and script killed, you can launch it from command line as Nick suggests :
php raspberry_run.php
and see what happens.