Troubleshooting
Overview
If you encounter problems with your PC SDK application follow these steps before contacting ABB support.
| Action | |
|---|---|
| 1 | Check whether your problem is in the in the next section. |
| 2 | Answers to many questions are available in the Release Notes of the specific PC SDK release. The document is also available on Developer Center. |
| 3 | Pinpoint the problem by debugging your code so that a precise problem description can be provided. |
| 4 | Visit ABB’s User Forums, which includes a section dedicated to discussion and chat on PC SDK topics. Check Developer Tools section in User Forum. |
Checklist
Some of the common issues and their solutions that you encounter with PC SDK are tabulated here:
| Issue | Solution |
|---|---|
| Unable to connect to controllers? | Ensure that the RobotWare option is available in the system on the controller. This applies to both virtual and real controllers. |
| Is the GUI hanging? | Ensure to use Invoke when modifying the user interface due to a robot controller event. For more information, see Controller events and threads. |
| Do you encounter a problem that is related to netscan? | You must increase the time allowed for scanning if NetworkScanner.Scan does not find the robot controller during netscan. Increase the time in an app.config file as explained in Application configuration file or add the time directly in the code as follows.NetworkScanner aScanner = new NetworkScanner(); aScanner.Scan(); System.Threading.Thread.Sleep(4000); aScanner.Scan(); |
| Do you get Invalid Client ID when trying to do a read operation towards the robot controller? | This issue can be resolved by ensuring that you are logged in to the controller. To write to RAPID data or to write to the configuration database, mastership is required. To get write access, the client must request mastership of the controller resource it wants to manipulate. For more information, see Logon and Logoff and Mastership. |
Important support information
If you are unable to solve the problem, make sure that the following information is available when you contact ABB support:
Written description of the problem
Application source code
System error logs
A backup of the system
Description of work-around if exists