Topics created by koreandi

@koreandi thats correct. theres no restriction on what pin can be used for what other than what hardware its connected to (or if theres some underlying restriction itself in the MCU design on what each pin can do)

@oliof acceleration is always specified in mm/sec^2. The problem arises because RRF allocated and published the M203 command (in the RepRap wiki), then Marlin added support for M203 and chose mm/sec as the unit. In fact there is no reason for slicers to generate M203 commands, but unfortunately they do.

@koreandi My understanding of a tool changed pretty much with this approach, of ... gcodes.
A tool is a complex thing, and allows many items to be associated, for working in sync. For example, you need to start many items at once, and stop them at once, when start printing and stop printing.

Because of this, you need to associate to a tool the heaters, the fans, the motors, etc. However, there are limitations and cautions to this... as I learned too. For example, you usually do not want to associate with the tool all thermostatic fans, always, etc.

Because of this, you may need to associate both your motors to that tool, AFTER defining them, of course.
I only have one though:

M563 P0 S"E0" D0 H1 ; define tool 0, one motor, one heater ; or M563 P0 S"E0" D0 H1:2 ; define tool 0, 1 motor two heaters ;or M563 P0 S"E0" D0:1 H1 ; define tool 0, two motors, one heaters ; but this one idin not tested if it works, even if it is in plan

@koreandi said in Cheapest way to connect 3 Hotends:

Is there any general recommendation about 12V / 24V system?

For a new system, always use 24V. It keeps the heater currents lower and allows the motors to move faster.

@T3P3Tony
okay, thank you.
I'll search there.

@droftarts

Hi Ian,

thanks a lot for your advice.

Regarding the firmware.
As I said: this machine is used in an experimental phase and we want to keep everything as stable as possible. And since we did not recognise any advantage with a newer version we kept it as it was.

About the filament sensor:
We just used

M591 D0 P3 C"io6.in" S1

in our config.g.

Then we started a small manual programm:

homing move z to 50 mm extrude 200 mm filament end

Here are the results from the console in timed order:

18.7.2023, 09:56:29
M32 "0:/gcodes/Test extrusion filament sensor.gcode" File 0:/gcodes/Test extrusion filament sensor.gcode selected for printing

18.7.2023, 09:56:46
Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, mag 129 agc 82, no calibration data

18.7.2023, 09:57:51
Finished printing file 0:/gcodes/Test extrusion filament sensor.gcode, print time was 0h 1m

After typing M591 D0 into the console we got this message:
18.7.2023, 09:58:11
Duet3D rotating magnet filament monitor v4 on pin io6.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, mag 130 agc 82, no calibration data

Are there any further advices?
Anything that we can change and try.
The communication seems to work. But there must be any other mistake we did.
Or another possibility could be a faulty device/part.

greetings
Andreas

Hi everyone,

Just wanted to let the Duet team knows that this is also something of interest to us.

But we also are at an early stage of our work regarding this matter.

@dc42
Just a quick reply...
I replaced the mosfet with:
AOSS32334C

It was a little challenging to solder but I could replace the part and the board just works fine again.

Thanks for the support.

@koreandi said in Travelspeed when using G32 & G29:

; Z-Probe G31 P45 X0 Y22 Z0.95 ; Set Z probe trigger value, offset and trigger height (G31 P25 X0 Y0 Z1.3 ) M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H10 F250 T1000 ; set Z probe type to bltouch and the dive height + speeds M557 R130 S20 ; Define mesh grid

The G31 line must come later than M558, because you can't create an offset for a tool that wasn't defined yet

@koreandi said in T1 Offset on dual extrusion:

G91 ;set to relative
G1 Z5 F9999 ;move Z 5 mm up
G91 ;set to relative
G1 Z-2 F9999 ;go back to initial Z-Position

@koreandi said in T1 Offset on dual extrusion:

G91 ;set to relative
G1 Z5 F9999 ;move Z 5 mm up
G91 ;set to relative
G1 Z-5 F9999 ;go back to initial Z-Position

These relative moves are just raising the Z further and further. raise by 5, lower by 2? That doesn't seem right?

...jay_s_uk

Thanks a lot.
I changed the code and it wors.
I used my Endstop before to home Z and just thougth I could change the direction.

🙂

I've just tested my duet 3 + SBC system and it boots up in ~35secs. I am running it with an SSD rather than an SD card (although its only a cheap £10 60gb one from amazon).
I believe the mini 5+ was due to be released around November time but I don't know if that has been pushed back.

With whats currently available if you want wifi, your options are
duet 2 wifi
duet 3 with SBC or ethernet to wifi adapter
STM32 port with either wifi or SBC