Technical FAQs

Ask a Question

NOE will reject the logout command from Concept if the programming connection is broken.

Goals and Symptoms

The '140NOE771xx' module will reject the logout command from Concept when a programming session is
interrupted by a broken 'Ethernet TCP/IP' connection that is caused by a network disruption (not a physical cable
break)

Facts and Changes

All '140NOE771xx' modules

Causes and Fixes

Under normal conditions when Concept is logged out by the user, it disconnects from the PLC and also resets
the' Ethernet TCP/IP' connection in the '140NOE771xx' module. When a Concept programming session is
interrupted by a broken 'Ethernet TCP/IP' connection that is caused by a network disruption (not a physical cable
break) and the user tries to log back into the PLC , Concept will detect that the initial session has not been logged
out. If this occurs, Concept is designed to send a logout command to the PLC before it issues the login command.
The logout command is sent to the PLC on a new Ethernet connection and will get rejected by the NOE module.
This happens because the connection for previous programming session is still open in the NOE module and
only one (1) programming connection to the PLC is allowed. The NOE module will need to be reset before Concept
can be re-connected to the PLC. Resetting the NOE module can be accomplished by lifting the module off the
backplane and reseating it back onto the backplane. The PLC can also be power cycled to reset the NOE module,

As a workaround an MSTR block can be configured to send a 'Reset Option Module' command to the NOE when
the Concept programming connection is broken. The rest command will send a function code 10 which
instructs the NOE module to reset the connection so that the user can log back in.


Legacy KB System (APS) Data: RESL182288 V1.0, Originally authored by AlCh on 02/27/2007, Last Edited by AlCh on 02/27/2007
Related ranges: Modicon Quantum
Was this helpful?
What can we do to improve the information ?