kewakl (Customer) asked a question.

October 19, 2023 at 5:42 PM
DL06 Clear PLC Memory
Now, I cannot establish comms on port 1

I do not have much recent experience with the DL-series CPUs.

I have to update several DL programs. I used my testbench CPU to test port 2 comms (485) with a Solo temperature controller. I could not establish comms with the solo.

I cleared the PLC memory using PLC.Setup->Clear CPU Memory

I selected all memory locations.

 

I am left with a paperweight. I cannot establish comms with PLC on port 1.

Auto detect does not find a connection.

The PC/D2-DSCBL works on other DL05/06 CPUs, just not on my testbench CPU.

Any hope for this CPU?

 

Any advice would be appreciated.

 

Thanks.

  • 7 answers
  • 54.89K views

  • HOST_franji1 (HOST Engineering)

    I'd be real concerned about a twitchy mode switch if this is controlling or interfacing with anything worthwhile.

    Selected as Best

  • ADC TechnologyGroup_05 (AutomationDirect)

    Things to note: Port 1 on the DL06 has

    • FIXED Baud Rate of 9600
    • FIXED Parity of Odd
    • FIXED Station Address of 1.

     

    I am using the following for my test:

    • PLC: D0-06DR-D
    • Date Code: 2338A
    • Firmware version: 4.20
    • Cable: EA-MG-PGM-CBL

     

    Within Device Manage on my PC I see the following:

    Device Manager > Ports (COM & LPT)

    • Prolific USB-to-Serial Comm Port (COM5)
      • Baud: 9600
      • Data bits: 8
      • Parity: Odd
      • Stop bits: 1
      • Flow Control: None

     

    Opening DSLaunch, I observe:

    • DSLaunch > DirectSoft6 version 6.3

     

    Opening Link Wizard, I select the following:

    1. Ports: COM5
    2. PLC Families: DL 0/1/2/4/350 Family
    3. Protocols: K-Sequence
    4. Address: 1
    5. COMPLETE > Name Link

     

    While in DirectSoft6, I execute the following:

    • PLC > Clear PLC Memory > ALL
    • PLC > Disconnect
    • PLC > Connect > SUCCESS

     

    Is there anything in the list that helps? If not, is there anymore information you can provide that might help shed some light on your situation?

    Expand Post

    • kewakl (Customer)

      I will try a bit more tomorrow.

      I do thank you for your input!

  • kewakl (Customer)

    I have some confidence that the problem is related to the RUN/TERM/STOP switch.

    I noticed that the CPU was in RUN mode while the switch was in STOP position.

    I cycled power, tried to connect, saw the message about limited comms access with the switch in TERM position - but the switch WAS in STOP position.

     

    I was able to connect, then was able to reproduce AND RESOLVE the initial problem.

     

    Will try cleaning/replacing the RUN/TERM/STOP switch!

     

    Thank you for your input.

     

    I do not see a character string on the label that I can interpret as a datecode. See image .

     

    20231020_080422 

    Expand Post

  • kewakl (Customer)

    As long as I do not move the RUN/TERM/STOP switch from TERM, I can use the CPU.

    If I move the switch to STOP, the run light stays on for a few seconds, then the CPU faults. Seems like a bad switch.

    Either way, I cannot communicate with the Solo.

     

     

    • HOST_franji1 (HOST Engineering)

      I'd be real concerned about a twitchy mode switch if this is controlling or interfacing with anything worthwhile.

      Selected as Best

      • kewakl (Customer)

        @HOST_franji1 (HOST Engineering)​  Agreed. Thank you 👍

        This is a bench dev/debug unit only.

         

         

 

Did this information resolve your issue?