After Completing Software Configuration for XP-SNET Controller, the xPortalNet Software Showed Controller "Down" Status

After completing the software configuration for XP-SNET controller, the xPortalNet software showed controller "Down" status.

Figure 1: XP-SNET Controller Status Shown as "Down"

The Server PC is able to ping the the controller as shown below. The xPortalNet Server software configurations are checked to be configured correctly.

Figure 2: Server PC Able to Ping Controller IP Address

After further investigation in the web diagnostic, the Controller ID field (controller Unit No) is shown as "01" whereas in the software, the configured Unit No of XP-SNET controller is "00".
The mismatched controller Unit No on the physical controller board via the DIP switch settings and the software configuration setting is causing the controller to not be able to communicate with the software.

Figure 3: Controller ID Field in Web Diagnostic Window

Summary:

• To configure the DIP switch settings to Unit No. "00".

Step-by-step Guide:

• To configure the DIP switch settings to Unit No. "00":

Step 1: Go to the XP-SNET controller and open the cover of the enclosure.

Step 2: Change the DIP switches for ADDESS to "00", as shown below:

Figure 4: DIP Switches for Address of "00"

 
Step 3: Login to the web diagnostic for XP-SNET and click System Info.

Figure 5: Web Diagnostic Window

Step 4: Notice the Controller ID has changed to "00", which now matches the controller Unit No setting in xPortalNet software.

Figure 6: System Info Window

Step 5: In xPortalNet software, notice that the XP-SNET controller status in Device List > Controller will be shown as UP.

Figure 7: XP-SNET Controller Status Shown as UP