climode-iss2: Logbook Entries

climode-iss2: INFO Messages: 2 Entries..

Return to Logbook Contents Page
Entry Date Title Site Author #Graphics
24 Wed 28-Feb-2007Tilt sensorRV KnorrGary
23 Wed 28-Feb-2007POP Ship DataRV KnorrGary


24: INFO, Site RV Knorr, Wed 28-Feb-2007 21:04:34 GMT, Tilt sensor
The tilt sensor is being sampled and recorded at 10 Hz on the display manager
computer by a process called 'dsm'.  The dsm program is controlled by the
script /iss/etc/init.d/dsmctl.  That script can also be run as 'tilt'.  So
run 'tilt' to get usage info.  The tilt sensor recording should start
automatically when the ISS display manager boots, same as any other ingest
process.  The real-time tilt data can be displayed from any terminal 
window by running 'tilt dump'.  Type Ctl-C to interrupt the dump.

If the data look bad, stuck, or the dsm program is not running (as indicated
by 'tilt dump' reporting "Connection refused"), then try restarting the
tilt sensor with 'tilt stop; tilt start'.  You can also try cycling the
power on the tilt sensor by unplugging the power cord from the silver power
supply box behind the ISS display manager keyboard.

23: INFO, Site RV Knorr, Wed 28-Feb-2007 20:57:57 GMT, POP Ship Data
POP expects ship navigation data to appear in C:\radar\cns.  There is a 
script on the profiler PC called shipdat.py, and a shortcut to it on the
desktop.  There is a copy of that shortcut in the Startup folder, so that
the script starts when the iss user logs in.  The script just runs and echoes
the raw navigation data to the console window, and it writes to the ship.dat
file.  If it is ever not running, just double-click the shortcut icon in the
lower left corner of the desktop that looks like a snake.  It is ok to try
to run it while it is already running; in that case it will just exit without
interrupting the already running instance.

While POP is running, POP displays in the lower right the median filtered 
ship data read from ship.dat.  So it is a good idea to periodically check
those values and make sure they are consistent with the current data on the
ship's real-time data display, either on the video monitors or the web page.
They will not match exactly thought, because the ship.dat values are a median
of the last 30 seconds of ship data, so they lag behind the real-time values.