CoTASA (V3.0) VNE alarm, horizon, etc
CoTASA (V3.0) VNE alarm, horizon, etc
The beta version of CoTASA V2.0 is almost ready and should be available tomorrow.
For the time being, the recovery of an existing CoTASA.ini file is not implemented and the documentation is only in English.
If you are willing to perform tests (preferably rather thorough), please contact me by PM.
For the time being, the recovery of an existing CoTASA.ini file is not implemented and the documentation is only in English.
If you are willing to perform tests (preferably rather thorough), please contact me by PM.
Last edited by Bre901 on Tue Nov 03, 2020 7:36 pm, edited 5 times in total.
CN: MPT — CondorUTill webpage: https://condorutill.fr/
Re: CoTASA V2.0
.
CoTASA version 2 is now available.
Many thanks to all the beta-testers for the time they spent hunting bugs and the suggestions they made
CoTASA V2 (installer or Zip package) may be downloaded from the new webpage : http://condorutill.pagesperso-orange.fr
There have been many changes since version 1.1, even previous users should take some time to read the manual.
A short description of the new features can be found in the changelog.txt file
Special attention should be put to setting up the Condor UDP.ini file.
No questions will be answered about the issue explicitly described in the manual
On the webpage, you can also find the older version and the other utilities I have developed.
Please do not use the old Google Drive links any more as they won't be maintained in the long term.
CoTASA version 2 is now available.
Many thanks to all the beta-testers for the time they spent hunting bugs and the suggestions they made
CoTASA V2 (installer or Zip package) may be downloaded from the new webpage : http://condorutill.pagesperso-orange.fr
There have been many changes since version 1.1, even previous users should take some time to read the manual.
A short description of the new features can be found in the changelog.txt file
Special attention should be put to setting up the Condor UDP.ini file.
No questions will be answered about the issue explicitly described in the manual
On the webpage, you can also find the older version and the other utilities I have developed.
Please do not use the old Google Drive links any more as they won't be maintained in the long term.
You do not have the required permissions to view the files attached to this post.
CN: MPT — CondorUTill webpage: https://condorutill.fr/
Re: CoTASA V2.0
Big Thank You!
José Oliveira
Hey you Chicks flying bricks....
Come Fly Gliders ! Be Outsiders!
Hey you Chicks flying bricks....
Come Fly Gliders ! Be Outsiders!
Re: CoTASA V2.0
thank you very much Marc,
as a beta-tester I use vers 2.0 for a longer period.
The application is stable, very intuitive,adaptable and helpful.
It's good to have you as a coding expert in the community.
best regards
Ikarus DB1
as a beta-tester I use vers 2.0 for a longer period.
The application is stable, very intuitive,adaptable and helpful.
It's good to have you as a coding expert in the community.
best regards
Ikarus DB1
Re: CoTASA V2.0
At the risk of not getting an answer as I havent yet read the manual is there any chance to get a wind indication?
For a moment I thought the blue arrow in the attitude indicator was the wind direction, but it seems to just indicate North.
Is there any wind information in the UDP data stream?
For a moment I thought the blue arrow in the attitude indicator was the wind direction, but it seems to just indicate North.
Is there any wind information in the UDP data stream?
Re: CoTASA V2.0
yes
No, it is the wind directionFor a moment I thought the blue arrow in the attitude indicator was the wind direction, but it seems to just indicate North.
NoIs there any wind information in the UDP data stream?
... but there is some in the flight plan
CN: MPT — CondorUTill webpage: https://condorutill.fr/
Re: CoTASA V2.0
You could defer the actual windspeed and direction with some clever math. But you would need the position data from the NMEA output.
Difference between G/S and airspeed for strenght. And heading and groundtrack for the direction. Thats how XCSoar and LX and all those clever bits of kit show wind.
Difference between G/S and airspeed for strenght. And heading and groundtrack for the direction. Thats how XCSoar and LX and all those clever bits of kit show wind.
PH-1504, KOE
Re: CoTASA V2.0
Of course, but my intention was not to replace any of those clever bits of kit but to complement them.wickid wrote: ↑Wed Feb 20, 2019 10:22 amYou could defer the actual windspeed and direction with some clever math. But you would need the position data from the NMEA output.
Difference between G/S and airspeed for strenght. And heading and groundtrack for the direction. Thats how XCSoar and LX and all those clever bits of kit show wind.
I'm a happy user of XCSoar and NMEA developments in CoTASA are explicitly excluded.
CN: MPT — CondorUTill webpage: https://condorutill.fr/
Re: CoTASA V2.0
Hello,
thank you for this plugin - very helpful!
I can't see water balast indicator-no such belt to the right of text window...
Any idea?
thank you for this plugin - very helpful!
I can't see water balast indicator-no such belt to the right of text window...
Any idea?
Re: CoTASA V2.0
Could you please be more precise :
Glider ?
Amount of water taken before take-off ?
CN: MPT — CondorUTill webpage: https://condorutill.fr/
- Capricorne
- Posts: 397
- Joined: Wed Jul 08, 2009 6:34 pm
- Location: Strasbourg (France)
- Contact:
Re: CoTASA V2.0
May be you forget to say in COTASA.ini that you want to see "WaterBallast"....?
# TEXT & BALLAST
# velocities displayed [0/1]
Display TAS=1
Display VNE=1
Display VA1=1
Display Units=1
Display IAS=1
# netto vario, etc.
Display Netto Vario=1
Display Long-term Integrator=1
Display Stopwatch=1
# Flaps : 0=No, 1=effective setting, 2=optimal setting
Display Flaps=1
# Water-Ballast : 0=No, 1=digital, 2=graphical, 3=both
Display Ballast=3
or you used a plane with no Water in "Stettings"
This is perhaps a little bug we din't discus in beta test, but but no water at all at start, is not like 0 liter after vidange...!
Capricorne - S67
Re: CoTASA V2.0
I proposed this during beta tests: No water taken (or glider without ballast) = no water indicators. IMHO it is OK.
Re: CoTASA V2.0
OK, will correct .ini file.
Thanks
Thanks
Re: CoTASA V2.0
A few issues;
IAS seems to indicate well above what my instruments give me. When I fly 200 KmH indicated on the ASG, Cotasa shows me ~215
After landing it was stuck on 13 KmH
This isnt entirely reproducible though, other times it deviates by just 3 KmH? I tried a few planes and airstart vs tow, but I cant really see the pattern, and I was using the same fpl.
Im also skeptical of your TAS conversion. I have dont done the math, but the difference with IAS seems rather big to me. It could be right though it just seemed high Ill look up some numbers later.
The combination of both issues, the too high IAS and TAS which I assume is derived from the IAS (and I suspect slightly inflated on top of that), makes the overspeed alarm almost unusable to me, even with safety margin set to 0 it starts shouting at me far too quickly.
Lastly, cotasa doesnt notice when you switch gliders. Not sure if you can solve that, but it would be nice
IAS seems to indicate well above what my instruments give me. When I fly 200 KmH indicated on the ASG, Cotasa shows me ~215
After landing it was stuck on 13 KmH
This isnt entirely reproducible though, other times it deviates by just 3 KmH? I tried a few planes and airstart vs tow, but I cant really see the pattern, and I was using the same fpl.
Im also skeptical of your TAS conversion. I have dont done the math, but the difference with IAS seems rather big to me. It could be right though it just seemed high Ill look up some numbers later.
The combination of both issues, the too high IAS and TAS which I assume is derived from the IAS (and I suspect slightly inflated on top of that), makes the overspeed alarm almost unusable to me, even with safety margin set to 0 it starts shouting at me far too quickly.
Lastly, cotasa doesnt notice when you switch gliders. Not sure if you can solve that, but it would be nice