Max Padding Exceeded

Submitted by jdr0berts on Wed, 16/03/2016 - 08:14

Hi there,

I noticed that I've stopped getting updates to the My Solar app - it's showing as 2777W constantly.

On checking the feeds list (screenshot), there are a number of fields tagged with "MAX PADDING EXCEEDED".

MAX PADDING EXCEEDED
Id Name Tag Datatype Engine Public Size Updated Value
63904 Real power MAX PADDING EXCEEDED REALTIME PHPFIWA 16Mb inactive 2777
63907 Real solar MAX PADDING EXCEEDED REALTIME PHPFIWA 16Mb inactive 0
63910 Mains Voltage MAX PADDING EXCEEDED REALTIME PHPFIWA 16Mb inactive 237.8
64505 Usage MAX PADDING EXCEEDED REALTIME PHPFIWA 16Mb inactive 2777
64528 Export MAX PADDING EXCEEDED REALTIME PHPFIWA 16Mb inactive 0

Any help greatly appreciated.

Thanks

James

Re: Max Padding Exceeded

Submitted by TrystanLea on Wed, 16/03/2016 - 15:12.

Hello James, I've checked the feeds you detailed and Im a little puzzled as this usually happens when a feed has not been updated for much longer than the 16 days or so yours have not been updated for, it should be 242 days with a 10s feed. The tag is set by a maintanence script that disconnects feeds where they have not been updated for a very long time as its better to start a new feed if the gap is 242 days+ otherwise the feed just eats up disk space filling the gap with 'padding' (nan values) I wonder if you could try reconnecting your feeds to your input processing to see if they come back online? sorry about this

Re: Max Padding Exceeded

Submitted by jdr0berts on Thu, 17/03/2016 - 17:46.

Thanks Trystan,

No problem - how do "reconnect your feeds to your input processing"?

Thanks

James

Re: Max Padding Exceeded

Submitted by andrea.rimo on Sat, 19/03/2016 - 22:48.

I have exactly the same problem. maybe it can help to trouble shoot knowing that the channel that stopped is the temperature of the emonGLCD, but the signal is still being recorder.

Re: Max Padding Exceeded

Submitted by mattwire on Mon, 21/03/2016 - 09:54.

This has happened to me as well. 11 of my feeds (all of the PHPFIWA ones) have the MAX PADDING EXCEEDED error and I can't see any good reason why.

Re: Max Padding Exceeded

Submitted by TrystanLea on Mon, 21/03/2016 - 11:56.

I've reconnected the affected feeds - there where 38 feeds misclassified with the max padding exceeded error all together. Im very sorry for the missing data on these feeds.

Re: Max Padding Exceeded

Submitted by andrea.rimo on Tue, 22/03/2016 - 08:08.

My problem was limited to 1 feed, from the emonGLCD temperature. now it works again but I see it under NoGroup instead of node:20 in the feeds page (while it's listed correctly under Node:20 under the input page).

is there anything that I can do about it?

Also, do you have an understanding of why this happened? can we do anything to prevent it in the future?

Thanks

Archived Forum