-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Added sensorConfig #10
Open
MarioFPVdev
wants to merge
1
commit into
OpenIPC:main
Choose a base branch
from
MarioFPVdev:patch-2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be a problem. When the read value does not match any of element in the list the first one is used.
So when by default the milos bin are not in the firmware, this will lead to a sensor config /etc/sensors/imx415_milos10.bin after the first save in the ISP section even when it's not there.
Does this work with majestic ?
There are also some shenanigans going on in datalink tweaksys.
Not sure how to handle this in a generalized way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is the defaulting: https://github.com/OpenIPC/msposd/blob/main/osd/util/ini_parser.c#L247
In this loop the actual value is set https://github.com/OpenIPC/msposd/blob/main/osd/util/ini_parser.c#L277-L282
When
strcmp(output, value_list[i]) == 0
is never true the default stays.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sensorConfig options is more like an example of how to import and then select an available bin file directly from the VTX menu.
If the majestic doesn’t find the bin file that the user chose, it will automatically use the default bin file based on the camera sensor.
We are planning to use the Milos calibration files as default for imx415 and imx335 once we have an acceptable result. However the sensorConfig will give flexibility to the user to select a different calibration file based on their preferences or weather conditions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, If that goes to the official firmware, it will be available on ALL devices as default options.
It is simply not a good idea to have two very specific config options in the standard install, provided that these two files are not included in the standard OpenIPC firmware.
Relying on majestic "recovery from invalid config setting" is also not a good thing. Imagine this changes some day and after some update majestic crashes on invalid sensor file setting.
I would offer to add an option to download the vtxconfig.ini from the configurator. This way a user who adds new sensor.bin files will simply download the appropriate vtxmenu.ini for them.
Of course, the best option would be to make the list in the options filled via a bash script that lists all files with a wildcard, sorted so that the first option is the standard file.
This way the user will need to only upload whatever file he decides and they will appear in the list.
But this is something that @henkwiedig can add I suppose