Typical case: Communication error on the extension backplane (16 # 1409). Check if the expansion cable is securely connected and if the terminal resistor is connected (if using the AHAADP01EF-5A fiber optic module, check the fiber optic link).
6.5 Program running exception related errors
When an error occurs after compiling and downloading the program, special auxiliary relays such as SM0~SM2047 will indicate the specific problem:
SM0: Program execution error (instruction or device issue)
SM5: Program structure error (missing END, no labels, etc.)
SM8: Watchdog timeout
SM9: CPU parameter/ID/password/communication configuration error
SM10: Module table error
SM453: Memory card error (undetected, write protected, insufficient capacity)
Solution suggestion: Use "online mode" and "debug mode" in ISPSoft to step through the program, observe the changes in device values in the monitoring table, and view the last 20 error records in combination with the error log window (system log).

Quick troubleshooting of motion control module and network module faults
7.1 Motion Control Module (AH05PM-5A/AH10PM-5A/AH15PM-5A/AH20MC-5A)
Common error codes (16 # A002~A020):
16 # A00B: Single speed target position error (out of range)
16 # A00D/E: The speed setting value is incorrect (cannot be 0)
16 # A012: Positive pulse disabled (triggered by positive limit sensor)
16 # A014: Reaching limit switch
16 # A01A: Division error (division by 0)
Solution: Check the motion program written in PMSoft to confirm that the speed, position, and acceleration/deceleration parameters are legal; Check if the external limit switch signal returns normally.
7.2 Network modules (AH10EN-5A, AH10DNET-5A, AH10PFBM-5A, etc.)
AH10EN-5A Error 16 # A001: IP Address Conflict - Modify IP and re download parameters.
AH10DNET-5A Error 16 # A0F4: Bus shutdown - Check the DeviceNet cable and terminal resistance (121 Ω) to ensure that all nodes have consistent communication rates.
AH10PFBM-5A Error 16 # A4E2: Offline slave detected - Check PROFIBUS-DP bus connection and slave power supply.
Storage card (SD card) usage and system backup
AH500 supports SD/SDHC cards (up to 32GB) for program backup, system recovery, and log storage.
System backup (manual):
Set DIP switch SW3 to ON and SW4 to choose whether to backup device values.
Press and hold the CLR button for 5 seconds, the SYSTEM LED will flash, and the LED will turn off after the backup is complete.
The backup file (AUTOEXEC. dup) is saved in the SD card AH500 SysDup directory.
System recovery:
Set DIP switch SW2 to ON, and set SW1 and SW3 to OFF.
Power on again, the system automatically performs recovery, the SYSTEM LED flashes, and turns off after completion.
After restoration, SW2 must be turned back to OFF, otherwise it will be restored repeatedly every time it is powered on.
Common SD card errors:
16 # 005D: Memory card not detected - check if it is inserted correctly.
16 # 0061: Insufficient capacity - Use a larger capacity card or clean up old files.
16 # 0062: Write Protection - Move the SD card side lock to the unlock position.
16 # 0066: System backup error - reformat SD card to FAT32 and retry.
Maintenance recommendations and lifespan management
Regular functional inspection: According to the safety level requirements, emergency stop shall be triggered monthly or annually to confirm that the safety output is disconnected normally.
Battery replacement: The CPU's built-in battery (TSX PLP 01, mentioned in the manual) is used to maintain locked data and real-time clock. It is recommended to replace it every 2-3 years. When the battery voltage is too low, SM will prompt.
Firmware upgrade: Upgrade CPU and module firmware through SD card or ISPSoft, and backup the project before upgrading.
Cleaning and fastening: Check the torque of the backplate screws, module fixing screws, terminal wiring once a year, and clean dust if necessary.
Error log analysis: Utilize ISPSoft's "System Log" function to regularly view historical error codes and predict potential issues.
