PC -> IRC5 compact connection problem on local lan

Laro88

Whenever my pc app attempts to connect to an IRC5compact on a machine local lan (pc, safety and IRC5 only) then the connection establishment takes 20-40 seconds.

I have no idea what is going on - I have log statements just before performing a network scan :

networkScanner = new ABB.Robotics.Controllers.Discovery.NetworkScanner();
networkScanner.Scan();

It seems there is a long delay inside some ABB code.

How do I circumvent this issue - is there some DNS timeout or gateway missing issue that I can solve this with.

It is in 5.15.01 and also in the older 5.14.xx

Any suggestions?

Niklas Skoglund

Hi Laro,

is this correct:

networkScanner = new ABB.Robotics.Controllers.Discovery.NetworkScanner();
networkScanner.Scan();

...

// Time consuming operation starts here

Controller c= new Controller(myControllerId);

// Time consuming operation ends here

...

Niklas Skoglund

Or is it thins line that is slow

networkScanner.Scan();

Laro88

Hi Niklas.

.Discovery.NetworkScanner() takes between 0.2 and 12 seconds.
networkScanner.Scan(); can take up to a bit more than 10 seconds

However when drilling some logfiles from myh machine I start to suspect that the:
controller = new Controller( ControllerFactory.FormatControllerId( g ) );

Also causes some delays, however I done have any detailed enter exit logging - yet.

I am suspecting some DNS / gateway issue since connection is working perfectly when connected to a local lan with DNS and gateways.

Niklas Skoglund

Hi again,

I'll ask a colleague who knows more about the implementation on the protocol level to have a look on this thread. 

Unfortunately I have no good answer or explanation or workaround myself. 

Do you experience a similar behaviour in RobotStudio as well? The Add Controller list on the Controller tab does the equivalence of NetworkScanner.Scan() (but it is not using PC SDK).

I'm trying to isolate the problem to PC SDK or the underlying communication protocol implementation...

I would also like to recommend you to contact support since this seems to be a problem that requires some amount of investigation.

Laro88

Hi Niklas.
Sorry for being sloppy - busy commisioning machines + more.
RobotStudio is responding immediately - no issues there - so it seems to be isolated in NetworkScanner.Scan()

I will contact sales / support today - I need to order a couple of 140 bots soon :-)

Henrik Berlin

Hi Laro,

A few releases ago we had performance problems with the components managing the controller communication. Running the script available on the RobotStudio / RobotWare DVD solves this particular problem, see <RobotWare DVD>\Utilities\Reg_ComServer_NetScan.cmd. Just double-click on the file and the script will run. Ensure that RobotStudio is not running when the script is launched.

It may be worth to run the script to check if it solves your problem.