Tuesday, May 14, 2013

Tier 2 "pre-test"

Tier 2 "pre-test"
  1.  Prior to test, I put into on_connect.mcs:
subscribe interval=60 duration=21600 list=[$altitude $heading coord.pos.sibs.ra coord.pos.sibs.dec $true_airspeed $ground_speed $latitude $longitude]
  1. Also on_alertscon.mcs the following:
watch trigger=fms.altitude min=30000 max=40000
watch trigger=fms.heading min=0 max=40
  1. Start software (MGT and GUI).
  2. Connect from GUI to ebox (MGT) by going to the GUI's Ebox Pane(Tab?) and in the Inits & Setups and click the Connect button.
  3. Click the machwinit button.
  4. Click on the  Ebox I/O Pane and type in the Command text box:
1 debugtele
3 loglevel
  1. Connect to SSC SIL from the Telescope: dropdown on the bottom right
  2. You should see something like this in log window
>>150: obsconnect
MCS 10.4.1.17:6555 
connecting main to MCS machine 10.4.1.17, port 6555
MCS main input opened
main got: 117 A 
main got: 117 : 
main got: 118 A 
main got: 118 I das.ins_1_25hz.hybrid_alt=2587.000000 das.ins_1_25hz.hybrid_true_heading=89.999374 coord.pos.sibs.ra=23h48m47.069s coord.pos.sibs.dec=87d51m05.569s das.adc_1_8hz.true_airspeed=0.000000 das.ins_1_25hz.hybrid_ground_speed=0.000000 das.ins_1_12hz.hybrid_lat=34.6135523790000 das.ins_1_12hz.hybrid_lon=-118.0754739010000
Error in send-receive to MCS: "subscribe interval=60 duration=21600 list=[$altitude $heading coord.pos.sibs.ra coord.pos.sibs.dec $true_airspeed $ground_speed $latitude $longitude]"
  1. then later such things as this: (every 60 seconds)
main got: 118 I das.ins_1_25hz.hybrid_alt=2587.000000 das.ins_1_25hz.hybrid_true_heading=89.999374 coord.pos.sibs.ra=23h49m47.866s coord.pos.sibs.dec=87d51m08.270s das.adc_1_8hz.true_airspeed=0.000000 das.ins_1_25hz.hybrid_ground_speed=0.000000 das.ins_1_12hz.hybrid_lat=34.6135523790000 das.ins_1_12hz.hybrid_lon=-118.0754739010000

Next I want to write FITS file and see if the matching entries that change with the incremental (I) MCCS responses to the subscribe command.  We can use fake data if we want.  So this is not quite ready for prime time

No comments: