I may be doing something wrong but when I used the configurator to set up my config files for a Voron 2.4r2 I just built I noticed that the only way to add stepper drivers was to add them as Extruders. It was not a big deal, I just modified the config.g file after it was created by the configurator to include the missing drivers. However, since many printers today have multiple Z steppers it might be worth considering adding the option to add more Z drivers in the configurator. It is a great tool and I use it frequently and I understand it is designed to be a starting point only. Thanks for considering this.
Best posts made by JADoglio
-
More Z Driver Options Needed
-
RE: When I home Y axis the motor moves forward about 5mm than stops.
@fcwilt I have resolved the issue. Thanks for your help. Yes, it does mean that those three options are about all there is. In fact, I started at the switch and checked continuity at all points where a break could occur all the way back to the JST connector on the board. They all passed. So, I took the pins out of the JST connector and checked those, they were fine. When I put it back together and connected it to the board, it started working. It appears the problem was the pins in the connector were not making a connection (which makes no sense but that is what is seems to have been).
-
RE: RRF 3.4 Will Not recognize my Extruder
@sputnikoc3d Thanks for the help. I ordered a new Duet 2 WiFi yesterday to get this machine up and running and it has already shipped. I also ordered a new Prusa XL... unfortunately that wont ship until who knows when.... but if I ever get it it will replace this machine. Thanks to Phaedrux, Siam, and yourself for trying to help.
-
RE: Config.g file for CNC Application with dual Y drives Question
@phaedrux Thank You that is exactly what I needed to know. Appreciate the help.
-
RE: M591 S option question
@jay_s_uk Thank you. That makes sense. I am so used to not thinking about the SD card capturing the upload from DWC that this confused me for a bit.
-
RE: RRF 3.4 Will Not recognize my Extruder
@jadoglio I installed the new board...big surprise everything works now. Thanks again for trying to help.
-
RE: BLTouch and : Pin 'zprobe.in' is not free
@jay_s_uk OK thanks. I didn't realize that. I will give it a try. I am doing a PID Autotune on the bed right now as I just replaced that as well. Once it is done I will try your suggestion.
-
RE: Duet 3 Mini 5+ Fried??
Sorry, now it is really idiot/rookie confession time. I checked the things you suggested and found no obvious issues. However, when taking pictures I did notice something that is about as rookie a mistake as is possible that I had completely overlooked. As Occam once said... the simplest solution is probably the best/right one. The 10A fuse blew. When I replaced it all began to work as expected.
I curious what that fuse does as everything worked generally as it should but it did not work right. I assume that it has something to do with the 24v system but is there more to it than that?
Sorry for wasting your time and thanks. Jim
-
RE: Duet 3 Mini LED Question
Thanks, I figured it out. I was using M564 H0 and using DWC to check movements but somehow it was messing things up. When I stopped using it and went to the procedure you provided everything began to behave as it should.
-
RE: BLTouch and : Pin 'zprobe.in' is not free
@JADoglio Thanks You very much. I don't care how many hours I spend printing, building printers, and upgrading there is always something new to learn and thankfully someone out there to teach it.
Latest posts made by JADoglio
-
RE: Probe no retracting at end of macro
So, without changing anything else, I added a G28 to home after the Z offset probing commands. With just the G28 the system homes but the probe still does not retract. However, if I add a M402 command after the G28, the system does the G30 probes, then the G28 homes, then M402 forces the probe to retract. I also added manual G1 commands to the end of the file to retract the probe and those work as well. Not sure if that helps understand what is going on, but I hope it means something to somebody here because I should not need the last G28/M402 or the manual movements to retract the probe in this macro. At least I have a work around for the issue but I would like to understand why macro does not work as it should. Thanks for any help anyone might have.
;Z Offset Calibration Finish M98 P"Check to see if probe is attached.g" G90 ;set absolute M401 G1 Z20 ;raise Z up 20 mm G30 S-1 F150 ;(G30) home z (S-1) record z height G4 P500 ;pause .5 sec G1 Z20 ;raise Z up 20 mm G30 S-1 F150 ;(G30) home z (S-1) record z height G4 P500 ;pause .5 sec G1 Z20 ;raise Z up 20 mm G30 S-1 F150 ;(G30) home z (S-1) record z height G4 P500 ;pause .5 sec G1 X175 Y175 Z25 ;move Hot End to X175 Y175 M291 P"Check Consule for Results of Probing " S2 ;instruct user to check results in Consol G1 X63 Z20 F20000 G1 Y345 G1 X175 G1 Y175 ;G28 Z ;M402
-
RE: Probe no retracting at end of macro
@Phaedrux Do you have any ideas why a macro would execute normally up until the last command line and then terminate without reporting an error and without executing the last command line in the macro (in this case M402)? It seems not executing all lines in the macro would create some kind of abend that would trigger some kind of error? Thanks
-
RE: Probe no retracting at end of macro
@OwenD Thanks for the input. See comments below.
So your condition is going to return true any time the micro switch is not actually pressed if it's an N/O circuit and likewise return false if it's an N/C circuit
How is it defined in config.g?Config.g M558 P5 C"^io2.in" H10 A10 S0.005 F1200:150 T18000 ; set Z probe type to switch type for Voron PCB Klicky on pins IO_2.in and the dive height (H10)
Switch is NCYou can check in the object model browser which value you have during the process.
When connected as a NC switch the probe value is 0. When triggered it is 1000I would have thought you'd be checking if the probe was attached rather than whether it's "active" ?
Semantics.. I used active/attached interchangeably in this case, attached is more descript.EDIT
Your code seems to assume that as soon as the probe is picked up you get a value of 1000. When picked up, as noted above, the probe value is 0. The code doesn't assume this, that is what happens.That may be possible, but as stated the value is meant to be an indicator of whether the switch is depressed by touching the bed.
If the probe is docked and not electrically present do you get a null value? Sorry, not sure what this is asking.
That may be a way to check if it's attached.Also it's much better to put your code in blocks rather than as attachments Thanks will use this in the future.
-
RE: Probe no retracting at end of macro
@Phaedrux Thanks. I just did that (M291 P"Check Consule for Results of Probing " S2) and it did block and ask for OK to proceed, when I clicked on the OK the system just cleared the message and then stopped. Probe still not docked.
BTW, if I manually issue a M402 the probe docks as it should. But if I include M402 in the file, it just reports "Probe Retract Failed"
-
Probe no retracting at end of macro
I am running a Duet 3 Mini 5+ (Mini5plus)
Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.4.6 (2023-07-21)
Duet WiFi Server Version: 1.27
Probe: PCB KlickyI included the set of macros I use for determining my Z offset. The first file is used to start the process and then bed.g is called to tram the bed, then the finish macro runs the G30 probing to determine the offset.
Everything runs as expected, except that at the end of the Z Offset Calibration Finish file either the hot end just stops after the M291 command and the probe does not retract, or I get a message "probe failed to retract". Which one depends on what I put after M291. The current version just stops and does not retract with no message. If I use M402, or M98P"retractprobe.g" I get the error. I even tried adding a g28 at the end. With that, it did the homing but still did not retract the probe.
Any ideas to get this probe to retract after this routine would be appreciated. Thanks
_Z Offset Calibration Macro.txt
bed.g.txt
Z Offset Z Calibration Finish.g.txt
retractprobe.g.txt -
RE: Klicky Probe Accurcy
@moth4017 Thanks. That pretty well answers the question. I am buying an Omron and will start over. I suspect it will help.
-
Klicky Probe Accurcy
As always, I am never quite sure where to ask questions. So, if this is the wrong group, please point me in the right direction. I built a new klicky probe for my Voron 2.4 running Duet 3 Mini 5+ hardware and DWC 3.4.6. I bought cheap Chinese switches instead of the Omron (my mistake). The switches seem to be less accurate than the Omron I was using , as it seems to often take more probe attempts to get a good reading.
I did a probe repeatability and got these results;
M292 G32 bed probe heights: -0.090 -0.094 -0.094 -0.097 -0.097 -0.097 -0.090 -0.090 -0.094 -0.094 -0.094 -0.094 -0.092 -0.094 -0.094 -0.097 -0.099 -0.097 -0.094 -0.092 -0.090 -0.092 -0.096 -0.094 -0.097 -0.094 -0.092, mean -0.094, deviation from mean 0.003. These results seem pretty good to me, but if anyone can confirm that, or tell me what they should, be that would be appreciated. -
RE: G30 Causing G28 can not be called in homing file error
@gloomyandy Thanks. That was the source of the issue. I figured out how to get around it. I appreciate the help. Regards, Jim
-
RE: G30 Causing G28 can not be called in homing file error
It is a macro that is called at the start of a print. If the machine is already homed, it will not home again even though there is a G28 in the start g code file for the printer.
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed ; if homed don't home again
G28 ; if not, continue homing -
RE: G30 Causing G28 can not be called in homing file error
@dc42
David, thanks for the reply. Here is the file you asked forgloomy,
The command to test for probe attachment is in the file. When I remove it, I get the same error
if sensors.probes[0].value[0] == 0 ; if sensor value is 0 do this, 0 = probe attached
echo "Probe already attached"Thanks all