Author Topic: Problem when starting with loss of DF1 connection  (Read 2453 times)

Tril

  • Newbie
  • *
  • Posts: 9
    • View Profile
Problem when starting with loss of DF1 connection
« on: August 14, 2013, 11:13:17 AM »
I'm using version 3.52 with a SLC 500 connected with a DF1 connection with a RS232 cable connected to a RS232 to USB cable. It works fine when the cable is connected. When the cable is not connected on the PLC end, the HMI start time is long and the form is slow to react to user input. The startup time increases with the number of controls on the form. With about fourty controls, it takes about two minutes for the form to appear on screen.

It looks like most of the startup time is spent inside line 340 of DF1Comm.vb (inside the dll) :
Code: [Select]
result = DLL(MyDLLInstance).SendData(CommandPacke, MyNode, TargetNode)
When that line executes with one control on the form, the following output appears in the ouput window of the debugger :
Code: [Select]
The thread '<No Name>' (0x3d4) has exited with code 0 (0x0).
The thread '<No Name>' (0x1e48) has exited with code 0 (0x0).
The thread '<No Name>' (0x129c) has exited with code 0 (0x0).
The thread '<No Name>' (0x1458) has exited with code 0 (0x0).
The thread '<No Name>' (0x1d1c) has exited with code 0 (0x0).
The thread '<No Name>' (0x1da4) has exited with code 0 (0x0).
The thread '<No Name>' (0x1510) has exited with code 0 (0x0).
The thread '<No Name>' (0x1648) has exited with code 0 (0x0).
The thread '<No Name>' (0xac8) has exited with code 0 (0x0).
The thread '<No Name>' (0x1f04) has exited with code 0 (0x0).
The thread '<No Name>' (0x1da0) has exited with code 0 (0x0).
The thread '<No Name>' (0x818) has exited with code 0 (0x0).
The thread '<No Name>' (0x1eac) has exited with code 0 (0x0).
The thread '<No Name>' (0x1d20) has exited with code 0 (0x0).
The thread '<No Name>' (0x1d38) has exited with code 0 (0x0).
The thread '<No Name>' (0x1aec) has exited with code 0 (0x0).
The thread '<No Name>' (0x1824) has exited with code 0 (0x0).
The thread '<No Name>' (0x494) has exited with code 0 (0x0).
The thread '<No Name>' (0x1b7c) has exited with code 0 (0x0).
The thread '<No Name>' (0x1640) has exited with code 0 (0x0).

After that, the following line appears in the output window of the debugger :
Code: [Select]
A first chance exception of type 'MfgControl.AdvancedHMI.Drivers.Common.PLCDriverException' occurred in AdvancedHMIDrivers.dll
Those lines repeat every 10 seconds. If there are many controls on the form, this seems to cause a slowdown of the application.

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5269
    • View Profile
    • AdvancedHMI
Re: Problem when starting with loss of DF1 connection
« Reply #1 on: August 15, 2013, 08:16:06 AM »
I posted a version 3.54 with some fixes to the SLC/Micro driver. Try this version and let me know what results you get from it.

Tril

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Problem when starting with loss of DF1 connection
« Reply #2 on: August 15, 2013, 10:50:01 AM »
I tested both 3.40 and 3.54. I used one DF1Comm and two BasicLabel to two different addresses. With the cable connected, the form appears after two seconds. With the cable unconnected, the forms takes 20 seconds to appear (roughly 10 seconds/control on the form).

I tested on one computer with a RS232/USB converter and another computer with a serial port. Same result.