adccommunitymod (AutomationDirect) asked a question.

Remedied a "No Response from PLC" Error.

Created Date: February 27,2006

Created By: joydivision

**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****

Hey all, Had a little glitch yesterday while trying to program our DL06 through Com1 using a laptop with DirectSoft32. We tested the cable and it was ok. The PLC Com 1 was ok because it was able to communicate with the HMI in run mode. Still the error showed up. We narrowed down the problem to the serial com port on the laptop instead. So what we did was to remove the serial com port hardware profile from System/Device Manager and reinstall it. Now, everything works as before. Strange if you ask me but I hope this trick can help someone out there. Thanks for reading.


  • adccommunitymod (AutomationDirect)

    Created Date: February 27,2006

    Created by: Tech Guy

    There are several applications that "hijack " the com port and refuse to "share ". PDA device software, digital camera software, and a few industrial programming packages are notorius for this. Some of these applications hijack the port at a very low level and the only way to "remove " them is to do what you did, uninstall and reinstall. If you are using a "Pro " version of a Windows OS, you can sometimes find these applications in the "Services " listing (Start -> Programs -> Administrative tools -> Services or Control Panel -> Administrative tools -> Services) and disable them.

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: February 27,2006

    Created by: joydivision

    Hey all,

    Had a little glitch yesterday while trying to program our DL06 through Com1 using a laptop with DirectSoft32.

    We tested the cable and it was ok. The PLC Com 1 was ok because it was able to communicate with the HMI in run mode. Still the error showed up. We narrowed down the problem to the serial com port on the laptop instead. So what we did was to remove the serial com port hardware profile from System/Device Manager and reinstall it.

    Now, everything works as before. Strange if you ask me but I hope this trick can help someone out there.

    Thanks for reading.

    Expand Post