![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#18
|
|||
|
|||
![]()
I've heard from one user also that the Vega driver can also be used for reading IGC files and writing tasks
Impossible. The Vega is not a logger. Its protocol cannot be used for any of that. Seems I got confused there. It might have been the Altair Pro/RU driver instead. Why not implement the driver according to the protocol documentation without any workarounds and assuming no bugs. Because ClearNav refuses to cooperate with us, that's why. There will not be a ClearNav driver in XCSoar because nobody will write it. I think if there is a high demand for it, someone will step up and do it. Whether it will be me or someone else, I don't know yet. I clearly don't see the problem here, besides ClearNav missing the point of being an open vendor. Why would they care? They would care if it turns out to be important for their (potential) customers. What you wrote makes people think openness doesn't matter, because, uh, you wrote that it will likely work anyway, and if not, we will disable some workarounds, and then it may work (or not?), yadda yadda. But it will not work, and nobody will figure it out. What you wrote is misleading and only distracts from the real problem. You make it worse, because your post seems to approve ClearNav's behaviour, instead of explaining why openness matters. I admit you didn't explicitly write that, in fact your posts don't say anything, it's only speculation and rumor, devoid of facts. But it's rhethorically suggstive to people who have less insight into this big problem than we do. To be honest, I don't know how much more open they need to be. They gave the information on the protocol and they created a forum to discuss the implementation. All they did not do yet was lending or donating hardware, but I don't expect every vendor to do that. If they don't they will simply have to wait until someone steps up to do the driver. I think this has started to be a rather pointless off-topic discussion since the original thread was about the quality of the vario itself, and not the connections to external devices. Sorry about that! |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Where are you Butterfly vario? | [email protected] | Soaring | 17 | May 25th 14 05:49 AM |
Butterfly vario review | [email protected] | Soaring | 3 | October 10th 12 08:50 PM |
YouTube Video of the new Butterfly Vario | Richard[_9_] | Soaring | 11 | September 25th 12 10:00 AM |
Butterfly vario info | [email protected] | Soaring | 1 | August 7th 12 10:08 PM |
New Butterfly Vario | Paul Remde | Soaring | 238 | February 20th 12 04:05 AM |