Filter
Top Products
8 Important Product Information
GFK-1490C
Problems Resolved in Firmware Version 9.01
SNP Master mode on CPU Ports
With some very large configurations and version 9.00 firmware, after a power-cycle, CPU ports set up for SNP Master
would need to have their configuration re-stored for the protocol to accept COMM_REQs. This is corrected in version
9.01.
Online Changes to Reference Tables
Making online changes with the programmer to reference tables could result in a watchdog timeout. This has been
corrected in version 9.01.
Read from Flash
In version 9.00, reading a folder from flash memory could result in the PLC going into a faulted state. This is corrected
in version 9.01.
CPU364 Restrictions and Open Problems
Multiple Log Events
The Ethernet Interface sometimes generates multiple exception log events and PLC Fault Table entries when a single
error condition occurs. Under repetitive error conditions, the exception log and/or PLC Fault Table can be completely
filled with repetitive error messages.
DDP2 Name Not Used
In systems using more than 75 Ethernet Global Data exchanges, the Ethernet Interface may not initialize with the user-
configured DDP name (if any), but rather use the default DDP name. Attempts by remote stations to communicate with
the Interface using the user-configured name will fail. Possible workarounds include:
1. Reconfigure the application to use less than 75 exchanges, or
2. Have remote stations refer to the Interface by its default DDP name
Same IP Address
Use of the same IP Address by the CPU364 and by another device on the same network results in the PLC Fault Table
message “Bad remote application request; discarded request”. This condition should be identified more precisely.
Trace LZ
While a local Station Manager “TRACE LZ” troubleshooting command is in effect at an Ethernet Interface, do not issue
Station Manager “REM <node> TEST” commands to it from a remote Interface. Doing so can cause errant behavior,
including module lockup and loss-of-module in the PLC fault table.
EGD status code
The status code of an EGD exchange is not updated to “16” while performing Name Resolution as described in the
manual. The first status code update occurs when the Name Resolution is complete, either “0” if successful or “4” if
unsuccessful.
Write Channel Retasking Error
When retasking a Write Channel, the Ethernet Interface may very intermittently generate exception log event 1c, entry
2 = 5. The channel stops with status code 9590 (= internal error). The application program may issue another Write
Channel COMMREQ to start this channel.