automatische Schmetterlingsaufzugsverkleidung

An updated version is now available in Jeti Studio. This fixes a small bug that prevented you from using something like a Logic Switch as the crow control in the app. It will now work properly. Some models use throttle and crow brake on the same stick, with the output from a proportional logic switch controlling the crow brakes. This update lets you use that same proportional logic switch in the app.

Bei mir ist da irgendwas schief gelaufen. DS16 V2 aktuelle Software drauf, und bis vor dem Auto.Crow Update hat auch alles einwandfrei funktioniert. Ich finde die App sogar sehr hilfreich, bzw. nutze die bei allen Seglern.

Gestern nach dem Update (an den Einstellungen vom Modell usw. wurde nix geändert), blieb das HR auf neutral, bzw. die eingestellte und auch sichtbare Kurve hat nicht mehr gegriffen. Ist mir blöderweise erst bei der Landung aufgefallen. Hab da länger rumgesucht, aber nix gefunden warum das nicht mehr geht.
Mach ich da was falsch, oder hab ich was übersehen??

Hab dann eben ein Backup, welches ich vor dem Update noch gemacht hatte, wieder eingespielt. Geht wieder alles, aber...


patrick

Hi Patrick,

Sorry you are having an issue with the app.

It is not immediately obvious to me what happened but here are some things to check. I apologize in advance if this is too much information.

First, let me explain how the Autocrow app stores configuration data. It does not use the standard Jeti lua API approach to this (the system.pSave function if you know the lua api). The reason for this is that the settings are lost when the app is updated and you have to start over. So what I do on some of my apps with a lot of configuration information (where it takes a long time to reset things) is to save them in a JSON file in the app's directory. In the case of auto crow, the files are in the DFM-Crow directory and the file names are of the form "C-xxx.jsn" where xxx is the model name.

The only downside of this approach is that if you change the model name, you would have to re-enter all the configuration or you'd have to know how to change the file name which most pilots would not probably want to do. But my assumption is that the app is updated much more frequently than the model name is changed. I wish there were a better solution but this is how I am doing it today.

So if for any reason the "C-ModelName.jsn" for the model called "ModelName" was removed during the update, it would act the way you observed. But I have not seen the update process delete files, so I am not sure this is what happened. If you do another update you can look at the contents of the DFM-Crow directory in the Apps folder before and after the update and see if any of the C- files were removed .. if so, that's the problem.

One last note, if there is a space in the model name, it is replaced by "_" so if you have a model called "P51 Mustang" the file would be "C-P51_Mustang.jsn".

Hope this helps.
Dave

Great work, thanks to all the contributors to this app! The functionality of this app would be very helpful for many kind of mixes. I would have one specific use-case, so just one question if I may: Is it possible to use the app to modify a function curve? I have a mixer RUD->AIL defined in a separate function curve. Reasons for that are another story Having the possibility to change this mix on-the-fly would be great.

Is that possible or is the app specific to the Butterfly->ELE mixer, a.k.a. Schmetterlingsaufzugsverkleidung?

Kriz, Thank you for the very nice comments.

This app was originally inspired by an app on openTX where the lua system allows apps to change internal mixers. The Jeti lua implementation does not allow that, so our app has to make its own mixer built in to the app.

You can leave the app running after the mix values are determined, or you can transfer the values to a built-in multiopoint mixer. Harry Curzon covers that in his video on this app - we actually have two variations of the app .. one intended for airbrake-pitch trim mixing, and one for knife edge flight that handles mixes for two surfaces.

In the videos, Harry shows how to transfer the app's mixer to the built-in mix curve. I think it should also be possible to transfer it to a function curve but we have not tried that.

Dave

Hi Dave. Thanks for the clarification, that was of great help. Will watch the video!