- Příspěvky: 519
- Obdržená poděkování: 2
Všechny otevřené přihlášky jsou k dispocizici zde :
stoupak.cz/souteze/kalendar-akci/prihlasky
Světový pohár F5J Lanškroun
- Radim Barč
-
- OFFLINE
- Malý bůh
-
Méně
Více
9 roky 2 týdny nazpět #18885
napsal Radim Barč
Odpověď od Radim Barč na téma Světový pohár F5J Lanškroun
Ještě přidávám trošku pohybu:
Pro možnost přispívání do fóra je nutné: Přihlásit se .
9 roky 2 týdny nazpět #18886
napsal sgames
Odpověď od sgames na téma Světový pohár F5J Lanškroun
moc pěkné ! a jinak Plus je tam dost detailně natočeno, krása
Pro možnost přispívání do fóra je nutné: Přihlásit se .
9 roky 2 týdny nazpět #18887
napsal hrabacek
Odpověď od hrabacek na téma Světový pohár F5J Lanškroun
První recenze na víkendové létání:
Thank you for the great weekend. Was a good competition.
Kind regards,
Peter Zweerst
Thank you for the great weekend. Was a good competition.
Kind regards,
Peter Zweerst
Pro možnost přispívání do fóra je nutné: Přihlásit se .
9 roky 2 týdny nazpět #18892
napsal sgames
Odpověď od sgames na téma Světový pohár F5J Lanškroun
Tak se nám na FB ve skupině FXJ po výsledcích z Lanškrouna rozběhla diskuse na téma záznamy z finálových letů. Až se dorazilo na Tomaszových 13 m a jeho záznam.
viz jeho vyjádření :
www.facebook.com/groups/332833164809/10155382564674810/
As requested by other competitors I am posting my flight logs here.
After analysis with no doubt one can conclude that my logger gave incorrect measurement during last final flight. Just after aircraft was switched on altitude dropped to approximately -9 m below zero level and was not recalibrated by logger as new "zero". It means that correct measurement of start altitude should be equal to about 22m.
First of all, what has to be said this error had no influence on overall outcome of competition (I checked influence of this error and even if 22m was noted on scoring card nobody would have finish on worst/better place overall).
Second thing is I do not why this error occurred. I could have said that I made 13m and pretend than nothing ever happened and not show the logs because I do not have such a obligation, but I would like to be fair and discuss that matter. I am using stock Altis v4 which is using 5.5 firmware, is connected as recommended by producer and was never dissasembled. A proof for that is that my aircraft passed inspection before finals and gave appropriate reading during this process (after switching motor on and off showed 0.1 m). The only reason which I could think of is that my logger is 3 years old and its wear might be a problem. Nonetheless, to check what is wrong with it the only solution which I see is to send it to the aerobtec to get it checked, which I could do if F5J community want me to do so. If in the future anybody wants to see my installation during any moment of the competition there is no problem, I can show it to you I have nothing to hide and want to be transparent.
Now the question arises- am I only one which had problem like this? This time it has been clearly visible, so it was checked, but what if measurement errors like that are also common among other competitors and unnoticed have influence on overall outcome of the competition? How to prevent such a thing from happening in the future?
To my mind, a root of this problem is a barometric altimeter which is used in this device. As I am working a lot with UAVs which are using autopilot modules such sensors fluctuating reading is a frequent, serious and well known problem.
I see several solutions- first is change of the way that measurement is done. As one can observe in my case altitude dropped just after aircraft was switched on and stayed like this till the end of flight. If start altitude would be measured as absolute value between "F5J alt." and "Motor Switch On" such error would have not ever happened. This might be small change on next Altis firmware versions which could have enormous influence on overall results during competitions when starting altitudes are really low.
Second solution that I see is to double check all finals competitors logs after flights. In my case display on altis showed 13.6m and this was altitude which was noted by timekeeper. It is not possible to validate such a reading without usage of a computer. Therefore, during competitions where such a low start highs occur it might be useful to ensure reading on the display is correct.
Finally, if the wear of a device is a problem, devices older than some amount of time should be prohibited which will eliminate mentioned problem. (Even though rules does not say that I still promise to switch to newer Altis
)
I hope we can discuss encountered problem and find a solution to prevent such situations from happening in the future. As I said I want to be fair with others rather than sweep whole case under the carpet. Additionally, what is worth mentioning, I shared whole unedited logs instead of print screens which could be changed without any problem to cut out the part which shows the problem. Believe me I could do this in photoshop in such a way you would never noticed that something was changed
. In the future if other pilots share their logs please do the same, only then everything is clear and obvious. ![:) :)]()
zkráceně výškoměr ukazoval o 9 metrů méně...
viz jeho vyjádření :
www.facebook.com/groups/332833164809/10155382564674810/
As requested by other competitors I am posting my flight logs here.
After analysis with no doubt one can conclude that my logger gave incorrect measurement during last final flight. Just after aircraft was switched on altitude dropped to approximately -9 m below zero level and was not recalibrated by logger as new "zero". It means that correct measurement of start altitude should be equal to about 22m.
First of all, what has to be said this error had no influence on overall outcome of competition (I checked influence of this error and even if 22m was noted on scoring card nobody would have finish on worst/better place overall).
Second thing is I do not why this error occurred. I could have said that I made 13m and pretend than nothing ever happened and not show the logs because I do not have such a obligation, but I would like to be fair and discuss that matter. I am using stock Altis v4 which is using 5.5 firmware, is connected as recommended by producer and was never dissasembled. A proof for that is that my aircraft passed inspection before finals and gave appropriate reading during this process (after switching motor on and off showed 0.1 m). The only reason which I could think of is that my logger is 3 years old and its wear might be a problem. Nonetheless, to check what is wrong with it the only solution which I see is to send it to the aerobtec to get it checked, which I could do if F5J community want me to do so. If in the future anybody wants to see my installation during any moment of the competition there is no problem, I can show it to you I have nothing to hide and want to be transparent.
Now the question arises- am I only one which had problem like this? This time it has been clearly visible, so it was checked, but what if measurement errors like that are also common among other competitors and unnoticed have influence on overall outcome of the competition? How to prevent such a thing from happening in the future?
To my mind, a root of this problem is a barometric altimeter which is used in this device. As I am working a lot with UAVs which are using autopilot modules such sensors fluctuating reading is a frequent, serious and well known problem.
I see several solutions- first is change of the way that measurement is done. As one can observe in my case altitude dropped just after aircraft was switched on and stayed like this till the end of flight. If start altitude would be measured as absolute value between "F5J alt." and "Motor Switch On" such error would have not ever happened. This might be small change on next Altis firmware versions which could have enormous influence on overall results during competitions when starting altitudes are really low.
Second solution that I see is to double check all finals competitors logs after flights. In my case display on altis showed 13.6m and this was altitude which was noted by timekeeper. It is not possible to validate such a reading without usage of a computer. Therefore, during competitions where such a low start highs occur it might be useful to ensure reading on the display is correct.
Finally, if the wear of a device is a problem, devices older than some amount of time should be prohibited which will eliminate mentioned problem. (Even though rules does not say that I still promise to switch to newer Altis
I hope we can discuss encountered problem and find a solution to prevent such situations from happening in the future. As I said I want to be fair with others rather than sweep whole case under the carpet. Additionally, what is worth mentioning, I shared whole unedited logs instead of print screens which could be changed without any problem to cut out the part which shows the problem. Believe me I could do this in photoshop in such a way you would never noticed that something was changed
zkráceně výškoměr ukazoval o 9 metrů méně...
Pro možnost přispívání do fóra je nutné: Přihlásit se .
9 roky 2 týdny nazpět #18895
napsal hrabacek
Odpověď od hrabacek na téma Světový pohár F5J Lanškroun
Tak co na to elektronici ? Nestává se to častěji? Z vlastní zkušenosti vím, že mi výškoměr po zapnutí a vypnutí motoru ukázal + 6 m! A to několikrát!!! Poslal jsem ho do Altisu a ty mně napsali, že to mohlo být špatně utěsněnou kabinou, kde vlivem proudění vzduchu mohl vzniknout mírný podtlak? Můžu doložit e.mailem!
-9 m svědčí o momentálním přetlaku v kabině nebo špatném barografu!!!
-9 m svědčí o momentálním přetlaku v kabině nebo špatném barografu!!!
Pro možnost přispívání do fóra je nutné: Přihlásit se .
9 roky 2 týdny nazpět #18897
napsal pik
Odpověď od pik na téma Světový pohár F5J Lanškroun
Ahoj Lojzo, jestli sem to dobře pochopil, tak tohle je trošku něco jiného. Došlo k chybě při kalibraci, jinýmy slovy, když zapojil baterku, tak se výškoměr nezkalibroval na nulu
Pro možnost přispívání do fóra je nutné: Přihlásit se .
Vygenerováno za 0.253 sekund