ABB AC500-S User Manual (English)

Other manuals for ABB AC500-S

Questions and Answers:

J
Jamie HarrisAug 18, 2025
What to do if PS501 Control Builder Plus / ABB Automation Builder hangs during project modification?
- D
  Dean ChavezAug 19, 2025
  If the PS501 Control Builder Plus / ABB Automation Builder application appears to hang when closing, saving, or modifying a CoDeSys Safety project, it may be due to the user management requiring you to re-confirm your log-on credentials for safety components. A log-on message box might be in the background. Find the log-on message in the background of your Windows desktop, log-on, and continue your previous actions. If this happens frequently, set a longer user log-on session time for PS501 Control Builder Plus / ABB Automation Builder.
B
bradyadamAug 21, 2025
How to fix SM560-S ABB Safety CPU login issues from CoDeSys Safety project?
- L
  Lauren ColemanAug 21, 2025
  If you cannot log in to the SM560-S from CoDeSys Safety project, it might be because the CoDeSys visualization is already connected directly to the SM560-S Safety CPU, blocking the connection. Only one connection to the SM560-S Safety CPU is allowed at a time. Disconnect the CoDeSys visualization from the SM560-S Safety CPU.
B
bobby42Aug 23, 2025
What to do if SM560-S ABB Safety CPU goes to RUN state but Safety I/O modules go to RUN state?
- C
  Courtney GonzalezAug 23, 2025
  If the SM560-S Safety CPU is in RUN or DEBUG RUN state, but all Safety I/O modules suddenly go to RUN (module passivation) state, your program may contain an endless loop. This prevents the SM560-S Safety CPU from sending valid safety telegrams to Safety I/O modules in a timely manner (within the configured watchdog time). Check (debug) your safety application program and ensure that there are no endless loops.
B
Brandy MartinezAug 26, 2025
Why is login to ABB SM560-S Safety CPU not possible?
- K
  Kelsey WilkersonAug 26, 2025
  If you cannot log in to the SM560-S Safety CPU, it might be due to incorrect “Communication parameters…” settings. Ensure that the correct settings of “Communication parameters …” are used in CoDeSys Safety to connect to the SM560-S Safety CPU.
W
wtrevinoAug 27, 2025
What to do if safety digital input channel is occasionally passivated with an internal error diagnostic message (Err. Class: E3, Comp.: 14, Device: 1 … 10, Module: 31, Channel: 31, ID: 43) in ABB?
- C
  Carl BeasleyAug 28, 2025
  If your safety digital input channel is occasionally passivated with an internal error diagnostic message (Err. Class: E3, Comp.: 14, Device: 1 … 10, Module: 31, Channel: 31, ID: 43), one potential reason is that your input signal frequency exceeded an allowed input channel signal frequency. Check that your input signal does not exceed the allowed digital input signal frequency.
T
Tina VillegasAug 30, 2025
What to do if unable to login to ABB SM560-S Safety CPU from CoDeSys Safety after logout?
- M
  Madison WashingtonAug 30, 2025
  If you are unable to log in to the SM560-S Safety CPU from CoDeSys Safety after logging out, you might be trying to log in too quickly. Wait a few seconds (~ 5 – 10 s) after logging out from SM560-S before attempting to log in again in CoDeSys Safety.
A
Amanda ReevesSep 1, 2025
What causes DX581-S ABB module to power on without power supply connected to UP clamps?
- F
  Frances VillegasSep 1, 2025
  If the DX581-S module is powered on, but no power supply is connected to the UP clamps, there may be a wiring error. This can occur when +24 V DC is connected to at least one of the safety digital output clamps of DX581-S, causing it to power on through the safety digital outputs. Check the wiring of DX581-S and disconnect +24 V DC from the safety digital output clamp(s).
E
Eric CollinsSep 4, 2025
What to do if safety I/O module is occasionally passivated without a reason in ABB?
- E
  Erika VelezSep 4, 2025
  If some channels of a Safety I/O module or a complete Safety I/O module is occasionally passivated without a clear reason, it might be due to poor electrical contact between the Safety I/O module and the TU582-S terminal unit. Ensure that you pressed the Safety I/O module into the TU582-S terminal unit with a force of at least 100 Newton, as prescribed in AC500-S checklists.
D
dcookSep 6, 2025
How to resolve long list of internal constants with a green font colour for PROFIsafe F- Host instances after login to CoDeSys Safety in ABB?
- B
  Brandon RodgersSep 6, 2025
  If, after logging in to CoDeSys Safety, you see a long list of internal constants with a green font color for PROFIsafe F-Host instances, the option “Replace constants” is selected in CoDeSys Safety. To resolve this, go to the CoDeSys Safety menu, select “Project è Options è Build,” and unselect the option “Replace constants.”
L
lopezvictorSep 8, 2025
What to do if serial driver shows communication error after login/logout in ABB?
- C
  Cynthia WilliamsSep 8, 2025
  If you're using the serial driver to connect to the SM560-S Safety CPU and encounter a communication error after executing a “Login” command shortly followed by a “Logout” command in CoDeSys Safety, the serial driver may not have enough time to re-initialize. Wait for at least 20 seconds before executing the “Login” command after a “Logout” has been performed.

ABB AC500-S Specifications

General

Programming Software	Automation Builder
Protection Class	IP20
Communication Protocols	Ethernet/IP, Modbus, PROFINET, PROFIBUS, CANopen
Programming Languages	IEC 61131-3 (LD, FBD, IL, ST, SFC)
Safety Standard	IEC 61508
Power Supply	24 V DC
Certifications	CE, UL, cUL, ATEX