Re: lexical analyzer for .db?

[Ralph Lange <Ralph.Lange@bessy.de>]

Probably only true if you want to do that scan rate change in a running 
system.

Generally: As soon as the hardware allows different scan rates, I would 
always make the appropriate SCAN fields a macro that gets substituted 
when blowing up the template database:
If you put one input plus the attached calc into a template DB file and 
set both SCAN field to $(channel_scan), you can instantiate an arbitrary 
number of those per-channel structures, specifying the scan period of 
each of them (channel_scan=".2 second") to whatever seems appropriate.

Ralph


Rodney R. Porter wrote:
> One disadvantage of this method is that if you ever want to change the scan
> rate, the change needs to be coordinated between different records.  Having
> a process chain with only 1 record setting the scan rate makes it easier if
> you ever foresee someone else wanting to change the scan rate.
>