Duet 3 Not responding to DuetPi... why?



  • My setup in all the latest software... but the commands go unanswered.

    Here is the output from the Duet Control Server Debug file:

    pi@duet3:~ $ sudo /opt/dsf/bin/DuetControlServer -l debug -r
    Duet Control Server v3.1.1
    Written by Christian Hammacher for Duet3D
    Licensed under the terms of the GNU Public License Version 3

    [info] Settings loaded
    [info] Environment initialized
    [info] Connection to Duet established
    [info] IPC socket created at /var/run/dsf/dcs.sock
    [debug] IPC#2: Got new UNIX connection, checking mode...
    [debug] IPC#2: Subscription processor registered in Patch mode
    [debug] IPC#3: Got new UNIX connection, checking mode...
    [debug] IPC#3: Command processor added
    [debug] IPC#4: Got new UNIX connection, checking mode...
    [debug] IPC#3: Received command AddUserSession
    [debug] IPC#4: Subscription processor registered in Patch mode
    [debug] IPC#5: Got new UNIX connection, checking mode...
    [debug] IPC#5: Command processor added
    [debug] Requesting update of key boards, seq 0 -> 0
    [debug] Requesting update of key directories, seq 0 -> 0
    [debug] Requesting update of key fans, seq 0 -> 0
    [debug] Requesting update of key heat, seq 0 -> 9
    [debug] Requesting update of key inputs, seq 0 -> 0
    [debug] Requesting update of key job, seq 0 -> 1
    [debug] Requesting update of key move, seq 0 -> 40
    [debug] Requesting update of key network, seq 0 -> 1
    [debug] Requesting update of key sensors, seq 0 -> 2
    [debug] Requesting update of key spindles, seq 0 -> 0
    [debug] Requesting update of key state, seq 0 -> 1
    [debug] Requesting update of key tools, seq 0 -> 14
    [debug] Requesting update of key volumes, seq 0 -> 6
    [debug] IPC#5: Received command ResolvePath
    [debug] Updated key limits
    [debug] Updated key directories
    [debug] Updated key fans
    [debug] Updated key heat
    [debug] Updated key inputs
    [debug] Updated key job
    [debug] Updated key move
    [debug] Updated key network
    [debug] IPC#6: Got new UNIX connection, checking mode...
    [debug] IPC#6: Command processor added
    [debug] IPC#6: Received command ResolvePath
    [debug] IPC#6: Connection closed
    [debug] Updated key sensors
    [debug] Updated key spindles
    [debug] Updated key state
    [debug] Updated key tools
    [debug] Updated key volumes
    [debug] IPC#7: Got new UNIX connection, checking mode...
    [debug] IPC#7: Command processor added
    [debug] IPC#7: Received command ResolvePath
    [debug] IPC#7: Connection closed
    m[debug] IPC#8: Got new UNIX connection, checking mode...
    [debug] IPC#8: Command processor added
    [debug] IPC#8: Received command SimpleCode
    [debug] Waiting for execution of M115
    [debug] Processing M115
    [debug] Waiting for finish of M115
    [debug] HTTP: Sent M115, remaining space 1512, needed 24
    It never gets a response that I can tell... all commands get the same result.
    HELP!


  • administrators

    What issue are you seeing, as it looks like DCS can connect to the Duet 3:

    [info] Connection to Duet established
    

    Is DuetWebserver running?



  • Absolutely.
    It looks nice... but does nothing.



  • @beachtec said in Duet 3 Not responding to DuetPi... why?:

    My setup in all the latest software..

    can you connect to the Duet using just the usb console and check both what it identifies as and try sending M115?

    how did you update the Duet to 3.1.1, and from which version?



  • @bearer
    M115 from the web interface (or terminal) hangs.
    M115 from the USB returns the current firmware (3.1.1 I believe)



  • It's a new board, BTW.


  • administrators

    @bearer said in Duet 3 Not responding to DuetPi... why?:

    how did you update the Duet to 3.1.1, and from which version?

    @beachtec this is a good question, It might be incompatibility between the firmware on the Duet and the version of DCS on the Pi.

    Can you post the M115 response you see over USB pls



  • You are right; it is definitely related to something in the Pi.
    I have a few of them... 2's 3's and 4's. I had been using a Pi 3 B+ as the SBC, mainly because it appears to have been used in it's development. So yesterday, just for grins, I pulled the Pi 3 and install a Pi 4 (4GB) in its place.

    It works perfectly.


Log in to reply