quote:

---

Originally posted by papaxiclas

Have you tried disabling the Checksum option?
I don't know but that checksum number with only one digit is correct? don't you need to indent them?

---

sprintf(command,"$LK8EX1,999999,%ld,%d,99,999,*%X\n!",valor,vel,ck);

quote:

---

Originally posted by katfly

Just an ideea,i saw the "more than impressive" work of Hari ( www.pixelproc.net) ,one of his varios ( http://pixelproc.net/pic24hj12vario.html ) can be used as ""vario co-processor" in a flight instrument. It will respond to commands on the SPI bus to set the sinktone and climbtone thresholds, turn the audio on and off, or return data such as altitude, temperature, climbrate etc."
There is plenty of room inside a Mio m400 for such a small vario.
Beat that {insert name of big vario producer}!

---

quote:

---

Originally posted by katfly


Someone said that pixelproc's vanishment has something to do with a commercial project ( best of luck and many thanks for the inovations).
Right now i stick with Jaros approach , both projects are exactly what i want ( and i have bought a Skytraxx 2 ,splendid thing).

---

quote:

---

Originally posted by katfly

Sorry to hear about your ST2 ,i saw you are not the only one with this issue ( i personally know someone with exactly the same problem,unit replaced,all good) mine is working great ( gift from loving wife ,that's why :D)
However,even i don't do comps i feel that my deck is not complete whithout LK8000...

---

quote:

---

Aside from SMD fine pitch soldering, knowing how to read and understand a microcontroller datasheet/manual, you will have to ensure the timing cycle of the sensor sampling is not affected by sending NMEA messages. This requires understanding the code, knowing how and where to add new code without breaking old code, ability to hook up to a scope or LA to recheck the timing, changing the clock frequency.

That said, its possible and would not be a big task for someone with embedded software and hardware troubleshooting experience (that doesn't mean a college degree in electronics). So your best bet would be to find someone with this experience and infect him with your enthusiasm for the project or bribe him with his poison of choice. If you can find someone, forward the following paragraph :

Even the coin vario should work, unless there is something I haven't foreseen. You would have to increase the clock speed to possibly a few MHz to allow you to generate a UART baud rate that is close enough to a standard baud rate recognized by the Holux, and high, e.g. 38400 baud so that the NMEA print takes less time. Then you would have to insert the code in the right place in the sensor timing cycle to print the NMEA sentence. You would then have to time the sensor cycle to see how the sensor sampling has been affected, and tweak the parameters so that the climbrate calculation is still accurate. There would be other hardware issues and practical trade offs at every step that you would have to make decisions on.

If you can't find someone to do it, and there are enough people interested to donate a Holux 61CS, I'd be happy to do it. Thats right I'm getting mercenary. But I've seen enough designs that are obviously ripoffs (with no attribution) of what I've published on the website, that there has to be something in it for me !! (I already have a gps-vario-gsm project on the shelf that keeps me occupied when I feel the urge to tinker, though I really should get out and actually fly more).

regards
hari

---