Re: Increasing scan rate to 10 kHz

[Benjamin Franksen <benjamin.franksen@helmholtz-berlin.de>]

On Thursday, November 28, 2013 14:28:20 Benjamin Franksen wrote:
> On Tuesday, November 26, 2013 17:57:43 Andrew Johnson wrote:
> > On 11/26/2013 05:20 PM, Evgeniy wrote:
> > > I can easily set scan period to 0.01 second by adding:
> > >
> > > choice(menuScan_01_second,".01 second")
> > >
> > > in dbd file.
> >
> > Note that if the IOC's processing of all the records that have
> > SCAN=.01 second takes longer than 0.01 second to execute, the scan
> > rate will drop to 10Hz automatically. The code in
> > base/src/db/dbScan.c enforces this (3.14.12.4 will not be as strict,
> > but does still limit the processing rate if it takes longer than the
> > scan period to process all the records on the scan list).
>
> I am shocked/confused.
>
> Does that mean SCAN field and menuScan semantics will change from
> 3.14.12.3 to 3.14.12.4? I thought it was agreed upon to only make bug
> fixes when increasing the patch level version (i.e. the 4th part of
> the version number). New features would have to be in 3.15 or
> 3.14.13.
>
> Could you clarify the versioning policy, please?

What I meant is the possibility to configure other scan rates by (just)
changing the menuScan definition. So the question is: is this a new
feature or this already possible in R3.14.12.x? I thought that this is a
new feature in R3.15....

Cheers
--
"Make it so they have to reboot after every typo." ― Scott Adams

Attachment: signature.asc
Description: This is a digitally signed message part.