Duet3 0.6 Issues



  • So i decide to dig out my Duet 3 0.6 today as a new rpi3b+ arrived.

    Well bu**er me this is a complete p.i.a

    I have NOTHING connected to the board other than the Rpi

    Im powering the duet via the "EXT5v" header with the "internal 5v En" jumper REMOVED, the 5V -> SBC & SBC -> 5V* jumpers are installed.

    a copy of the "DuetPi" image has been added to a NEW SD card (actually multiple new SD cards just in case)

    I can SSH in via putty. So I setup wifi once into the system using the raspi-config tool.

    sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

    And inputting my SSID and password this all appears to be successful. I can "connect" via a browser of sorts.

    After the new software release for the duet 3 came out I followed what it said and did the following (multiple times)

    sudo apt-get update
    sudo apt-get upgrade

    That reports the following

    pi@duet3:~ $ sudo apt-get update
    Hit:1 http://archive.raspberrypi.org/debian buster InRelease
    Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
    Hit:3 https://pkg.duet3d.com stable InRelease
    Reading package lists... Done
    pi@duet3:~ $ sudo apt-get upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Calculating upgrade... Done
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

    This is Because it already updated (or so it says)

    I then started the services

    sudo systemctl start duetcontrolserver

    sudo systemctl enable duetcontrolserver

    And

    sudo systemctl start duetwebserver

    sudo systemctl enable duetwebserver

    These all complete with NO listed errors

    I also did the following: sudo apt list duetcontrolserver

    that gave the following output:

    pi@duet3:~ $ sudo apt list duetcontrolserver
    Listing... Done
    duetcontrolserver/stable,now 3.1.0 armhf [installed,automatic]
    N: There are 6 additional versions. Please use the '-a' switch to see them.

    So now I should be able to go to my browser and play with things !!!

    When i do i get the following being displayed in a loop

    <img src="https://i.ibb.co/s9vnf5p/error.png" alt="error" border="0">

    I also did this:

    sudo /opt/dsf/bin/DuetControlServer
    sudo /opt/dsf/bin/DuetWebServer

    to see what it was saying i got a huge amount of errors...


    [info] Starting macro file config.g on channel Trigger
    [warn] Deprecated firmware detected, please update it in order to use DSF
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Restarting transfer because the number of maximum retries has been exceeded
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Restarting transfer because the number of maximum retries has been exceeded
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Restarting transfer because the number of maximum retries has been exceeded
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Restarting transfer because the number of maximum retries has been exceeded
    [warn] Bad header checksum (expected 0x0000, got 0x39db)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Restarting transfer because the number of maximum retries has been exceeded
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Restarting transfer because the number of maximum retries has been exceeded
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xedd9)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
    [warn] Restarting transfer because the number of maximum retries has been exceeded
    [warn] Bad header checksum (expected 0x0000, got 0xec9a)
    [warn] Note: RepRapFirmware didn't receive valid data either (code 0x0001005f)
    [warn] Lost connection to Duet (Timeout while waiting for transfer ready pin)
    [warn] Bad header checksum (expected 0xffff, got 0xb225)


    Also i cant really send any G codes via the console as it just keep looping

    Any one any ideas ?



  • @CaLviNx said in Duet3 0.6 Issues:

    [warn] Bad header checksum (expected 0x0000, got 0xec9a)

    try updating the duet (over usb) with bossac from the Pi?

    @bearer said in Duet3 - firmware update with RPi:

    ref update via usb https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

    (or if you have the Duet connected to the pi via USB just run wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash)

    (edit: the wget line will take care of getting bossac compiled and send the firmware from the reprapfirmwre package that resides in /opt/dsf/sd/sys/ )

    if dcs still not happy ref https://forum.duet3d.com/post/149055 and down? (Haven't finished the writeup of a cleaner case study so its a bit all over the place for a couple of posts).



  • @bearer

    Thanks for the input, I was reading about that, I (mistakenly) expected the new update package codes to complete successfully.

    Evidently it's not foolproof yet.

    I will play with it more tomorrow I had to walk away in disgust at it tonight.



  • @CaLviNx said in Duet3 0.6 Issues:

    Thanks for the input, I was reading about that, I (mistakenly) expected the new update package codes to complete successfully.

    would have been interesting which version it tried to update from; think its just as shortcomming of apt that cannot enforce the incremental updates needed.

    but if there are no further changes to spi protocols or the IAP files then it shouldn't repeat itself.

    in any case from the other reports you may want to give 3.1.0 a pass for a week or two.



  • @bearer

    This 0.6 board is as it arrived from Duet3d. I had never even applied power to it until today.

    As it stands its a paperweight in its current state so I will try a bossa update, I have already had the Rpi install the required bossa files to allow me to flash via the Rpi.

    I will report back after I attempt this tomorrow.

    Thanks again.



  • @bearer

    An update of the firmware via Bossa cured the firmware issue, i now have a stable connection.

    As a side note is there a list anywhere of what the output error codes mean ?

    Now the fun of getting motion begins, thank you for your assistance.



  • I see i qouted the wrong line, I meant to

    [warn] Deprecated firmware detected, please update it in order to use DSF

    however maybe that should be an [error] and not a warning I guess.

    chrishamm did update the errors relating to the spi connection following the other thread i linked to so it will be quite verbose if there is a connectivity issue between the pi and the duet (alhtough a faulty Pi can still make things "interesting")



  • This post is deleted!


  • seems the Pi isn't detecting the Duet connected via USB; it would show up as /dev/ttyACM0 under normal circumstances.

    you could run lsusb to see what devices the Pi does find, but odds are its a usb connectivity issue.



  • @Flex3D adding a new problem to a topic tagged solved is probably not the best approach, nor is adding your own problem to someone elses topic (you don't get notifications unless tagged explicitly, but everyone else does). Best make your own topic.

    edit 👇 yeah, that happens



  • sorry, i was in the wrong topic thread searching for the command wget.


Log in to reply