GE MDS iNET 900, Reference Manual

Page: 64 / 188

54 iNET Series Reference Manual 05-2806A01, Rev. J
•
Fragment Threshold
—Before transmitting over the air, if a packet
exceeds this number of bytes, the transceiver sends the packet in
multiple fragments that are reassembled before being delivered
over the Ethernet interface at the receiving end. Only even num-
bers are acceptable entries for this parameter. Over-the-air data
fragmentation is not supported on AP units.
(See
“ PERFORMANCE NOTES” on Page 144 for additional
information.) [
256–1600 bytes; 1600
]
TIP: In an interference-free environment this value should be
large to maximize throughput. If interference exists then
the value should be set to smaller values. The smaller the
packet the less chance of it being interfered with at the cost
of slightly reduced throughput.
•
RTS Threshold
—Number of bytes for the over-the-air RTS/CTS
handshake boundary. (See “ PERFORMANCE NOTES” on
Page 144.) [
0 to 1600 bytes; 500
]
NOTE:
While the transceiver accepts RTS Threshold settings below
100, the lowest functioning value is 100.
TIP: Lower the
RTS Threshold
as the number of Remotes or
overall over-the-air traffic increases. Using RTS/CTS is a
trade-off, giving up some throughput in order to prevent
collisions in a busy over-the-air network.
The
RTS Threshold
should be enabled and set with a value
smaller than the
Fragmentation Threshold
described above.
RTS forces the Remotes to request permission from the
AP before sending a packet. The AP sends a CTS control
packet to grant permission to one Remote. All other
Remotes wait for the specified amount of time before
transmitting.
•
RSSI Threshold (for alarm)
—Level (dBm) below which the
received signal strength is deemed to have degraded, and a crit-
ical event (alarm) is generated and logged. Under these condi-
tions, the
PWR
lamp flashes, and an SNMP trap is sent to the
configured SNMP manager. [
0 to -120; -90
]
•
SNR Threshold (for alarm)
—Value (dB) below which the sig-
nal-to-noise ratio is deemed to have degraded and a critical
event is generated and logged. Under these conditions, the
PWR
lamp flashes, and an SNMP trap is sent to the configured SNMP
manager. [
0 to 40; Not Programmed
]
•
Channel Con fi g
(Only applies to iNET-II)
—Brings up the submenu
discussed in Channel Config Menu on Page 55.
•
RF Hopping Format
(Only applies to iNET)
—This option must be
specified when the order is placed and cannot be modified in the
field by the user. Operation must be compliant with coun-
try-specific restrictions. The available formats are: