Trouble Shooting Controller Communicaton

Created by Robert Owen, Modified on Tue, 28 Jan at 12:41 PM by Robert Owen

Introduction:


The aim of this document is to help troubleshooting and diagnose problems communication issues with the controller
 

Firstly check the controllers TX and RX leds.  The leds should be completely off when software not running if the RX is on 


Either the TX and RX are connected the wrong way around or you must connect a 120 Ohm resistor across the TX and RX.



In case there are 2 or more controller sharing the same RS485 bus, the 120Ω resistor should be installed ONLY on the last controller,
as shown here: 



Once the RX and TX are off when software is off the next step is to check the controller address:


The controller has a dip switch block coloured red with 8 switches:



The controller must be rebooted after any changes are made.


Next Step is to determine how the controller is connect either via TCP/IP or USB Com port.


If the controllers are connected via USB Com Port see this article


If the controllers are connected over Ethernet see this article


Once you have established the connection is all OK then run your GP10 software: 


Ensure the setting such as Adapter, IP address or COM Number and Port are correct



If communication is still not established. we most move to more complex trouble shooting or it would be worth sending back the controller for further diagnosis:


See Advanced Trouble Shooting

 


 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article