@syko_symatic That looks like it might be related to the loose fit at one end of the worm to me. It is similar to what I got when a bearing was getting worn out.

@dc42 Ok i understand. I'll switch to rrf3 so, to be able to have this multiple endstop working... Thank tou for your patience and this wonderful piece of hadware (and software) It's great to keep it opensource with a really strong support. Keep up the good work!

did you save your g32 calibration results in your config.g? also see http://boim.com/DeltaUtil/CalDoc/Calibration.html

@cj-bravo said in Machine properties - Logical drive - weird assignment: @cj-bravo firmware updates should be checked online or there's an auto-update checker? Not yet, but also on the wish list. You can subscribe to be notified of firmware releases, go to https://github.com/dc42/RepRapFirmware/releases and click on the Watch button.

@denis, I suspect it is at least partly a temperature issue. From @Veti's post above: @veti said in Quality problems. Duet vs. Marlin: if your bed is a semitec thermistor see the configurator for b and c values for that thermistor. the marlin thermistor file says B4100 for thermistor 13. If your Marlin config assumes B4100, that will give you significantly different temperatures from RepRapFirmware which you have configured for B4267.

@nightreaver said in BLTouch Self-Triggering during multipoint probing: @dc42 Can you confirm that M558 A has upper limit? When I set it to 15 with works okay, when I set it to 50 it seems like the limit goes down to A2 or something. Is this right? From the Bug Fixes section of the firmware 2.03 release notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md: Setting M558 A parameter to anything >31 set it to 0 instead of to 31

Yes it would be possible to calibrate nonlinear extrusion using the filament monitor. This is unfortunately one of many things that I don't have time to implement right now. You could do it semi-automatically like this: Create GCode files to print, that extrude into air at various speeds while also moving the print head in the XY plane. At the start of each file, put the filament monitor in calibration mode (M591 Pn S0). At the end of each file, use M591 Pn to report the calibration parameters, which includes the measured/commanded extrusion percentage. You could combine all these files into a single file, using M226 to pause between the sections (which restarts the calibration).

This is supported in firmware 2.03. The extruder doesn't have to be in the middle, it can be offset. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter#Section_Adding_additional_towers_to_carry_flying_extruders.

That height map looks terrible, as if you are probing off the edge of the bed or something like that.

I'm marking this as solved, because the original problem in the title is.

I'm sorry about that, I've updated the link in my post above. Try again.

@jstevewhite, please can you repeat those tests, but after each G28, G32 and G29 command (and after any individual G30 commands you do), run M122 and look at the "comp offset" value in the Move diagnostics. This is a new field that I added in firmware 2.03. Please check what value is reported there, and whether any nonzero values are related to the height offset shown in DWC. I would like to get to the bottom of this before I do a 2.03.01 firmware release.

@veti said in BLV mgn Cube - 3D printer Project: at a build plate of 500 i would expect that the 2 rails would not be enough to ensure the stability of bed. you could modify the build and add 2 additional rails and obviously the front panel would not fit anymore. if you are not comfortable about doing your own mods you could have a look at the voron 2.1, which allows for such build volumes Thank you for the response! That looks like a really viable option.

@dc42 said in DM556 driver not working with duet expansion breakout board: I don't know about the DM556, but on some external stepper drivers the EN+/EN- are actually a disable input, not an enable input. So try with those wires disconnected, or change R0 to R1 in the M569 command. Does the manual say what the constant red LED means? @dc42 your are a genious! Thats it. Thank you. For Leadshine DM556 driver do not connect Enable+ and Enable- as this disables the driver. You can connect the other leads directly to the breakout board driver connector. Config: M569 P5 S1 R0 T5:5:5:0 ; Drive 9 goes Forwards M584 Z5 ; Power Z with drivers 5 Also check for driver number if the motors are not spinning: https://duet3d.dozuki.com/Wiki/Duet_Expansion_Breakout_Board

@phaedrux said in duetwifi breakout board and bltouch wiring: https://duet3d.dozuki.com/Wiki/Duet_Expansion_Breakout_Board https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch It looks like the breakout board still exposes Heater 6 PWM and Heater 7 PWM. So I think you could use Heater 7 pin, to connect the servo wire, and use M307 H7 A-1 C-1 D-1 to unbind the heater from it, and then use P7 in your M280 servo commands. And I think you would still need to invert the M280 commands since the heater 7 pin is still on the expansion header. For example M280 P7 S10 I1 to deploy. The breakout board inverts the heater/servo signals to be the "right way up", just as on the DueX boards, so you won't need the I1 parameter on the M208 commands.

@jakemestre said in Firmware 2.03RC5/1.24RC5 released: @dc42 I've got a delta with end stops that are shy of ultimate height movement. There's a tool changer in the dead space of the delta and this way I can easy move in XY to get new tools. Any way the "target position outside machine limits" could controlled with the M208? Not currently; but with care you could use G1 S2 individual motor moves to move beyond the limits.

The "Target position not reachable" message on a delta usually means the effector is at/near the top of its travel (e.g. because you have just homed the printer) and you have tried to move it horizontally to a position that can't be reached at that height.

@nikker said in Z Probe Already Triggered only when using G32: but something happens on the first G30 command to probe the front left of the bed. What exactly happens? Do you mean the probe reading goes to 1000 before the sensor is close to the bed? @nikker said in Z Probe Already Triggered only when using G32: I also noticed that along the Y axis once I get close the the limits of travel, with 0,0 being bed center the Z probe trigger value hits 1000. I think this is where the Z probe already triggered is coming from but why? I checked all the wiring and all is good. If the sensor has an LED to indicate that ti is triggered, does the LED turn on at the same time the reading hits 1000? Are there any pieces of ferrous metal (e.g. linear rails, leadscrews) at either end of the Y axis that could be triggering the sensor?

@bondus said in Best lead screw - ball bearing mount system: The nice screw @claustro has should solve that problem. Where did you find such a screw? I am not a native english speaker so maybe I am l misunderstanding something. My lead screw is a regular 2mm pitch Chinese lead screw and it is connected with a 8mm to 8 mm coupler with a 8mm shaft. I am having quite difficult aligning perfectly the lead screws but I think that it will not affect a lot the Z if the bed is correctly fixed in X and Y ( with V slot wheels in my case). I can't understand the shaft collar and 15 degree angle bearing. What would be the advantages over thrust bearing and regular ball bearing like I did?

@fm16055, to use it in single-ended configuration, connect all the + step/dir/en inputs of your drivers to +5V from one of the servo connectors on the expansion breakout board. Leave the + step/dir/en outputs of the breakout board not connected.