Archived Forum

Hi Alex, You may not find much support for doing anything beyond 'normal' operation with that OS. Although it is raspbian based it is not raspbian enough to make any assumptions.

We have since progressed onto using a lightly converted genuine raspbian OS that retains all its features and has a huge community for support and development.

oem gateway has also progressed to emonhub. I am pretty sure you could spend far more time and effort trying to get what you want from that image than it would take to make the switch to the latest image.

Off the top of my head I think you would just need to move your oemgateway.conf settings across to the new emonhub.conf (the files a quite alike but not directly interchangeable so beware of typos etc)

I've used I²C on raspbian so I know the modules can be loaded and work as expected but wouldn't know how to help you with I²C on IPE-R1 or even know if its possible.

Paul

Hi Alex,

As Paul says, you'd be much better off switching to the latest version of the SD card software.

The reason you're getting the error is IPE is in Read-Only mode. To switch it to Read-Write mode, issue the command ipe-rw. Once you've done that, you can try loading the i2c modules. To put it back in RO mode, issue the command ipe-ro.

Again, the current software is a big improvement over IPE.

Thanks for your replies.

Ok, so I've downloaded and burnt this image https://github.com/emoncms/emoncms/blob/bufferedwrite/docs/setup.md and now the pi won't boot normally. 

It boots really slow and whenever it gets stuck I need to press ctrl-c a couple of times for it to move on. Once that's finished it's so slow that there's like a second delay per key stroke. However if I reboot from the terminal it then boots up fast with no issue. Can get the modules loaded with the new image no probs.

Any ideas what might be wrong with it?

Cheers,

Alex

[There is no need for 5 copies. If your post does not appear, please watch for a message that tells you that it has been queued for moderation. Posting multiple copies only wastes everybody's time. Moderator (RW)]

The latest (beta) version, it's precursors and a discussion about the changes that it incorporates, is linked in this thread: http://openenergymonitor.org/emon/node/10163

Ok so using the latest version gave me the same results as using the feb release.

So I am now following this guide https://github.com/emoncms/emoncms/blob/bufferedwrite/docs/install.md

and when I get to this line:
sudo cp /var/www/emoncms/run/feedwriter /etc/init.d/

I notice that the /var/www/emoncms/run directory doesn't exist

where could of I gone wrong to not have this directory?

Well .... now for some reason the latest release image works fine on every boot.

So .... I don't see any feeds from the rfm12pi receiving messages from the emonTx. So is there a guide to set this up or should it already be doing this?

Thanks

Ok so now the SD-card with the latest release is not working anymore. After like 10 successful boots as I was typing in the terminal it became extremely slow again (1 second per character typed). And I can't get it to boot up fast anymore. 

So I'm back looking at the SD-card I build using this guide https://github.com/emoncms/emoncms/blob/bufferedwrite/docs/install.md

and I've noticed that on boot there's a few fails, here's what I get:

[....]  starting OpenEnergyMonitor emonHub: emonhubstart-stop-daemon: unable to start /usr/share/emonhub/emonhub.py (permission denied)

[ ok been started okLog is turned off

Error: file not found : ' /var/www/emoncms/run/feedwriter.php'

... ...

[Fail] startpar: service(s) returned failure: feedwriter ... failed!

Cheers,

Alex

A common reason for a Pi to slow down is lack of space, either the filesystem grows too big for the partition or more likely on a read-only image is the RAM being filled with runaway log entries for a unhandled issue. the latter is harder to detect since once it slows to a stop a reboot will reset memory use and the logs.

use df -h to check filesystem size and free to check ram use, check whilst all is good for a comparison to when it slows.

The current image should be trouble free, if the image fits onto the SD card ok and you edit the emonhub.conf using details from your oemgateway.conf the image should "just work" if it doesn't then that should be addressed before enabling emoncms etc.

"sudo cp /var/www/emoncms/run/feedwriter /etc/init.d/

I notice that the /var/www/emoncms/run directory doesn't exist

where could of I gone wrong to not have this directory?"

The run folder is only present in the "bufferedwrite" branch of emoncms.

​"So .... I don't see any feeds from the rfm12pi receiving messages from the emonTx. So is there a guide to set this up or should it already be doing this?"

Yes it should work, is the led on the rfm2pi flashing? what do you see in the emonhub.log file? did you define a serial baud in emonhub.conf or is emonhub auto-detecting?

"[....]  starting OpenEnergyMonitor emonHub: emonhubstart-stop-daemon: unable to start /usr/share/emonhub/emonhub.py (permission denied)

[ ok been started okLog is turned off

Error: file not found : ' /var/www/emoncms/run/feedwriter.php'

... ...

[Fail] startpar: service(s) returned failure: feedwriter ... failed!"

2 overlapping issues here emonhub apparently won't start due to a permission issue, and separately the afore mentioned run folder isn't found so cannot start the feed writer.

Paul

Ok Thanks, I was having a memory issue there, it was getting full, not sure of what but it was full. I unplugged the tp-link wifi dongle and it boots up fine now (so far) no memory issues no more.

Thank you!