Revision 7.10
2/28/2012
identified, it is prudent to never run a script on the glider “unknown”; one can never tell
what specific glider may be the “unknown” glider or when Dock Server will identify it
causing the “unknown” glider to disconnect and the correct glider to connect (possibly
switching scripts).
20060901T194640 Script on glider ru12 is UNLOADED
20060901T194640 Script on glider unknown is UNLOADED
20060901T194640 Script on glider sim015 is UNLOADED
20060901T194640 Script /opt/gmc/factoryscripts/glmpc.xml on glider sim012 is RUNNING.
20060901T194640 Script on glider ann is UNLOADED
20060901T194640 Script on glider ru11 is UNLOADED
20060901T194640 Script on glider sim05 is UNLOADED
20060901T194640 Started script /opt/gmc/factoryscripts/glmpc.xml at state waitForDisconnect on glider
sim012
The following log entries detail the expected device connected to each serial port. The
file dockServerState.xml specifies these connections (refer to section 2.6). After editing
the managed serial ports or their devices in this file, it is recommended that the changes
are verified by examining this portion of the log.
For example, this Dock Server is managing three serial ports: /dev/ttyG0_13,
/dev/ttyG0_14, and /dev/ttyG0_15. In addition, Dock Server will treat port 14 as if it is
directly connected to a glider or glider simulator and ports 13 and 15 as if freewaves are
connected. Refer to section 11.3 for how Dock Server treats these devices differently.
20060901T194640 Dockserver listening to glider detector on channel: /dev/ttyG0_14 direct
20060901T194640 Dockserver listening to glider detector on channel: /dev/ttyG0_13 freewave
20060901T194640 Dockserver listening to glider detector on channel: /dev/ttyG0_15 freewave
The next log entries show Dock Server successfully opening three serial ports. The
lines with no date / time stamp are output directly from the serial port driver. If Dock
Server appears unable to communicate with gliders, this portion of the log and the
previous portion detailing portdevice associations should be checked first. The more
common reason for no Dock Server to glider communications is that the serial ports did
not open successfully (usually caused by not connecting the 4port USB serial adapter).
The next most common reason is that the configured portdevice associations do not
match the real portdevice connections (usually a configured modem or direct
association actually has a freewave connected).
Page 180 of 228