How to Troubleshoot RS485 Communication between Controller and xPortal Software

• xPortalNet
• xPortal3000

• XP-GT1200L
• XP-GT3200L
• XP-GT1200LABX
• XP-GT3200LABX
• XP-GT3200LE
• XP-GT3200LCPX
• XP-GT500LE
• XP-GTR1200L
• XP-GTR3200L

• Controller's status in the Device List is shown as "Down"
• The software's Latest Event List failed to record any transaction updates from the controller
• Controller setting is not updated when users download settings from the software
• In the software Delivery Report, the delivery status is shown as "Sent Error" when downloading settings or updating the card user info to the controller 

• Wiring termination issues between controller and MCI or USB-to-serial converter
• Incorrect Comm Port No selected
• Incorrect controller Unit No. / System Addr No. selected in the controller and software xPortal Server
• Incorrect Baud Rate Setting between the controller, MCI, and/or xPortal Server
• MCI unit may be faulty
• Comm Port may be faulty

Step 1: Check and reconfirm that the wiring termination between the controller and MCI or USB-to-serial converter are terminated correctly and properly:

Figure 1: Wiring Termination from the XP-GT or XP-GTR (old series) to the MCI unit

.

Figure 2: Connection of Multiple XP-GT (old series) Controllers to One MCI Unit to be Connected to PC 

.

.

.

• To check and reconfirm software and hardware configuration settings:

Step 1: In the Edit Connection window, check and ensure that the Comm No and the Speed is configured according to the appropriate hardware connections

Figure 3: Add Connection Window

.

.

.

Step 2: In the Edit Controller window, check and ensure that the controller's Unit No is configured according to the System Address in General Parameter of the controller's programming menu.

Figure 4: Unit No Field in Edit Controller Window

.

Figure 5: System Address Setting in General Parameter Menu on XP-GT / XP-GTR (old series) Controller

.

Step 3: Check and ensure that the software is allowed communication access through the Windows Firewall and the respective antivirus software.

.

.

• To send in the MCI unit for repairs:

Step 1: If none of the above works to solve the issue, users are advised to swap the MCI with a known to be functioning unit of MCI to identify if the MCI unit is faulty.

.

Step 2: If the MCI unit is tested to be faulty, users are advised to send the faulty MCI unit for repairs with the MicroEngine Service Center.