Messages posted by: craig

PCM,

I suggest you download and install mango and see what it can do. The on-line documentation is very clear and complete.

You may have to test the data publisher yourself to see if it meets your requirements.

Have you google pachube? if you went to the pachube website you would know what it is and what it isn't pretty quickly.

look at httpimage data source

I have a patch to allow comments on point values. Contact me if you are interested
C

Hi Matt,

In the case where the logging interval is faster than the reporting interval, ie with a reporting interval of 15 minutes and a logging interval of 5 minutes, I'd expect the value at 2:00 to be the actual sample: 13.

The actual values logged could be instantaneous or the average of all the samples since the last logged value. For instance I have the modbus data source poll time set as low as I can without the polls starting to overlap, about 10s. Most variables I simply log the instantaneous value every 15 minutes, but for particularly noisy ones I log the average of the 6 samples/minute * 15 minutes = 90 samples. The result is there is some time delay in averaged samples, I think that it is acceptable, but I suppose it depends on the characteristic of the process.

For the second case, where the report interval does not coincide with the logging interval, I would linearly interpolate between each point. Thus to report on the value at 2PM a value after or at 2PM would have to be logged.

Slightly unrelated, but I've been meaning to look into how RRD (http://oss.oetiker.ch/rrdtool/) stores data as I believe it sets the bar for high performance logging and archival of time series data. There is a java port as well I believe.

2.) Can the .csv export be modified to place the different data points in columns across the spreadsheet instead of having each datapoint sequential? The result being to have the timestamp in column A, first datapoint value in B, second datapoint value in C, etc.

2) Multiple trend reports (for lack of a better name, referring to a single timestamp and associated point values) are tricky because there may not be a value at a given time for a given point. What would the report look like if you selected, say, a point that updates every 5 seconds, and a point that updates every 5 minutes?

I have a patch that is useful when interval logging is used. I believe I patched the interval logging to log the scheduled fire time of the log method as opposed to the actual, and also to log all values at the same interval (ie all values logged every 5 minutes get logged at 0 minutes past the hour, 5 minutes past the hour, etc).

Then there is another patch which puts all values in the CSV writer with the same timestamp on the same row.

I believe other scada packages interpolate and average the data as required to get a value in each column for each interval.

google for java generics

I was running mango with hundreds of points polling every 5-10s logging every 15 minutes with derby on IBM R50 laptops 1.5GHZ cpu single core and 512 mb ram and it worked, but I replaced the laptops with propers servers and I'm a lot happier now.

http://www.selinc.com/SEL-3354/

You could try http://babelfish.yahoo.com/ to translate relevant blocks of documentation to the language of your choice. Perhaps that would make it easier to understand.

the "logging type" (interval, all data, on change etc) on the point details edit page is not going to change the value of your point, only how often it is recorded.

The "on context update" is an attribute of meta points which dictates when the script is run.

Did you try this as the meta point script? Your meta point value would not be increasing if that were your script.
p1.value - p1.ago(DAY,1)

i've hacked in sending alarm messages via SMS if you are interested in that patch, but no support for incoming SMS.

as I understand his point value pulses every time a kwh passes. I assumed the magnitude of the pulse was 1, so the sum of pulses in the past day was the kwh for the day. even if the script was recursing, it doesn't reference itself, so shouldn't be growing like the other fellow's.

Perhaps his point value is already the sum of the pulses, and is slowly increasing. in this case he wants p1.value - p1.ago(DAY,1) to get just the pulses today.

I'm not sure. It would seem that the sum of your point over the past day is 4460.

try some of the other functions documented in the help file for meta points until you find the combination that supplies the answer you think is correct

add a meta point

It never occurred to me that a meta point script would be run again after its own update.

http://mango.serotoninsoftware.com/forum/posts/list/334.page#1554 might answer your question