Dual Markforged :idle IDEX carriage is not still during print
-
@martin7404 said in Dual Markforged :idle IDEX carriage is not still during print:
Muldex
Looks very similar to what I suspected. Forgive me, as I am not an expert in the Markforged kinematics system (or even CoreXY at that). Can you spot any errant rotation on the U-stepper motor during those motion changes?
The response of the U axis is consistent with the direction changes on combined tool 0 motion - mechanical, belt, etc? Unfortunately I don't have any specifics tips I could offer you at this time.
-
@sebkritikel Yes everything looks OK. There is more it exactly the same when U is printing and X have to be idle, then X is making the same small movement back and forth. So I suspect a problem with one of the Y motors setup or in the electronics
-
@martin7404 Maybe a long shot, but can you try tweaking the
M84 S120 ; Set idle timeout
command? S1000? Just a guess -
@martin7404 said in Dual Markforged :idle IDEX carriage is not still during print:
M350 X16 U16 Y16 Z16 E16:16 I1
Maybe I'm wrong, but IMHO the U-axis specs (and other axis, if there are any) have to come after Z-axis.
Not sure, if that was M350-related or another command...
Better do it in the right order in every command. -
It is getting more and more interesting.
Today moved the Z motors to Wifi and X,Y,Y and u on DUEX
And my center Z , connected on P2 is not working, switched to P0 same story, made a mistake in updating config and it works look at this config.g, it is working properly, but it should notG90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Muldex" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives ;M569 P0 S0 ; X physical drive 0 goes backwards M569 P1 S1 ; Z M569 P2 S1 M569 P3 S0 ;M569 P1 S0 ; Y right physical drive 1 goes backwards ;M569 P2 S1 ; Y left physical drive 2 goes forwards ;M569 P3 S1 ; U physical drive 3 goes forwards M569 P4 S1 ; E1 physical drive 4 goes backwards M569 P5 S0 ; X M569 P6 S1 ; Y right M569 P7 S0 ; Y left ;M569 P5 S1 ; Z left physical drive 5 goes backwards ;M569 P6 S1 ; Z center physical drive 6 goes backwards ;M569 P7 S0 ; Z right physical drive 7 goes forwards M569 P8 S1 ; E2 physical drive 8 goes forwards M569 P9 S1 ; U M584 X5 Y6:7 U9 Z1:0:3 E4:8 ; set drive mapping M350 X16 U16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation M92 X100 U100 Y100 Z799.2:799.2:799.2 E813.07:830.00 ; set steps per mm (1760nimble) M566 X600.00 U600.00 Y600.00 Z80.00:80.00:80.00 E100.00:100.00 ; set maximum instantaneous speed changes (mm/min)(Nimble 40) M203 X12000.00 U12000.00 Y12000.00 Z1000.00:1000.00:1000.00 E4200.00:4200.00 ; set maximum speeds (mm/min) M201 X800.00 U800.00 Y800.00 Z350.00:350.00:350.00 E600.00:600.00 ; set accelerations (mm/s^2)(500)(Nimble 120) M906 Y700 Z700:700:700 E1000:1000 I50 ; set motor currents (mA) and motor idle factor in per cent(Nimble 500) M906 X700 U700 I50 M84 S120 ; Set idle timeout ; Axis Limits M208 X-18 Y0 U40 Z0 S1 ; set axis min - adjust X to align nozzle M208 X350 U422.7 Y333 Z300 S0 ; set axis max M669 K0 Y1:1:0:1 ; select Markforged Kinematics Y to react with X and U ; Endstops M574 X1 S1 P"xstop" ;X axis active high endstop switch ;M574 Y2 S1 P"ystop+e1stop" ;Y Double max active high endstop switch M574 Y1 S4 ; configure sensorless endstop for low end on Y ;M574 Y1 S4 ; configure sensorless endstop for low end on Y M574 U2 S1 P"e0stop" ;U axis active high endstop switch ;M574 Z2 S4 ;Stall Detection(no used) ;M574 Y1 S4 ; Y axis stall detection ;M915 P1:9 S3 F1 R0 ; Y axis stall detection ; Z-Probe M671 X-20.6:200:420.6 Y14.3:333.3:14.3 S10 ; Locations left, center, right M950 S0 C"duex.e6heat" ; create servo pin 0 for BLTouch M558 P9 C"zprobe.in+zprobe.mod" H10 F600 A1 T8000 ; set Z probe type to bltouch and the dive height + speeds G31 P25 X-29 Y0 Z0.80 ; set Z probe trigger value, offset and trigger height(lower number farther away)1.8build 1.7glass M557 X10:320 Y20:290 S60 ; probe from X=10 to 390, Y=10 to 290mm with a mesh spacing of 20mm ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4534 C9.565227e-8 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C0 R4700 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M308 S2 P"e1temp" Y"thermistor" T100000 B4725 C0 R4700 ; configure sensor 2 as thermistor on pin e1temp M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2 M143 H2 S280 ; set temperature limit for heater 2 to 280C M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off M950 F3 C"duex.fan8" Q500 ; create fan 3 on pin duex.fan8 and set its frequency M106 P3 S1 H2 T45 ; set fan 3 value. Thermostatic control is turned on ; LEDs M950 F4 C"duex.fan6" ;Q500 ; create LED 4 on pin duex.fan6 and set its frequency M106 P4 S128 H-1 ; set LED 4 value. Thermostatic control is turned OFF M950 F5 C"duex.fan7" ;Q500 ; create LED 5 on pin duex.fan7 and set its frequency M106 P5 S128 H-1 ; set LED 5 value. Thermostatic control is turned OFF ; Tools M563 P0 D0 H1 F0 S"Left" ; define tool 0 Left G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets y was .45 G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 D1 H2 X9 F2 S"Right" ; define tool 1 Right G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets - adjust Y to alignn nozzle G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 D0:1 H1:2 X0:9 F0:2 S"Copy" ; define tool 2 Copy G10 P2 X90 Y0 U-90 S0 R0 ; set tool 2 axis offsets (WAS 105) M567 P2 E1:1 M568 P2 S1 ; turn on mixing for tool 2 ; set mix ratio 100% on both extruders ;G10 L1 P1 X0.0 Y0.0 Z-2.55 M501 ; Record
This config is working OK,
But in M569 P2 is active and P0 is not active
IN M584 P0 is assigned and P2 not ?????
and this is working
something is wrong with my DUET wifi for sure -
Can you send M98 P"config.g" and post the results?
Z799.2:799.2:799.2
Remove the duplicate entries for the Z axis. All the linear axis are configured as a single axis. It's only the extruders which remain independent and need to be configured per driver.M906 Y700 Z700:700:700 E1000:1000 I50
There appears to be an extra space after M906. Not sure it matters.You can send the motor config commands by themselves to check that they are configured as expected. For instance, sending M906 in the console to see what the motor currents are actually set to.
-
@sebkritikel i tried 100 % idle current, no change
-
M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C The M568 command is no longer needed Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 723C Warning: Heater 2 appears to be over-powered. If left on at full power, its temperature is predicted to reach 528C
-
@Phaedrux ```
m906 Motor current (mA) - X:700, Y:700, Z:500, U:700, E:1000:1000, idle factor 50% 3/8/2021, 11:35:56 PM M98 P"config.g"
-
@martin7404 said in Dual Markforged :idle IDEX carriage is not still during print:
m906
How bout for the other commands? M92 M305 M201 M203 etc etc
-
m203 Max speeds (mm/min): X: 12000.0, Y: 12000.0, Z: 1000.0, U: 12000.0, E: 4200.0:4200.0, min. speed 30.00 3/9/2021, 7:12:00 AM m201 Accelerations (mm/sec^2): X: 800.0, Y: 800.0, Z: 350.0, U: 800.0, E: 600.0:600.0 3/9/2021, 7:11:43 AM m950 Error: M950: exactly one of FHJPS must be given 3/9/2021, 7:11:32 AM m308 Error: M308: missing parameter 'S' 3/9/2021, 7:11:21 AM m305 Error: M305: M305 has been replaced by M308 and M950 in RepRapFirmware 3 3/9/2021, 7:05:16 AM m92 Steps/mm: X: 100.000, Y: 100.000, Z: 799.200, U: 100.000, E: 813.070:830.000 3/9/2021, 7:03:45 AM Connection established
-
I have a solution of the problem by chance.
I am still waiting for my new Duet wifi , and the setup is the strange one with Z on duet and X,y and U on Duex.
Because the machine is working somehow I continued with the commissioning I started Dual material print with both tools and in the begining of gcode both tools are defined temps with G10 and then with Tn P0 , both are activated for a moment in order to reach standby temp. Then G28 G29 etc....
It happens that when both tools are activated and the idle is on standby there is no movement in stanby tool -
My new duet wifi is here , installed, updated firmware to 3.2.2, X,Y,U axes are back on mainboard, first print ongoing
-
So it is printing with U carriage at the moment an the X carriage that is standby is dead still during print
-
@martin7404 said in Dual Markforged :idle IDEX carriage is not still during print:
So it is printing with U carriage at the moment an the X carriage that is standby is dead still during print
Assuming you home both carriages before doing a print, then both motors should have current flowing in them, unless you subsequently use M18 or M84 to set one or more motors idle.
-
@dc42 in the start G code there is always homing X U Y Z. But when I enable only Left or Right extruder with G10 in the beginning, during print the tool that was not active was moving a little back and forth with Y-axis changing direction.
Then I found a faulty mainboard
......
The whole time there was no unactivated axis motorSo I think it is now sorted with new mainboard