Firmware 1.20 released



  • OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"

    The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.

    I'll report back once I confirm that this is the issue and is sorted.



  • This is confirmed - it was a slicer setting, nothing at all to do with the Duet firmware but a bit strange that the prior version didn't report errors with that format. Anyway, all sorted, thanks.

    @RGN01:

    OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"

    The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.

    I'll report back once I confirm that this is the issue and is sorted.


  • administrators

    @RGN01:

    This is confirmed - it was a slicer setting, nothing at all to do with the Duet firmware but a bit strange that the prior version didn't report errors with that format. Anyway, all sorted, thanks.

    @RGN01:

    OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"

    The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.

    I'll report back once I confirm that this is the issue and is sorted.

    It's because RRF now recognises lower case command letters, and also parses lines of gcode more thoroughly.


  • administrators

    @Captain_sq:

    I'm not sure wich number you're after so I copied the entire response:

    17:34:17.154 : Last reset 00:07:46 ago, cause: power up
    17:34:17.154 : Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 8620 bytes (slot 2)
    17:34:17.154 : Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087e6c
    17:34:17.155 : Stack: 000bfb1f 01c8a8c0 fffffff9 00ffffff 20087ebc 20070fe8 01c8a8c0 20087ebc 000a6221 000a6220 21000000 20087ea0 2007a938 00000000 2007376c 200737a8 20087ebc 0000012c 2007aea8 75207369 01c8a8c0 2007376c 000a5b1d 2001376c
    ...

    Thanks, that should help me to track the problem down.



  • @dc42
    I've gone back to 1.19 while your busy finding the rodent messing around in the Network task in the 0.6 hardware. I kept the newest DWC and found that this also works with 1.19 FW. Nice with some new functionality. I'm not sure wether all the new controls works for real with 1.19 but the extended system edit possibilities are welcome.


  • administrators

    I have it on my list to investigate your report before the 1.20.1 release, however I need to get the prototype laser filament sensors completed and shipped first to avoid additional delay to production of filament sensors.



  • Just tried to upgrade from 1.19 to 1.20. I've uploaded DuetWifiFirmware.bin, but I cannot connect anymore to the printer via wireless. Any idea?



  • Adding some bits. I also tried connecting through USB but the serial device is not recognized by my linux machine (before upgrading used to work).
    EDIT: i have tried the fallback procedure #2 described at https://duet3d.com/wiki/Updating_main_firmware but it still doesn't work.


  • administrators

    The USB interface code did not change between 1.19 and 1.20, so I don't understand why you can't access the Duet over USB any more. Do you have any evidence that the firmware update succeeded in other ways, e.g. because an attached PanelDue is working?



  • I don't own a PanelDue. I don't know how to debug this.


  • administrators

    So as far as you know, the board isn't running at all. See https://duet3d.com/wiki/What_to_do_if_your_Duet_or_Duet_WiFi_won%27t_respond.



  • I just want to report that the github link on this wiki page is broken. https://duet3d.com/wiki/Updating_main_firmware



  • @abitidi:

    I just want to report that the github link on this wiki page is broken. https://duet3d.com/wiki/Updating_main_firmware

    Works for me. Maybe it got fixed between your post and mine?



  • @deckingman:

    Works for me. Maybe it got fixed between your post and mine?

    Weird…I still get a 404 when I try the link.


  • administrators

    I just tried it again (using the link in deckingman's post above) and it works for me.



  • it also works for me with no issues (From the OP's original link)



  • do i have to redo my config file after the update?


  • administrators

    @rar26:

    do i have to redo my config file after the update?

    Read the upgrade notes to see whether you need to make any changes.



  • Both of my Duets stopped printing any G-code file with brackets in it's name after 1.20 update. The files upload fine,it's just that the subsequent M32 command fails with "Gcode file not found". Same files worked fine in 1.19 and before, so it's probably something that was changed with 1.20.

    Edit: Rechecked, it's definitely the firmware - already uploaded file prints on 1.19.2, gives error with 1.20 or later. Web interface version had no effect on the outcome.


  • administrators

    It's because standard GCode uses brackets to enclose comments, therefore anything enclosed in brackets is stripped out. Workaround is to use double quotes around the filename in the GCode command. The beta PanelDue firmware already does this, and DWC will do so soon.


Log in to reply