The code for synchronizing a time master with NTP has been greatly +revised. It should now synchronize to NTP within about .01 seconds.. In +addition the out of sync error messages from the clients can be suppressed. +The following new vxWorks shell command is available:
+TSsetSyncReportThreshold(syncMilliseconds,syncUnixMilliseconds)+where +
error reporting threshold in milliseconds for normal UDP broadcast + synchronization messages from master to clients. The default is 0, i.e. + report all out of sync events.
+Error reporting threshols in milliseconds for synchronization message + after a TSsetClockFromUnix command has been given to the master. The + default is 10 millliseconds.
+This command can be issued on the master and on clients. The value the +client uses is the maximum of the master and client values. For example +if syncUnixMilliseconds is 0 on the master and 10 on the client than the +syncUnixMilliseconds is 10 milliseconds.
+If a client is not changed it will also resync closer to NTP but out +of sync message can not be suppressed.
+ +Data Base Request Option DBR_ENUM_STRS for the DTYP field of soft records +does not report failure. It may cause a task to crash on some board suppot +packages.
+The GNU version of getopt.c that was being included in the Win32 version of -libCom was replaced with a BSD version.
+ +The GNU version of getopt.c that was being included in the Win32 version +of libCom was replaced with a BSD version.
When a CA user asked for display or control limits as a float a 0 value was returned as -1.17549435E-38. This is now fixed.
The sequencer did not properly keep track of number of channels connected. -It now checks if it is actually connected/disconnect before it increments/decrements the counts.
+It now checks if it is actually connected/disconnect before it +increments/decrements the counts.Several device support files have been removed that were not being built by -default, some of which would not compile anyway. These are:
+ +Several device support files have been removed that were not being built +by default, some of which would not compile anyway. These are:
The access security configuration rules now accept quoted strings -where just names were allowed previously.
-A new shell command "ascar(int level)" is now available. -It produces a report of the INP channel access connections. -Level (0,1,2) produces (a summary report, summary plus unconnected channels, -summary plus report of all channels)
+ +The access security configuration rules now accept quoted strings where +just names were allowed previously.
+ +A new shell command "ascar(int level)" is now available. It produces a +report of the INP channel access connections. Level (0,1,2) produces (a +summary report, summary plus unconnected channels, summary plus report of all +channels)
The fields ZRST,...,FFST are now special(SPC_MOD). -init_record now checks to see if state strings or values are defined -during pass 0. Previously if another record had a DBR_STRING link to -an mbboRecord it thought the field was a USHORT instead of an ENUM.
+ +The fields ZRST,...,FFST are now special(SPC_MOD). init_record now checks +to see if state strings or values are defined during pass 0. Previously if +another record had a DBR_STRING link to an mbboRecord it thought the field +was a USHORT instead of an ENUM.