RCT Jeti VarioMeter released

FuniCapi wrote: Hallo zusammen
Wer meine Code testen möchte muss das Signalkabel zum Empfänger vom Pin D3 auf den Pin TX umlöten.
Gruss Lukas

hallo Lukas,
würde deinen code gerne mal testen.
wo finde ich den?

gruss
gerhard

Würde den ebenfalls gerne testen aber mit BMP280. Ist der berücksichtigt?

Gruß Volker

Hallo Gerhard und Volker

Ich habe meinen Esens all-in-one Sensor hier veröffentlicht.
Der Code ist mehr als nur Vario. Wer die anderen Sensorwerte nicht über mittelt haben möchte muss die entsprechenden Codezeilen auskommentieren/löschen.
Der BMP/E280 ist nicht unterstützt, aber ich schau mir das mal an.
Wenn ihr den Esens-Code testet, dann schreibt doch bitte euer Feedback/Anregungen für Erweiterungen.

Gruss Lukas

Hallo Lukas,
Ich habe noch ein Vario basierend auf RCT, mit BMP280.
Dieses würde ich eben gerne mal mit deiner Software ausprobieren um zu sehen ob dein Filter gegenüber dem aktuellen in RCT Vorteile bringt.

Neue Varios baue ich nur mit MS5611 u. basierend auf OXS.

Gruß Volker

Hallo Lukas,
Danke für Deine Antwort.

Meine HW-Konstellation:
Arduino: Pro Mini 3,3V/8MHz
Sensor: BMP180

Gruss
Gerhard

Hmm. Looks like I'm not getting notifications from this thread for some reason

This discussion is getting a bit scattered around, I'm hoping we could keep it somewhat close to RCT-Vario found on RCT website. If we need a "Vario development discussion" it should in my opinion be a separate thread. My intention with threads like "RCT VarioMeter released" and "Jeti Fuel Sensor released" etc is to announce here that they are available (everyone does not read RC-Thoughts.com) and to give support in a place where users meet, not just by email that I get a lot of too. I hope you understand my side on this

About UART / SW Serial:

Yes, software serial will rarely perform as good as hardware-serial. In some cases (with some Jeti libraries) it also may disturb or even make it impossible any time-based operations making it necessary to use different software-serial and jeti library combinations, they all do not work with each others. (This is also one of the reasons I'm using different software-serials and Jeti libraries in my sensors)

What I'm curious about is the question "how to make software serial faster", why? What are you guys after?

My simple Vario uses a interrupt-driven (by Radek Voltr modified) "NewSoftSerial" and by design has some flaws. But in my use the advatages are greater than flaws If I remember correctly some of my sensors use AltSoftSerial which is less sensitive for interrupt-delays. If you want to tinker with it all necessary library-files are always included in the zip-package you download from my github for respective sensor.

I have no skills, time or in fact need to for example write my own library or to make sensor-code without libraries. I have one (Jeti-)project going on that will maybe require me to write telemetry-code from scratch but that will take a long time and at the moment I do not believe it will be usable in sensors.

RCT-sensors are designed to be very affordable single sensors with performance close to or better than Jetimodel's "real" sensors and something pretty much everyone can build and try. And in that I think I have succeeded.

I have mixed feelings if DIY-sensors should be seen as "replacement" for Jetimodels sensors or as "entry level"-steps to the wonderful world of telemetry. I'm letting everyone make that decision for themselves