How to replace 140NOE by 140NOC in system
Some user replace Quantum NOE by NOC, which is always used for communicating with SCADA or 3rd party's device as ModbusTCP server.
The communication may fail after the replacement, why can't the connection establish?
The most likely cause of this issue is the UnitID in the client setting as 255. UnitID255 for NOE is normal UnitID, but for NOC, it is used for Diagnostic in NOC module itself.
There is a note in NOC's user manual. Please refer to the attachment.
The solution is to change the UnitID from 255 to 0~254.
The communication may fail after the replacement, why can't the connection establish?
The most likely cause of this issue is the UnitID in the client setting as 255. UnitID255 for NOE is normal UnitID, but for NOC, it is used for Diagnostic in NOC module itself.
There is a note in NOC's user manual. Please refer to the attachment.
The solution is to change the UnitID from 255 to 0~254.
Udgivet til: Schneider Electric Danmark
Brug for hjælp?
Produktvælger
Find hurtigt og nemt de rette produkter og det rette tilbehør til dine anvendelser.
Få et tilbud
Start din salgsforespørgsel online, så vil du blive kontaktet af en ekspert.
Find forhandler
Find den nærmeste Schneider Electric-distributør.
Hjælpecenter
Find supportressourcer til alle dine behov på ét sted.