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: 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
-
G30 Causing G28 can not be called in homing file error
NOT SURE WHERE TO POST THIS SO I THOUGHT I WOULD START HERE. SORRY IF IT SHOULD BE IN A DIFFERENT CHAT!
My machine is a Voron 2.4r2.
Board: Duet 3 Mini 5+ (Mini5plus) with the 2 port expansion board
Firmware: RepRap Firmware for Duet 3 Mini 5+ 3.4.6 (2023-07-21)
Duet WiFi Server Version: 1.27
The Situation
When I issue a homeall.g command using DWC HomeAll Button. X and Y home as they should while Z homes but issues the error message below. The homing files are attached as is my config.g. As I am using a klicky probe I have written macros to check to see if the probe is attached before the execution of the most moves. During maintenance I seem to frequently leave it attached and that creates issues chasing it down when it gets knocked off.
The Issue
When I include G30 in the homing file I get the error message below. When I don't include the G30, Z moves to position to home, but does not home. I assume G30 is calling G28 which is why the firmware complains about it but then ignores it and does the homing anyway. I would like to find a way to make this home without getting the error. Is that possible?
4/2/2024, 4:08:46 PM M292
Error: G28 may not be used within a homing file
Probe already attached
Attach Probe Successfulconfig.g.txt
HomeAll Incuding X Y Z Files.txtNot a huge issue but I suspect there is a simple solution.
Thanks
-
RE: Save As
Thanks, Interesting. I got it working. Since I am inside my home network I assume this is a secure connection? Is that correct? I know FTP is a pretty obsolete protocol and as a general rule is not very secure. Thanks again and I look forward to any other comment you might have.
Jim
-
Save As
Not sure exactly where to post this si I will start here. It would be useful to have both save and save as buttons on the edit screens for system and macro files. Then you could not only save it to the SD card you could save a backup on your computer. In that regard it would also be useful to include a file download button on the system and Macro folder screens for the doing the same thing in bulk. I know I can use the SD card and a computer to do this but on my build it is not that easy to get to the SD card, so just a suggestion. Thanks
-
RE: Can a macro or job write a message to the DWC console?
Lee, I am not very familiar with its use but I believe M118 can be used for that purpose. You can also use the "echo" command in macros to sent messages to the console as he macros progress. No G code required and no parameters required. just add a line "echo "sending note to console"" and when it is read in the macro it will be sent. The following example is my current deployprobe.g file. Hope that helps.
M564 S0 ; let travel outside print zone if sensors.probes[0].value[0] == 0 ; if sensor is value ia 0 do this, 0 = probe attached echo "Probe already attached" if sensors.probes[0].value[0] == 1000 ; if sensor is 1000 do this, 1000 = probe detached G1 X53 F20000 ; X position of klicky dock G1 Y347 F20000 ; Y position of klicky dock M400 G1 Y175 F12000 ; slide out of dock return to bed Y center G1 X175 F12000 ; slide out of dock return to bed X center M400 ; wait for moves to finish if sensors.probes[0].value[0] == 1000 ;Check to see if probe is attached 1000 = not attached G1 X175 Y175 F10000 abort "Attach probe FAILED!" else echo "Attach Probe Successfull" M564 S1