Archived Forum

Hello webby, can you give a bit more detail on your setup?

Looking through your previous posts, of course your using emoncms.org, sorry for my forgetfulness. Looking at your account now it looks ok from here updated within 5-10s. It may have been a temporary hold up. Thanks for asking and notifying, its good to know if anything goes amiss.

Have had no updates for 10hrs Now!

rebooted rpi and now seems ok. something was badly amiss because rpi seemed to be sending huge amounts of data aking up all my bandwidth. SOrted as soon as I rebooted.

What OS and software are you running on pi? how is connected to LAN WiFi or Ethernet cable? how are nodes connected to pi? there are checks you can do to locate the issue if it happens again, if you are using rfm2pi has the firmware been updated?

There are known WiFi issues with the drivers for some adapters on early IPE-R1 based oem-gateway and there are known issues with rfm2pi v2 locking out on earlier firmware, both can be temporarily resolved with a reboot.

Paul

std software as delivered on sd card recently updated. Emons.org hosted  All connected by Ethernet cable. It seems that another piece of software that my pc is running is causing some kind of conflict as updates are fine once I disable it and reboot the rpi. The other piece of software which is an ip camera monitoring service is also being messed up and it just begins to hog all bandwidth (5mbs) whilst not working either. Possible port conflict????

How recently did you update the SD card? and did you update Raspbian or OEM gateway or both?

There was an issue with IPE-R1 when updating raspbian with "sudo apt-get upgrade" see http://openenergymonitor.org/emon/node/4036 but there have been several updates to Raspbian since then that may or may not of affected the upgrading result.

The IPE-R1 hasn't been updated by the original author but I did notice on his site a link to a 3rd party IPE-R1v2. 

I cannot vouch for it though as I reverted to using an early un-updated version (which I was very happy with aside from not being able to update it) until recently switching to using stock Raspbian in read-only mode http://openenergymonitor.org/emon/node/5331.

I can't tell you if this is the issue or not but if you used "sudo apt-get upgrade" I certainly wouldn't be surprised if it was.

It is quite possible that it's a port or IP address conflict causing network issues, does restarting your router fix the issue or only rebooting the pi? I assume from your comments if you disable ip camera monitor, the pi doesn't recover by itself.

Paul

The rpi does not recover when the camera monitor is disabled. Nor does it recover when the router is restarted with the camera monitor disabled. Only rebooting the rpi gets it to work again. Not sure what this tells us? DO you know what port the rpi uses? The ip camera system uses ports 9001 and 9002 for external monitoring of cameras. I did not use the update that you refer to.

Thanks for your assistance

By default OEM gateway opens a port on 50011, this can be disabled by 'commenting out' each of the lines in the [[Socket]] settings in the oemgateway.conf with a #.

If the Pi was able to recover by itself that would tell us we should probably look elsewhere for an issue, the fact the Pi doesn't recover suggests there is a problem with the Pi, however it doesn't rule out the possibility that the cause is external to the Pi and the Pi's issue is the inability to handle the external fault. does the fault only occur if the IP camera system is running?

What are the current symptoms is it a consistent delay or does it just stop posting or both?

Your original post said the inputs where updating every 40 secs, was that number taken from the "last updated" column or did you calculate that result? The reason I ask is, for example if that column varies between 0 & 40 or 15 & 55 the updates are indeed every 40secs but if it's varying between say 30 & 40 then it is updating every 10secs but there is a 30 second time difference or delay, these are 2 different situations and it's quite easy to get led in the wrong direction.

Trystan said he checked your account and it was updating every 5-10secs at that time, do you recall if matched what you were seeing at that time? your next post after this said it hadn't updated in 10hrs, do you know if the delay gradually built up or it just suddenly stopped?

I assume you are collecting data via a rfm2pi? have you tried the oemgateway "troubleshooting" section at the end of this page http://emoncms.org/site/docs/raspberrypigateway. this will confirm successful receipt of packets, which can confirm update time, frequency & interval and if the frames are dispatched successfully. It can also tell us if the fault is persistent when restarting the gateway service & serial connection, all valuable info even if just for elimination.

Paul

Solved! seems to have been a router issue.further research ongoing. Thanks for your help everybody.

Not quite solved!

Major issue with large home network now seems to be fixed However:

Inputs are now updating regularly but there is a delay which varies around 50 to 65 secs. It used to be 5-10 secs.

Can anybody explain this(and hopefully the solution) to an ignoramus such as myself?

Also I have never got to the bottom of why my PHP feeds are logging a day behind my SQL feeds.

Is trystan still working on it or do I have my time zone set incorrectly somehow?

I think I am having the same (or similar) issue. All has been working fine for weeks then a few data ago emocms stopped updating. Updates are happening but are intermittent and often with the wrong values.

What was you router issue?

Thanks..

Hi webby, The important thing is you are receiving regular updates. The variation "around 50 to 65 secs" means you are getting good data arriving regularly, emoncms is counting up to a max of ~65sec since update and dropping back to a minimum of ~50secs since update.

The ~50 second discrepancy is  probably consistent and signifies either a delay, which is rare or more likely a time difference somewhere, I frequently even see  minus 5 seconds since last update in emoncms. so it will vary. ~50secs seems quite high though.

Can you confirm if it's a time inaccuracy or a delay by watching emoncms and switching on a large load on a monitored supply and see how long until that change is displayed relative to the "since update" value at the time of update?

I'm not entirely sure where the times are derived off the top of my head but you can resync the time on the Pi by running sudo ntpd, it is common for them to be out of sync due to not having a RealTimeClock onboard.

Paul

Hi Paul

It seems that syncing the times correctly in my managed switches and router has solved the delay issue. It is now 5-10 secs.

The other problem still eludes me but setting the time correctly in the RPi could well be it.

I just need to remember how to do it on a MAC!