6/14/93

patch to v02.05.08 for:

(1) crn 296: bogus sync lost/sync found message in async_char and ip protocols

(2) crn 298: unable to set line speed in async_char receiver task

(3) crn 299: 

    (3.1) fifteen_53_lr bus controller reading sub address up to # 30 and
          incorrect computation of # of subaddresses

    (3.2) addition of user control delay between two accesses of sub address
          10 to 25 when the xfer size is greater than 8192 bits. This is
          be controlled by a latest_data entry (default value is 0):

EXTERNAL_ELEMENT 	=> Name of the stream
ITEM_NAME		=> DELAY_BETWEEN_RE
DATA_CLASS		=> NUMERIC
EU_UNITS		=> DN
DN_LOW			=> delay expressed in millisecond: 20 for 20 mills
                           (note:the resolution of the delay is about 10 mills)

Note: The user should make sure that the sum the delay in the "sample" 
statement and this delay * ((number of access to sub address 10 to 25) - 1) is
lower that the RT production rate.

(4) crn 297:

With this patch, the set up of an IEEE-488 application is as follows: 

(1) Single Board Application

The set up described in the release notes for OASIS-CC v02.05.06 applies.
But, make sure that when using NI's ibconf, the devices are named (in /dev) 
dev1 to devxx and that you can read/write the devxx files from the account 
where OASIS-CC is run.

(2) Multiple or Single Board Application

This set up is mandatory for multiple board application and may be used in
single board application:

(2.1) All the devices (even listerner only devices) MUST BE declared as
secondary streams.

(2.2) The devices description SHALL NOT be entered in the 
IEEE_DEVICE_DESCRIPTIONS table.

(2.3) The devices descriptions shall done using NI's ibconf program, with the
"devx" devices being renamed with the names used in OASIS-CC, in UPPERCASE.