Usage : CONSAD is the Java Open Access Client (OAC) process which performs device consolidation in an array format. It allows you to concatenate several individual devices into a single array device. CONSAD differs from CONSAR in that component devices are only updated when there is a request for the composite device and that an offset to the composite device is applied to all of the component devices. (Note: No error words are interspersed with the data as in FRCONS.) You can view log files for CONSAD in the directory 'daesrv\\engines\files\oac'. CONSAD creates an array of device readings, without error bytes interspersed. The defining expression can be a list of subordinate devices, separated by whitespace, commas, or plus signs. There are two additional options. One is if the first device name is FILL, then this invokes special MILCW-style zero-filling of each device's field to a length specified in the last byte of the device's SSDN. The second equation option is if the equation is just one word: FAMILY. This directs CONSAD to use the last 4 bytes of the SSDN as the device index (DI) of the family device and to build the equation using all the device names contained in that family. The same expression is used for both STATUS and READING properties, but for the READING property where the FILL option is used, the length in the SSDN is multiplied by two. (This is for MILCW compatibility: it may go away in the future.) * FILL T:A0APG+T:B0APG+T:C0APG+T:D0APG+T:E0APG+T:F0APG * FILL T:A0ARP U:FILL0:0:2 U:FILL0:0:2 T:D0ARP U:FILL0:0:2 U:FILL0:0:2 * FAMILY Restart: CONSAD is restarted when its DAE is restarted. Keeper : Dennis Nicklaus
Keeper: Dennis Nicklaus
OAC Node: dce37
Now: Fri Aug 29 01:57:49 2008