Multiple Errors Duet3



  • I bought Duet3 board for my new 380x660mm Delta printer, and I can't configure the firmware in any way. I bought Pi4, downloaded DuetPi Lite (I try DuetPi also), get updates (sudo apt-get update
    sudo apt-get upgrade). Using https://configtool.reprapfirmware.org/Start I configured Delta printer settings. After loading the system files and reloading board, web interface looks just as empty (in the attachment).
    I see 10 errors in the Console :
    Error: Bad command: Q0 @"Custom settings are not defined"
    Error: Bad command: Q0 @"Tools"
    Error: Fan number 1 not found
    Error: Fan number 0 not found
    Error: Response timeout: CAN addr 1, req type 6027, RID=10 ...

    And a warning. Warning: Incompatible firmware, please upgrade as soon as possible

    Please help me find out what the problem is and how I can fix it.
    I've already read all the manuals 5 times but I can't figure out what the problem is



  • get updates (sudo apt-get update

    And a warning. Warning: Incompatible firmware, please upgrade as soon as possible

    you probably need to upgrade to RRF 3.0 first. I'd try in ssh

    echo M115 | /opt/dsf/bin/CodeConsole
    cd /opt/dsf/sd/sys
    wget -q https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet3iap_spi_MB6HC.bin
    wget -q https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet3Firmware_MB6HC.bin
    echo M997 | /opt/dsf/bin/CodeConsole
    echo M115 | /opt/dsf/bin/CodeConsole
    wget -q https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet3Firmware_MB6HC.bin
    echo M997 | /opt/dsf/bin/CodeConsole
    echo M115 | /opt/dsf/bin/CodeConsole
    
    

    edit: hmm, that might not work once you've updated with apt. two options, re-image your sd card with DuetPi (lite if you like) and run the above commands before updating apt.

    or try https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware - skip past apt and go with the windows or pi solution using usb.

    (for the pi, i've wrapped it up in a script, so all you need to do is connect the micro usb cable from the duet to the pi and run wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash <- assumes the updated firmware is in /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin as a result of upgrading with apt and loosing the connection to the duet)


  • Moderator

    It may be easier to get up and running with the Duet 3 in standalone mode to ensure the firmware is updated and ready to go before adding the Pi4 into the mix.



  • I re-image sd card with DuetPi and see the same empty DWC screen. When I try to connect to Pi4 via ssh in Terminal (I use Mac) I see WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
    IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
    Someone could be eavesdropping on you right now (man-in-the-middle attack)!
    It is also possible that a host key has just been changed.
    The fingerprint for the ECDSA key sent by the remote host is
    SHA256:vB0nvZExndjvDSVpb545HYrolT0a1g/iInydOf8zvQ0.
    Please contact your system administrator.
    Add correct host key in /Users/dmitrykomkov/.ssh/known_hosts to get rid of this message.
    Offending ECDSA key in /Users/dmitrykomkov/.ssh/known_hosts:3
    ECDSA host key for 192.168.1.5 has changed and you have requested strict checking.
    Host key verification failed.

    Is it related to the firmware or is it a computer problem?



  • I also tried BOSSA, but it's freeze at 44-45%



  • @dk said in Multiple Errors Duet3:

    Is it related to the firmware or is it a computer problem?

    it happened because you re-imaged the sd-card, which generates new host keys on the pi - and the client keeps track of the hostname and fingerprint of the past keys to detect changes (or attacks). nothing to worry about as you did (unknowingly) change they keys on the pi

    @dk said in Multiple Errors Duet3:

    I also tried BOSSA, but it's freeze at 44-45%

    from the pi or the computer? try the other one and try a different usb cable, seems to help for most cases.


    did you make a not of what happened when trying to run M997 after downloading the 3.0 files?


  • Moderator



  • @bearer Bossa finally works! third cable!
    Thank you very much for your help!
    Now I trying to figure out how to get BL-touch on 1LC Tool board get to work. It can't be done through https://configurator.reprapfirmware.org isn't it?



  • @dk said in Multiple Errors Duet3:

    BL-touch on 1LC Tool board

    https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations

    afaik thats not going to work until 3.3 is released, unless the toolboard is also controlling the z motor


  • Moderator

    @bearer BLTouch on toolboard works fine for Z homing and bed levelling. Some people are having issues with intermittent comms or power supply, but we’re having difficulty replicating that to troubleshoot.

    Ian


  • Moderator

    @dk said in Multiple Errors Duet3:

    Now I trying to figure out how to get BL-touch on 1LC Tool board get to work. It can't be done through https://configurator.reprapfirmware.org isn't it?

    For physical connections, see https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Connecting_a_BL_Touch

    The configuration tool can produce the code, but doesn't set the CAN address, and I've noticed an error in the input pin drop down. So you'll need to edit config.g afterwards. Setting the following:
    600e1828-8bff-41e9-8722-bbf3cc8bf061-image.png

    and

    684b65cc-4d2f-4270-9492-0ae87ae4c891-image.png

    Produces:

    ; Z-Probe
    M950 S0 C"1.io0.out"                           ; create servo pin 0 for BLTouch
    M558 P9 C"^1.temp1" H5 F120 T6000              ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X0 Y0 Z2.5                            ; set Z probe trigger value, offset and trigger height
    

    Assuming CAN address is 121, change this to:

    ; Z-Probe
    M950 S0 C"121.io0.out"                           ; create servo pin 0 for BLTouch
    M558 P9 C"^121.io0.in" H5 F120 T6000              ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X0 Y0 Z2.5                            ; set Z probe trigger value, offset and trigger height
    

    Not sure if you actually need the pull-up resistor ^, but shouldn't hurt. Test and report back!

    Ian


  • administrators

    @droftarts said in Multiple Errors Duet3:

    Not sure if you actually need the pull-up resistor ^, but shouldn't hurt. Test and report back!

    All Duet 3 ioX.in ports have permanent pullup resistors, on the main board and on expansion boards. So you never need to use ^ in the name. We recommend that you do not, because enabling it reduces the noise margin..



  • @droftarts Unfortunately, this didn't help. I tried with and without ^. BL-touch lights up in red but does not extend.
    Can I find somewhere configuration files for any real working Delta printer on Duet3 with Tool board? This would help me a lot in setting up my printer.


Log in to reply