Discussed in UA Telcon today and decided:

Because EU range is Mandatory and EU Range is a subset of the Instrument Range, then the proper test is for EU Range, not Instrument Range. Part 8 says this about clients writing values outside the EU Range:

"Similarly a Client may attempt to write a value that is outside of this range back to the server. The exact behaviour (accept, reject, clamp, etc.) in this case is Server-dependent. However, in general Servers shall be prepared to handle this. "

Therefore test cases need to be developed to accept all of the allowed behaviors (accept, reject and clamp).

Cloned to CTT to update test cases. No change required in Part 8.

The EURange is understood, values are allowed outside of the limit specified. There are already test cases for EURange that accept all of the values. The question was about instrument range - should it be treated as eurange and allow value out side of the range of an instrument, note: if an instrument range is not specified then it is the range of the datatype i.e. if the value is an int32 then the instrumentRange is the range of an Int32. So writing something outside of the instrument range is not possible. Are you proposing that no tests be run on the Instrument range other then the minimum set (i.e. hi is above low and if Eurange is present it is inclusive of the instrument range) I would think an instrument range is a hard range. values outside of it are clamped or rejected. The EuRange is the typical operating range, while an instrument range is what is possible from the device. Is this what was discussed?

Part 8 does not describe what is expect of an instrument range - the text does describe EuRange

InstrumentRange defines the value range that can be returned by the instrument.
Example: InstrumentRange::= {-9999.9, 9999.9}
Although defined as optional, it is strongly recommended for Servers to support this Property. Without an InstrumentRange being provided, Clients will commonly assume the full range according to the DataType.

EuRange is clear

EURange defines the value range likely to be obtained in normal operation. It is intended for such use as automatically scaling a bar graph display.
Sensor or instrument failure or deactivation can result in a returned item value which is actually outside of this range. Client software must be prepared to deal with this possibility. Similarly a Client may attempt to write a value that is outside of this range back to the server. The exact behaviour (accept, reject, clamp, etc.) in this case is Server-dependent. However, in general Servers shall be prepared to handle this.

The EuRange text does not apply to InstrumentRange

Discussed in call again today with Paul. Decision stands that there are no additional behavior ctt tests necessary for Instrument Range. The test for EU range that are provided is sufficient and any additional test for IR would not add any value.