Posts made by T3P3Tony

@konvalm please email sales@duet3d.com

@omtek one for @chrishamm

@Razani yes those are the same diodes. The change is due to different 5V power supply current maximums now we support 48V.

@luca-Massimiliano please stop writing in ALL CAPS, its stresses me out.

looking at thingiverse there are plenty of examples you may be able to base yours on:

https://www.thingiverse.com/thing:31983
https://www.thingiverse.com/thing:1762302
https://www.thingiverse.com/thing:2369089
https://www.thingiverse.com/thing:3436158
https://www.thingiverse.com/thing:4162418/

etc etc.

@fractalengineer as a test please try a fresh DuetPi bookworm build on the SD card on the pi. Don't modify it other than to setup your printer.

@Adrian52 thanks for reporting it. We will have a new build out shortly which h we would like you to test.

@adrien_tobeca more recent firmware reports the raw angle:

M591 D0
Duet3D Roto magnetic filament monitor, enabled always, 25.20mm/rev, allow 10% to 190%, check printing moves every 2.0mm, agc 45, raw angle 354, no calibration data

Also you can use the "S" parameter in M591 to monitor movement all the time if you prefer:

Sn 0 = disable filament monitoring (default), 1 = enable filament monitoring when printing from SD card, 2 = enable filament monitoring all the time (S2 is supported RRF 3.5.0 and later ). Filament monitors accumulate calibration data (where applicable) even when filament monitoring is disabled

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensing

@adrien_tobeca mag is not the angle of the magnet it is the strength of the magnet, as modified by agc.

@adrien_tobeca said in Impossible to get the rotating filament monitor working:

However, still this issue of having no evolution of the mag in the sensor

What are you expecting to see in the M591 D0 output?

@adrien_tobeca said in Impossible to get the rotating filament monitor working:

DWC is 3.4.5 on Duet 2 Ethernet and Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.5.3 (2024-09-18)

Please upgrade to 3.5.4 or (preferably) 3.6beta4 because more information is reported on the filament monitors in newer firmware.

@adrien_tobeca said in Impossible to get the rotating filament monitor working:

mag 146 agc 0

agc of 0 means the magnet is pretty close, maybe slightly too close but this is probably not the main issue.

What happens when you print for a bit and the send M591 D0? the filament monitor needs to see some filament movement to calibrate.

@SpeedyDad said in Mini 5+ Odd fan behavior and now nothing. Blown Out3 and Out4?:

I tried to test it via the web interface by trying to turn on the hotend fan through the interface.

Thermostatic fans cannot be controlled through the web interface they are based on the hotend temperature.

You may not have blow the ports, as you say the other way around the part fan came on.

If you set the ports to normal fan control, not thermostatic, temporarily, and then try a known good fan on each one that will confirm if the ports are working.

See this documentation for more information about thermostatic fans etc:
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Fans_connecting

@developeralgo222

I would get it working directly and then see how that translates to OpenPnP

@Chriss said in How many tools?:

@jay_s_uk The XT30 2+x are nice, but that is the idea to get CAN out of the board than? A other connector? Solder pats?

The EXT30 2+2 are used as stubs normally.

@dwuk

Your homeu for reference (please use code blocks for these file, it makes it easier for people, especially on phones):

;echo "homeU disabled"
;M99
; homeu.g
; called to home the U axis
M569 P1.0 S0 D3 V500 ; driver 1.0 goes backwards (U axis)
M569 P1.1 S0 D3 V500 ; driver 1.1 goes backwards (V axis)
;
; generated by RepRapFirmware Configuration Tool v3.5.10 on Thu Jan 23 2025 15:02:10 GMT+0000 (Greenwich Mean Time)
;M913 U40 V40
;M400

; increase Z
G91 ; relative positioning
if exists(param.Z)
    ;G1 H2 Z{param.Z} F6000
else
    G1 H2 Z5 F6000; move Z relative to current position to avoid dragging nozzle over the bed
G1 H2 V10 U-10
M400
G90 ; absolute positioning

; home U
G91 ; relative positioning
var maxTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
G1 H1 U{var.maxTravel} F8000 ; coarse home in the +U direction
G1 U-5 F6000 ; move back 5mm
G1 H1 U{var.maxTravel} F3000 ; fine home in the +U direction
G90 ; absolute positioning

; decrease Z again
G91 ; relative positioning
;G1 H2 Z-5 F6000 ; move Z relative to current position
G90 ; absolute positioning

;M400
;M913 U100 V100
;M400

M569 P1.0 S0 D3 V2000 ; driver 1.0 goes backwards (U axis)
M569 P1.1 S0 D3 V2000 ; driver 1.1 goes backwards (V axis)

you are setting U and V configurations in home U. I would remove the references to V in home U.

This is an issue:
var maxTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
given U is not axis 0. It probably working if U and X are the same length though.

Also you are lifting Z but not returning it (that may not be an issue)

I see you are switching the speed of switch from stealthChop to to spreadCycle mode during homing. and the U and V are in stealthchop while the other axes are in spreadCycle so i expect thats the route of the issue/different behaviour.

Try getting everything working in spreadCycle and then explore sensor less homing

@luca-Massimiliano I think that would make the system over constrained? Someone with more knowledge of mechanical systems would need to confirm that.

As this post is in the multi axis printing area though i will highlight that is you split one of the sets of parallel arms on 1 tower into two and control them independently, you get rotation as well as translation of the effector, see this cool video:
https://www.youtube.com/watch?v=3yUislC0aS0&ab_channel=OleksandrStepanenko

I don't expect that is what you want though?

For an overview of adding new Kinematics to RRF, see:
https://github.com/Duet3D/RepRapFirmware/wiki/Adding-New-Kinematics

@T3P3Tony said in 4 Z Axis Leadscrews:

Please paste config.g in use the code block (</> icon in the text formatting menu), to format it

I have edited your post to paste in the contents of the file in a code block. this makes it much easier for people to help you.

from the documentation here:
https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_auto_levelling#axis-levelling-using-endstops

When homing, RRF3 will home both axes, and stop each motor when each endstop is triggered. Note that DWC and M119 will only show one endstop per axis, but will show the axis endstop as triggered if either switch is triggered. So you can test them by triggering one at a time.

That is true for the object model as well.

@dwuk It would be good to work out why homing was not working as expected in 3.6beta4. Where have been a lot of changes between 3.5.4 and 3.6 so the release notes may explain why. If not then please share your U and V homing files so we can have a look at those.

@luca-Massimiliano is this for a 4th set of delta arms, or something different? if its for a 4th set of delta arms I think it would need an appropriate kinematics done, but importantly, why would you want to do this?

@gnydick does it tune successfully at a lower temp (e.g. 220?)

@SANJR said in FREQUENT DISCONNECTION:

DWC : 3.4.5
Duet 3 MB6HC : 3.4.6

Please update the system to 3.6beta4
It looks like you have a 3HC in the system as well so be sure to update that as well. ideally in the following order:
Update 3HC
Update 6HC
Update DWC

Multiple motions systems is only supported from RRF 3.5 and later.

@Snyggis-0 you are uploading the output from the config tool which is not that useful. Please paste config.g in use the code block (</> icon in the text formatting menu), to format it