• M
    mihairosu

    Hey Matt,

    Actually this is all on the same internal network, I only need to migrate the data source between the two devices. Network communication is not a problem.

    Thanks for the very helpful instructions; as soon as I get a chance, I'll see if I can work it out.

    posted in User help read more
  • M
    mihairosu

    Looks to me like this is something we would be interested in pursuing in case we want to change the data source:

    It would be possible to achieve what you want by terminating mango and performing some operations on the database to change the dataSourceId column of the data point to the new source's id. This is not recommended but is possible if you know what you are doing.

    With regards to this:

    There are some migration tools with the NoSQL module assuming you use that for you point value store. Those tools coupled with the JSON Import/Export feature would likely work. The other option is to publish the data to the enterprise server assuming you are ok with the point becoming a Persistent TCP type data point and it won't have to be attached to a BACnet data source.

    I may not have explained myself well or misunderstood your instructions. I want to make sure we're on the sama page. We already publish this data point to the Enterprise server, so there's no need to move the actual data from the ES. I'll attach an image, it might work best:

    0_1574786287338_migrate bacnet.png

    Thanks

    posted in User help read more
  • M
    mihairosu

    • Replace a data source device, but we want to retain the same points.

    This means that we will have to replace a PLC or other data gathering device but want to retain the same point and history. For example, measuring temperature somewhere in a system. The new PLC may not have the same network address. However, if it did have the same address, I guess Mango won't know the difference, correct? However, if the new connect via another protocol: example, we want to upgrade from Modbus Serial to Bacnet PLC, and still want to retain data history.

    As for the rest of your suggestions, unfortunately, we do not have the expertise to do that sort of work.

    It would be ideal for us if we could do this type of task with the GUI. My interpretation is that the data points are too rigidly tied up with the device address or something like that.

    I'm not sure what we can do going forward. We would like to upgrade our equipment, but this is making it very difficult for us.

    posted in User help read more
  • M
    mihairosu

    From a practical perspective, we will have to do these two kinds tasks:

    • Replace a data source device, but we want to retain the same points.

    • Move a data point from one data source to another (migrate to another device)

    • Move BacNet point data source (all all respective points) from a MangoES to a Mango Enterprise server.

    What do I need to do to make sure that we can make these changes while retaining all of our historical data.
    Is it only necessary for the XID to stay the same?

    posted in User help read more
  • M
    mihairosu

    The scripts worked fine over the weekend. Thanks for the help Terry.

    posted in Scripting general Discussion read more
  • M
    mihairosu

    I can't confirm 100% is was on that day, but it's very possible, which is why I didn't mention it, but you are probably right.

    I will make these changes and get back to you.

    posted in Scripting general Discussion read more
  • M
    mihairosu

    This script used to work just fine, but is throwing errors every night since 10/16/2019 at the exact time its running 23:59:57.

    /*
    //Script by Phil Dunlap to automatically generate lost history
    if( my.time + 60000 < source.time ) { //We're at least a minute after
      var metaEditDwr = new com.serotonin.m2m2.meta.MetaEditDwr();
      metaEditDwr.generateMetaPointHistory(
          my.getDataPointWrapper().getId(), my.time+1, CONTEXT.getRuntime(), false);
      //Arguments are, dataPointId, long from, long to, boolean deleteExistingData
      //my.time+1 because first argument is inclusive, and we have value there
    }
    //Your regular script here.*/
    
    
    return CwConsumed.value-CwConsumed.ago(DAY, 1) //Subtracts this moment's gallons used minus one day ago
    

    Here's the error:

    'MetaDataSource': Script error in point "Main Historian - DHW Consumed Daily Count": Expected } but found eof return DhwConsumed.value-DhwConsumed.ago(DAY, 1) //Subtracts this moment's gallons used minus one day ago ^ at line: 12, column: 129Add comment
    

    posted in Scripting general Discussion read more
  • M
    mihairosu

    @phildunlap said in Cannot upgrade:

    administration/system/information

    That was it, thanks Phil

    posted in MangoES Hardware read more
  • M
    mihairosu

    I am getting an error on all of our Mango instances when trying to upgrade modules from the old GUI:

    Your instance cannot be upgraded due to a versioning problem: store.url environment property blank, cannot check for updates
    

    I searched the forum and found another similar issue was due to their internet connection, but our works perfectly well. Are there any other possible reasons for these failures?

    posted in MangoES Hardware read more
  • M
    mihairosu

    After today's reboot (for OS and module updates) everything is working well. It could also have been the previous time the modules were updated, as we only reboot these for updates.

    posted in User help read more