Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

I think you misunderstood the single cell ranges. You still need a multi cell rage for time stamps and all historical values.. You would then add a single cell range called point2.LastValue and you will get the last value for the data point associated with the names range point2

WOOHOO! Thank you Terry. That sorted the problem. Cheers Brian

Hi Joel, It's more trial and error shifting Mango onto cloud based server at the moment. The two different errors were coming up when trying two different ports for comms. I have port forwarding set up on my router for two devices. I was just wondering why one port got one error and the other port the other error. I have yet to establish communication with the Modbus devices but this is a network issue - nothing to do with Mango as I have found out. Rgds, Dominic

No, that's only for the H2 database but there is a similar tool for NoSQL depending on what version you have. Its on the NoSQL tab on the main menu but I think this is only in 2.6. You can just unzip the NoSQL database and copy it into the databases folder to replace what is there.

Thank you very much. I look forward to the release. Cheers

ok , joel ! Helped me. Thank you! Regards!

In what way are the folder names different. I downloaded the zip file and the file names in the MangoTSTD directory appear to be the same as in the zip file Bryan

Yes, you can not use the scadaBR database in Mango directly. It doesn't matter if the database is Derby or MySQL you will still not be able to use it in Mango. Your only option is to export the JSON from scadaBR and import your configuration into Mango.

If you are using MySQL to store point values the column is named TS (as in Time Stamp) and the time is stored in Unix Time. If you are using the Enterprise version of Mango then point values are store in a NoSQL database and in a different format.

I seem to have overcome this issue by going to (start>run>services.msc) and starting the MYSQL instance. All seems to be going fine now.

I increased the update period, and my controller is using COV but not the other sources.

I'm not sure as I've never used it this way but it probably depends on how you have the point set to log. If you have it set to log on change I would expect you would not get duplicates. You might see duplicates in the cache but only the change should be logged to the database.

@StephenVDK said: Hello everyone, When I try and add the multistage point to a graph or indicator in dglux, it says it's null, when it's not. How do I get it to display the proper value? Thanks. Generally with a multistate point I would (and this may not necessarily be the best way) use the 'Map' property binding type, then enter the multistate text string and respective text value. For example if you were binding to a gauge with a range of 0 to 100, you could enter the string 'low' as binding to 25, 'medium' to 50, 'high' to 75 etc.

Great thank you!

Thanks, Terry. I was thinking that duplicating the TCPIP data source would be a good start and save a lot of work. Another option is to simply add a UDP checkbox to the TCPIP source, though that may require renaming the source to "IP."

@hanse1pk said: Managed to get it working. Had to use 4 byte float swapped Next item is for me to take in these integers such as in second example and have them be shown and recorded as what they represent. This doc might be useful to you: http://wiki.infiniteautomation.com/doku.php?id=tipsandtricks:bestpractice In my experience (having added probably a dozen different types of device to Mango using Modbus) there is always a bit of fluffing around initially to discover the magic transformation to get from the manufacturer's address to the address that Mango expects. The first thing I usually do is look in the documentation for the modbus registers and find a register that can be easily identified - usually something like a 'hardware model number' or other known value. Then you can use the 'Modbus Read Data' and 'Point Locator Test' functions on the Data Source page to test out different registers to try to hit the value you want. In an extreme example, the manufacturer's documentation may say that a holding register is located at 43004, but you might find that the actual register you need to input into Mango is 3003 (43004 - 40001). Software such as 'Modbus poll' or 'CAS Modbus Scanner' also helps in figuring this out.

I may be wrong, but from memory, the chart colours only apply to reports. The charting stuff looks to have been completely overhauled in the newest beta anyway: http://infiniteautomation.com/forum/topic/1872/new-features-coming-soon