|
Problem with modbus TCP on Spacelynk 2.6.0
|
26.04.2021, 14:45
(26.04.2021, 13:00)admin Wrote: Thanks for the access. The problem was caused by a bug that reset the slave ID from 255 to 247 when the Modbus device properties were edited. I've changed the address back and it started working. Be careful when editing it before it is fixed in the next firmware Big thanks for your help?
Done is better than perfect
|
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Problem with modbus TCP on Spacelynk 2.6.0 - by buuuudzik - 23.04.2021, 18:35
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by admin - 26.04.2021, 07:05
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by buuuudzik - 26.04.2021, 07:32
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by admin - 26.04.2021, 07:38
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by buuuudzik - 26.04.2021, 08:15
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by admin - 26.04.2021, 13:00
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by buuuudzik - 26.04.2021, 14:45
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by benjii - 17.05.2021, 07:40
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by Daniel - 17.05.2021, 07:41
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by benjii - 17.05.2021, 07:59
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by Daniel - 17.05.2021, 07:59
RE: Problem with modbus TCP on Spacelynk 2.6.0 - by benjii - 17.05.2021, 08:03
|
