search

RobertK66 / obc_1769_core

Implements hardware abstractions and Layer2(3) modules for usage of the OBC hardware in cubesat projects
GNU General Public License v3.0
1 stars 1 forks source link

Base for OBC RADTest version #37

Closed RobertK66 closed 2 years ago

RobertK66 commented 2 years ago

My Idea was to make a 'normal' developer -> master Pull Request/Release cycle as example how to make an OBC Software release.

My personal principle about "Software releases" is, that I make a 'labeled' version every time the Software (in this case the ClimbOBC axf file (together with its documentation) 'leaves the developer sphere'. Here it is used for a special out of the house test where this release will document for later times what exactly was run on the OBC hardware in this test. Other examples would be if somebody else gets an OBC EM hardware for integrating his/her subsystem and therefore needs some (actual) version of OBC image.

@kodsurf : For your Thruster module. If you want to disable functionality during the tests possible solutions (other than deleting code temporary) would be:

RobertK66 commented 2 years ago

Current version of this branch was done in my IDE after cleaning up our merge-mess. I will now review it and check if I did everything correct. And I will start a How To doku for our manual (because I still do not get every single point of the eclipse git gui).....

kodsurf commented 2 years ago

Hello,

I am sorry I don't have internet till Tuesday ! I cannot do any remote work or review from mobile 4g :(

There is no need to disable thruster parser for RAD test.

No bytes would just be sent to OBC from thruster side.

And function thrsendbytes() that was used in Rad test module should still work without problem.

Kind regards

On Sat, 13 Aug 2022, 11:01 RobertK66, @.***> wrote:

My Idea was to make a 'normal' developer -> master Pull Request/Release cycle as example how to make an OBC Software release.

My personal principle about "Software releases" is, that I make a 'labeled' version every time the Software (in this case the ClimbOBC axf file (together with its documentation) 'leaves the developer sphere'. Here it is used for a special out of house test where this release will document for later times what exactly was run on the OBC hardware in this test. Other examples would be if somebody else gets an OBC EM hardware for integrating his/her subsystem and therefor needs some (actual) version of OBC image.

@kodsurf https://github.com/kodsurf : For your Thruster module. If you want to disable functionality during the tests possible solutions (other than deleting code temporary) would be:

  • make a precompiler #ifdef false/true to remove code parts but you can de-activate later with only removing the #ifdef line
  • do not init your module at all in main.c (just comment the one line in the modules table
  • make a special 'feature mode' for this test (printing the strings the test excepts to output but do not react on thruster rx date (which I understood that will not be sent from test harness, or will there be something? -> ask abbas)

You can view, comment on, or merge this pull request online at:

https://github.com/RobertK66/obc_1769_core/pull/37 Commit Summary

File Changes

(13 files https://github.com/RobertK66/obc_1769_core/pull/37/files)

Patch Links:

— Reply to this email directly, view it on GitHub https://github.com/RobertK66/obc_1769_core/pull/37, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP3QEW5NFIA6XPWCOYI4DZDVY5P6XANCNFSM56N2CYLA . You are receiving this because you were mentioned.Message ID: @.***>