Thanks for your answer. If I don't place another HSCDEF within a function of previous HSCDEF statement's function. It will fire over and over if it dither's around a particular set point in the counter. My thoughts maybe are better explained with an example.
HSCDEF 1,1,1000
Function 1
OUTPUT[1]=0
REFRESH
....
....
....
Now as the HSC counter(connected to an encoder) moves back and forth dithering around the set point firing function 1 over and over. Can this cause a problem even if there isn't a re-entrant function possibility can this make the same function fire at a proportional frequency of the dither around the set point?
What technical ramifications would this have at high frequency, large function size or both?
I know this kind of operation could be desirable especially if a particular location from encoder data was desired from a moving table or gantry mechanism across a given set point. It's fine if its desired motion that caused the firing of the function, if a dither around the setpoint for whatever reason caused it, it may be undesirable.
I am sure it can be cured by placing this statement in function 1 at the beginning.
HSCDEF 1,15,-4545434 //whatever count cannot occur in the system.
Just trying to get my head around these situations without too much programming or machine connections, just thinking.