On Fri, 2 Feb 2024, Marius wrote:
Date: Fri, 2 Feb 2024 10:32:54 +0200 From: Marius <[email protected]> Reply-To: EMC developers <[email protected]> To: Alec Ari via Emc-developers <[email protected]> Subject: Re: [Emc-developers] Repositories for buildbot on bullseyeMore information regarding this issue This is the max timings at startup of linuxcnc running Gmoccapy Parameters: Owner Type Dir Value Name 56 s32 RW 32713 comp.0.tmax 56 s32 RW 21741 comp.1.tmax 56 s32 RW 21649 comp.2.tmax 56 s32 RW 15801 comp.3.tmax 56 s32 RW 6484 comp.4.tmax 36 s32 RW 0 hm2_7i96s.0.read-request.tmax 36 s32 RW 937642 hm2_7i96s.0.read.tmax 36 s32 RW 79396 hm2_7i96s.0.write.tmax 29 s32 RW 35491 motion-command-handler.tmax 29 s32 RW 80781 motion-controller.tmax 39 s32 RW 22747 pid.b.do-pid-calcs.tmax 39 s32 RW 32665 pid.c.do-pid-calcs.tmax 39 s32 RW 36771 pid.s.do-pid-calcs.tmax 39 s32 RW 35744 pid.x.do-pid-calcs.tmax 39 s32 RW 32242 pid.y.do-pid-calcs.tmax 39 s32 RW 45865 pid.z.do-pid-calcs.tmax 30 s32 RW 1022059 servo-thread.tmax Then this is the max timings right after the crash Parameters: Owner Type Dir Value Name 56 s32 RW 93620 comp.0.tmax 56 s32 RW 21866 comp.1.tmax 56 s32 RW 30257 comp.2.tmax 56 s32 RW 21831 comp.3.tmax 56 s32 RW 22149 comp.4.tmax 36 s32 RW 0 hm2_7i96s.0.read-request.tmax 36 s32 RW 941321 hm2_7i96s.0.read.tmax 36 s32 RW 163732 hm2_7i96s.0.write.tmax 29 s32 RW 52368 motion-command-handler.tmax 29 s32 RW 152143 motion-controller.tmax 39 s32 RW 45604 pid.b.do-pid-calcs.tmax 39 s32 RW 46064 pid.c.do-pid-calcs.tmax 39 s32 RW 93254 pid.s.do-pid-calcs.tmax 39 s32 RW 37166 pid.x.do-pid-calcs.tmax 39 s32 RW 48941 pid.y.do-pid-calcs.tmax 39 s32 RW 45865 pid.z.do-pid-calcs.tmax 30 s32 RW 1031395 servo-thread.tmax Take note of the motion controller and the hm2_7i96s.0.read.tmax threads.
What is the CPU clock speed? Peter Wallace Mesa Electronics _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
