As the title would it be possible to relax the agressiveness of the "spam" detector to actually allow editing of posts without this thing preventing me from correcting speling mistakes.

As most users of the Voron 2.4 machines appear to run klipper being a duet hardware user, comes across as being in a minority, and in my opinion there is a lack of mods for use with the duet.

I wanted to install a Tool-board on mine so I came up with what you see below.

I have created a set of files for the users of the Duet Hardware specifically to employ the "LC1" tool-boards for the Stealth Burner (both CW1/2) while attempting to not get too ugly.

I have the CW1 version on my own machine with a Phaetus Rapido hot-end and The Orbiter 2.0 extruder so all other files are not tested and only drawn in C.A.D.

The set i printed for my own use worked out of the box from C.A.D so i don't envisage too many issues as basically they are the voron released files with new clothes on.

The main shroud is 10mm wider (5mm per side) and everything actually looks bulkier in C.A.D. than it does when printed.

I did previously release my initial files, but a klipper user accused me of plagiarising an idea he had published for klipper tool-boards and i was getting harassed on discord for this "theft" so as i dont need the trouble i took them down.

Having considered it in depth and having been approached on numerous occasions regarding the files i decided to draw up the version for CW2 over the weekend and modify the hot-end mounts.

You can see what we have below.

If there is enough positive interest I will consider putting the files up on my github page.

@Rushmere3D said in Dr D-Flo's big build:

but than I'm not so arrogant to question someone's project.

I am genuinely curious to be able understand how you made the mental leap/connection from someone possibly asking a genuine question for an explanation or reasoning behind an aspect of a project, for you to consider doing so to be arrogant ?

We are all human, none of us are perfect, so surely any intelligent person with an open mind who has a quest for enlightenment and knowlege would (or should) willinging accept (and consider) differing points of view, and logically analyse their merits and validity, points of view that we might not have considered, everyone can bring something new to the table,

if one is unwilling to accept that possability, then to do so is a distinct sign of arrogance.

without being questioned we will never evolve

I would list the sequence as following the logical procedure as being :

1. G28 which homes all Axes X,Y,Z ,you must home the printer BEFORE doing anything else, see Here For a detailed explanation.
2. G32 which allows you to "level" the print surface for it to be perpendicular to the tool head, see Here For a detailed explanation.
3. G29 which carries out a mesh bed probe, see Here For a detailed explanation.

In your case as you list the machine vas a BLV which only has Two Z axis Lead Screws and therefore can only adjust across the X axis and connot carry out true levelling along both the X & Y axes you need to level the gantry only

By deploying G32 For this machine you send the tool head to probe close to the left leadscrew and probe that point then to the right leadscrew and probe the second point, it will then level the toolhead to allow the head to be perpendicular to the print surface along that axis, See Here for setting up your machine to use independantly use multiple Z axis motors for levelling.

The DWC error is being displayed because the probe locations listed in you're bed.g file are incorrect, due to the probe points being outside the area of where the probe can reach.

To me logic would dictate that your bed.g needs to look something similar to what i have listed below

G90                                         ; Use absolute positioning moves
G30 P0 X40 Y70 Z-99999                      ; Probe near the left lead-screw
G30 P1 X250 Y70 Z-99999                     ; Probe near the right lead screw
G30 P0 X40 Y70 Z-99999                      ; Probe near the left lead-screw (Second Pass)
G30 P1 X250 Y70 Z-99999                     ; Probe near the right lead screw (Second Pass)
G1 X150 Y208 F9000                          ; Place the probe in the centre of the bed on the X & Y axes
G30                                         ; Probe and set the height as probed
G1 Z25 F6000                                ; Lower the Z axis   
M400                                        ; Allow all moves to complete        

It must also be noted that you need to have the Z axis motors connected up to the board in the same order as is listed in your config.g otherwise instead of "levelling" the ganrty it will compund the error making it worse see M584 For further explanation.

@jay_s_uk

yes I am but not yet, I have been bitten releasing files early before, I want to wait until I get my rails here and test everything works as intended before I let the files loose.

Allow me to make this easier on the eyes.....

Hi there Duet users.
For quite a while I have had a loading file error, This error was not allowing files to load that were around 3 to 5 mb or larger.

I was so frustrated. Most of my own drawing's/ models were over 5mb I tried everything and asked lots of people for suggestions. I read every post and forum I could find. It seemed that not many other users were having this issue.

But I did read about a few users that were having the same exact problem. So I tried everything possible. I do feel that resoldering all the pins on the wifi module and the sd card holder did help the data transfer. But still it was struggling to load larger files.

So I read all the information about ajax time out errors. Also sometimes I could load a smaller file around 1 mb then as soon as it loaded, I would send the larger file of around 5mb. Many times this would let the larger file load. So I read more about this.

Then I wrote down all my settings and started trying different settings in the machine specific communication area on the duet web control page. Took me a number of tests. But I nailed it. Now my files load very quickly.

I have now tested this many times so I wanted to share my settings. General tab "5,000 ms" Machine specific commmunication - number of Ajax settings "6 " This was set at 4 and I feel this made the biggest difference. Update interval 250 (ms) Extended status update interval 20(ms) retry threshold for file transfer 350(ms). Now my Duet loads the larger files very fast with no errors. Running ViaCad V12 pro...and Moi3d... SuperSlicer....and my Elite Machine Works UXL. I get some amazing prints using this combination.

Thank you Duet3D for making such an awesome product. I love my panel due as well. Happy New Year 2023. P.s I did read all those tech tips that a Duet tech replied to my posts awhile back. I really appreciated those tips. Peace out from Colorado.

@gumby said in Preferred GPIO pins? For Relay Control Duet 3 Mini 5+:

I don't want to ask stupid questions

The only stupid question is the un-asked one, if you don't know, you don't know.

You cannot be though ill of for asking and trying to educate yourself, problems begin when the "entitled" don't try to learn instead they expect others to spoon feed them the solutions.

1. What printer (cartesian, core-XY, delta etc) ?

2. What board and where did you buy it from ?

3. What exactly are you having an issue with ?

4. Please post FULL copies of you Config.g & Homing files.

5. Please post a decent quality picture of how you have wired the board up to the printer.

And by the way Posting multiple instances of the middle finger emoji isnt really going to endear yourself to people and isnt really going to encourage people into spending their free time assisting someone who doesnt appear very greatful.

@yuval said in using IO pins:

Hello

It might be prudent to Read This Post and follow its advice this might result in people being in a better position to assist .

@jay_s_uk

thank you

@too-stroke said in Another Delta Homing Issue:

@cosmowave
I can see how the M400 can be useful however it hasn't improved my issue.
I was thinking it might be a endstop triggering prematurely, however, I watched the endstop trigger LED's on the mainboard while homing and none of the endstops triggered (visibly) prematurely when my Y axis refused to home.

maybe try adding the following after M400

M400    ; Allow all moves to complete
G4 P200 ; Pause

@oliof

I am quite happy to share my code/solution.

My rationale is listed with the code at the bottom (be aware it’s a long read)

There are hardware features that I purposefully had to “engineer” in which are key to the macro operating successfully, and the G92 Z offset needs to be tuned to the correct (positive) offset once to get everything to operate as intended.

In this case the setup will work (I have tested) with both a “collectable” probe and a BL-Touch.

We basically want to know the offset distance between the nozzle and the probe, we have done this manually for a long time by placing the nozzle (heated or not) in a certain location and then lowering the nozzle close to the bed until we have a comfortable clearance (which I measure using a feeler gauge)

We then send G92 Z0 to set a datum point and then jog the bed down (or the head up) to allow clearance to attach the dockable probe (no need for this with a BL-Touch) we then send G30 S-1 to the printer to have it report the height at which the probe was triggered, then we normally edit the G31 command (the Z switch) to the height at which the probe triggered.

That is all carried out with NO requirement for conditional G-code, so if it can be done manually with out any conditional G-code it can be automated and do it without conditional G-code with lateral and logical thinking.

I looked at how others were doing it and I initially looked at the one where a huge number of extra macro’s were required with global’s, status, files etc etc being required to get the thing to work.

I tested the very first conditional g-code probe “status” file in the downloadable zip file to find it didn’t actually work I had to change two lines of code for the status file to actually report the probe was attached (or not) so I went hunting through the rest of the code and just thought there is no need for all this, if we can manually set the Z offset with no conditional g code there must be a way to automate the action of doing it manually with a simple macro.

First you need to know what the offset would be if you did this manually, this I did and noted the offset number.
Then I first edited my config.g probe section to the following.

My collectable probe & the second probe (Z End-Stop) use the following M558 & G31 commands

M558 K0 P8 C"121.io0.in" H25 R0.1 F2000 T15000 ; Collectable probe
G31 K0 P500 X-32 Y39 Z10

M558 K1 P8 C"!io0.in" H2 R0.1 F2000 T15000 ; Z End-Stop                         
G31 K1 P500 X0 Y0 Z0

I then created the macro and made sure everything is homed before collecting the probe, place the nozzle above the Z End-Stop Pin and send G30 S-1 K1 (the Z End-Stop Switch) to have the nozzle come into contact with the pin of the switch.

It doesn’t really matter what the system reports here as you don’t care, all you care about is that you have now automated the manual action of placing the nozzle close the bed by having the Z End-Stop switch replace the bed surface, and that the printer has stopped what it was doing so you can now proceed to the next part of the automation and set the desired G92 Z offset.

Then Send G92 Zxx.xxx to the printer, this number is where the fine tuning is required to get the second probe offset number to match what doing it manually would report.

Then Drop the bed (or raise the head) by a set amount to allow clearance (to prevent crashing) for the already attached probe (or Bl-touch) between the probe and the Z End-Stop pin.

Then place the probes switch (or the BL-Touch pin) over the centre of the Z End-Stop Pin and send G30 S-1 K0 (The collectable probe or BL-Touch)

This switches over the probes from the Z End-Stop (K1) to the Probe (K0) to get the correct readings to be reported/stored.

Now this is where I had to Engineer in some thought.

I encountered a variance issue (a fix for which turned out to be only needed on the collectable probe as the issue didn’t manifest itself with the BL-Touch)

I originally used two normal microswitches for both the collectable probe and the Z End-Stop, not really thinking that would cause any problems, but as said I was getting a variance in the reported offset on the second G30 K0 probe which I tracked down to the fact that I was using two of the same switches both being activated at exactly the same time during the second probe, both requiring the same amount of force to activate.

The switches (from their data sheet) required 0.44N to be triggered, so in effect the trigger distance was being “doubled” because both switches were being triggered by each other, I tried to work my way around it by further editing the G92 Zxx.xxx offset.

That in reality helped but I couldn’t get a really consistent result for the second G30 S-1 offset.

So I sat on it and thought about it for a few days and kept coming back to what was going on when we do this manually, which is we use the bed as a Fixed datum point and used the trigger point of the probe switch to report the offset, so I needed to find a (mechanically simple) way to have the Z End-Stop react to the nozzle touching it but not to react when the probe switch touched it.

The solution I came up with is to use a Switch on the Z End-Stop that requires a higher force to be activated.
In this case I changed the Z End-Stop switch to one which now requires 2.45N to activate and the Z axis motors can easily provide enough force to activate the new switch, but when the collectable probe switch touches the Z End-Stop pin with an activation force of 0.44N that switch activates but the Z End-Stop Switch Doesn’t instantly getting rid of my variance issue.

And because the BL-Touch evidently requires less than 2.45N to activate is the reason why the BL-Touch worked with the original switch but my collectable probe didn’t.

With that part of the problem solved I just finished everything up by using
M500 P31 to save the automatically formulated Z Offset in the config-override.g file

I have a single macro entitled autozoffset.g placed in the sys folder and have placed
M98 P”autozoffset.g” in the last line of my start.g file in my slicer and if you change anything the config-override.g file is automatically updated for you.

The switch on the probe is nothing special, it is a kw11-3z micro switch

The Second Switch on the Z End-Stop with a higher activation force is a TWS4417 (But im sure others will work too, as long as the switch on the Z End-Stop requires a higher activation force)

And the Actual Macro

;
; Auto Z offset calibration
; autozoffset.g
;
M291 S3 R"Heating up nozzle" P"Wait for the nozzle to reach printing temperatures"    ; Notification
M568 P0 S210			                                                      ; Set tool temp
M116 P0 H5					                                      ; Wait for temp 
G29 S2                      							      ; Disable mesh bed compensation and clear the height map
G90                    							              ; Revert back to absolute positioning moves
M98 P"homexy.g"                                                                       ; Home the X & Y axes	
M400                                                                                  ; Allow all moves to complete
G4 P100                                                                               ; Pause
M98 P"collectprobe.g"                                                                 ; Collect the probe
M400                                                                                  ; Allow all moves to complete
G4 P100                                                                               ; Pause
G30                                                                                   ; Home Z using the probe and set the height as probed
M564 H1 S0             		                                                      ; Remove boundary limitations 
G91                    								      ; Switch to relative positioning moves
G1 Z15 F15000						                              ; Lower the bed 
G90                    								      ; Revert back to absolute positioning moves
M83							                              ; Use relative extruder moves
G1 E-5 F300 				                                              ; Retract filament
M400                                                                                  ; Allow all moves to complete
G4 P100						                                      ; Pause       
M291 S3 R"Clean the nozzle" P"Remove any plastic from the nozzle"                     ; Notification/Action request
G1 H1 X120 Y-9 F18000                                                                 ; Place the nozzle over the Z End-Stop
G30 S-1 K1                                                                            ; probe the nozzle
G92 Z9.63                                                                             ; Set the nozzle height to "Zero" (tune once to suit)
G91                                                                                   ; Switch to relative positioning moves
G1 Z20                                                                                ; Lower the Z axis
G90                                                                                   ; Revert back to absolute positioning moves
G1 H1 X78 Y-6 F8000                                                                   ; Place the probe over the Z stop pin
G30 S-3 K0                                                                            ; Set the offset
G91                                                                                   ; Switch to relative positioning moves
G1 Z5 F18000	                                                                      ; Lower the Bed
M400                                                                                  ; Allow all moves to complete
G4 P100                                                                               ; Pause
G90                                                                                   ; Revert back to absolute positioning moves
M500 P31                                                                              ; Save new found Z offset
M564 S1 H1      	                                                              ; Restore boundary limitations
G91                                                                                   ; Switch to relative positioning moves
G1 Z5				                                                      ; Lower the bed
G90                                                                                   ; Revert back to absolute positioning moves
G1 H0 X160 Y200 F15000                                                                ; Place the probe in the centre of the bed on the X & Y axes
G30 S-1 K0                                                                            ; Home Z 
G91                                                                                   ; Switch to relative positioning moves
G1 Z5 F18000	                                                                      ; Lower the Bed
M400                                                                                  ; Allow all moves to complete
G4 P100                                                                               ; Pause
G90                                                                                   ; Revert back to absolute positioning moves
M98 P"stowprobe.g"                                                                    ; Stow the probe    
M400                                                                                  ; Allow all moves to complete
G4 P300                                                                               ; Pause
echo "The action to calculate the Z offset has been completed"                        ; Notification

I am currently very slowly trying to get my head around the required conditional g code to have two sets of RGB L.E.D.s react to the states of both switches with Red being displayed when the collectable probe is not attached, Green when attached & Blue when triggered, and Red or Blue when the Z End-Stop is triggered

I have marked this as solved

There is no actual documentation covering how this is done practically.

After a lot of looking at how others made this work and coming to the conclusion that certain solutions were nothing more than an overly complicated MESS, with some parts of code that don't actually work.

I sat and logically thought through what i wanted to achieve and managed to come up with a simple single file macro which measures the offset,(using a Z stop switch over and above a dockable probe) you need to "tune" the settings once then it does everything itself with no need for conditional g code.

And NOT a M401/M402 command in sight.

i also managed to use some conditional g code to check the attached (or not) status of my dockable probe, to abort is certain conditions were not met

Thank you to all for the suggestions

The Can-Bus protocol was specifically invented to be a "rough-service" network communication protocol by Bosch and it was designed for the harsh environmental conditions seen in the automotive industry.

Nine times out of ten the main problem that causes disconnection issues is "mechanical" that is where i would start looking, and as a lesser possibly at electrical noise creating problems

you could (if you havent done so already) start logging to see if anything gets picked up during a print

@o_lampe said in Hollow shaft extruder:

@Herve_Smith said in Hollow shaft extruder:

M8x1.5mm pitch bolts, i could pop those out in 10 minutes on a lathe for less than a euro each

If the funssor version uses 8mm OD bearings and threaded rod it won't cut at all.
The screw extruder I made uses 6mm OD bearings. At least that would work with 8mm threaded rod ( OD ~7.8mm).
Where can I order your 1€ version?

Who said anything about Threaded Rod (that stuff is skata, it is like chocolate) ?

Personally i would use M8 fine pitch bolts, grade 12,9 (really hard) bolts which can be purchased cheaply in bulk

The mechanical properties of such bolts are listed Here

whereas 8mm threaded rod is usually grade 2, 5 (or 8 if high tensile is specifically specified)

And i only make such things for my own use, its not worth the trouble to deal with people

@breed said in Hollow shaft extruder:

https://a.aliexpress.com/_mK0e0jY

Anyone seen this

You can tell these have been (badly) made from M8x1.5mm pitch bolts, i could pop those out in 10 minutes on a lathe for less than a euro each

@moth4017 said in Looking for particular documentation ( I cant find it):

@Herve_Smith not that familiar with a voron but does it have a z endstop stop and a z probe?

Yes the voron has both, I have built voron 2.4 but not yet had time to fully commission it software wise.

I wanted to get this system up and running properly on one of my other core-XY machines that i mainly use for testing stuff and then i think i am in a position to begin commissioning my voron.

@moth4017

I just come upon This one which employs RRF i will see if i can follow it

@oliof

Thank you i will have a look.

I am working through a possible solution that im testing, there are some hurdles (well for me at least) my current road block is to get the Z axis to stop moving when the Z stop switch is activated outwith what the z probe does.

@moth4017 said in Looking for particular documentation ( I cant find it):

@Herve_Smith you could use sensorless homing on z and then save the z offset into the config.g but this would depend on how good your Z sensorless homing was . then could you trust it? if there was a bit of filament left on the end of the nozzle it could throw it all out .

Sensorless homing isnt a route i wish to travel.