Messages posted by: craig

sprokkie wrote:
The device that is providing the pulses to the ds2423 gives 1 pulse for each kwh.
When the sun is down the value must be the total value of the counted pulses for that day.
..
I would like to see the value for each day.
So at 00:00 the graphical view must show 0 and during the day as the sun warms up the collector the value must be increasing 1 kwh at the time.

Sprokkie you can do this with a Meta point. Add a new meta point and read the help file for it by clicking the question mark icon.

I think you want to enter the script in the meta point as:

since you say it is pulses. you will have to replace p45 with your own point.

Hi Sprokkie,

Maybe you should run mango on the webserver (in addition to your home server).

You could set up a publisher to publish the data from your home mango instance to the remote webserver mango instance.

Alternatively, you could create a 'custom view' .jsp file on your home server mango instance, and download that to your remote webserver with a program like wget.

From the 1.8 changelog:

"Custom view pages
A new approach to creating views has been added to Mango. Now you can create your own custom view pages using simple JSP tags. Simply create a JSP page in the Mango file system, and within your HTML specify the points that you want displayed where you want them. You can also display compound charts with custom plot colours. And, using javascript you can write simple scripts to set point values as well."

click the brick icon for the point, go to the point properties edit page and near the bottom you can set up a chart renderer. this will give you the mouse over chart

ok then in the graphical views editing page you would add a "image chart"

image chart, new in version 1.6 or 1.7 i think

look in WEB-INF/dox

i've got this working, I'll send it along in a few months when it is properly tested.

adding Numeric datatype to the multistate renderer seems like it might be the wrong way to go about it...

Better to add mango multistate datatype to the modbus data point locator: I think I will add a select option to the pointlocator dialog to select either numeric or multistate when a numeric modbusDataType is specified.

I suppose I will have to modify the format the blob pointlocator data is stored in as well to store this additional field.

Is this as simple as editing com.serotonin.mango.view.text so that

reads

I can't see any downsides...

In case anyone runs into this message it is because the point value has changed in between the time the point event detector was triggered and the point event detector delay expired and the new point value has caused the point event detector to be set to inactive. Generated from a multistate point on a virtual data source:

WARN 2010-01-12 06:05:48,450 (com.serotonin.mango.rt.event.detectors.StateDetectorRT.setEventActive:94) - Call to set event active when state is not active. Ignoring.

/**
 * @author Matthew Lohbihler
 */
abstract public class StateDetectorRT extends TimeDelayedEventDetectorRT {
    private final Log log = LogFactory.getLog(StateDetectorRT.class);
    
    /**
     * State field. Whether the state has been detected or not. This field is used to prevent multiple events 
     * being raised during the duration of a single state detection.
     */
    private boolean stateActive;

private long stateActiveTime;
    private long stateInactiveTime;
    
    /**
     * State field. Whether the event is currently active or not. This field is used to prevent multiple events being 
     * raised during the duration of a single state detection.
     */
    private boolean eventActive;
    
    protected boolean isActive() {
        return eventActive;
    }
    
    public boolean isEventActive() {
        return eventActive;
    }
    
    private void changeStateActive() {
        stateActive = !stateActive;
        
        if (stateActive)
            // Schedule a job that will call the event active if it runs.
            scheduleJob(stateActiveTime);
        else
            unscheduleJob();
    }
    
    abstract protected boolean stateDetected(PointValueTime newValue);
    
    @Override
    public void pointChanged(PointValueTime oldValue, PointValueTime newValue) {
        if (stateDetected(newValue)) {
            if (!stateActive) {
                stateActiveTime = newValue.getTime();
                changeStateActive();
            }
        }
        else {
            if (stateActive) {
                stateInactiveTime = newValue.getTime();
                changeStateActive();
            }
        }
    }
    
    @Override
    synchronized public void setEventActive(boolean b) {
        eventActive = b;
        if (eventActive) {
            // Just for the fun of it, make sure that the state is active.
            if (stateActive)
                // Ok, things are good. Carry on...
                // Raise the event.
                raiseEvent(stateActiveTime + getDurationMS());
            else {
                // Perhaps the job wasn't successfully unscheduled. Write a log entry and ignore.
                log.warn("Call to set event active when state is not active. Ignoring."); // *******ERROR GENERATED HERE
                  eventActive = false;
            }
        }
        else
            // Deactive the event.
            returnToNormal(stateInactiveTime);
    }
}

The event detector had a delay of 1 second. It looks like pointChanged was called again before the one second delay on setEventActive was up. I've removed the delay and will see if the message still occurs.

I do the following:
1. make sure you have eclipse release which includes the web tools project.
2. unpack mango source in a directory called "myMangoBranch" inside the eclipse workspace directory
3. Do File->New->Other, choose "Dynamic Web project" from under "Web"
4. Make Project name "myMangoBranch" (must match existing directory name)
5. I don't have to change any other options on the new dynamic web project dialog, target runtime is apache tomcat 6.0 (you may have to add a target runtime), so I hit next.
6. Source folders on the build path i leave as "src" and default output folder I leave as build/classes, so i hit next
7. Content Directory I change from "WebContent" to war. Hit finish!

apl wrote:JFreeChart supports multiple scaling groups, it would be handy to draw values that lie in a different range onto the same chart with different scalings.

It would sometimes be nice to have primary and secondary Y-axis on charts. A simple checkbox beside the point when added to reports would suffice to indicate if it should be plotted on lefthand or righthand Y axis.

I encounter some funny charts where a value chages drastically in a short term (it jumps) and was before for a long time very stabel. Instead of a steep acend I get a slow.

This sounds like having points logged "On change", if they were logged on interval your jump would only be as big as the largest change during a single interval.

I mostly use "interval" logging and would like to one day make it so missing intervals are plotted as null values so the line is not continuous. I've done that before with JFreeChart.

Solution: If a value changes store not only the actual changed value but store as well the last value of the stable sequence.

"if/then" logging code like this complicates the matter quickly, and often has disconcerting unintended consequences. Overall, I'd be very hesitant to start logging data values that were not actually received from the data source.

As a worst case you could log the preceeding point value for every point value that is logged, if the preceeding point value wasn't logged already. You would end up with twice as many point values logged, but would have no "jumps" on the plot larger than the "on change" tolerance.

Since I'm not using traps I changed the trap port in SNMP datasource settings to a large port number and no longer get the BindException.

If I were using traps I think I'd do some port translation on the firewall so that incoming UDP port 162 packets were sent to a higher port on the mango instance

netstat -anutp reveals one listening UDP port per SNMP data source, but not port 161

If I disable an SNMP data source and re-enable it, I get the BindException. If I reboot the server I get the BindException but the data source still seems to update.

None of this is critical for me, I'll let you know how it pans out.

gotcha. but shouldn't need to bind to port 162 if not using traps right?