New minor firmware release 1.17d


  • administrators

    This is now on github. The changes since 1.17c are:

    New features:

    • G2 and G3 arc movement commands are implemented.

    • If the controller is reset because of a Hard Fault exception, additional debugging information is stored in the Software Reset Data and displayed by M122

    • Faster step pulse generation - now up to 180kHz simultaneously on 3 motors on the Duet WiFi

    • The M102 command (generated by S3D when using firmware retraction) is ignored instead of provoking a warning message

    • Firmware retraction/unretraction now defaults to 2.0/2.0 instead of 1.0/2.0 mm

    Bug fixes:

    • If tool mixing was used with absolute extruder coordinates, the extrusion amount was calculated incorrectly.

    • The second SD card didn't work on Duet085 and RADDS builds

    • The [deprecated] M206 command takes account of whether the units are mm or inches

    I also fixed a bug with absolute extruder coordinates introduced in temporary versions 1.17c+1 and +2.



  • I think you made a typo. The debugging information is M122.

    Thanks for the great work and really quick response time.


  • administrators

    @dvmourik:

    I think you made a typo. The debugging information is M122.

    Thanks for the great work and really quick response time.

    Thanks, I've corrected it.



  • Awesome, might I suggest archiving some of the older versions so as not to confuse newcomers looking for firmware.

    Jeff



  • Hello,
    I have seen you included a map file in GITHUB now.
    Is that to be uploaded to the duet too?
    Antoine


  • administrators

    The map file does not need to be uploaded. I have preserved it to make diagnosis easier in the event of a Hard Fault report.



  • @(In)Sanity:

    Awesome, might I suggest archiving some of the older versions so as not to confuse newcomers looking for firmware.

    Jeff

    Maybe use the releases feature in GitHub?


  • administrators

    @iDevelo:

    @(In)Sanity:

    Awesome, might I suggest archiving some of the older versions so as not to confuse newcomers looking for firmware.

    Jeff

    Maybe use the releases feature in GitHub?

    I meant to use it for the 1.17 release but I ran out of time to get familiar with it. I'll look at it for 1.18.



  • Really strange problem. I upgraded to 1.17d and now I can't home the printer. I get 'homeall.g not found' errors.
    But, I have a delta, and I can see (and open and edit) the homedelta.g file through the duet-wifi interface.

    I reverted to 1.17.c and rebooted several times but the problem still exists.



  • I think I've managed to reset it to 1.17c using the sam-ba method - I won't have time to reconfigure and test until later this week.


  • administrators

    If it says homeall.g wasn't found then it probably didn't process config.g so it was still in Cartesian mode. Did you try resetting the Duet?



  • Yes, I did, more than once.

    Now I can't connect to it all except if I connect by USB to pronterface, stop/start the wifi and then connect to wifi - but the minute I try to edit the config.g or upload a new one, it disconnects and then I cannot connect again by wifi until I reboot and go through the pronterface procedure again.

    FYI: Pronterface reads 'Macro file homeall.g not found.'

    I'll try pressing the reset button again and see what happens.



  • I should probably post this in the 1.17a thread, but figure this one is probably getting more attention right now…

    I've got a CoreXY machine with a DuetWifi. I was running firmware 1.17 on it and everything was great. I decided to upgrade to 1.17d and things got weird…

    With the same config.g and the same gcode file (a simple 20x20x5 cuboid), 1.17 prints it normally. However, with 1.17d, it suddenly is acting as if the G1 speed (FXXX) is being slowed way down. It moves very VERY slowly, particularly on rounded corners like the skirt around the cube.

    Assuming I must have messed something up somewhere, I decided to go back to 1.17. With the same config.g and the same gcode file, it again printed perfectly fine.

    "Hmmm... that's strange", I thought.

    Wondering if this was specific to 1.17d, I decided to try 1.17a. I got the same odd feedrate behavior. One more time, keeping the same config.g and model gcode file, I went back to 1.17 again, and it started working normally.

    It almost looks like the F parameter on G1 is being changed somehow, but I have no idea how to troubleshoot what is really going on. I looked through the commits for 1.17a and did see a change to how the G1 feedrate is being set in gcodes2.cpp (it is now multiplied by the new "secondsToMinutes" constant), but since I can't seem to find anyone else talking about this issue, I have to believe it is something else.

    Here's the line of code I'm referring to:
    https://github.com/dc42/RepRapFirmware/blob/660e9c7d1ca95df5e31693734c018172f2bae7d8/src/GCodes/GCodes2.cpp#L117

    Thoughts? I'm happy to post config files, videos, etc. if it will help. At this point I'm going to stick with 1.17 until I can figure out what the heck is going on.

    Thanks!

    PS. The model gcode was generated by Cura 2.3.1 if that matters.



  • Okay, think I've fixed it. I removed the SDcard, wiped my /sys dir and copied the /sys_dc42Kossel to /sys

    Now all the commands work again, though it's not configured for my printer.
    I think there must be something wrong with my config.g file, so I'm going to reconfigure the config.g by hand instead of re-copying it.


  • administrators

    I'm glad it's working. You might like to use configtool to generate your new config.sy file.



  • I had an issue after downloading the .bin file was only 43k, I was about to flash it when I noticed, so I downloaded it again and it was 260kb or so which is the right size. Until the webinterface can do an automatic update it's worth checking the file size is right. Any chance of some sort of md5 check or something similar?

    No issues with 1.17d though working perfectly for me.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.