I enabled a tag (just using the system uptime value) and turned it on to be available via Modbus from the Flexy.
In the oast when I have used tag number 1 it would be available at 40001, but this time it’s available as 30001, not sure why and what I did different.
Took me a while to find it…
What device is acting as the ModbusTCP client (master)? Is it the same one that you’ve used in the past?
I’m using the Chipkin CAS Modbus scanner
I’m not sure what you did differently, but there are two different addressing standards:
but why is it showing up as 30001 instead of 40001 ?
Hello @landersson,
A 30000 register is an input register while a 40000 address in a holding register. They are used for differed memory locations on a device. input registers are read only while holding registers support read/write.
the ewons addresses should all be mapped to holding registers.
Deryck
Agreed, but when I define this as number 1 in the Tag config, it’s not showing up as 40001, but instead as 30001.
I have done this before and it has worked.
The System Uptime value is read-only so it’s not possible to set as a Holding register.
Aah, thanks for that explanation.