[nasa/nos3#298] OnAIR Integration #402
Conversation
…adjustments to the docker_launch script to launch OnAIR with NOS3
…are (thus far) necessary
…cessary for communication between cFS and OnAIR
…nAIR to compile alongside NOS3, instead of it having to be compiled separately but run together
…ack again, hopefully with minimal trouble
…now, it has been necessary to set USER_ID and GROUP_ID equal to 1000 to get the Dockerfile to build properly.
…ace and have the right name so as to make compiling/running as easy as possible
… sbn_tcp just yet (not sure if needed);
…op, and removed extra OnAIR submodule definition;
…ill crashing on startup;
…me Resolution. Currently doesn't seem to fully work, and should be improved in the future to be less hacky.
…ively (seems to work better than previous workaround, but still not fully integrated)
…AIR. Likely should be fixed in CMAKE later
…y to the sys path, and added __pycache__ to gitignore
…ution code for SBN and SBN-Client. Still is broken and cycle crashes cFS.
… on OnAIR Launch, added pcap to gitignore
…ug prints from C now that it is debugged.
…config to include OnAIR launch
…ackets by OnAIR through NOS3, and commented out debug prints after verification
kevincbruce
requested review from
jlucas9,
szemerick,
msuder,
Donnie-Ice,
rjbrown2,
dacarter22,
zlynch2 and
Isgaroth-the-Green
jlucas9
changed the title
There was a problem hiding this comment.
SBN_CLIENT has connection errors specifically with sbn_client_sockfd,
Full text:
sc_1 - OnAIR
Current Data Headers: ['SAMPLE. CommandErrorCount', 'SAMPLE. CommandCount', 'SAMPLE. DeviceErrorCount', 'SAMPLE. DeviceCount', 'SAMPLE. DeviceEnabled', 'SAMPLE. DeviceHK. DeviceCounter', 'SAMPLE. DeviceHK. DeviceConfig',
'SAMPLE. DeviceHK. DeviceStatus' ]
SBN Adapter ignoring data file (telemetry should be live)
SBN Client library loaded: '<CDLL 'sbn_client.so', handle 55ebdab84d10 at 0x7f25579c9870>'
SBN_Client Resolving Name sc_1_nos_fsw
SBN_Client Resolved sc_1_nos_fsw to 172.18.0.5
SBN_Client Connecting to 172.18.0.5, 2234
connect err = Connection refused
SERVER CONNECT_ERROR: Connect failed error: -1
SBN_CLIENT: ERROR Failed to get sbn_client_sockfd, cannot continue.
SBN_Client_Init error 256
SBN Client init: 256
Enter Create Pipe.
Create Pipe, PipeID Not Null. PipeID: 0
Enter Pipe Tbl If.
Pipe Info:
PipeTbl[i].PipeID: 0
PipeIDPtr: 0
PipeName: cmd_pipe
SBN Client command pipe: 0
SBN Client sbn_load_and_init pipe: c_uint(0)
SBN_Adapter Running
SBN_CLIENT: ERROR SendSubToSbn! !
SBN Client subscribe msg (id 0x8fa): 0
Terminal
NOS3 Igniter - Version ... sc_1 - OnAIR
sc 1 - NOS3 Flight Sof ...
42 Cam (on fortytwo)
2 Cam (on
42 Map (on fortytwo)
ortytwo)
42 Unit Sphere Viewe ...
here Viewe ...
NOS3 Launcher (on 8 ...
Packet Viewer : Form ...
There was a problem hiding this comment.
I have to change the duration of the wait in "scripts/onair_launch.sh" to get this to work. At 12 seconds (the value present right now) it does not work; at 20 seconds it works sometimes, and at 30 seconds it always appears to work. My suggestion would be that we leave it at a value useful for most NOS3 VMs, however, and not adjust it to suit my particular case.
It is worth indicating somewhere that this might be a problem for people, though.
|
May be worth bumping the default sleep time up to 15 or 20. Had it at that before I made it tighter in case it was waiting too long, and it did work, so may be worth making the change to that at least. I do plan to make a wiki covering the basics (where to config to grab a particular packet, how to modify that time to tune it to your VM, links to OnAIR documentation, etc) right after we push. |
Integrated SBN, SBN_Client, and OnAIR into NOS3. Verified successful data transmission across SBN and into the OnAIR vehicle_rep.py file for the Sample_HK_TLM packet, and its inset Sample_Device_HK_TLM packet. It should all work out of the box on a git pull, git submodule update --init --recursive, and make cycle.