RepRapFirmware 3.3beta1 now available

oliof

I have an early tool board (v0.6), but i did update the bootloader late last year:

M122 B10
Diagnostics for board 10:
Duet TOOL1LC firmware version 3.3beta1 (2021-02-14 16:34:04)
Bootloader ID: SAMC21 bootloader version 2.1 (2020-11-03b2)

User3D

@dc42 is it any different from 3.3beta release available on dropbox? (released 10-15 days ago)

dc42

@User3D said in RepRapFirmware 3.3beta1 now available:

@dc42 is it any different from 3.3beta release available on dropbox? (released 10-15 days ago)

Yes, it's more recent. There is an even more recent one at https://www.dropbox.com/sh/q5uqqkjbmhgvlhq/AACYqG0ynLME9ogoLd1zLB2Xa?dl=0 but it should only be used if you need the new features in it, described at https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3_Beta.md.

oliof

The deprecation of G10 for setting tool temperature is a bit awkward as PrusaSlicer only recently implemented support for using G10 for RepRapFirmware temperature control ...

chrishamm

@oliof We'll undo the deprecation notice in the next beta, please ignore it for now.

stewwy

Having a slight problem when I change from 3.2 to 3.3 beta 1 my z-probe does not work

from my config.g file

M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P8 C"^!zprobe.in" H3 F500 T9000 ; set Z probe type to unfiltered(8) and the dive height + speeds (inductive probe via optocoupler)
G31 P500 X-32 Y-26 Z3.020 ; set Z probe trigger value, offset and trigger height
M557 X5:235 Y25:235 S15 ; define mesh grid

Is my config a problem I checked the notes and could not see any indication of change

The probe is a highly accurate industrial probe,

dc42

@stewwy said in RepRapFirmware 3.3beta1 now available:

Having a slight problem when I change from 3.2 to 3.3 beta 1 my z-probe does not work

from my config.g file

M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P8 C"^!zprobe.in" H3 F500 T9000 ; set Z probe type to unfiltered(8) and the dive height + speeds (inductive probe via optocoupler)
G31 P500 X-32 Y-26 Z3.020 ; set Z probe trigger value, offset and trigger height
M557 X5:235 Y25:235 S15 ; define mesh grid

Is my config a problem I checked the notes and could not see any indication of change

The probe is a highly accurate industrial probe,

Which Duet?

stewwy

Duet wifi 1.03

Should also note that it was constantly triggered (.i.e. the triggered light was on constantly)

dc42

@stewwy said in RepRapFirmware 3.3beta1 now available:

Duet wifi 1.03

Should also note that it was constantly triggered (.i.e. the triggered light was on constantly)

If it's connected via an optocoupler as you said, then there is no way that the Duet can cause the LED on the probe to light up.

stewwy

My Bad I should have been clearer, Just finished a print on 3.2 now flashed 3.3 to check

The web page shows it as being on constantly ( Z-probe showing 1000 constantly) regardless of whether the z probe is triggered or not.

The probe indicator works normally, it turns on 8mm from the bed surface but is not being read properly by the duet. it works on 3.2 but not on 3.3.

stewwy

OK that's interesting,
on 3.3 on first turning on the probe shows 0 on the web page
if I activate the probe ( with a piece of metal) the webpage z-probe display latches to 1000 to get it to zero again I have to restart the duet.

The optocoupler display led acts normally, on when probe activated, off when probe is not activated.

dc42

Post a schematic showing how the optocoupler is connected.

If the optocoupler is leaky then you might need to add an external pullup resistor between IN and +3.3V on the Z Probe connector.