Test.ini - Studer OnAir 3000 Service Instructions Manual

Digital mixing system
Hide thumbs Also See for OnAir 3000:
Table of Contents

Advertisement

Compact SCore Technical Info
The third area starts with the tag <I2CBoundaries> and ends with </I2CBoundaries> respectively. In this area
the user may specify boundaries for the voltages and temperatures read via the I2C-Interface (see chapter YY
"Live Monitoring"). For each of the seven values there exist two boundaries, lower and upper. Those values are:
5V, 3.3V, 2.5V, 1.8V, 1.5V, temperature of the Vdca and temperature of the DSPs. The syntax is as follows:
( Value lower upper )
In case an error occurs when reading those values, the user is warned and internal values are used. Those
internal values are:
For the voltages the boundary is 5% plus or minus the expected value. For the temperatures the boundaries are 0
and 65 degrees Celsius. To check what the currently set boundaries are, select View->I2CBoundaries from the
menu.

5.3.2 test.ini

This file specifies which tests and with which parameters those tests are executed in a batch test. The syntax is
similar to the one in cts.ini; except one difference. There are no tags, but to specify the two global parameters
TestCard and MirrorCard a similar syntax is used. This is subject to change in the next release since the syntax
should be uniform.
Here it goes:
<TestCard testCard>
<MirrorCard mirrorCard>
with testCard and mirrorCard both representing numbers between "0" and "5". They do what you expect. In
addition you specify a testcase as follows:
( testID processorID duration )
With: testID: one of the values specified in cts.ini, area <TestTypes>
processorID: one of the following
0 – All DSPs
1 – DSP1
2 – DSP2
3 – DSP3
4 – DSP4
5 – DSP5
6 – DSP6
7 – SH4
duration: with 0 – until user presses STOP or any positive number specifying the
duration in seconds
A valid example would be:
( 502 0 3 )
Caution: Don't change the syntax or capitalizations; also take care to keep the white spaces after opening
brackets and before closing brackets. To comment out the rest of a line write "#". To comment out the
rest of the file, write a single "*" into one line.
18/22
STUDER Professional Audio GmbH
13.Feb.06

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents