Windows Commands for Testing Suitelink Communications
Last updated: March 3rd, 2026Description
- Author: Zach Burns
- Published: March 3rd, 2026
Details:
Suitelink is a core AVEVA protocol that enables communication between InTouch, OMI, and other AVEVA components. This TechNote outlines command-line tools and steps to verify and troubleshoot Suitelink connectivity.
SLSPING Command
The slsping command can be used to test the Suitelink connection from the PC to PLC, alarm manager, view application, or any other AVEVA component communicating via the Suitelink protocol.
The syntax is:
slsping <Hostname or IP> <Application Name>SL V2 SUCCESS indicates unsecure communication is enabled.
SL V3 SUCCESS indicates secure communication is enabled.
To change between V2 and V3, you will need to configure SMS from the configurator.
Examples:
In the following example we are testing Modbus communication via Suitelink using slsping <Node name> MBTCP. In the example below, we can see that our Modbus is configured for unencrypted communication via Suitelink V2:

To reconfigure for secure communication, the SMS configuration will need to be updated using the configurator. Once making the changes to enable SMS, you must deactivate and then reactivate the communication driver. Once this is done, you can use the slsping command to verify the change. Our Modbus is now speaking Suitelink V3:

The slsping command can also be used to verify Suitelink protocol communication between other AVEVA components such as:
InTouch WindowVIewer Application
slsping <HostnameOrIP> view
Alarm Manager
slsping <HostnameOrIP> alarmmgr
Suitelink communicates via port 5413 so the following commands can also be used to determine Suitelink connectivity:
Check if Suitelink is listening on the local machine:
netstat -ano | findstr :5413
In the example below, the local machine is listening on port 5413 (Suitelink) on ALL network interfaces (0.0.0.0):

Check if a connection can be made to a Suitelink server(Powershell):
Test-NetConnection -ComputerName <ServerNameOrIP> -Port 5413
We can see below that we successfully connected to the remote machine via TCP Suitelink:

By using these tools, you can quickly identify connectivity issues and confirm secure communication settings.
Recommended articles
[ISS Support Case] PLC Communication Failure
Client reached because after user migrated the Galaxy none of the tags are communicating.
Read More[ISS Support Case] lost connection to PLC
PLC L33er- compact logix is able to ping the PLC
Read More[ISS Support Case] OPCUA Communication Failure
Client has multiple tags in the same device group two of them show good quality data and communication while the other shows bad data quality and configuration. When using WWclient it shows bad configuration error for connection. When viewing tags in OPC Quick client on OPC server they all show good communications. Client is using auto binding for tags.
Read More