On Fri, 7 Apr 2017, Gene Heskett wrote:
> Date: Fri, 7 Apr 2017 12:38:45 -0400
> From: Gene Heskett <ghesk...@shentel.net>
> Reply-To: "Enhanced Machine Controller (EMC)"
> <emc-users@lists.sourceforge.net>
> To: emc-users@lists.sourceforge.net
> Subject: Re: [Emc-users] for PCW?
>
> On Friday 07 April 2017 12:15:10 Peter C. Wallace wrote:
>
>> On Thu, 6 Apr 2017, Gene Heskett wrote:
>>> Date: Thu, 6 Apr 2017 22:19:56 -0400
>>> From: Gene Heskett <ghesk...@shentel.net>
>>> Reply-To: "Enhanced Machine Controller (EMC)"
>>> <emc-users@lists.sourceforge.net>
>>> To: "Enhanced Machine Controller (EMC)"
>>> <emc-users@lists.sourceforge.net> Subject: [Emc-users] for PCW?
>>>
>>> Greetings Peter;
>>>
>>> 1) This config I started out with has a watchdog.reset as a separate
>>> addf'd function which I suspect is in the leftovers that are now
>>> past their use-by date column. Can I nuke that addf entry?
>>
>> In 2.7 and > the hm2 pet_watchdog function has been merged with the
>> hm2_write function so it should no longer be called
>>
>>> 2) I'm not that familiar with threads when they are added, slower
>>> than servo threads.
>>>
>>> So, can I move the final write to the 7i90 to the end of that string
>>> of servo-thread addf's, and treat the other slower thread for my jog
>>> wheel thread stuff as independent of the servo-thread list?
>>
>> You should ba able to, this is the normal LinuxCNC operation order:
>>
>> read inputs
>> process
>> write outputs
>
> IOW, my slow thread has to have its addf list between "process"
> and "write outputs"
I think that Jon is right and the faster thread runs to completion first
before a slower thread is launched which means the order of addfs only applies
to a single thread
BTW heres a way to dump all the tmaxes:
pcw@pcw-G41M-Combo:~/linuxcnc-dev/scripts$ halcmd show param | grep tmax |
grep -v increased
23 s32 RW 0 hm2_7i76e.0.read-request.tmax
23 s32 RW 484870 hm2_7i76e.0.read.tmax
23 s32 RW 96197 hm2_7i76e.0.write.tmax
13 s32 RW 36898 motion-command-handler.tmax
13 s32 RW 92834 motion-controller.tmax
17 s32 RW 41030 pid.0.do-pid-calcs.tmax
17 s32 RW 35255 pid.1.do-pid-calcs.tmax
17 s32 RW 52240 pid.2.do-pid-calcs.tmax
17 s32 RW 27198 pid.3.do-pid-calcs.tmax
14 s32 RW 581638 servo-thread.tmax
Note that these times are all in CPU clocks
>
> So, I guess the best way to test this is to raise the slow-threads rate
> to match the servo-thread and see if that causes timeing overruns out
> the wazoo. Or set it down to really slow and see if it still works.
>
> What we need is not "hard real time" out of threads, but a way to set the
> priority of the threads it creates, and we do not now have that.
>
> Is it too late for a feature request for "soft threads" to get into 2.8
> final? This jog-wheel stuff can I'm sure, be run on leftover time as
> long as there is some "leftover" time.
>
> Thanks Peter.
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <http://geneslinuxbox.net:6309/gene>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
Peter Wallace
Mesa Electronics
(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
