Archived Forum

When I got emontx on the same group the script seems to be running now/green..so this is ok now.

This can happen if you're not receiving from emontx. Did you check minicom to see your receiving data ok?

Note you may need to stop cron to be able to read minicom first:

Open crontab: $ sudo nano /etc/crontab

Add # line to start of line   */1 * * * * root cd /var/www/emoncms/Modules/raspberrypi && php raspberrypi_run.php

Reboot the pi with $ sudo reboot

Hi

Now I got the temp from emonglcd to emonbase and "peak" power from emontx pulse sensor to emongldc but clock is wrong. How can I have the clock right?

Emonbase id is 15  (code default i think)

I mean that time is not sended to emonglcd.

Thanks.

I've got similar problems with the ready to go image. They seem to appear when de raspberry is updated. My next step is to use the image, not update the raspberry and get the newest versions (emoncms etc.) from github.

keep you posted.

plan worked.

i've used the image

then followed thes steps:

- downloaded the image

- expanded the root partition

- DID NOT UPDATE

- removed the emoncms directory: rm -r -f /var/www/emoncms

- changed directory to www: cd /var/www

- pulled emoncms from github: git clone git://github.com/emoncms/emoncms.git

- changed directory to emoncms: cd emoncms

- copied the defaul settings to settings: cp default.settings.php settings.php

- changed user to root, password to raspberry en database to emoncms

- changed directpory to Modules : cd Modules

- pulled raspberry form github: git clone https://github.com/emoncms/raspberrypi.git

- logged into emoncms and updated the database (admin tab)

- adjusted the raspberrypi settings

- then back to the SSH session and I used part 12 of the instruction:

• once logged in via ssh enter $ ps -A | grep cron  to view the current process list
• To kill the cron process enter $ sudo kill xxx  replacing xxx with the cron process number from the list above, there might be more than one cron running. Repeat this step until all cron processes have been killed. $ ps -A can be run again to check.
• Within 1 minute the php script must also be killed before it gets re-spawned. To do this enter $ sudo top then kill xxx where x is the php process number (usually at the bottom of the list, press 'down key' to scroll down).
• reboot the pi & sudo reboot

- and it worked.

- I think in my case i may have experienced some HF interference as well, after moving the raspberry to a HF friendly place in my home i had less problems with receiving. (it was near my server, wifi router, switch etc.)

hope this helps!

Do you mean that you fixed that cron problem or clock(time) problem?  Now I have just time issue in my emongldc.

yep, i've no longer have problems with the cron.