News:

  • June 09, 2026, 07:36:39 AM

Login with username, password and session length

Author Topic: Connecting to DirectSoft  (Read 42044 times)

PLCGuy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 677
Connecting to DirectSoft
« on: January 29, 2008, 07:54:16 PM »
When I connect to the PLC, DL205, my network connection connects then 3secs later disconnects, the connects, disconnects. When I connect to our plants wired system, I do not notice it doing this. I tried to disable my wireless, but same results. I doubt it is the software. Any one have some insight? I will have to connect to the plant system to see if it does it there too.

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6158
  • Yes Pinky, Do-more will control the world!
Re: Connecting to DirectSoft
« Reply #1 on: January 29, 2008, 08:22:55 PM »
There are a handful of things that we poll from the controller every 2 seconds. Does it do that when ladder status is turned on? If not, it may be a very short timeout on your network connection.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

PLCGuy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 677
Re: Connecting to DirectSoft
« Reply #2 on: January 29, 2008, 10:21:54 PM »
Yes, the status is turned on. I have not tried it with it turned off. When I read the error list it says something about protocol something something, timed out. The icon on the bottom of windows keep appearing saying network cable disconnected, then second later says network connected. This keeps repeating itself over and over again.

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6158
  • Yes Pinky, Do-more will control the world!
Re: Connecting to DirectSoft
« Reply #3 on: January 30, 2008, 12:19:24 AM »
Ah...Windows thinks the cable is pulled...hmmmm...

Definitely sounds like a physical layer issue, as you suspected. I don't think there is anything that DirectSoft could be doing to cause it. I've never seen behavior like that, but I'd try the obvious stuff like cables and such first, and then move through the more painful equipment shuffling later.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO