Features coming

[Romolo]

Model compare tool, simply drag and drop two models on the tool and you will see the differences

[flashbang]

Awsome tool.

[bertrand35]

Indeed, a lot of work from Romolo here!
Bertrand.

[Romolo]

Due to the presence of many MB and firmwares, we have implemented in SVN the possibility to store firmwares profiles with their options and recall them fast from the toolbar.
There are 10 profiles slots that can be used and recalled.
To save a slot you press "save profile" from preferences windows.

[Rob Thomson]

Ooh! Just what I wanted!


Sent from my iPhone using Tapatalk

[bertrand35]

Rob you have *only* 2 radios
Bertrand.

PS: Everything here from Romolo, not really "we"

[Rob Thomson]

5

But only two versions.... And 3 spare ones for when you can't get them anymore!


Sent from my iPhone using Tapatalk

[Romolo]

PS: Everything here from Romolo, not really "we"

WE are a team .... but indeed bugs are from me

PS: Bertrand released the windows installer...

[Kilrah]

Perfect feature and timing to include another little suggestion of mine

I just modded my 2nd 9x tonight, and was thinking about the problem of calibration. The thing is I'd like to be able to use the same models with both radios, so I'll likely be copying one radio's eeprom to the other very often when I do adjustments / create a model or even just adjust trims during a flight. The annoying thing is that stick calibrations are obviously different, so a simple read-write is no good, one has to read the eeprom from one TX into C9X, open another eepe file with the 2nd radio's general settings, copy those over to the first document, and only then write to the other TX.

Sooo... would it be possible to store the analog calibration parameters in those profiles? That way we can just read one radio's eeprom and write to the other, the only thing is to make sure the 2nd radio's profile is selected, and the file automatically gets patched with the corresponding calibration data

I.e. C9X always patches the calibration data from the currently selected profile before sending anything to avrdude. Maybe with an option in preferences to enable that functionality or not, disabled by default, so that those who only have one TX are not required to make a profile.

I've been thinking of that issue for some time already, but couldn't think of an easy way to handle it... but that profile feature seems the perfect thing to include it!

[Romolo]

Well,
The idea is bad (Bertrand's Tm) so I will have a look how to do it
The problem is how and when store data in the profile. Maybe a button in general settings editing ?
Then for sure a checkbox in a burndialog like: use calibration data from current profile.
I will have a look. We like bad ideas.

EDIT:
Only calibration or the whole general settings ?
For me the whole general settings maybe make more sense ... but maybe I'm wrong.
What do you think ?

Storing calibration settings and displaytype is done, retrieving and patching eeprom on the fly will follow...

[Kilrah]

Then for sure a checkbox in a burndialog like: use calibration data from current profile.

Yep, just make sure it's remembered from one time to the next, unlike the change splash option (maybe fix that too? )

Only calibration or the whole general settings ?
For me the whole general settings maybe make more sense ... but maybe I'm wrong.
What do you think ?

Well, some of the general settings are preferences that are subject to change, like the timer beeps, the alarms, etc... so I'd say all directly hardware-related parameters:
- Analog calibration
- Display type and contrast
- Stick mode
- Audio settings (for ER9X as there are some that depend on the audio mod)

[Romolo]

Ok at the moment I'm storing:
stick/pot calibration
TrainerCalibration
g_eeGeneral.vBatCalib
g_eeGeneral.currentCalib
g_eeGeneral.PPM_Multiplier
g_eeGeneral.stickMode
g_eeGeneral.optrexDisplay
g_eeGeneral.contrast
g_eeGeneral.backlightBright
g_eeGeneral.beeperMode
g_eeGeneral.beeperLength
g_eeGeneral.hapticMode
g_eeGeneral.hapticStrength
g_eeGeneral.hapticLength
g_eeGeneral.speakerMode
g_eeGeneral.speakerPitch
g_eeGeneral.speakerVolume

Something still missing ?

[Kilrah]

Hmm maybe remove the PPM multiplier (that depends on the student radio, right)?

Seems fine otherwise.

Is it already implemented? I was actually surprised to see the 2 patch checkboxes in the write eeprom from fil dialog

[cre8tiveleo]

g_eeGeneral.speachMode
g_eeGeneral.speachPitch
g_eeGeneral.speachVolume
g_eeGeneral.speachGender
g_eeGeneral.speachAccent
g_eeGeneral.speachCussing

[Romolo]

Yes ! Sir, already implemented...
Maybe something need to be added but already patches what is described in the previous post.
You may try easily...
read your radio, create a profile slot, save calibration in profile.
create a new eeprom, while writing, select patch calibration and your radio, even with a clean eprom, should be calibrated.

[Kilrah]

Hmm I don't think I manage to...

OK, then:
- Read radio in a document
- Go to Preferences, choose a profile slot, name, click "Save Profile"
- I don't see where to save calibration in?

EDIT:
Oh, you have to open general settings!
OK, then I can store the parameters in the profile indeed. But when I create a new document and flash it, I have the defaults...

EDIT2:
OK, you have to open general settings again and "read from profile" first. Couldn't we just have the same patch dialog and checkboxes there is when writing from a file?

[Romolo]

You need to save from the general settings of the radio...
Not from the general settings of the new document...

[Kilrah]

OK, new post instead of EDIT3: Little problem!

If I create a new document, open general settings, go to the calibration tab, and click retrieve calibration I can see the numbers updating. I close general settings, reopen them, and they're still there.

However, if I read one radio, open general settings, go to the calibration tab, and click retrieve calibration I can see the numbers updating, BUT if I close general settings and reopen them the old numbers are back

Flashing from file with patching enabled works fine though

[Romolo]

Consider that the patch is performed while writing to the radio and doesn't alter the original file. The same while writing from a document open in memory.
About values not altered while retrieving I will have a look for next release...

EDIT: Fixed and released

[Romolo]

New features and fix..
Better compatibility with er9x/ersky9x in telemetry V*2 values supported (trasparently)
Function switches now present parameters combo box for haptic playsound and reset functions
Some fix around in vario and telemetry bars settings.