• P
    Phillip Weeks

    The time of p1a and p2a are controlled by a controller and uses system mode to increment one register or the other so it should not trigger together. I changed the CONTEXT update from logged to update on the p3 and this has made a difference I see after a single point test. times are lining up. now so I am re-running a few months across several hundred points to see the outcome. Input meter values are time correct, so when it finished and I will look close at the data timestamps and report back.

    posted in User help read more
  • P
    Phillip Weeks

    I have two meta points P1 P2 that get logged when and if 2 input context points P1a, P2a are logged on change (they increment). I now want a third meta point P3 that logs the value of either P1 or P2 context points whenever either are logged. Only p1 or p2 can be logged at any one timestamp controlled at the source.
    My issue is real time and history recalculation must both work and I can get real time to work but not a history with the correct timestamp on p3.

    IN CONTEXT:p1,p2;
    var p3=0;
    var timestamp = Number(CONTEXT.getTimestamp());
    if (Math.abs(timestamp - Number(p1.time)) < 1000)
    p3 += p1.value;
    if(Math.abs(timestamp - Number(p2.time)) < 1000)
    p3 += p2.value;
    return p3;

    This logs all data and p1 or p2 updates p3 CONTEXT when either is logged and they are only logged if their CONTEXT points have logged and this only happens when they have changed. So the plan is that p3 will log the value and timestamp of either p1 or p2 whichever triggers the update. So far I cannot get this to work. Any advice would be helpful.

    posted in User help read more
  • P
    Phillip Weeks

    AHHH I upgraded to 3.5 and saw the meta data go wild. So I rolled it back to 3.4 and restored a backup. Hence the Excel Schema warning.
    We have not use the logged event to trigger any meta point updates.
    So changing the meta points to use p.last(2, true) enables cache and script will work after we update to 3.5?
    I assume last(2,true) only works in mango 3.5 correct?

    posted in User help read more
  • P
    Phillip Weeks

    Are these statements equivalent?
    Counter Context update
    var values= Counter.last(2);
    var INCREMENT = Counter.value - values[0].value;
    var INCREMENT = Counter.value - Counter.pointValueBefore(values[0].time).value;

    posted in User help read more
  • P
    Phillip Weeks

    If a meta point update is triggered and the new value in context is the same as the value last logged for this point, does the logger consider this value changed and to be logged as well?

    posted in User help read more
  • P
    Phillip Weeks

    Thanks Phil; restore worked out fine after.

    posted in Mango Automation Installation read more
  • P
    Phillip Weeks

    I just put a clean copy of 3.4.4 on our cloud server. I want to restore a database from backup so I selected a recent H2 backup and it said it was restored so how does the NOSQL and the configuration get restored as well?

    posted in Mango Automation Installation read more
  • P
    Phillip Weeks

    So I triggered it with a minute update event and YES it does log now. Wow thanks guys it is working this way. You are correct about the green check not really setting the value and something tells me I knew this last year.

    posted in User help read more
  • P
    Phillip Weeks

    I am attempting to set a metapoint value in script at the end of a loop. the result acknowledges the setpoint however the point value does not log and I am logging all data for that point? Shouldn't this be sticking?

    dataPoints[0].runtime.set(value,timestamp);
    Setting point Last_Unit_Processed to Velo-201 @12/09/2018 17:03:50

    When I look at this point it has no value logged.

    posted in User help read more