GSE 672 - A;D Interval

Model 672/675 Technical Reference Manual
9-107
of custom transmits or database transmissions, the transmit interrupt is not enabled until the transmit is
complete or the transmit buffer becomes full. However in the case of the %$ and %& macro commands,
the transmit interrupt is not enabled by itself. Instead it requires the %q command to enable transmitter and
begin the transmission. Otherwise data will continue to collect in the transmit buffer until it becomes full at
which time the transmitter will become enabled automatically.
%
%
r
r
A
A
/
/
D
D
I
I
n
n
t
t
e
e
r
r
v
v
a
a
l
l
Syntax Set A/D Interval
< scale# > , < interval > %r
Get A/D Interval
G < scale# > %r
Wait for A/D Interval
W < scale# > %r
Arguments
scale# Select from the following scale numbers:
0 Current scale
Scale 1
Scale 2
Scale 3
Scale 4
* All scales (Set A/D Interval only)
interval A/D interval at which weight values are recalculated.
Notes
The interval is specified in terms of 1/60th second intervals with an offset of 1 (interval + 1 =
A/D conversion rate). For example, an interval of 0 results in the fastest A/D conversion
rate, 1/60th second. An interval of 1 yields a conversion rate of 2/60th second. An interval
of 59 yields 1 conversion per second.
Setpoint status is monitored and updated using the A/D interval specified for scale #1.
Set A/D Interval
< scale# > , < interval > %r
Sets the rate at which weight values for the specified scale are recalculated. Reducing the A/D conversion
rate can significantly increase macro execution speed by reducing the time the processor must spend
calculating active weight parameters. For example,
1,59%r
sets the A/D interval for scale #1 to once per second. This results in 59 fewer interrupts from the A/D
converter reporting new weight values. Consequently, more macro commands can be executed each
second.
Reducing the A/D interval is most useful when executing lengthy macro routines (see example - Changing
the A/D Interval to Increase Macro Execution Speed). However, it is important to realize that weight data
and setpoint status will not processed as often. Therefore, do not reduce the A/D interval significantly during