![Teledyne Dock Server User Manual Download Page 134](http://html.mh-extra.com/html/teledyne/dock-server/dock-server_user-manual_1080796134.webp)
Revision 7.10
2/28/2012
Note that there are also
virtual
serial ports which service RUDICS Internet
Communications. They appear as net/<0>. This section does
not
apply to the virtual
serial ports. See section 12, Internet Communication: Iridium RUDICS.
Devices behave differently in the areas of character transmission and Carrier Detect
support. Although the glider can transmit characters at 115,200 baud, it suffers from
“buffer overrun” when receiving characters at this rate. In the context of servicing all its
tasks, the glider’s main persistor simply can not consume the characters in the
hardware receive buffer fast enough. Thus, the glider appears to drop received
characters at 115,200 baud.
For freewave devices, Dock Server solves this overrun issue by verifying that each
character sent to the glider is echoed by the glider. Once Dock Server receives a
character’s echo, it sends the next character and waits to receive its echo. Simply
adding a delay between sending characters does not work since the communicating
freewaves have their own character buffers and transmission timing. For direct devices,
Dock Server uses the intercharacter delay approach to solve this overrun issue. For
modem (Iridium) devices, this issue does not occur due to the inherent low baud rates.
Typically, Dock Server monitors the Carrier Detect (CD) line to determine when a glider
is initiating and terminating communication. When the CD line transitions low to high,
Dock Server assumes a glider is initiating communication and notifies all Glider
Terminals accordingly. When the CD line transitions high to low, Dock Server assumes
a glider is terminating communication and again notifies all Glider Terminals. This
approach to determining glider to Dock Server communication status works for modem
and freewave devices since they support CD. However, since direct devices do not
support CD, Dock Server treats gliders connected by a direct device as always in
communication with the Dock Server. That is, in Glider Terminal, the icon next to such
a glider is never red – regardless of whether or not a glider simulator is actually
attached.
11.4 How Does Dock Server Recognize a Glider
Dock Server performs many functions that depend on knowing a glider’s name. Among
these functions are notifying Glider Terminals when a specific glider has connected and
disconnected and sending glider status emails to that glider’s subscribers.
Page 134 of 228