@craigweb Hi! Sorry about late answer. The root cause of the problem was finally tracked to our outstation which was using wrong DNP3 profile and since that we got only integer values through DNP3.

@terrypacker Thanks for your response again. I'm also quite sure that the implementation of the floating point data type is done correctly in Mango DNP3. If there would be something wrong with the data type support the integer part of the value wouldn't be correct at all. But could there be any other setting or something else that causes value to floor? We will record communication with wireshark during next weeks. It's still possible that our outdevice floors value before sending data eventhough it shouldn't behave like that.

@terrypacker Hi Terry and thanks for your response. Now I've installed DNP 3.7.2-beta.0. I'm still testing but it seems that all decimals in floating point values are always floored to zero or then I've missed some setting. Picture below is from the last test run and there should be fluctuation also in the decimal part of the value. Text rendering is set to plain.

@mattfox I've used watchlist so far.

@mattfox Hi, thanks for the tip. In text rendering I've tried both: Plain and Analog with format 0.00 and the result was same (decimals have value 0).

I'm facing a problem with decimals in DNP3 Datapoints. I have Simatic RTU3041C as an outstation and I'm reading analog (32-bit floating point) values to Mango. For some reason the integer part of the number is correct but all decimals are replaced by zeros in Mango datapoint. For example the value 33.87 is shown as 33.00 in Mango. Does anybody have ideas what could cause this and how to solve the problem?

I'm using DNP3 Data source version 3.7.1 and Mango Core version 3.7.7.