Unsupported IP protocol issue while reading modbus data source

usi

Hi,

We get such an error from the data source we were able to access earlier. Although communication states are successful, we cannot read data. What could be the cause of this problem?

MattFox

To better deduce the issue, could you put a copy of the mangodir/logs/ma.log here between code tags?
That and the version of mango you are using.
Gives us a fighting chance

Fox

usi

Hi Matt,

We encountered this problem in version 3.7.7.
Since the file characters exceed the 32767 limit, I could not add it to the code text. Can you download the ma.log file from the link below?
lma_log

MattFox

Yeah I got it. Id advise emailing it to their support team. That error is from something under the hood...
I believe it is support@radixiot.com...

Fox

terrypacker

@usi I just took a quick peek at the logs and can see one problem, however it isn't going to be the same thing that is causing those events to be raised in your first post.

The data source trying to convert the value using the multiplier setting on the data point. I would check all of your data points on that data source and confirm the multiplier is set to 1 (or something that you want to multiply by). It seems one (or many) of your points have something that isn't numerical set on that setting.

ERROR 2021-03-10T09:33:47,909 (com.serotonin.m2m2.util.timeout.TimeoutTask.run:61) - Uncaught Task Exception 
java.lang.NumberFormatException: null
	at java.math.BigDecimal.<init>(BigDecimal.java:497) ~[?:1.8.0_231]
	at java.math.BigDecimal.<init>(BigDecimal.java:383) ~[?:1.8.0_231]
	at java.math.BigDecimal.<init>(BigDecimal.java:809) ~[?:1.8.0_231]
	at com.serotonin.m2m2.modbus.rt.ModbusDataSourceRT.updatePointValue(ModbusDataSourceRT.java:404) ~[?:?]
	at com.serotonin.m2m2.modbus.rt.ModbusDataSourceRT.doPoll(ModbusDataSourceRT.java:230) ~[?:?]
	at com.serotonin.m2m2.rt.dataSource.PollingDataSource.doPollNoSync(PollingDataSource.java:228) ~[mango-3.7.7.jar:?]
	at com.serotonin.m2m2.rt.dataSource.PollingDataSource.scheduleTimeoutImpl(PollingDataSource.java:183) ~[mango-3.7.7.jar:?]
	at com.serotonin.m2m2.rt.dataSource.PollingDataSource$1.scheduleTimeout(PollingDataSource.java:85) ~[mango-3.7.7.jar:?]
	at com.serotonin.m2m2.util.timeout.TimeoutTask.run(TimeoutTask.java:59) ~[mango-3.7.7.jar:?]
	at com.serotonin.timer.Task.runTask(Task.java:179) ~[mango-3.7.7.jar:?]
	at com.serotonin.timer.TaskWrapper.run(TaskWrapper.java:23) ~[mango-3.7.7.jar:?]
	at com.serotonin.timer.OrderedThreadPoolExecutor$OrderedTaskCollection.run(OrderedThreadPoolExecutor.java:314) ~[mango-3.7.7.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_231]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_231]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231]

usi

I checked the multipliers of the data points on your recommendation. IP change occurred due to revision in servers. For this reason, it seems like a problem arising from our querying and processing data other than the data point we target. For now the problem seems to be gone, I will inform you again when the ports are opened,
thanks Terry.