Firmware 2.02 released!

[mveinot]

@wilriker Darnit! I forgot all about having that in there. Yep, that did it. Thank you so much.

[dc42]

@mveinot, you can avoid the move to X5 and G92 X0 if you change the M208 lower X limit from 0 to -5.

[mveinot]

@dc42 Thanks, I've made that change as well. Seems to work!

[Hornetrider]

Hi Guys,

I hope you can help me out.
I have updated to latest FW2.02 and DWC2.0.0-RC3 and at first it looked great.
But since the update I can't home my axes, any of it. I tried to modify the home files, f.e. homex.g with very slow movement but that didn't help.

I allways receive the error G0/G1:insufficient axes homed

I checked the switch states again and they work fine.

It seems like S1 is ignored...

Here the config.g:
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M550 P"RicDuet" ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S0 ; Drive 3 goes backwards
M350 X32 Y32 Z32 E32 I0 ; Configure microstepping without interpolation
M92 X160.00 Y160.00 Z8000.00 E210.02 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X10020.00 Y10020.00 Z198.00 E10020.00 ; Set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z100.00 E3000.00 ; Set accelerations (mm/s^2)
M906 X1200.00 Y1200.00 Z1200.00 E1200.00 I0 ; Set motor currents (mA) and motor idle factor in per cent
M84 S0 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X210 Y297 Z220 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 S0 ; Set active low and disabled endstops

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M558 P5 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z0.750 ; Set Z probe trigger value, offset and trigger height
M557 X5:170 Y5:275 S20 ; Define mesh grid

; Heaters
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C

; Fans
M106 P0 S1 I0 F500 H1 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S0 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Automatic saving after power loss is not enabled

; Custom settings are not configured

; Miscellaneous
T0 ; Select first tool

---

and f.e. homex.g

; generated by RepRapFirmware Configuration Tool v2 on Mon Dec 31 2018 02:05:14 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
;G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-215 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X6 F6000 ; go back a few mm
G1 S1 X-215 F100 ; move slowly to X axis endstop once more (second pass)
;G1 Z-5 F6000 S2 ; lower Z again
G90 ; absolute positioning

Just unmarked the Z axis movents not to be anoyed...

Any ideas?

BR
Ric

[Phaedrux]

@hornetrider Can you post your other homing files? Homex looks correct.

[Hornetrider]

@Phaedrux

thanks for the quick reply.
The homeall.g looks similar to the homex.g as it was generated with the RepRapFirmware Config Tool.
It uses the same controls just for all axes and including the G30 for the Z Probing.

The strange thing is, before the FW update (done 02.01.19) the homing worked fine...

Also
G1 S1 X-215 F1800
G1 X6 F6000 ; go back a few mm
work fine as the X-Axe goes back the distance after hitting the first time the switch....

But at the end of the script the error message appears.

[Hornetrider]

@phaedrux

pls see bellow

---

G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-215 Y-302 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-215 Y-302 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X15 Y15 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

---

Tried also to replace the Sx by Hx and it didn't help other than generating an error message less precise then the G0/G1

This is kind of anyoing.

BTW
in the SYS Folder, what files should be there.
After Update I have far more there...

[wilriker]

@hornetrider Your homeall.g looks OK to me. Though I don't use G30 in my setup so not sure if there is anything needed to adjust.

Regarding the amount of files in /sys: the new simplified update with just on ZIP file contains all the various update files for Duet Wifi, Ethernet and Maestro. This will add some files to your /sys folder that you don't need but they don't do any harm either.

[Hornetrider]

@wilriker

thx.
Did you have a Cartesian Style Printer?
Have you had to change any commands after update?

I am going crazy...and most likely it is something tiny...like allways...arghhh

[wilriker]

@hornetrider Yes, I do have a Cartesian printer and since I follow along all Beta/RC versions and usually immediately adapt to all introduced changes I did not have to adjust anything special here.

Here's my homeall.g for comparison:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Sat Apr 28 2018 20:07:26 GMT+0200 (CEST)
G91                     ; relative positioning
G1 H2 Z2 F3000          ; lift Z relative to current position

; X and Y
G1 H1 X-300 Y-300 F3600 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F3000          ; go back a few mm
G1 H1 X-300 Y-300 F360  ; move slowly to X and Y axis endstops once more (second pass)

; Z
G1 H1 Z-300 F900        ; move quickly to Z axis endstop and stop there (first pass)
G1 Z2 F3000             ; go back a few mm
G1 H1 Z-300 F180        ; move slowly to Z axis endstop once more (second pass)

G90                     ; absolute positioning

[Hornetrider]

@wilriker
HI Manuel
just used your setup and it didn't work....

It seems to stop right after x/y hit the first time the limit switch...

Ric

[dc42]

I think the problem may be the I0 in M906 and the S0 in M84. My guess is that this sets the motor currents to zero immediately after the homing move stops, and that is flagging the axes as not homed again.

[Hornetrider]

@dc42
You are a genius!
After setting I0 in M906 to I0.1 it works fine again!

Thank you very much!

[BPisLife]

@dc42 thanks for incorporating my feedback on the latest PanelDue firmware with both the Stop button taking priority and actually stopping the printer immediately as well as the 2mm/s federate on the extruder.

Really liking the notification system on the latest firmware! Nice work to everyone involved.

[joestefano]

David, I am having trouble with Z height reliability. I am using your Z IR probe, I have a slightly tinted glass heat bed approx. 6mm thick. I have placed a piece of black paper under the glass at my home location. I test it by homing the printer then entering G1 Z0 and most of the time the Z gap is tight against the glass (to tight to print first layer). I repeat the procedure with G92 Z0 after adjusting the Z gap then runG30 S-1 and enter value in M558. Is there anything I can do to improve this.

I am running 2.02

; Endstops
M574 X1 S0 ; Define active low and unused microswitches
M574 Y2 S0
;M574 Z1 S1
M564 H0
M558 P1 X0 Y0 Z1.297 H0 F500 T3000 ; Set Z probe type to modulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 Z 1.1 ; Set Z probe trigger value, offset and trigger height

[dc42]

G1 Z0 should place the nozzle just touching the glass if you have set the trigger height correctly in the G31 command. The printer will command the nozzle to the first layer height before it prints the first layer, for example it will send G1 Z0.2 if your first layer height is 0.2mm.

If you are using a config-override.g file, check that the trigger height isn't being overwritten by another G31 command in that file.

[leif]

Installed 2.02 today. Download and install of .zip was insanely easy. No issues here on a kossel mini with smarteffector. Homing et.al. worked as expected.

Thanks again for your hard work @dc42

[Catalin_RO]

Just upgraded my WorkBee to firmware 2.02 as I have to do some parts. There was no change required in the configuration files.

But, as I had to machine a cylindrical shape, I can clearly see a possible problem with the G2/G3 segment length correlated to the arc radius. The piece was milled at very low speed, so the cutting tool could not make such regular marks.

The whole GCode is made up of G2/G3 for the cutting. The circle radius varies between 15mm and 18mm and the facets are perfectly aligned between the two diameters.

Is there a way to control the relative segment length or chose between new and old behavior?

[dc42]

Perhaps I should change the firmware to reduce the segment length when the commanded speed is low. What would be a typical milling speed?

[Catalin_RO]

@dc42 It depends a lot on material and cutting tool. Standard WorkBee can't exceed 2500mm/min for screw driven, but it can be as fast as 10000mm/min for belt driven one. Also, CNC machining can have two passes (and most of the time it does so!) - roughing, when the bulk of the material is removed and quality is not important as there is some left over material for the second pass, and finishing, when just a fine layer of material is removed and the machining parameters are focused toward surface quality. The picture shows a piece half finished, with the remaining finishing to be done with a different setup.

P.S. Maybe adding some parameter to upper limit the segments length?