nttoole
commented
2 years ago Relevant section of AIT config updated:
dsn:
sle:
initiator_id: LSE
# password only matters if we're doing auth and can stay as 'pw'
password: pw
responder_id: SSC
# peer password only matters if we're doing auth and can stay as 'pw'
peer_password: pw
downlink_frame_type: TMTransFrame
heartbeat: 25
deadfactor: 5
buffer_size: 256000
responder_port: 'default'
rcf:
inst_id: sagr=LSE-SSC.spack=Test.rsl-fg=1.rcf=onlc2
hostnames:
- atb-ocio-sspsim.jpl.nasa.gov
- example.hostname.2
port: 5100
version: 6
spacecraft_id: 250
trans_frame_ver_num: 0
auth_level: 'none'
raf:
inst_id: sagr=LSE-SSC.spack=Test.rsl-fg=1.raf=onlc1
hostnames:
- atb-ocio-sspsim.jpl.nasa.gov
- example.hostname.2
port: 5100
version: 5
auth_level: 'none'
fcltu:
inst_id: sagr=LSE-SSC.spack=Test.fsl-fg=1.cltu=cltu1
hostnames:
- atb-ocio-sspsim.jpl.nasa.gov
- example.hostname.2
port: 5100
version: 5
auth_level: 'none'
Addresses all of the issues and recommendations listed in #139
Includes example script that runs the SLE Mgr interface for any of the supported services: raf, rcf, cltu. When connected to RAF or RCF, a log message is printed for each 'download' event. For CLTU, chunks of junk data is periodically uploaded to the CLTU service.
Fixes #139
Includes a command line service launcher for running the service and testing.
Usage of the service launcher:
Testing performed against SSPSim at http://atb-ocio-sspsim.jpl.nasa.gov:7070/ssp ..using the same setup steps as captured in examples.
RAF mode with debug transferbuffer handler:
Command:
./ait/dsn/sle/util/test/run_sle_interface_mgr_server.py --type raf --verboseRCF mode with debug transferbuffer handler:
Command:
./ait/dsn/sle/util/test/run_sle_interface_mgr_server.py --type rcf --verboseCLTU mode with simulated CLTUs uploaded: Command:
./ait/dsn/sle/util/test/run_sle_interface_mgr_server.py --type cltu --verbose --simSection of resulting log:
Note: Some "interface X brought up" messages appear after data appears to be flowing. This is due to a wait-timer in the start request before proceeding with the status message.