Technical FAQs

Ask a Question

ETY4103 cannot find configured IO Scanner devices after starting the PLC.

Goals and Symptoms

The ETY4103 cannot find the configured IO Scanner devices after starting the PLC immediately following download
of a UNITY or PL7 application.

Facts and Changes

TSX ETY 4103 version 4.0

Causes and Fixes

Configured IO Scanner devices cannot be found after starting the PLC immediately following a
download of the Premium PLC application. If you try to ping the ETY module, the test fails. If there
are no devices connected to the ETY module and the IO scanner table is configured, the debug
screen in UNITY will not show the error condition correctly. Resetting the PLC using the 'Reset' button
on the PLC or power cycling the PLC corrects the problem.

This is an outstanding issue that is part of another problem which has been fixed in an improvement of
the IO scanner. The fix will be included in the next version of the exec firmware for the ETY4103.

The problem is due to the time that it takes to boot up the CPU being longer than the time it takes the ETY
module's IO scanner to bootup. This was a results of some organizational changes made in 'Executive
Firmware version 4.0'. The problem does not happen if you wait about 30 seconds after downloading
the PLC application.

As a workaround, you can either:

  • Wait several minutes before starting the PLC after downloading the application
  • Downgrade the 'Executive Firmware' to version 3.5.
The fix is scheduled to be included in the next version of the Executive firmware which will be a sub
version of 4.0. It is expected to be released sometime in the beginning of Q3/08.
Was this helpful?
What can we do to improve the information ?