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.

If there were, it would be a nightmare to investigate it through console screenshots. You can email your logs and your latest Mango/backup/core-database-H2-...zip file to support@infiniteautomation.com and I'll give it a look.

Hi Nikos, Yes, you could use a meta point like, var dayStartTime = new Date(); dayStartTime.setHours(0); dayStartTime.setMinutes(0); dayStartTime.setSeconds(0); dayStartTime.setMilliseconds(1); //Get the value before the first millisecond of the day // (00:00:00.000, or the last value from yesterday if it didn't change) var subtracter = variableContextPoint.pointValueBefore(dayStartTime.getTime()) var subtrahend = energyContextPoint.value; if(subtracter == null) return -subtrahend; return subtracter.doubleValue - subtrahend;

You should look into the SQL data source, as a place to start.

Hi Nikospps, I'm not certain. Are you getting any events or log messages? If I had to guess, there is an illegal address exception in your logs, and the actual modbus requests span your existing point and your new point, but in between in those addresses is one the device doesn't grant permission to read. So, to fix, use the "Contiguous batches only" setting, or decrease your maximum register / bit request size until it stops happening.

Thanks for contributing Thirawad! Hi Nikospps, Thirawad is correct about how to change the port. If you haven't already you'll want to copy your Mango/classes/env.properties file into Mango/overrides/properties/ and then edit it there. This was, if you update Mango your env.properties is not overwritten with the default. You need to restart Mango for a port change to take effect.

No worries! I think I found something else important anyway in the course of answering, so thanks for asking a good question.

@nikospps said in Setting Data Points in Modbus IP using HEX Addresses: [SOLVED] Hopefully that i found the solution, which was easy. I converted hex->decimal and used the result as offset gave me values. I will finish my effort and keep you informed. Yeh I've found I have had to convert the hex address to decimal (using Google's friendly calculator) and it works almost every time. Dan

@Nikospps It is indeed something that should be displayed on the new UI. We are working on it - https://github.com/infiniteautomation/ma-core-public/issues/1140

Hi Nikospps, welcome to the forum! The Modbus scan tool is only to make identifying slave IDs somewhat easier or assessing which slave IDs are currently up. The tool simply attempts to read Holding Register 0, and if it succeeds it reports that slave ID as existing on the network. You do not need to purchase Mango in your use case. You need to create data points that correspond to the data mapping in your external device. If it's a standard sensor / component / PLC it may have a modbus map in the manual for a device that explains register range, data type, register offset and possibly scale factors that you can use to create points. Try using the "Point locator test" tool on the same page as the scan and using that to create a data point. If your device has hundreds of registers preconfigured in that modbus map, know the free license is limited to 300 points and non-commercial use so you may need to be choosy about which points you are collecting data on. [image: P6nm6pS.png]