New DuetWiFiFirmware 1.14

dc42 · 2 Jul 2016, 16:34

I have just released new firmware at https://github.com/dc42/RepRapFirmware/blob/dev/Release/DuetWiFiFirmware-1.14.bin (follow the link and press Raw to download it). The changes in this release since 1.13b are:

Fix for uncommanded stepper motor movement on some systems following a software reset
When multiple motors are due to step, generate simultaneous step pulses for all of them
Added support for multiple drivers for a single axis (M584)
Added support for extended step pulse width when using external drivers (T parameter on M569 command)
Removed XYZE params from M569 (use M584 instead)
Added M913 command (set motor % of normal current) to allow motor current to be temporarily reduced
Added Z probe type 5, which is a normally-closed switch or active-high 3.3V digital signal connected to the IN pin of the Z probe connector
Duet WiFi default Z probe threshold is now 500 (the recommende dvalue for most types of Z probe)
Duet WiFi defaults to using a low end homing switch on the X axis (Ormerod and Huxley, users take note!)

The other firmware files (DuetWiFiServer.bin and DuetWebControl.bin) are unchanged.

curieos · 2 Jul 2016, 23:12

I finally got things hooked up today and I was on 1.13b and updated the config file and it did the crazy dance. This update fixed it, great job DC. Also nice to see the other cool improvements.

jerry426 · 3 Jul 2016, 05:27

David,

Thanks! The crazy dance after software reset is fixed for me too!

Hugues · 4 Jul 2016, 07:20

Also for me ! Great !

Hugues · 4 Jul 2016, 19:52

Hi,

I noticed today a deconexion of few second after pushing the emergency stop. I didn't notice this with the previous version but i can be wrong…

RichRap3D · 7 Jul 2016, 16:07

@cubexupgrade:

Hi,

I noticed today a deconexion of few second after pushing the emergency stop. I didn't notice this with the previous version but i can be wrong…

I had that on the original / previous version. I just assumed that it was reasonable to expect a disconnect after an emergency stop.

RichRap3D · 7 Jul 2016, 16:20

For some reason I didn't have the iap4e.bin file in /sys

So the automatic firmware update failed with the message -

17:10:54Error: In-application programming binary "iap4e.bin" not found
17:10:53M997
Can't rename file or directory /sys/DuetWiFiFirmware-1.14.bin to /sys/DuetWiFiFirmware.bin

So I manually copied the new firmware to the /sys and added the missing iap4e.bin

Then booted and ran the command M997 S0

And it all updated perfectly !

The axis wiggle has gone, I'm testing the rest now.

Cheers,

Rich.

dc42 · 7 Jul 2016, 16:39

@cubexupgrade:

Hi,

I noticed today a deconexion of few second after pushing the emergency stop. I didn't notice this with the previous version but i can be wrong…

This is a known issue, see https://duet3d.com/wiki/Pre-production_hardware_limitations_and_known_firmware_issues. The reason is that DuetWebControl doesn't yet allow for the fact that after a reboot, the networking on the Duet WiFi takes longer to connect than on the Duet, because it has to establish a connection with the access point.

dc42 · 7 Jul 2016, 16:48

@RichRap3D:

For some reason I didn't have the iap4e.bin file in /sys

So the automatic firmware update failed with the message -

17:10:54Error: In-application programming binary "iap4e.bin" not found
17:10:53M997
Can't rename file or directory /sys/DuetWiFiFirmware-1.14.bin to /sys/DuetWiFiFirmware.bin

So I manually copied the new firmware to the /sys and added the missing iap4e.bin

Then booted and ran the command M997 S0

And it all updated perfectly !

The axis wiggle has gone, I'm testing the rest now.

Cheers,

Rich.

Thanks, Rich. I've asked T3P3 to check the contents of the SD card image they use for SD cards sent with the Duet WiFi.