Solved Multiple motion system homing malfunction
-
Homing files
; homex.g ; called to home the X axis ; G91 ; relative positioning G1 H1 X-550 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F6000 ; go back a few mm G1 H1 X-550 F360 ; move slowly to X axis endstop once more (second pass) G90 ; absolute positioning
; homey.g ; called to home the Y axis ; G91 ; relative positioning G1 H1 Y-460 F1800 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y5 F1800 ; go back a few mm G1 H1 Y-460 F360 ; move slowly to Y axis endstop once more (second pass) G90 ; absolute positioning
; homez.g ; called to home the Z axis ; G91 ; relative positioning G1 H2 Z2 F6000 ; lift Z relative to current position G1 H1 Z510 F1800 ; move Z up until the endstop is triggered G92 Z510 ; set Z position to axis maximum
; homeall.g ; called to home all axes ; G91 ; relative positioning G1 H2 Z2 F6000 ; lift Z relative to current position G1 H1 X-550 Y-460 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-550 Y-460 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 H1 Z510 F360 ; move Z up stopping at the endstop G90 ; absolute positioning G92 Z510 ; set Z position to axis maximum
-
daemon.g and macro files
;daemon.g while (true) M596 P1 G91 while (global.weldtorchstate == 1) G1 H4 U99999 F1000 ;selects the U axis & sets the feedrate G4 S0.2
; Weld Torch ON M42 P3 S0 ; turns on the relay to start welder M42 P4 S1 ; set U axis endstop to high ; set weldtorchstate to ON set global.weldtorchstate = 1
; Weld Torch OFF M42 P3 S1 ; turns off the relay M42 P4 S0 ; set U axis to low end ; set weldtorchstate to OFF set global.weldtorchstate = 0
-
@T3P3Tony said in Multiple motion system homing malfunction:
@SANJR please post your config.g, the homing files, daemon.g and the macros you refer to.
Hi Tony pasted the filesplz take a look .......
-
@o_lampe said in Multiple motion system homing malfunction:
@SANJR I believe you have to rethink the daemon.g code or the macros. They should only be active after x,y,z-axes are homed.
You can check for homed axes in the object model.I'm not sure where the variables for homed axis can be found, maybe someone else can chime in?
Hi
Yes you are correct. The daemon and the macros needs to be active after homing the first motion X,Y,Z axis. I have pasted all the files plz take a look......
And about checking for the homed axes in the object model? Sorry not able to understand where and how to check the object model.... Apologies i am not able to understand.......
-
@SANJR said in Multiple motion system homing malfunction:
;daemon.g while (true) M596 P1 G91 while (global.weldtorchstate == 1) ; maybe an if-condition would be better here? G1 H4 U99999 F1000 ;selects the U axis & sets the feedrate G4 S0.2 ; this delay should be related to the while(true) loop
-
-
You have no indentation in your second while statement.
-
@OwenD said in Multiple motion system homing malfunction:
You have no indentation in your second while statement.
Hi Owen,
Is it the while (global.weldtorchstate == 1) refereing to?
And indentation meaning.....could u plz show it in the code plz -
daemon.g while (true) M596 P1 G91 while (global.weldtorchstate == 1) ; maybe an if-condition would be better here? G1 H4 U99999 F1000 ;selects the U axis & sets the feedrate G4 S0.2 ; this delay should be related to the while(true) loop
-
-
@OwenD said in Multiple motion system homing malfunction:
You have no indentation in your second while statement.
Thanks Owen
By changing the indentation was able to get it right
-
@oliof said in Multiple motion system homing malfunction:
daemon.g while (true) M596 P1 G91 while (global.weldtorchstate == 1) ; maybe an if-condition would be better here? G1 H4 U99999 F1000 ;selects the U axis & sets the feedrate G4 S0.2 ; this delay should be related to the while(true) loop
Thanks Oliof
Its good now
-