Advanced Search

I am using byte2bot, and my XY axes are based on a CoreXY system.Right now, I’m trying to use homing, but when I enter the system, I can only use the XY axis after the joints are homed. However, I am unable to home both joints at the same time.Is there a way to skip joint homing and directly enter the XY system, then perform homing from there?
Like the attached picture.

Hallo PCW, 

vielen Dank für deine Hilfe

der Befehl hat folgenden Output 

cnc@cnc:~$ sudo chrt 99 ping -i .001 -c 6000 -q 10.10.10.10
[sudo] Passwort für cnc: 
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
6000 packets transmitted, 6000 received, 0% packet loss, time 5999ms
rtt min/avg/max/mdev = 0.066/0.078/0.143/0.007 ms

Bezogen auf den Takt von 1ms sind die Ping Zeiten ja eher gering. 

Was sonst kann den Watchdog Fehler auslösen?
Aus dem halcmd show param *.tmax sehe ich die Werte für read.tmax und write.tmax sind ein vielfaches höher als alle anderen Werte zusammen. Deshalb die Vermutung die Ursache liegt in der Verbindung zur Mesa Karte.

Grüße 
Erwin

 

rodw live view. Hopefully Alfred turns out to be a whole lot of not much.
Live View

what i found out in the meanwhile that at the time where the cyclic of do_homing() seem to be stopped, one of the synchronized joints is still in status "PK_PEAxisState_axHOMING_BACKING_OFF". but it allway seems to stop when the status changed to PK_PEAxisState_axHOME.

in that cas it's legit that one of them is still not homed, but for me is still unclear why the cyclic calls of do_homing() are being stopped.
the other miracle is why the flags of both joints are set to:
.homed = 1
.homing =0

edit 7 new findings:
i now tried to workaround the problemb changing the home Sequences so that the Y will get Home sequence 3. and X&X2 get home_sequence -2: that endet up that now the joint for Y doesnt get homed (i mean halui.joint.2.is-homed still shows 0)
   
that seems that it is not related to the synchronized homing sequence of joint.0 and joint.1, but more likely to the last sequence that is being homed.
and also logging showed that the cyclic calls of do_homing() (or all calls to home_comp) are being stopped right at the moment when the PulseEngine Status changed to 10 (= homed). 

as i'm quite sure that Linuxcnc motion or Halui know nothing about PE_AxisState, i think it is not the status change itself but something related to it, but i didnt see the debug message message. that do_homing() returned 1. so it is most likely something else

Yeh, I saw you had been there. Its still very normal here and Alfred has decided to be a day late.
There is some pretty rough weather to the south of us even though we are closer to the crossing point