Intuicom Communicator
TM
User Manual
Revision A © 2001 Intuicom, Inc.
58
September 2001
In a Multipoint system there are two critical parameters which must be set correctly to establish a
communications link:
1. The slave's Call Book must contain the serial number or Network ID of the master and/or
repeaters to which it will be communicating.
2. All radios must be set to run at the same RF data rate. Unlike point-to-point systems,
slaves in a Multipoint system do not change their RF data rate to match the master's rate.
"In bench testing several units in a Multipoint system, it appears that they are not
communicating through the Multipoint repeater. When all units are powered the slaves' Carrier
Detect lights are green, indicating a connection, yet when I unplug the repeater those slaves set
up to communicate through that repeater remain connected."
In a Multipoint system a slave will attempt to communicate with any master or repeater (which
looks like a master in a Multipoint system) that is in its Call Book. Therefore, it may be that the
slaves are communicating with the repeater when it is powered, and when it is unplugged they
are establishing a link with the master. To test whether or not this is what is occurring go into
the Call Book of the slaves which are set up to communicate through the repeater and remove the
master's serial number. When all units are powered the slaves’ Carrier Detect lights should be
green, when the repeater is unplugged the slaves should lose contact and Carrier Detect should
turn red.
"My transceivers have established a solid connection as indicated by the LEDs, yet the
application I am running is not transmitting and/or receiving data correctly."
The quickest acid test in a situation like this is to try to get the application up and running using
an RS232 null modem cable before deploying The Communicator in the field. The
Communicator essentially functions as a null modem cable. If the application will not work with
a hard wire connection then it will not work with The Communicator, and the problem lies
within the application or other hardware (such as the computer serial ports).
"I have 2 DGR-115 transceivers set up between two computers and have been unsuccessful in my
attempts to establish a link using LapLink."
At various times difficulty using The Communicator with LapLink has been documented by
Intuicom. The cause, while not confirmed, is believed to be due to LapLink changing baud rates,
which The Communicator does not support. If you encounter this problem it is recommended
that you test the link with a terminal program such as Windows 3.1 Terminal, Hyperterminal, or
Procomm. If either of these applications is used and characters typed on one computer appear on
the screen of the other computer in the link, then the transceivers are functioning properly.