Excellent question Gary!
No it does not :D
How many do you want, and how would you like them to work ?
(This is the good thing about doing this "ourself" ;) )

PS: Jokes aside, this is a very good idea Gary, very nice to get some inputs and ideas from you guys !!!

HoundDog, I agree, this is also how I do it when flying something that does not go like a rocket (I have to get the screen out to an arms distance anyway, my eyes are not young anymore :D )

hehe once again the genius Carsten makes toys.. :D

Carsten,
How do you get AoA data?
Did you make an AoA vane?
I've been working on my own telemetry as well for quite some time.
I also hooked up a small GPS receiver and an SD card interface for FDR purpose.

Yann, if you look in the ASSI thread you can see some details. Baaically it is a special Pitot tube with 4 ports.

Did some more work on the Android system. Also developed a small GPS receiver that works together with the system (connects via the CAN bus). It delivers GPS positions and it has a very sensitive Altimeter mounted (resolution around 20 cm (8 inches) !)

Used one of my recorded flights (Ready2Fly Venom with P20SX), simulated a dual engine setup using these data (using the single engine data for simulating a second engine)
This now enables some nice features on twin engine jets :)

Work continues, more updates when I have some more news....

https://www.youtube.com/watch?v=n28znVqEOsc

https://www.youtube.com/watch?v=n28znVqEOsc

Cartsten, Super!!!!
now get this ready for those Evojet Ecu's..... want this for my Tomcat...........

:) Still waiting for some info from them

Something new regarding the telemetry, now it is possible to connect to a small "Bluetooth gateway" I have running. That means that you no longer need to have the small radio module connected to the phone via the USB port !
The idea is then to have the BT gateway with reach of yourself when flying (max distance around 15 meters or so), it will then relay the live data from the plane to your phone !

Hoping the BT gateway is not a 250 kgs armored box :p

How about AMT, any news from Ray about the interface?

Jan

Hi Jan,
no, not yet

Carsten, did I see somewhere that your devices will soon be compatible with the Behotec ECUs??

Hi Mark,
If I remember correctly, Oli is talking to them (I'm sorry, but I kinda lost track of all the turbine manufacturers, they are initially interested. Then it takes forever to get information etc from them. Guess the need/market is not big enough for this stuff).
So far, the only confirmed working ECU's are all the JetCats and all that uses the new Xicoy ECU's
Maybe when my device/system is finished they will open their eyes ;)

Just an FYI I use Carsten's ASSI units and they are amazing! I can just flip a switch and it tells me in an earbud exactly how many ml of fuel I have in the tank. Very handy at jet meets when it seem's like everyone needs to land at the same time.

Don't overlook his gear air pressure sensor. Brilliant piece of work .. saved me from a gear up landing a couple times .. worth it weight in gold!

Only thing would like to see an option for mph and psi so I don't have to convert in my head.

All products have performed flawlessly over a hundred or so flights.

Thanks for these products, Carsten.

Hi Steve,
thanks for the kind words :D
I try to do my best with this stuff :o The Android app will have a "imperial"/"metric" setting for this stuff! If I remember correctly from my "JetCat info display" I did some years ago, most people want the EGT of the engine(s) still in deg C instead of Fahrenheit, does that still apply ?

The fuel amounts will be in oz, pressure in psi and the speeds in mph when coming from the Android phone.
I will gradually go away from the Futaba/SBUS2 telemetry, it is just too limited and kind of "ugly" the way I have to mis-use the various sensors on the radio.

The newer systems I will be making will apart from Futaba also support JR transmitters (XBus) ;)

When done, I will only use the data from the receiver "one way", that is only information about the channels position (servo). No data will flow "to" the receiver like telemetry etc.
This way all telemetry will come from the Android device, this enables us to do exactly what we want from a system like this !!

Great to see all this new gear being developed .. thanks as always Carsten.

For those of us in the old backward "yard-pound" world, as Futaba calls it, yes, we would prefer to have turbine EGT in centigrade .. since that's all we've ever seen we are all "mentally" calbrated to that. For all other readings our mental calibration is in mph, oz, feet, etc.

Dave

Thanks Dave,
the "centigrade" stuff was explained to me the same way a couple of years ago :) I will make it so that the other stuff can be adapted to imperial values, no problem

I look forward to being able to buy this.
Will there be a function to acknowledge a warning and turn off voice prompt for that warning?
Will it only transmit ASSI info or will it be able to process sbus2 info from other sensors - eg a vario in a jet powered glider?
Where can I buy air pressure sensor?

Keep up the good work :)

Thanks Graham :)
The way the warnings are made currently, is the unit will announce the warning twice, and then keep quiet. If the warning goes away (f.ex the airspeed warning) and then triggers again, you will get the announcement two times again etc. Another way would be to assign a switch on the TX that you would have to hit to acknowledge the warning, maybe that is a good idea also (sonfigurable) ?!?

As it is now, no other SBUS2 info is sent back to the Android device, but that might also be a good idea to include the 32 slots of data, and then assign the sensor type for each slot (as we do in the TX) !
It would only be supported for SBUS2 then (and not other TX types)

The airpressure sensor (for retracts etc) can be ordered from Oli from Ultimate Jets: http://www.ultimate-jets.net/collect...ressure-sensor
It will show the airpressure on the TX also (using SBUS2) as well as the Android system once it becomes available

Can't wait to get my telemetry system prototype:o

I would think that you would want to maybe pause low fuel warning but have the airspeed continue warning whilst below the low trigger point and should go away again once above the minimum.
Someone else suggested that perhaps not having that function arm until that speed was passed would be good so that you would not get readings while taxying

I get your point Graham!
The IAS is only announced when the speed is above 20 km/h and below the settable point (60 km/h in the example) so you do not get any announcement when taxiing. But the abillity to have warnings with different severity could be a good idea, I will look into this!

Just implemented support for JR XBus in the ASSI device, this means that the features of the ASSI device (autothrottle, flaps monitoring/warning of IAS/AoA) will function and at the same time the telemetry data is delivered to the ground via the Android app :) More video etc once finished, but so far everything is looking good!

https://www.youtube.com/watch?v=0gpWX0NAOQM

:cool:

A rough drawing of what can be connected to what :)
Note: AMT support not yet finished