OHM RoSat - Cubesat configurator v170610

[OrbitHangar]

Author: crisbeta

This is a demo for cubesat satellite configurator.

Last update:

- move parameters from scenarios to config

Features:
- angle above target (deg)
- direct distance to target (km)
- path loss signal to target (dB)
- dynamic mass calculator
- cubesat structure
- body mounted solar panel power generator
- isInShadow calculation
- reference location is in config
- power management / battery
- onboard computer
- antenna + transceiver
- receiver / transmitter signal strength (dBm)
- upload at source / download base (source / base configurable in scenary)

Credits:
- Adam Mitchell (kodiak) for cubesat meshes and textures
- BrianJ for calculation of sun attitude

Source code included. No commercial use without my permission.



DOWNLOAD

 

[Kyle]

Downloaded!

 

[Voyager_VI]

I think your math formula is backwards on your dB strength, it goes lower as you get close to Cape Canaveral and then goes back up as you move away. Unless I'm misunderstanding what the Loss signal to target is suppose to represent...

 

[crisbeta]

I think your math formula is backwards on your dB strength, it goes lower as you get close to Cape Canaveral and then goes back up as you move away. Unless I'm misunderstanding what the Loss signal to target is suppose to represent...

This is not the signal strength. This is the path loss; further away, bigger the loss. The signal strength will be show when I implement the power management and the transceiver.

 

[Voyager_VI]

OK, so I was misunderstanding it. Thanks!

 

[fred18]

This is not the signal strength. This is the path loss; further away, bigger the loss. The signal strength will be show when I implement the power management and the transceiver.

Hi Cris, I'm just resuming my work on the space network addon, and I think we can talk about how you think to implement this and share some part of it?

 

[boogabooga]

Will this ever consume power or transmit?

 

[crisbeta]

Will this ever consume power or transmit?

Yes, it will. Next release will contain battery.

 

[crisbeta]

Source code released

Source code included. No commercial use without my permission.

- upload at 1200 bps at 450MHz (UHF).
- download at 9600 bps at 150MHz (VHF).

 

[crisbeta]

When you download data to base, you will use more power.

 

[Voyager_VI]

Have you thought about source or destination being a spacecraft (ie: Relay satellite)?

Like what you have done so far, thank you!

 

[crisbeta]

Features to came, features to remain written

This is possible. But I think that will be simulated very well in "Space Network" by Fred. I don't what to overlap to much with his add-on because we will both waste time implementing the same think. Also Fred add-on is more user friendly (animated meshes, configuration windows, MDFs).

What I have in mind for this project:
- other components: attitude actuators, attitude sensors, propulsion, payloads
- other options for current component
- configuration file sources and bases (let say a hundred sources (like cities) and a few bases)
- sources generates uplink data and request downlink data
- bases receives the uplink data and transmits download data to sources
- I am thinking of using channels (even with different bandwith) for different frequency
- signal strength is dependent of frequency (now I use only 150MHz and 450 MHz)
- different modulations also will require different minimal signal strength (2PSK, 4PSK)
- once you deploy more satellites there will be direct link, but also frequency conflicts
- I will try to simulate some economics (satellite cost, satellite revenue, launch cost)

Probably many of this features will remain only written in this post, but the source code will be available for everyone who want to improve it.

:tiphat:

Now I realised that I have to check twice the title for misspells, because I can't change it

 

[Donamy]

I tried to use this with my SC3 cubesat launcher attached as a payload, but when I jettison it, the mesh is the Carina. Funny thing is, when I looked at the scenario file. It has the same info that is in the RoSat scenario supplied with the addon. :shrug:

 

[Face]

I tried to use this with my SC3 cubesat launcher attached as a payload, but when I jettison it, the mesh is the Carina. Funny thing is, when I looked at the scenario file. It has the same info that is in the RoSat scenario supplied with the addon. :shrug:

Due to the code posted for this addon, I think I can explain that:

• AFAIK, SC3 spawns the "real" paylod on jettison on-the-fly.
• The code shows that a scenario line "STRUCTURE_CONFIG" with value 1 must be present to configure for RoSat.
• On-the-fly spawning of vessels conveys no scenario lines (obviously), so that value remains at default, which should be 0 (it is not initialized explicitly, but since there is a constructor call and this is Windows, I'm pretty sure it is zero-initialized). Thus spawning that RoSat (e.g. via scenario editor) will always show the Carina mesh (hardcoded).
• Saving the scenario after spawning the vessel will still write out the STRUCTURE_CONFIG line, but it should show the value 0.

 

[crisbeta]

Face described very well, step by step, what is happening :thumbup:

The quick fix for this will be to move every system configuration from 1 to 0; let's say default config.

In the next step I will have to read config data from a config file (obviously :lol.

In the next release I will put the "quick fix".

:tiphat:

I checked the code and the "quick fix" will not work. The solar array are defined at the moment as an area (m^2). so even you have all the default components, you will not have any power

I will try to move to a config file as soon as possible.