Getting signals with RW5.14.03.01 very slow

Developer Tools
1

Hello,

I have been noticing a very slow response time from the PC-SDK when trying to get a list of signals from the controller. The issue seems to only occur when using RW5.14.03.01. Here is an example of the command I am calling:

SignalCollection signals = ctrl.IOSystem.GetSignals(IOFilterTypes.Digital | IOFilterTypes.Input);

My application will hang on this command for 10 minutes before I get a response.

I can take a pack and go of the system, and unpack it with RW5.14.02.01 and the response time is a few seconds.

Has anyone else seen this problem? Did something change in the PC-SDK or RW in this area? Are there any workarounds for this problem?

Thank you.

2

This is a real problem when a robot key prevents downgrading to an earlier version. Maybe someone at ABB could chime in…

3

Hi sehe,

when you say it works as normal when you unpack it with RW5.14.02.01, are you using the same version of PC SDK as in the case where it is slow?

Our Developer Tools team is investigating this problem and the last news I have is that the problem is located to PC SDK, and that it is not related to which RobotWare version you are using.

If you run the call to ctrl.IOSystem.GetSignals a second time, for the same controller, do you get the same slow result or does it perform as usual?

There is a caching mechanism in PC SDK which speeds up I/O signal retrieval, which may be involved here…

4

Hi Niklas,

I did not change the PC SDK version. I just created a pack and go of the 5.14.03.01 system and unpacked it on the same computer.

With 5.14.03.01; when I call ctrl.IOSystem.GetSignals for the first time, it takes about 10 minutes. This crashes my application. If I run the command a second time it only takes a few seconds.

With 5.14.02.01; the first call takes about 10 - 15 seconds, then the subsequent calls are just a couple of seconds.

Let me know if you need any more information.

5

Hi sehe,

my vacation starts today, but I have made sure someone will continue posting on this thread in my place.

The fact that you did not change PC SDK implies that the problem is located in the Controller… We have to verify this.

6

Is there any update on this?

7

Hi again,

now I’m back.

The latest is that the subsystem where the problem is located has been identified.

Problem still not solved.

We have also got a support case logged. Not sure if it was from you.

8

The problem has been found in RobotWare and a fix is planned for RobotWare 5.15 this autumn.

9

Robotware 5.15.00 does fix this problem. Thank you for the help.