-
Notifications
You must be signed in to change notification settings - Fork 82
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.
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
AC.bvb
field not written on socket
#128
Comments
It's intentional, to enforce the discipline of "FSW shouldn't have to access the ground truth". 42 allows some cheats (access to ground truth, ideal actuators) to enable rapid early prototyping, but by the time you're using "remote" controllers, it's recommended that you grow out of those. |
Thanks, |
Sure, that should work. |
Thank you very much for the clarifications so far. This would be useful for a remote ACS in order to, e.g., tune the navigation filtering algorithms without needing replicated configuration files. Is such information available over the IPC communication and I couldn't figure it out? Or would it somehow break the system philosophy? |
You might want to study Database/Readme.txt. |
Hi, Many thanks |
The field
AC.bvb[]
is filled with the ground-truth magnetic field vector in the case where no magnetometers are available to the spacecraft (42sensors.c
, line 452, current master branch).However, this field is not written on the IPC message (
SimWriteToSocket.c
), and thus the relative information is not made available over the socket connection to a remote FSW.Is this a mistake or intentional?
I can see that the FSW shouldn't have to access the ground truth, but I can't quite understand why a "local" controller should have different information respect to a "remote" one.
Am I missing something here ?
Many thanks
The text was updated successfully, but these errors were encountered: