You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to Open Source user feedback, we plan to start creating guides on how to properly develop missions in NOS3, starting with commonly edited tables and COSMOS scripting. So far, a basic guide on tables is added to the Wiki, which should explain the use of DS tables (File and Filter) in depth, with guides on SC RTS tables and SCH tables soon to follow on that same page. We also plan to add a guide on COSMOS Scripting in Ruby, and perhaps other commonly used features. If users, or developers, have any inputs on these guides, either in what we should add, or comments on existing guides for their accuracy, detail, or if they are flight-like, please post them here so we can foster discussion and a comprehensive guide for our users.
The text was updated successfully, but these errors were encountered:
How to add custom component; So far, the only way is to use sample, but steps described there is not very detailed and full:
Probably this is more related to cFS not NOS3, but it will be interesting to get some details on that how NOS3 could be ported for FreeRTOS and real board.
Due to Open Source user feedback, we plan to start creating guides on how to properly develop missions in NOS3, starting with commonly edited tables and COSMOS scripting. So far, a basic guide on tables is added to the Wiki, which should explain the use of DS tables (File and Filter) in depth, with guides on SC RTS tables and SCH tables soon to follow on that same page. We also plan to add a guide on COSMOS Scripting in Ruby, and perhaps other commonly used features. If users, or developers, have any inputs on these guides, either in what we should add, or comments on existing guides for their accuracy, detail, or if they are flight-like, please post them here so we can foster discussion and a comprehensive guide for our users.
The text was updated successfully, but these errors were encountered: