New firmware 1.21RC3 available

c310

Strange, does WiFi 1.21RC1 work for you?

yes, i managed to put it in.

Current combination has full range of Rcx

Firmware Version: 1.21RC3 (2018-02-28 build 4)
WiFi Server Version: 1.21RC1
Web Interface Version: 1.21-RC4

GrodanB

Why does my home all not work anymore?

[[GCode]]
; Lift Z relative to current position
T0
G91
G1 Z4 F6000
G1 X-350 Y-240 F3000 S1  ; move up to 240mm in the -X and -Y directions until the homing switches are triggered
G1 X6 Y6 F600      ; move slowly 6mm in +X and +Y directions
G1 X-10 Y-10 S1    ; move up to 10mm in the -X and -Y directions until the homing switches are triggered
G90

; #############################################

; Go to Center of the bed probe point and home the Z axis
G1 X150 Y100 F3000
G30
;dock
T0
M117 Docking Printhead.
G1 X70 Y200 F3000
G1 X70 Y235 F3000

Get this output:
10:40:33 G28 Error: G0/G1: insufficient axes homed

Worked fine when using RC2

Also tried to print something that worked fine and got this:
10:34:47 M25 Resume-after-power-fail state saved Printing paused
10:34:42 Error: G0/G1: insufficient axes homed
10:34:41 M32 "Monopoly_Replacement_Part_Wheelbarrow.gcode"File Monopoly_Replacement_Part_Wheelbarrow.gcode selected for printing

Why does it claim that it tries to restart after power-failed? I just tried to start my print as I always has done… It is not impossible that I have bad start-up scripts... (my home seem to be suddenly wrong) But I do not understand this from reading the change log...

[[GCode]]
;BigBox Printer Start Script Begin

;extruder offset - refer to the wiki | http://wiki.e3d-online.com/wiki/Printer_Commissioning#Dual_Nozzle_Alignment
M117 Print Starting

G91 ; Relative coordinate
G1 Z5 F400 //Lower Bed 5mm//
G90 ; Absolute coordinate

;Homing
M117 Homing.
G28 ; home all axes
G29 S1 //This command loads the stored IR bed levels//
G30 P0 X25 y100 z-99999
G30 P1 X275 y100 z-99999 S2
G30 P0 X25 y100 z-99999
G30 P1 X275 y100 z-99999 S2
G30 P0 X25 y100 z-99999
G30 P1 X275 y100 z-99999 S2
G30 P0 X25 y100 z-99999
G30 P1 X275 y100 z-99999 S2

;dock
T0
G1 X70 Y200 F3000
G1 X70 Y235 F3000

M117 Print Starting.
;BigBox Printer Start Script End

I find it strange that I cannot move my Z axis away from the bed to enable the probe to be at a "safe" detection distance to avoid the hot-end to crash into the bed because the probe is to close and already passed the trig threshold. (tried that one MANY times…)

T3P3Tony

GrodanB, please see David's release notes:
https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md

You will see you need to either home Z first, or specify the lift with S2 to override the axis homing protection.

GrodanB

OK, amazing that 3-4 readings and still miss this… I assumed that was the probable root cause...

Fixing immediately! Thanks

So I practice the method that it is better to ask and be an idiot for five minutes then being it for the rest of you life
Edit: Re-reading it is so obvious... First time I just assumed that not allowing movement to an not homed axis was OK and did not register the homing issue...
The resume weirdness also disappeared when adding the S2 to the G1 Z-axis movement. Strange...

New issue?: Why can I not upload files unless there is at least one XXX.Gcode in the gcode directory? Via the up-load button.

Did a emergency stop (reset) and the button was available again.

lolorc

ttyACM3 16°> M115
SENDING:M115
FRMWR_NAME: epapirwae orDut WiF ad ue Ethene FRMAR_VERSON 121C2ELRNIS:Dut ii .0or101FIMWRE_AT: 01-0-1 bil 2
o T170 0. B16.7 /00

I've tried to upload DuetWifiFirmware.bin several time from webui.
M115 was still reporting 1.21RC2
I've copied DuetWifiFirmware.bin to /sys and M997 S0

something borken again.

SputnikOC3d

@kraegar:

The bltouch / multi-tap fix works great.

Probe configuration:
M558 P9 X0 Y0 Z1 H5 F50 T6000 A5 S0.02

3 point leveling result:
Leadscrew adjustments made: 0.004 -0.008 -0.000, points used 3, deviation before 0.005

is there a link to guide or tute or dozuki page outlining the implementation of this newly supported feature? My BL Touch bed leveling has been giving me fits and I think its due to inconsistent probing results - this would be rather nice

kraegar

@SputnikOC3d:

@kraegar:

The bltouch / multi-tap fix works great.

Probe configuration:
M558 P9 X0 Y0 Z1 H5 F50 T6000 A5 S0.02

3 point leveling result:
Leadscrew adjustments made: 0.004 -0.008 -0.000, points used 3, deviation before 0.005

is there a link to guide or tute or dozuki page outlining the implementation of this newly supported feature? My BL Touch bed leveling has been giving me fits and I think its due to inconsistent probing results - this would be rather nice

If you're referring to the multi-tap, the relevent bits there are the S0.02 (max deviation between two sequential taps) and A5 (allow up to 5 attempts). I never see it tap more than twice, though.

The new probe type, P9, is to specify it's a BLTouch specifically, and so you no longer need to manually deploy the probe, it does it automatically.

lolorc

@lolorc:

ttyACM3 16°> M115
SENDING:M115
FRMWR_NAME: epapirwae orDut WiF ad ue Ethene FRMAR_VERSON 121C2ELRNIS:Dut ii .0or101FIMWRE_AT: 01-0-1 bil 2
o T170 0. B16.7 /00

this was an serial issue I was not able to reproduce hopefully.

However I can't manage to upgrade to 1.21rc3, Duet2CombinedFirmware.bin been renamed to DuetWiFiFirmware.bin, uploaded through webui, copied to sdcard (+M997) M115 still reports 1.21rc2.

SputnikOC3d

@kraegar:

@SputnikOC3d:

@kraegar:

The bltouch / multi-tap fix works great.

Probe configuration:
M558 P9 X0 Y0 Z1 H5 F50 T6000 A5 S0.02

3 point leveling result:
Leadscrew adjustments made: 0.004 -0.008 -0.000, points used 3, deviation before 0.005

is there a link to guide or tute or dozuki page outlining the implementation of this newly supported feature? My BL Touch bed leveling has been giving me fits and I think its due to inconsistent probing results - this would be rather nice

If you're referring to the multi-tap, the relevent bits there are the S0.02 (max deviation between two sequential taps) and A5 (allow up to 5 attempts). I never see it tap more than twice, though.

The new probe type, P9, is to specify it's a BLTouch specifically, and so you no longer need to manually deploy the probe, it does it automatically.

Thanks very much for this … appreciated - but there must be some documentation for this somewhere right? How did you learn of these settings / features?

I will try and implement. Im also desperateyl trying to find some data on the sensititivty setting for the BL Touch - docs just said to use a low setting - it was default at 500 - I modded that to 25 - wondering if that is impacting my results ... I cant find jack in docs on that issue

okercho

@SputnikOC3d:

Thanks very much for this … appreciated - but there must be some documentation for this somewhere right? How did you learn of these settings / features?

You can check in the Gcode documentation
https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_Set_Z_probe_type

Regards

T3P3Tony

Also see:

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

I have linked a helpful tutorial for BL Touch by BeTrue3d.dk

SputnikOC3d

@T3P3Tony:

Also see:

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

I have linked a helpful tutorial for BL Touch by BeTrue3d.dk

Thank you …

Now i get ... Error: M997: Firmware binary "DuetWiFiFirmware.bin" is not valid for this electronics ????

SputnikOC3d

no blue light on wifi module … wth ... So doing some reading it stated on some docs that sometimes you need to make sure your wifiserver .bin and your firmware .bin are upload before executing the firmware update .... because Im getting M997 error - as stated above ... After upload of the new 1.21RC3 wifi server bin ... it asked if I wanted to upgrade or whatev's it calls it I hit YES.

It went thru some activity - showed me a green progress bar ... then now i get nothing no connection via wifi - no blue lights next to the wifi module on the board ... So now I have 1.20 firmware still and 1.21rc3 wifi server and no wifi connectivity - now what ?

release notes said it didnt matter if wifi bin or firmware bin done first ...

T3P3Tony

The blue light on the wifi module comes on only when uploading the wifi server firmware.

It looks like that is successful as you say the wifi server firmware version is 1.21rc3? Sounds like an issue with the main firmware upload. Try downloading the DuetCombinedFirmware.bin again (make sure you download the raw .bin file) then rename it to DuetWifiFirmware.bin then upgrade. You will need to comply it onto the SD card by putting it into your PC.

SputnikOC3d

@T3P3Tony:

The blue light on the wifi module comes on only when uploading the wifi server firmware.

It looks like that is successful as you say the wifi server firmware version is 1.21rc3? Sounds like an issue with the main firmware upload. Try downloading the DuetCombinedFirmware.bin again (make sure you download the raw .bin file) then rename it to DuetWifiFirmware.bin then upgrade. You will need to comply it onto the SD card by putting it into your PC.

TY … yes I agree. I did make sure and actually downloaded the main fw file again and renamed it as per instructions - before moving over the wifi server .bin file via the gui. But I will do as indicated - i have to go get a micro sd card adapter/reader for this pc - never use them in real life ... but now do.

Will report back ... Im following

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_How_to_recover_if_the_main_firmware_and_WiFi_firmware_versions_get_out_of_step_on_your_Duet_WiFi

please advise if there is a better guide to follow for my situation than the one linked to above.

TY again …

T3P3Tony

That guide is the right one for this situation

SputnikOC3d

Any ideas why I got the M997 error at the onset ? Did i need to be running a more recent firmware version than 1.20 ?

dc42

@SputnikOC3d:

@T3P3Tony:

Also see:

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

I have linked a helpful tutorial for BL Touch by BeTrue3d.dk

Thank you …

Now i get ... Error: M997: Firmware binary "DuetWiFiFirmware.bin" is not valid for this electronics ????

That normally means you downloaded the html page describing the firmware file, instead of the firmware file.

SputnikOC3d

@dc42:

@SputnikOC3d:

@T3P3Tony:

Also see:

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

I have linked a helpful tutorial for BL Touch by BeTrue3d.dk

Thank you …

Now i get ... Error: M997: Firmware binary "DuetWiFiFirmware.bin" is not valid for this electronics ????

That normally means you downloaded the html page describing the firmware file, instead of the firmware file.

well valuable lesson learned there … compare bytes and drill down into the github into the page where the actual files reside ... so ive followed the guide- run out and got a micro sd card reader - and moved the files and commented out the line in config .g ...

Issuing M997 S0 and M997 S1 ...

M115 gives me ...

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 1.21RC3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-02-28 build 4<lf>ok <lf>Im really not clear by looking at this whether the Wifi Server firmware part is the right version?

M122 gives me :

=== Diagnostics ===
<lf>Used output buffers: 1 of 32 (9 max)
<lf>=== Platform ===
<lf>RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21RC3 running on Duet WiFi 1.02 or later
<lf>Board ID: 08DGM-9568A-F23SD-6JTDD-3SJ6R-9ARZH
<lf>Static ram used: 16144<lf>Dynamic ram used: 100384
<lf>Recycled dynamic ram: 2256<lf>Stack ram used: 3568 current, 4528 maximum<
LF>Never used ram: 7760<lf>Last reset 00:14:41 ago, cause: power up
<lf>Last software reset at 2018-02-24 09:30, reason: User, spinning module GCodes, available RAM 11896 bytes (slot 3)
<lf>Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
<lf>Error status: 0<lf>Free file entries: 10<lf>SD card 0 detected, interface speed: 20.0MBytes/sec<lf>SD card longest block write time: 0.0ms<lf>MCU temperature: min 37.6, current 37.8, max 38.1<lf>Supply voltage: min 0.5, current 0.6, max 0.6, under voltage events: 0, over voltage events: 0<lf>Driver 0: ok, SG min/max not available<lf>Driver 1: ok, SG min/max not available<lf>Driver 2: ok, SG min/max not avai<warning: maximal="" number="" of="" bytes="" per="" line="" exceeded!="" check="" the="" end-of-line="" settings="" or="" increase="" limit="" in="" advanced="" terminal="" settings.=""></warning:></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf>

SputnikOC3d

M552 S0
M587 S"SSID" P"PWD"
M552 S1

Viola …

new firmware and wifi server and new DWC all synced up ... sorry for the trouble guys - im back and with just a bit more gcode and duet firmware savvy - 1 Bite at a time ...