@dc42
@Argo
I've tested the new firmware and it's ok. No bug with M291. The print was well paused during all the process.
Thank you very much !
Best posts made by noisettetbou
-
RE: filament-change.g
-
RE: U axis don't print
@sebkritikel
It works ! Thanks a lot. It's strange I need to map the driver 5 with the number 3 but the essential is that it works.
For mirror, I've put the M579 U-1 in tpost3.g and M579 U1 in tfree3.g for return to normal direction when T3 is unloaded.
Thanks again.
Latest posts made by noisettetbou
-
RE: filament-change.g
@dc42
@Argo
I've tested the new firmware and it's ok. No bug with M291. The print was well paused during all the process.
Thank you very much ! -
RE: filament-change.g
@dc42
I'm running in standalone mode with a Duet 2 wifi + Duex5. I haven't got Panel Due.It seems be the same bug that @Argo has mentionned here :
https://forum.duet3d.com/post/228870 -
RE: filament-change.g
@dc42 I don't know.
Usually I'm in dual extrusion but I've broken a heatbreak, so back to M600 -
filament-change.g
Hello,
I'm with RRF3.3beta3 and when I run M600, filament-change.g is called but the print resume between steps of the file instead of at the end of file :G91 ; relative positioning
G1 Z20 F1200 ; lift Z
G90 ; absolute positioning
M291 R"Déchargement de filament" P"Rétraction en cours..." S0 T5
G1 E-100 F900 ; Retract fast
M106 P2 S0 ; led
G4 P200 ; pause
M106 P2 S1 ; led
M291 R"Changement de filament" P"Changez de filament puis pressez OK" S2
M291 R"Changement de filament" P"Chargement en cours" S0 T12
G1 E70 F300 ; Unretract and purge
M116 ; Wait
M106 P2 S0 ; led
G4 P200 ; pause
M106 P2 S1 ; led
M291 R"Changement de filament" P"Filament changé" S2Somebody knows why ?
-
RE: Lightburn relative coordinates
@bks31
Hello. I had tried to connect to fan pin but there's not enough power for a laser of 40w.
You need to wire with a circuit like Duet says here :
https://duet3d.dozuki.com/Wiki/Laser_PWM_control
I've added a 12v power supply for the laser and now it's ok. -
RE: Lightburn relative coordinates
I've found. It was enough to write a G90 in the start code because my positioning of axis (park of X and centering of U) are in absolute coordinates.
Then Lighburn write G91 and no problem.
Is-it mean RRF turns relative mode when selecting laser mode ? -
Lightburn relative coordinates
Hello.
I've a laser on U axis (mapped on X with the laser tool selected) who works very well with Lightburn for cutting (gcode generate in absolute mode) but don't works in raster mode (relative mode). I've asked to Lightburn developper and he said it's normal his soft do that.
If I use relative mode in printer mode, no problem, but in laser mode M452, relative mode don't work (Error: G0/G1: target position outside machine limits) . An idea ? -
RE: Stall detection with 2 motors
@dc42 @Phaedrux @oliof
dc42 has reason. My voltage is enough for each axis but limit for all axis in the same time.
So i've decided to installing a Duex5. -
RE: Stall detection with 2 motors
@Phaedrux
I think too... but I would like to understand -
RE: Stall detection with 2 motors
@oliof
It's no a problem if current is respected. I use two motors on same driver in X axis and no problem. And I done as you said for trying, so there is only one motor right now, and no good stall detection...