Firmware 2.02 released!

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. 0_1547918741025_Z probe.jpg

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?

dc42

What would you consider a reasonable upper limit on segment length? 1mm?

Catalin_RO

@dc42 It depends on what needs to be machined. In the photo the facets are about 1.2mm wide. So 1mm would not be significantly different. Honestly I would consider something like 0.1mm a lot more suitable, but that is because the WorkBee accuracy is around that. If a CNC has much better mechanics, even 0.1mm might be too much. That is why the segment length upper limit should be configurable!

Right now I have an Al piece with corners machined with 3mm radius. I can clearly see the facets. A picture will come soon... once the machining ends and I can clean the Al part for a photo!

Catalin_RO

As promised
, a 3mm radius corner, with two facets properly visible.

dc42

Rather than making the upper limit configurable, I think it better to make it speed-dependent. The reason I made it radius-dependent in the first place is that users complained that in 3D printer mode, the maximum speed achievable for G2/G3 commands was too low. But speeds are much lower in CNC machines anyway, so I could leave the segment length at 0.1mm unless the requested speed requires a longer segment and the radius allows that without losing much accuracy.

Catalin_RO

@dc42 Sounds better! But it is important to know the threshold speed value. While roughing apparently is done at higher speed than finishing, it depends on many factors and it may be actually done at lower speeds (bulk material removal requires a lot more torque than just shaving off a thin layer). 4000mm/s is a reasonable upper limit for 0.1mm/s, if possible. The WorkBee that I have is capable of 2500mm/s, and it's not that rare that I need to set feed rates close to the top limit. If using larger cutters I would have to go faster, just that I know that the machine is not rigid enough for the associated torques and thus I don't go beyond a certain diameter.

DIY CNCs usually rely on lowest cost motion solutions - that is stepper. Considering a 300rpm limit for the stepper while still having meaningful torque, combined with the usual 1610 lead screw (16mm thick screw, 10mm lead), that gives 3000mm/min feed rate. That is why I consider 4000mm/min a reasonable limit for CNCs that use steppers rated for up to 3A. CNCs that use belts are imprecise at higher speeds because of the belts flexibility and the ones that use screws and can go faster have much larger steppers, impossible to use with the Duet 2.

Or make different rules depending on the controller mode if the threshold speed is too low - no more than or fixed at 0.1mm for CNC (whatever was before) and new algorithm for 3D printing.

Vlad

@dc42 have you stopped supporting DUETWIFI or something? I can't find any new firmware on that board, all firmware switched to DUET2WIFI, which is basically the same board, but the problem is that firmware won't install on DUETWIFI. Needless to say, that there is of course zero instructions about that.

Phaedrux

@vlad the duetwifi and duwt2wifi are one in the same.

Instructions for updating are the same.

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

Vlad

@phaedrux Thanks. Only if it was mentioned anywhere, as the firmware has different name and won't install, unless you rename it, which I did.

dc42

@vlad said in Firmware 2.02 released!:

@phaedrux Thanks. Only if it was mentioned anywhere, as the firmware has different name and won't install, unless you rename it, which I did.

I guess you didn't read https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Upgrading_a_Duet_2_WiFi_or_Ethernet_to_firmware_1_21_or_later_from_1_20_or_earlier.