Alarms 3500 - 3528 Advance - Siemens Maxum II Manual

# Text
3451 ? TFTP Client Checksum Er‐
ror
3452 ? TFTP Client Missing End of
File
3453 ? TFTP Client Invalid OS File Attempt to load OS with invalid address
3454 ? TFTP Client Invalid App
File
4.6.17

Alarms 3500 - 3528 Advance

GCP Alarm Descriptions 3500 - 3528 Advance
The following tables list the alarm number (#), type (+ information, ? warning, ! error) alarm
text, description, and actions.
# Text
3500 ? Reserved
3501 ! Advance Adapter Initializa‐
tion Failure
3502 ? Invalid Channel for Ad‐
vance Adapter %4
3503 ? Advance Adapter Back‐
plane Timeout on %4
3504 ? Advance Adapter Back‐
plane Error on %4
3505 ? Resource for %4 not avail‐
able on Advance Adapter
3516 ! No Advance Adapter detec‐
ted
3517 ! Advance Adapter Driver
Out of Memory
3518 ! Invalid Advance Adapter
Driver Command
Maxum edition II Analyzer General Maintenance
Manual, August 2018, A5E42019842001
4.6 Alarm Codes, Descriptions, and Suggested Actions
Description
File loaded had invalid checksum.
Attempt to load truncated file.
range.
Attempt to load App with invalid address
range. Loadfile may be OS file or corrupt.
Description
System error
Advance Adapter detected, but respond‐
ing improperly.
Reference to invalid channel on Advance
Adapter.
The referenced I/O on backplane board
did not respond.
The referenced I/O on backplane respon‐
ded improperly.
Memory or operating system object not
available for hardware access.
System error
Driver initialization failure due to lack of
memory.
Application requested invalid command
from Adapter Driver. Most likely a mis‐
match between the SNECON OS and
application.
General Maintenance and Troubleshooting
Action
Verify that loadfile is correct and uncor‐
rupted.
Verify that loadfile is correct and uncor‐
rupted.
Verify that loadfile is correct and uncor‐
rupted.
Verify that loadfile is correct and uncor‐
rupted.
Action
Contact Customer Support.
Repair or replace adapter.
Check reference to I/O channels in ap‐
plication tables.
Reseat or replace board corresponding
to hardware ID.
Reseat or replace board corresponding
to hardware ID.
Verify that SNE has sufficient memory.
Upgrade SNE.
Reset SNE.
Contact Customer Support.
Verify that SNE has sufficient memory.
Upgrade SNE. Reset SNE.
Reload SNECON software.
71