Correct Windows Serial Interface Config COSMOS5

[Donny3000]

Good Afternoon,

I've been able to successfully install/build COSMOS5 from main/master and have been able to successfully migrate my COSMOS4 target (following the upgrade guide) to COSMOS5, build and upload my target gem file into COSMOS5 running on my Windows 10 host. However, my target is unable to connect to my hardware over serial, as it's producing the following error in the Command and Telemetry Server log output over and over:

To provide more context, this is my migrated target's plugin.txt file

From the log output, it appears that COSMOS 5 is trying to use the posix_serial_driver.rb instead of the win32_serial_driver.rb backend for the serial interface.

Am I missing additional configuration steps necessary to get my target's serial interface working properly? Or is there a way to somehow force or configure and interface to use the Win32 Serial Driver? I read through the COSMOS 5 Interface Configuration documentation and it seems that my plugin.txt is correct. But, I might be overlooking something. Thanks in advance for any assistance!

[ghost]

You've run into the one real downside to Docker, in that you can't access local hardware (like serial ports), without running on a linux host and running a container with --priviledged (which is not ideal from a security standpoint).

The solution is to run an ethernet speaking bridge directly on the host computer, and configure COSMOS to talk to that.

This is implemented but not documented yet. Take a look at bridge and bridgesetup in the cosmos command line executable:
https://github.com/BallAerospace/COSMOS/blob/master/cosmos/bin/cosmos

You will also need to change your plugin to be a tcpip interface to connect to the bridge.

[Donny3000]

Thanks, @ryanatball for your quick response and clarification! I will take a look at the information you have provided to get COSMOS 5 talking to my hardware.

[ghost]

Feel free to update with any additional information that would be useful to the community.

[Donny3000]

I'm running into an issue trying to set up the TCP bridge that @ryanatball mentioned earlier. I'm assuming the first step would be to create the bridge configuration file via bridgesetup. But, when I execute the bridgesetup command I get the following ruby error traceback

From the error in the traceback, it appears that a connection is trying to be made to the redis COSMOS5 container at localhost:6379. So, I checked to make sure the redis container is indeed running with docker ps -a, of which it is.

So, to confirm we should create the configuration file first, and then use the configuration file to start the bridge? If so, why would I be seeing this ruby error when trying the create the bridge configuration file?

[ghost]

Couple issues here. I have a fix in an internal pull request. If you are running Ruby 2.7, you can set the environment variable COSMOS_NO_STORE=1 and it should work as a temporary workaround.

[Donny3000]

Thanks for the guidance, @ryanatball! I'll give that a try and see how I progress.

[ghost]

@Donny3000 The full fix is now pushed to the master branch

[abdelrahman47]

Couple issues here. I have a fix in an internal pull request. If you are running Ruby 2.7, you can set the environment variable COSMOS_NO_STORE=1 and it should work as a temporary workaround.

I have the same problem. could you please explain how to set the environment variable cuz I tried to set it to the linux variables but the error is still there