Posts made by gavatron3000

the stl's arent a requirement, but they only help in the situation when T4 is out of filament and the 50cm or so of left over filament is ejected out the front of the machine if you know what i mean. with the standard selector it will foul in this situation. i havent finished this yet as a filament runout on T4 is very low percentage of my issues but i will do this eventually

@computiger said in Multi color printing with Prusa's MMU V2 & Duet?:

@gavatron3000 said in Multi color printing with Prusa's MMU V2 & Duet?:

https://docs.google.com/document/d/13r_6BTYTO-xlD6cQeNwOx4qeCEYYGrxOcHc0mC-tT8Q/edit?usp=drivesdk

Hmm...

I didn´t understand as I have to.
Can somebody tell me where I have to plug in the Pinda probe. For now I putted him to E0 Endstop, but I can´t home the selector (drive U).

In the description I have to plug him to V but

Here some details of config.g

; Endstops
M574 X1 Y1 S1 ; Set active high endstops
M574 U1 V1 W1 S3 ; Set additional axes as sensorless endstops
M574 Z1 S2 ; Set endstops controlled by probe

;Drives
M569 P4 S0 ; Drive 4 goes backwards V
M569 P5 S1 ; Drive 5 goes forwards U
M569 P6 S0 ; Drive 6 goes backwards W
M584 X0 Y1 Z2 E3 V4 U7 W6 ; Apply custom drive mapping

the pinda is used as the V axis endstop in certain situations during loading so it must be plugged into that axis endstop input. U axis uses sensorless homing

ok no worries are we able to support it at the end of tpre and tfree instead?

@dc42 did you see my post above regarding m291?

@dc42 the m291 isn't unlocking a tool change still when called. Or is this impractical to do within a tool change?

My genuine smart bltouch has repeatability below 0.03. I had some issues which I found to be my z jerk was too high. I assume was during the z axis retract move causing it for me.

I'll push the firmware today and test also. But there's been no changes to M291 is that correct? It didn't unlock movement of the tool change in RC1.

unfortunately theres no change in the behaviour of M291 during a tool change, the message comes up at the instance the m291 is called but the tool change will continue until its finished

I put a fly back diode on my pump and run it from the heater output. Works a charm. I bought an in rush thermistor but haven't installed it and it's been fine so far. Average 7 amps inrush and settles around 1 amp when at speed

@elmoret said in Duet3D-2 New install uncertainties:

@dc42 said in Duet3D-2 New install uncertainties:

I think the reason nobody has ported any other firmware to the Duet is that RRF is so hard toi beat. Whereas RRF has been so successful that others have already ported it to LPC1768/1769 boards, and a port to STM-based boards is under way.

Gotta say I agree with that. No way I'd go back to Marlin after experiencing RRF.

100%

Ok no worries

Hmmmm. So whats the trigger for it to function thats the bit I'm missing or haven't understood

Ok so I've misinterpreted the behaviour of the filament-change.g.
So when the filament runs out a pause.g is called then when I intervene I'm meant to run M600? Woops I didn't realise

to be honest ive never manually sent a M600, im refering to when a filament out situation is detected during a print

Pause.g
pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool on Mon Feb 19 2018 19:56:04 GMT+1100 (AEDT)
M83 ; relative extruder moves
G1 E-5 F2000 ; retract 5mm of filament
G91 ; relative positioning
G1 Z10 F360 ; lift Z by 5mm
G90 ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0

Filament-change.g
T-1 ; deselect tool to unload filament
G90 ; absolute moves
G1 U75 F2000 ; move selector out of the way
G1 V900 F5000 ; drive filament out the front of MMU2
G1 W78 F10000 ; move W axis to safe position
M291 P"remove old filament, load new filament and press OK" R"Filament has run out" S2 ; display message to change filament Filament has run out
T R1 ; select previous tool
M24 ; resume print

Yes exactly, but I've got gcode in my filament-change.g macro and it still just pauses

Hey just curious if anyone else has had issues with getting filament-change.g to work? I've got the macro in the /sys/ folder but it won't use it. I'm sure I've missed setting something up. I'm on v2.03b3

Apart from the m291 issue I raised above. CoreXZ running normally. Just completed a 4 hour print

thank you

M291 doesnt pause a tool change if the message is blocking ie M291 S2, the message now appears at the correct time but the tool change carrys on anyway until completed.