New version of oXs configurator

[mstrens]

openXsensor offers lot of possibilities but the drawback is that setting up the configuration files (advanced and basic) can be quite difficult the first time you use it.

In the past, a configurator application had been developped to make it easier but this application had not been updated and could not be used with newer version of oXs.

I just made a new configurator version that I put on github here:
https://github.com/openXsensor/openXsen ... nfigurator

Please note that this is only a beta version and it supports only a subset of the oXs parameters.
Currently it can be used only for Frsky protocol (so not Jeti, Hott Multiplex) and it handles only the vario (even not all parameters), voltage, current and Gps.

The configurator is provided in 2 forms:
- sources that are written in python 3.7; in order to use it, you must install python 3.7 on your PC. To run it, start the script named oxsConfigurator.py
- an exe file that can be execute directly on a PC running Windows 10 64bits.

Use of the configurator is quite straigthforward. It allows you to enter/modify parameters. A set of parameters can saved (in an ".ini" file) and reloaded later on. When a set of parameters are filled, you can generate the oXs_config_basic.h and oXs_config_advanced.h files.
Those 2 files are currently created in the directory used to start the application and have to be copied manually in the folder where you store all openXsensor files.

I only make a few tests. So if you have trouble, just let me know.
I plan to fix the bug and to add some more oXs parameters.

Note: in order to use the files being generated by this application, you also have to use the current (=latest) version of openXsensor (because oXs_config_advanced.h has now been splitted in 2 files)

[jhsa]

Michel, you are a Star.. Thank you..
Does this support both Frsky D and X protocols? Thank you again. Currently I use mainly D8 protocol together with ErskyTX.

João

[mstrens]

It is supposed to support D and X protocols.
As in the config file you can select the one or the other or both.

[jhsa]

Wonderful, thanks.. It is amazing to see this project going again.. Thank you

João

[antlerhanger]

Thanks so much for doing this..I'm about to configure my vario , current , voltage , and GPS..Looks a lot easier ..I'm sure I will have questions tho .


Thanks again
Allen

[kalle123]

Hi Michel.

Just tried your latest python package under DEBIAN Buster.

I see this here

Code: Select all

kalle@nostromo:~/Schreibtisch/openXsensor-master/oXs_Configurator/Python 37 Sources$ ls
build        oxsAdc.py              oXs_config_basic.h    oxsCurrent.py  oxsHott.py     oxsMagnet.py     oxsSequence.py
config3.ini  oxsAddFields.py        oxsConfig.py          oxsFlow.py     oxsImu.py      oxsMultiplex.py  oxsVario.py
config4.ini  oxsAirspeed.py         oxsConfigurator.py    oxsFrsky.py    oxsJeti.py     oxsPpm.py        oxsVoltage.py
main.py      oXs_config_advanced.h  oxsConfigurator.spec  oxsGps.py      oxsLocator.py  oxsRpm.py        __pycache__
kalle@nostromo:~/Schreibtisch/openXsensor-master/oXs_Configurator/Python 37 Sources$ python3 oxsConfigurator.py
Traceback (most recent call last):
  File "oxsConfigurator.py", line 10, in <module>
    import tkinter as tk
ModuleNotFoundError: No module named 'tkinter'

Keep on the good work!

br KH

[mstrens]

Perhaps you have to install python3.7

Normally Tkinter is a module that is part of Python and, as far I know, Python is delivered with all Linux installation.

Still the syntax of Python has changed between Python2.x and Python3.x
E.g. the Tkinter module was Tkinter in 2.x and its becomes tkinter with 3.x.
Can you check which version you are using (and if needed install the 3.7)

[kalle123]

Michel, solved it myself

Needed the 'python3-tk (3.7.3-1)' package.



PS. Have here DEBIAN Buster and Testing. Both come with python 3.7. But you have to install that Tkinter package. I also run Linux Mint 19.2, but that distro lists python 3.6

br KH

[Endorphin]

Where do I find the Linux version download file please?
I use Linux Mint 19.1

[mstrens]

There is no compiled version for linux.
The source is here
https://github.com/openXsensor/openXsen ... %20Sources

You have to install (if not already done) python 3.7 (or more) and Tkinter

[Endorphin]

https://github.com/openXsensor/openXsen ... %20Sources
You have to install (if not already done) python 3.7 (or more) and Tkinter

Thanks.
I will now learn how to compile from source. (It's about time I did so!).
I have installed the python files. But I have not found Tkinter yet.

Jim.

[PeterB]

Just used this for the first time after downloading latest version on 18th Jan (2 days ago) & installing on Windows10 P.C.
Many thanks for this as it allows simple generation of much clearer config files.

However, a couple of things seem to need updating In the advanced_config.h file generation to prevent compile errors if this can be done please:

Add #include “oXs_config_macros.h”
Reference voltage needs to be in mV, not decimal Volts. (3.3 needs to be 3300 in the config file).

Again, great work guys.
Peter

[mstrens]

Just used this for the first time after downloading latest version on 18th Jan (2 days ago) & installing on Windows10 P.C.
Many thanks for this as it allows simple generation of much clearer config files.

However, a couple of things seem to need updating In the advanced_config.h file generation to prevent compile errors if this can be done please:

Add #include “oXs_config_macros.h”
Reference voltage needs to be in mV, not decimal Volts. (3.3 needs to be 3300 in the config file).

Again, great work guys.
Peter

2 days ago, I just made changes in many files in order to avoid compilation error due to #include “oXs_config_macros.h” missing.
Perhaps I forgot it in one of the file.
Can you give me a copy of the oXs_config_basic.h and oXs_config_advanced.h that provide the compilation error.

The fact that Reference voltage has to be in mV is to be changed in the configurator (when I have time).

[PeterB]

Hi mstrens,
When I tried to compile the attached files which were generated by the configurator I got errors, so compared them with working versions of the full config files.
I saw that the config_macros #include was missing from the advanced.h file, so manually added that.
The compile than went ok except for the VREF value issue (needs to be >2000), which again I manually changed to 3300 & then it compiled ok.

Many thanks,
Peter

[mstrens]

the config_macros #include is missing from the advanced.h file but with the last version (of oXs_sensor) this does not generate a compilation error anymore.
I just test it with your 2 config files.

There is still an error in the current configurator because the voltage reference should be e.g. 3300 instead of 3.3
Still if you change only this value, it compiles OK.

I am preparing a fix in the configurator for this.

[PeterB]

Ok many thanks for that.
I will check again that my project has the latest version of oXs.
Peter

[mstrens]

I just put a new version of oXsConfigurator on Github in order to fix the bug with the Voltage Reference (had to be in mVolt (no decimal)

[jhsa]

Thanks Michel..

João

[PeterB]

Michel,
Many thanks, but has the new Configuration tool been amended to require a 64bit version of Windows10?

The previous version would run ok on Windows10 Home edition, 32bit, but the new version will not run on either of my Windows10 machines. Windows diagnostics says the application is not compatible with my machine.
Peter

[mstrens]

I forgot to use the option --onefile in pyinstaller when I generated the exe file for windows.
I just put on github a new version of the exe file where I used this option.

I hope it fix the issue for your windows os version.

[PeterB]

Many thanks Michel, that fixed the Windows version

When you have a moment, could you please also add the latest Test1 & Test2 fill options (e.g. Number of Sats & Hdop).
Peter

[andre]

hi mstrens,
thanks for your work.

I've tried the new configurator for a simple single vario build, and noticed that the option "a MS5611 is added as second sensor" in the Vario tab is inverted, i.e. it generates "#define SECOND_BARO_SENSOR_USE MS5611" when not selected, and "#define SECOND_BARO_SENSOR_USE NO_BARO" when selected, in the oXs_config_advanced.h file.

thank you.
Andrea

[mstrens]

Thanks for reporting bugs.
I just put a new version that is supposed to support all options for Test1 ... 3 and fix the bug about second vario.
I also added 2 buttons to view directly the basic and advanced files that have been generated

[jhsa]

That is cool, thanks

João