Hi, since this program was released I have never been able to go beyond the screen present hereā¦every time it tells me that it canāt find the intermediate parametersā¦if someone can teach me in a simple way how to do it to be able to go further I would be grateful to him otherwise I will abandon that is, I will continue as I have always done in recent yearsā¦manually doing the various stepsā¦Iām sorry that I would have liked to have a tool that would make it easier for me and direct me to the various steps to follow to doā¦ Iāve been trying and trying for days but I canāt go any furtherā¦
Sure, Here it is.
- Use option 1
- As template source Select the diatone_taycan_mxc directory and after that the 4.5.1-params
- Leave the destination base directory unchanged
- Edit the text āMy vehicleNameā to something more descriptive.
- Press the button āCreate vehicle directory from templateā
Done
Next time you get stuck, ask for help instead of waisting your time.
The files get created on the directory you specified. So the next time you open the program, use option 2 and open the directory you just created
Thank you amilcarlucas for allowing me to continue using the programā¦I arrived at this window following your instructionsā¦but I see that another tab is set (The problem is that the intermediate parameter files created are for a Matek H743 flight controller ) and not my pixhwakā¦ .how do I set up my pix in the program.
Thanks again for helping me improve my learning.
Hello Luciano,
The matek is a template. As all templates it is a starting point that you need to modify to meet your needs.
You need to change all the values to match your vehicle.
Version 0.2.10 has a critical bugfix, please update ASAP
- Simplify and update the README.md (Dr.-Ing. Amilcar do Carmo Lucas)
- use the new windows installer filename explicitly (Dr.-Ing. Amilcar do Carmo Lucas)
- Spellcheck in GUI text (Dr.-Ing. Amilcar do Carmo Lucas)
- Simplify the test code and remove a FIXME (Dr.-Ing. Amilcar do Carmo Lucas)
- allow configuring option2 initial directory (Dr.-Ing. Amilcar do Carmo Lucas)
- cope with out-of-order and missing/unused BITMASK key entries (Dr.-Ing. Amilcar do Carmo Lucas)
- Bump version (Dr.-Ing. Amilcar do Carmo Lucas)
Version 0.3.0 introduces forced and derived parameter support it is now possible to implement the initial parameters spreadsheet inside the methodic configurator without changing a single line of python code!
Currently around 35 parameters get automatically set without user intervention, but the number will grow.
- Improve the Bitmask bugfix in corner cases (Dr.-Ing. Amilcar do Carmo Lucas)
- Remove code duplication, make it easier to add modular command line parameters (Dr.-Ing. Amilcar do Carmo Lucas)
- allow selection none as flight controller device on the command line (Dr.-Ing. Amilcar do Carmo Lucas)
- allow skipping the component editor windows via command line parameter (Dr.-Ing. Amilcar do Carmo Lucas)
- add component editor command line description (Dr.-Ing. Amilcar do Carmo Lucas)
- Small parameter file values changes (Dr.-Ing. Amilcar do Carmo Lucas)
- Force the value of 30 parameters, the user is not supposed to change these (Dr.-Ing. Amilcar do Carmo Lucas)
- Make sure only one bitmask window is possible at a time (Dr.-Ing. Amilcar do Carmo Lucas)
- Refactor parameter table to itās own file (Dr.-Ing. Amilcar do Carmo Lucas)
- prepare validation of derived parameters (Dr.-Ing. Amilcar do Carmo Lucas)
- Move template files to vehicle type subdirectory, to allow future expansion with ArduPlane, Rover, etc (Dr.-Ing. Amilcar do Carmo Lucas)
- remember last selected directories on windows #5 (Dr.-Ing. Amilcar do Carmo Lucas)
- pylint fixes (Dr.-Ing. Amilcar do Carmo Lucas)
- Initial work on derived parameters, derive 5 parameters from the information inputted in the component editor (Dr.-Ing. Amilcar do Carmo Lucas)
- Bump the version (Dr.-Ing. Amilcar do Carmo Lucas)
You need to manually give write permissions for your user to the file:
C:\Users\YOURNAME\AppData\Roaming\.ardupilot_methodic_configurator\settings.json
sorry for that, It will get fixed in the next version.
Hello Amilcarlucas, I am using the 0.3.0 version of Methodic Configurator. I have connected my FC to computer and editing the parameters. However i am not writing them to FC, i am choosing skip parameter file and everytime it asks whether i want to save those values in that particular param file, so i click yes and it moves on to next param file. This was what i wanted but when i did the same for ESC.param file and clicked on āskip parameter fileā instead of asking to save the params the program shut down. When i reopened the ESC param file the values and the reason that i had written were saved but when i manually select bat1.param file from drop down above the program again shut down. Can you please look at this.
I am using 4.4.4 param files as template. And my vehicle directory is in D folder whereas the application is installed in C folder in case this info is needed.
Thankyou
There is something wrong with your bat1.param file. post it here.
I have just created the directory by copying files from template. So right now it is default. However first 7 files i was able to edit. This 8th one is crashing
08_batt1.param (4.7 KB)
Did you correctly fill all the values in the component editor window?
Battery voltages need to be filled with .
decimal separator, not ,
you need a vehicle_components.json
file that you can copy from one of the provided templates.
Then it will open a component editor window before that one.
Commits
- fix linting by adding eval-used exception (Dr.-Ing. Amilcar do Carmo Lucas)
- two more forced parameters (Dr.-Ing. Amilcar do Carmo Lucas)
- write permissions to the %APPDATA%.ardupilot_methodic_configurator\settings.json file (Dr.-Ing. Amilcar do Carmo Lucas)
- cope with un-existing vehicle_components.json file (Dr.-Ing. Amilcar do Carmo Lucas)
- Windows site configuration directory fix (Dr.-Ing. Amilcar do Carmo Lucas)
- Bump version (Dr.-Ing. Amilcar do Carmo Lucas)
Commits
- Rename file_documentation into configuration_steps #8 (Dr.-Ing. Amilcar do Carmo Lucas)
- Remove duplicated code #8 (Dr.-Ing. Amilcar do Carmo Lucas)
- Automatically set the FC Firmware Type and version if available #8 (Dr.-Ing. Amilcar do Carmo Lucas)
- e11208d: IMPROVEMENTS pylint fixes. Refractor to remove duplicated code (Dr.-Ing. Amilcar do Carmo Lucas) #8
- MAVFTP add testing code. Does not work yet #8 (Dr.-Ing. Amilcar do Carmo Lucas)
- Add comboboxes and input validation to some of the component editor fields #8 (Dr.-Ing. Amilcar do Carmo Lucas)
- Validate battery voltages #8 (Dr.-Ing. Amilcar do Carmo Lucas)
- Bump version info #8 (Dr.-Ing. Amilcar do Carmo Lucas)
v0.4.0
Commits
- Add a way to get release statistics (Dr.-Ing. Amilcar do Carmo Lucas)
- Update the Architecture picture and text (Dr.-Ing. Amilcar do Carmo Lucas)
- Update the usermanual (Dr.-Ing. Amilcar do Carmo Lucas)
- Move documentation data detail to the backend (Dr.-Ing. Amilcar do Carmo Lucas)
- Remove pylint exception (Dr.-Ing. Amilcar do Carmo Lucas)
- reduce code duplication in configuration step parameter validation (Dr.-Ing. Amilcar do Carmo Lucas)
- move forced and derived parameter calculation to the backend (Dr.-Ing. Amilcar do Carmo Lucas)
- Improve gramar in comments (Dr.-Ing. Amilcar do Carmo Lucas)
- Make the list of supported vehicle types available (Dr.-Ing. Amilcar do Carmo Lucas)
- Add a class to validate the battery cell voltages (Dr.-Ing. Amilcar do Carmo Lucas)
- More pylint fixes in test code (Dr.-Ing. Amilcar do Carmo Lucas)
- moved component editor to a base class and the validation to a child class (Dr.-Ing. Amilcar do Carmo Lucas)
- add 3 more component editor derived parameters (Dr.-Ing. Amilcar do Carmo Lucas)
- Bump version (Dr.-Ing. Amilcar do Carmo Lucas)
Issue with v0.4.0 on launch:
PS C:\Program Files (x86)\MethodicConfigurator> .\ardupilot_methodic_configurator.exe
Traceback (most recent call last):
File "ardupilot_methodic_configurator.py", line 27, in <module>
ModuleNotFoundError: No module named 'frontend_tkinter_component_editor'
[22436] Failed to execute script 'ardupilot_methodic_configurator' due to unhandled exception!
Strange one. Can you try the latest release (not the 0.4.0) in a few minutes?
Yep, works with the dev release