Tapco BLINKERBEAM Скачать руководство пользователя страница 9

Страница: 9 / 20

BlinkerBeam™ Radio Operation Guide

Note:

If this radio’s

Hop Seq. (Hop Channel)

does not match the

Hop

Seq. (Hop Channel)

of the other radios in the network, see Set

Hop Channel in the

Radio Setup Menu

Model

identifies the TAPCO radio model. See Figure 20.

FCC ID

is the regulatory number assigned to BlinkerBeam® radios by the

FCC.

is the regulatory number assigned to BlinkerBeam® radios by the IC.

See Network Table

provides additional information on the radio network.

See Figure 21.

Network Table / Radio Network Menu

To access the

RADIO NETWORK

menu, select

MAIN MENU

Radio

Status > See Network Table

See Figures 22 and 23.

RADIO NETWORK:

To the right of the title is an indicator of the radio’s

network status.

-TX-:

This radio is a transmitter. See Figure 24

NOTICE

A second transmitter makes the network non-functional. There can

only be one transmitter in a network.

SYNC:

This radio is a receiver, and the binding code and hop

frequency have been recognized in the network. See Figure 25.

NOSYNC:

This radio is a receiver, but it has no network connection.

See Figure 26.

MyDevNum:

This field indicates the radio’s network role and status:

Trnsmittr:

This radio is a transmitter. See Figure 27.

##:

This radio is a receiver that is part of the network with a

transmitter. The number may be any number in the range 1-15. Scroll

through the entire list to view all networked radios. See Figure 26.

OutofSync:

This radio is a receiver, but it is not part of a network.

See Figure 26.

Transmit

shows the 10-digit serial number of the transmitter.

See Figure 27.

Device Numbers

are 10-digit serial numbers of each receiver in the

network. See Figures 28 and 29.

Notes:

To find the 10-digit serial number for a particular radio,

see the

Controller Status

menu.

If each digit of a device number is 0, then no device is in that

network slot.

Figure 28

RADIO NETWORK -TX-
MyDevNum: Trnsmittr
Transmit: ##########
Device 1: ##########
Device 2: ##########
Device 3: ##########
Device 4: ##########
Device 5: ##########
Device 6: ##########
Device 7: ##########
Device 8: ##########
Device 9: ##########
Device 10: ##########
Device 11: ##########
Device 12: ##########
Device 13: ##########
Device 14: ##########
Device 15: ##########

RADIO NETWORK SYNC
MyDevNum: ##
Transmit: ##########
Device 1: ##########

RADIO NETWORK -TX-
MyDevNum: Trnsmittr
Transmit: ##########
Device 1: ##########

RADIO NETWORK NOSYNC
MyDevNum: OutofSync
Transmit: ##########
Device 1: ##########

RADIO NETWORK -TX-
Device 6: ##########
Device 7: ##########
Device 8: ##########

RADIO NETWORK -TX-
Device 8: ##########
Device 9: ##########
Device 10: ##########

RADIO NETWORK -TX-
Device 11: ##########
Device 12: ##########
Device 13: ##########

RADIO NETWORK -TX-
Device 10: ##########
Device 11: ##########
Device 12: ##########

RADIO NETWORK -TX-
Device 1: ##########
. . .
Device 15: ##########

RADIO NETWORK -TX-
Device 7: ##########
Device 8: ##########
Device 9: ##########

RADIO NETWORK -TX-
MyDevNum: Trnsmittr
Transmit: ##########
Device 1: ##########

RADIO NETWORK -TX-
Transmit: ##########
Device 1: ##########
Device 2: ##########

RADIO NETWORK -TX-
MyDevNum: Trnsmittr
Transmit: ##########
Device 1: ##########

RADIO NETWORK -TX-
Device 1: ##########
Device 2: ##########
Device 3: ##########

RADIO NETWORK -TX-
Device 2: ##########
Device 3: ##########
Device 4: ##########

RADIO NETWORK -TX-
Device 3: ##########
Device 4: ##########
Device 5: ##########

RADIO NETWORK -TX-
Device 4: ##########
Device 5: ##########
Device 6: ##########

RADIO NETWORK -TX-
Device 5: ##########
Device 6: ##########
Device 7: ##########

RADIO NETWORK -TX-
Device 13: ##########
Device 14: ##########
Device 15: ##########

RADIO NETWORK -TX-
Device 12: ##########
Device 13: ##########
Device 14: ##########

RADIO NETWORK -TX-
Device 9: ##########
Device 10: ##########
Device 11: ##########

Figure 27