RepRapFirmware 3.0beta 11 released

A Former User

config

M558 P9 C"zprobe.in" H5 F120 T3000 A2 ; FW v3 BLTouch connected to Z probe IN pin
M950 S0 C"exp.heater3"                ; FW v3 create servo/gpio 
G31 P500 X35 Y0 Z2.2                  ; set Z probe trigger value, offset and trigger height

I removed the probe and tried to short gnd and zprobe.in (duet2eth board) and that did not detect it neither

maybe "zprobe.in" was renamed?

G31 ; nothing connected to zprobe.in
Current reading 250, threshold 500, trigger height 2.20, offsets X35.0 Y0.0

G31 ; me holding a screwdriver shorting zprobe.in to gnd
Current reading 0, threshold 500, trigger height 2.20, offsets X35.0 Y0.0

this does not look ok, should I invert something or .. afaik BLtouch is open drain pulling output to gnd on trigger so my screwdriver should of triggered it ?!

dc42

@JuKu said in RepRapFirmware 3.0beta 11 released:

@dc42 Is there a release notes document, what is new or changed?

No, because this is a beta and so much has been changed. You can look through the github commit logs in branch v3-dev if you want all the details. But the main improvements are:

Reduced RAM usage on Duet WiFi and Duet Maestro
Ported the fixes that are in 2.04RC4 (which are documented in the usual whatsnew file)
Endstop switches attached to expansion boards are working in some configurations
RPM readings from 4-pin fans connected to expansion boards are now available
Added support for G38 (thanks Manuel)
Extended M122 report from expansion boards
Added DotStar LED support on Duet 3 main board
Include spindle speeds in restore points
Expansion board firmware can be update from an attached SBC
Include laser power in the status information returned to DWC
Added mDNS support to the Duet Ethernet and Duet Maestro (thanks chrishamm)
Added self-check of firmware CRC at startup

dc42

@smece said in RepRapFirmware 3.0beta 11 released:

Was I dreaming or there was a way to upload web files to the sd cards too? Weird, had to remove the SD cards to put new DWC there

You were not dreaming, you just upload the Duet Web Control .zip file through the Upload System Files button.

dc42

@smece said in RepRapFirmware 3.0beta 11 released:

G31 ; nothing connected to zprobe.in
Current reading 250, threshold 500, trigger height 2.20, offsets X35.0 Y0.0

G31 ; me holding a screwdriver shorting zprobe.in to gnd
Current reading 0, threshold 500, trigger height 2.20, offsets X35.0 Y0.0
this does not look ok, should I invert something or .. afaik BLtouch is open drain pulling output to gnd on trigger so my screwdriver should of triggered it ?!

Thanks, I think you've found a bug. Setting the G31 P parameter to less than 250 (e.g. 100) may be a workaround.

A Former User

@dc42 so I just rename DuetWebControl-SD-2.04.zip to DuetWebControl.zip and upload to same place where I upload config.g and Duet2CombinedFirmware.bin and it will automagically fix everything, thanks will try

dc42

@smece said in RepRapFirmware 3.0beta 11 released:

@dc42 so I just rename DuetWebControl-SD-2.04.zip to DuetWebControl.zip and upload to same place where I upload config.g and Duet2CombinedFirmware.bin and it will automagically fix everything, thanks will try

You don't even need to rename it, just uploading it as-is should work.

A Former User

G31 ; bltouch attached
Current reading 0, threshold 10, trigger height 3.50, offsets X-35.0 Y0.0

I doubt I can get readout on trigger as it lasts too short, could hookup scope if it would help but I unplugged the zprobe.in cable (so that would be the 250 we seen earlier) during G30 move and it did not trigger

if there's anything else I can do to debug lemme know

dc42

Send G31 P100. Position the BLTouch well able the bed and send G30. Push the pin up before it reaches the bed and the downward motion should stop. If it doesn't, you can cut the power before it reaches the bed.

If the reading is 250 with nothing connected, I expect the BLTouch to give that reading when triggered too.

A Former User

tried that, didn't help, if you look at the last copy/paste from console threshold is 10, I tried 200, 100, 50 and 10 same issue, never triggers, I even disconnected the cable during G30 move (assuming long 250 read will happen) but nothing bed just keep raising

dc42

Thanks for trying. I'll bench test a BLTouch with this firmware tomorrow.

dc42

@smece, which model of Duet are you running RRF3 on?

A Former User

duet2eth, iirc 1.0.2 was on the board

dc42

Thanks. I found the problem, ir affects type 8 (unfiltered digital) and 9 (BLTouch) Z probes. The reading when triggered is 250 instead of 1000. So setting the G31 P parameter to less than 250 should fix it. The machine with a Duet WiFi that I used for testing has a type 8 probe (Smart Effector) but the G31 P parameter is set to 100. So that's why I didn't experience the problem.

A Former User

sorry no 1.2 was on the small ethernet board that I lost so I got a replacement from aliexpress, no clue if any version is on the board itself, will try to check but not easy to get to it now

dc42

@smece said in RepRapFirmware 3.0beta 11 released:

sorry no 1.2 was on the small ethernet board that I lost so I got a replacement from aliexpress, no clue if any version is on the board itself, will try to check but not easy to get to it now

No need, I've found the reason.

A Former User

cool, but I'm not triggering with a 100 neither

lemme try again with new config.g uploaded and restarted

A Former User

don't work I'm back to 3b10 (works ok with 3b10)
homex.g homey.g config.g homez.g homeall.g

TLAS

@dc42 said in RepRapFirmware 3.0beta 11 released:

Added DotStar LED support on Duet 3 main board

Any documentation on this yet?

TLAS

Disregard that last - looked through the code and found it in the gcode documentation under:
M150: Set LED colours

dc42

@smece said in RepRapFirmware 3.0beta 11 released:

cool, but I'm not triggering with a 100 neither

lemme try again with new config.g uploaded and restarted

It works for me. Tested using a BLTouch connected to zprobe.in and exp.heater3, G31 P value set to 100.

It's possible that you have a G31 command in config-override.g.

btw you don't need the M401 and M402 commands in your homez file, because probe deployment/retraction is done automatically (this has been the case for many firmware versions).