On Monday 07 December 2020 14:08:00 Todd Zuercher wrote: > Mostly, I was hoping to avoid the thread delays of having to go > through hal adding 1-2 more thread cycles to the "staleness" of the > data. (Encoder read/process to velocity, Hal read from Mesa, Hal > process value/scale, Hal write back to Mesa), and was just curious if > it had been tried before. > You only get that sort of problems if the addf order in the hal file is scrambled. If the order is correct, its read data, let it fall thru the process even if its 10 modules long, the results will be written on the next write. ALWAYS do the addf in the same order as the logic handling it. That addf list IS the order the modules will be executed in. Get it right and it all gets handled in the same servo-thread cycle.
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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
