Troubleshooting FlexPendant applications

1

Is it possible to start your application? If not see FlexPendant application does not start.

2

Have you checked the FlexPendant SDK Release Notes? Many questions will find an answer in the Release Notes of the specific release. These are available on the RobotWare DVD and at the Software Download Site.

3

Have you tried to pinpoint the problem by debugging the FlexPendant? If not see Debugging the FlexPendant device for information about how to do it.

4

Have you tried to get debug printouts? For more information, see Debug output.

5

Is the problem FlexPendant hangings? Make sure you use when modifying the user interface due to a robot controller event. For more information, see GUI and controller event threads in conflict and Invoke method. When a hanging occurs attach the Visual Studio debugger to the FlexPendant. On the Debug menu, point at Windows and select Threads. Examine the threads to discover any deadlocks.

The proxy assembly (*.gtpu.dll) is not built.

Correct any parameter error in the TpsView attribute. For more information, see FlexPendant TpsView attribute

The ABB Compliance Tool complains it cannot find the C# compiler.

It happens that the installation of Visual Studio does not set the path to the C# compiler properly. The C# compiler is necessary for running the ABB Compliance Tool.

Confirm that the C# compiler is available by starting a command window and run “CSC.EXE”. If the result is similar to this the path is properly set:

C:\>csc.exe

Microsoft (R) Visual C# .NET Compiler version 7.10.3052.4

for Microsoft (R) .NET Framework version 1.1.4322Copyright (C) Microsoft Corporation 2001-2002. All rights reserved.

fatal error CS2008: No inputs specified

If not, find CSC.EXE and copy its path to the dialog of your Visual Studio project. Also add the path to the system PATH environment variables.For Windows 2000 Pro and Windows XP find the dialog for this at:Control Panel -> System -> Advanced ->Environment Variables -> System variables-> Add new. Add the path to the directory where the C# compiler is kept. Notice that a semicolon separates the path items.Verify in the command window afterwards that the CSC.EXE runs.

The application does not appear in the ABB menu.

Make sure the robot system has the FlexPendant Interface option.

Null reference exception or "Can't find object" when tapping the application icon in the ABB menu.

Make sure all arguments in the TpsView attribute are appropriate. For more information, see FlexPendant TpsView attribute.

The bitmap constructor fails when the real FlexPendant tries to load your images, in the virtual environment this does not happen.

Change your images if they use more than 256 colors. The operating system of the first generation FlexPendant device (SxTPU1) only supports 256 colors.

The Virtual FlexPendant process remains alive.

If you forget to dispose an object that has a COM reference, such as the Controller object or a Signal, the Virtual FlexPendant process might stay alive. Go through the application and make sure that you dispose of all objects that have a Dispose method.