Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Run NOS3 Example with COSMOS and 42 on different VM #83

Closed
kabarr opened this issue Sep 22, 2022 · 14 comments
Closed

Run NOS3 Example with COSMOS and 42 on different VM #83

kabarr opened this issue Sep 22, 2022 · 14 comments
Assignees
@jlucas9 @msuder

Comments

@kabarr
Copy link

kabarr commented Sep 22, 2022

I've created 2 VMs and successfully changed settings to run COSMOS and 42 on one machine and the Sims on another. I've run into a snag that may not be possible to fix. The truth42Sim data is all 0's in the sim, and the 42 satellite location is "static". I suspect this is due to me not understanding all the connections between 42 and the sim. Is it possible to run 42 on a different machine?
@jlucas9
Copy link
Contributor

jlucas9 commented Sep 23, 2022

Hi @kabarr,
It should certainly be possible to run them in different VMs. I'm working now on dockerizing the simulators in issue #78, but it's a slow process. 42 should be directly feeding data to the simulators via the sim_common/src/sim_data_42_socket_provider.cpp interface. The simulators will timeout if they cannot connect to 42 if I remember correctly - maybe that's what's occurring?

@kabarr
Copy link
Author

kabarr commented Sep 26, 2022 via email

@jlucas9 jlucas9 moved this to Planned Next Release in NOS3 Path Forward Sep 29, 2022
@jlucas9
Copy link
Contributor

jlucas9 commented Oct 7, 2022

Quick update - I have been able to duplicate this issue on my side and am working with some other experts to debug!

@jlucas9 jlucas9 self-assigned this Oct 7, 2022
@kabarr
Copy link
Author

kabarr commented Oct 7, 2022 via email

jlucas9 added a commit that referenced this issue Oct 11, 2022
@jlucas9
[#83] Split startup scripts into VM0 and VM1 and update configuration…
7a66dab 
…s based on a special NOS3 NAT;
@jlucas9
Copy link
Contributor

jlucas9 commented Oct 11, 2022

^ From the nos3#83 branch 7a66dab:

  • vagrant up to deploy the VM
  • vagrant halt to shut it down
  • Inside the Oracle VM VirtualBox Manager
    • Tools > Network > Add
      • Network Name: NOS3
      • Network CIDR: 192.168.100.0/24
    • Edit the nos3_1.5.2 settings
      • Network > Adapter 1 > NAT Network > NOS3
    • Manually cloned the nos3_1.5.2 VM in the Oracle VM VirtualBox Manager
    • Updated cloned VM settings:
      • Network > Adapter 1 > Advanced > Adapter Type > Intel PRO/1000 MT Server
      • Note that this is different than the default provided to ensure it gets recognized as a different on the network

To summarize I've got:

  • NOS3 NAT setup in VirtualBox
  • VM0 - FSW and Simulators
  • VM1 - 42 and COSMOS (not setup)

I am getting valid 42 data in the truth simulator. If we want to get COSMOS running too in this branch let me know and I can fix it up.

@kabarr
Copy link
Author

kabarr commented Oct 17, 2022 via email

@kabarr
Copy link
Author

kabarr commented Oct 19, 2022 via email

@jlucas9
Copy link
Contributor

jlucas9 commented Oct 20, 2022

Final step for this issue is to (from the new dev branch 59e8ec6) recreate the above and get COSMOS command and telemetry working. @msuder

@kabarr
Copy link
Author

kabarr commented Oct 20, 2022 via email

@jlucas9 jlucas9 moved this from Planned Next Release to In Progress in NOS3 Path Forward Oct 20, 2022
msuder added a commit to nasa-itc/truth_42_sim that referenced this issue Oct 21, 2022
@msuder
nasa/nos3#83 - Add the ability for COSMOS to be on a different machin…
3bb86ae 
…e (not localhost) than the truth sim.
msuder added a commit that referenced this issue Oct 21, 2022
@msuder
#83 - Submodule pointer update: Add the ability for COSMOS to be on a…
d8f113b 
… different machine (not localhost) than the truth sim.
msuder added a commit that referenced this issue Oct 21, 2022
@msuder
#83 - Enable 42 map, orrery, and unit sphere windows.
278da2d
msuder added a commit that referenced this issue Oct 21, 2022
@msuder
#83 - Increase graphics window update period.
aca8372
msuder added a commit to nasa-itc/gsw-cosmos that referenced this issue Oct 21, 2022
@msuder
nasa/nos3#83 - Configure COSMOS to send/receive commands/telemetry fr…
9e5b0ec 
…om flight software/CI_lab/TO_lab on another VM.
msuder added a commit that referenced this issue Oct 21, 2022
@msuder
#83 - Configure NOS3 so FSW and sims run on one VM and 42 and COSMOS …
df95b32 
…run on another VM.
@msuder
Copy link
Contributor

msuder commented Oct 21, 2022 •
edited
Loading

DUAL VMs: nos3 repo, branch nos3#83-DualVM (with submodule cosmos branch nos3#83-DualVM) has been configured so that flight software (FSW) and simulators run on one VM with IP address 192.168.100.4 and 42 and COSMOS run on another VM with IP address 192.168.100.5.

The following files/commands have been modified so that FSW/sims run on 192.168.100.4 and 42/COSMOS run on 192.168.100.5:

  • sims/cfg/nos_engine_server_config.json
    -- configure the nos3 server URI to use 192.168.100.4:12001
  • sims/cfg/nos3-simulator.xml
    -- configure the nos-connection-string to be 192.168.100.4:12001
    -- configure the data-provider hostname to be 192.168.100.5 for each simulator (to connect to 42)
    -- configure the COSMOS IP for the truth simulator to be 192.168.100.5
  • sims/cfg/InOut/Inp_IPC.txt
    -- configure the server hostname to be 192.168.100.5 (for each 42 port that is used for a simulator)
  • sims/cfg/InOut/Inp_NOS3.txt
    -- configure the NOS3 time connection string to use 192.168.100.4:12001 (42 time connection)
  • config/tools/cmd_tlm_server/nos3_cmd_tlm_server.txt
    -- configure the MISSION_INT interface to connect to 192.168.100.4 (COSMOS to FSW/CI_LAB/TO_LAB connection)
  • COSMOS command: CFS TO_ENABLE_OUTPUT with DEST_IP '192.168.100.5', DEST_PORT 5011
    -- configure FSW/TO_LAB to send telemetry to COSMOS at IP 192.168.100.5

@msuder
Copy link
Contributor

msuder commented Oct 21, 2022

Useful for assigning static IPs to VMs: https://ernieleseberg.com/virtualbox-with-static-ip-on-ubuntu-server-guest/

msuder added a commit that referenced this issue Oct 21, 2022
@msuder
#83 - Configure NOS3 so FSW/NOS Engine Server runs on one VM, sims ru…
505ba24 
…n on another VM, 42 runs on another VM, and COSMOS runs on a fourth VM.
@msuder
Copy link
Contributor

msuder commented Oct 21, 2022 •
edited
Loading

QUAD VMs: nos3 repo, branch nos3#83QuadVM (with submodule cosmos branch nos3#83-DualVM) has been configured so that flight software (FSW) and NOS Engine Server run in one VM with IP address 192.168.100.4; sims run in a VM with IP address 192.168.100.5; 42 runs in a VM with IP address 192.168.100.6; and COSMOS runs in a VM with IP address 192.168.100.7.

The following files/commands have been modified for this:

  • sims/cfg/nos_engine_server_config.json
    -- configure the nos3 server URI to use 192.168.100.4:12001
  • sims/cfg/nos3-simulator.xml
    -- configure the nos-connection-string to be 192.168.100.4:12001
    -- configure the data-provider hostname to be 192.168.100.6 for each simulator (to connect to 42)
    -- configure the COSMOS IP for the truth simulator to be 192.168.100.7
  • sims/cfg/Inout/Inp_IPC.txt
    -- configure the server hosname to be 192.168.100.6 (for each 42 port that is used for a simulator)
  • sims/cfg/InOut/Inp_NOS3.txt
    -- configure the NOS3 time connection string to use 192.168.100.4:12001 (42 time connection)
  • config/tools/cmd_tlm_server/nos3_cmd_tlm_server.txt
    -- configure the MISSION_INT interface to connect to 192.168.100.4 (COSMOS to FSW/CI_LAB/TO_LAB connection)
  • COSMOS command: CFS TO_ENABLE_OUTPUT with DEST_IP '192.168.100.7', DEST_PORT 5011
    -- configure FSW/TO_LAB to send telemetry to COSMOS at IP 192.168.100.7

@jlucas9
Copy link
Contributor

jlucas9 commented Nov 29, 2022

Closing for now as new issues will be made to reference this one and further expand on the capability.

@jlucas9 jlucas9 closed this as completed Nov 29, 2022
Repository owner moved this from In Progress to Done in NOS3 Path Forward Nov 29, 2022
@Simon9050
Copy link

Hi,

First off, big thanks for your work on NOS3 simulator! It’s a game-changer for the space community.

I tried running NOS3 in dual VM mode, following the instructions, but it didn’t quite cooperate... Any tips or a specific branch I should use for this setup?

Cheers,

Simon

@Simon9050 Simon9050 mentioned this issue Feb 27, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jlucas9 jlucas9

@msuder msuder

Labels
None yet
Projects
NOS3 Path Forward
Archived in project
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jlucas9 @kabarr @msuder @Simon9050