New android based telemetry system for our jets (and other flying things :)
#76
Thread Starter
Danny,
Thanks for the words
The airborne system of mine just needs a SRXL output from your receiver. It will then send telemetry from the plane (engine data, G force, airspeed etc) to the ground. You can then receive the data on an android phone/tablet. If the xg28 would be able to act as a normal android device i dont know ?
Thanks for the words
The airborne system of mine just needs a SRXL output from your receiver. It will then send telemetry from the plane (engine data, G force, airspeed etc) to the ground. You can then receive the data on an android phone/tablet. If the xg28 would be able to act as a normal android device i dont know ?
#78
The Android app is available on Google Play.
Under RATS IGS .
https://play.google.com/store/apps/d...d=com.rats.igs
Under RATS IGS .
https://play.google.com/store/apps/d...d=com.rats.igs
#79
Thread Starter
Sorry, it's not Oli.
You need to have your email added before you can access the app in the play store
Matt, send me a PM with your email address, and I will add you ASAP !
You need to have your email added before you can access the app in the play store
Matt, send me a PM with your email address, and I will add you ASAP !
Last edited by Carsten Groen; 02-07-2015 at 07:11 AM.
#81
Thread Starter
Guys,
I have now opened my Android App up for general download!
It can be found in the Google Play Store: https://play.google.com/store/apps/d...d=com.rats.igs
There is a number of new things implemented. I have now introduced the possibility to add 3 different zone types:
1) Airspace (green definition in attached picture). This defines the allowed airspace you can fly in (typically the airspace that are associated with the airstrip(s) you are flying at.
2) Airfield (orange definition in attached picture). Defines the actual runway(s) you are operating from. I have few features in the making that will make use of this feature. Warning about non-optimum glideslope during landing etc. More to come
3) No-fly zones (red definitions in attached picture). You can define a number of no-fly zones, f.ex houses, windturbines etc that lies within the allowed airspace (defined in 1) above) but that must keep out of. No Fly zones can be defined as a square or a circle.
You will get a warning message if you leave the airspace you are flying in as well as if you cross the boundaries of no-fly zones. You can define as many airspaces, airfields and no-fly zones as you want. When the system tries to detect the correct airspace/airfield, it looks for one that is within 1 km of the current position of the plane.
These features requires the plane/ASSI device to be equipped with a GPS receiver, either the Futaba F1675, SBS-01G or my CAN-GPS device.
If you have defined airspaces, airfields and no-fly zones, you can export/import these so its easy to reuse them on another Android device.
If a flight is recorded for later playback, the file is now stored on the Android device as a comma separated file (.csv) so you can actually look at the raw data from the plane in f.ex Microsoft Excel etc.
None of this stuff changes the way the ASSI device works
Hope you enjoy it!
I have now opened my Android App up for general download!
It can be found in the Google Play Store: https://play.google.com/store/apps/d...d=com.rats.igs
There is a number of new things implemented. I have now introduced the possibility to add 3 different zone types:
1) Airspace (green definition in attached picture). This defines the allowed airspace you can fly in (typically the airspace that are associated with the airstrip(s) you are flying at.
2) Airfield (orange definition in attached picture). Defines the actual runway(s) you are operating from. I have few features in the making that will make use of this feature. Warning about non-optimum glideslope during landing etc. More to come
3) No-fly zones (red definitions in attached picture). You can define a number of no-fly zones, f.ex houses, windturbines etc that lies within the allowed airspace (defined in 1) above) but that must keep out of. No Fly zones can be defined as a square or a circle.
You will get a warning message if you leave the airspace you are flying in as well as if you cross the boundaries of no-fly zones. You can define as many airspaces, airfields and no-fly zones as you want. When the system tries to detect the correct airspace/airfield, it looks for one that is within 1 km of the current position of the plane.
These features requires the plane/ASSI device to be equipped with a GPS receiver, either the Futaba F1675, SBS-01G or my CAN-GPS device.
If you have defined airspaces, airfields and no-fly zones, you can export/import these so its easy to reuse them on another Android device.
If a flight is recorded for later playback, the file is now stored on the Android device as a comma separated file (.csv) so you can actually look at the raw data from the plane in f.ex Microsoft Excel etc.
None of this stuff changes the way the ASSI device works
Hope you enjoy it!
#82
Thread Starter
Just a headsup, the Android telemetry app (and ASSI device) now supports AMT engines
A small (crude quality) video can be seen here (running on sampled data from a Titan engine).
Thanks to Bennie and the gang at AMT for helping with protocol descriptions and testing!
https://www.youtube.com/watch?v=9G8TCvliZQg
https://www.youtube.com/watch?v=9G8TCvliZQg
A small (crude quality) video can be seen here (running on sampled data from a Titan engine).
Thanks to Bennie and the gang at AMT for helping with protocol descriptions and testing!
https://www.youtube.com/watch?v=9G8TCvliZQg
https://www.youtube.com/watch?v=9G8TCvliZQg
#84
Thread Starter
Thanks,
actually the ASSI also support Spektrum (SRXL port) and JR (XBus)
In the case of JR and Spektrum (more info in the ASSI thread here on RCU), no telemetry is sent to the transmitter itself, "only" on the Android device (which does not matter much as 95% of all transmitters are pretty limited when it comes to telemetry anyway )
actually the ASSI also support Spektrum (SRXL port) and JR (XBus)
In the case of JR and Spektrum (more info in the ASSI thread here on RCU), no telemetry is sent to the transmitter itself, "only" on the Android device (which does not matter much as 95% of all transmitters are pretty limited when it comes to telemetry anyway )
#85
Thread Starter
And I could not help it, a special message when the fuel is all gone, hope language used is not too disturbing
(Watch video to the end)
https://www.youtube.com/watch?v=e8TFN78rGUc
(Watch video to the end)
https://www.youtube.com/watch?v=e8TFN78rGUc
#87
My Feedback: (2)
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 !
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 !
Do you have any Gateway suggestions? There are quite a few bluetooth gateways out there. Probably depends on the CAN-RF connector correct?
By-the-way, has anyone confirmed JetCat V5.0 ECU compatibility with the ASSI yet?
Thanks,
Chris
#88
Thread Starter
Chris,
I will get to this in a couple of months (basically need the summer/flying season to be over ) then I will get to the gateway stuff
If you are a "electronics DIY" you can actually "roll your own" gateway. It just needs to pass the TX/RX from a radiomodule to a Bluetooth module (at 57.6KBaud). I have a prototype here running just perfect that way.
I will get to this in a couple of months (basically need the summer/flying season to be over ) then I will get to the gateway stuff
If you are a "electronics DIY" you can actually "roll your own" gateway. It just needs to pass the TX/RX from a radiomodule to a Bluetooth module (at 57.6KBaud). I have a prototype here running just perfect that way.
#89
#90
My Feedback: (2)
Just a note:
I attempted to use my Samsung Galaxy S3 Mini with the RF module connected via USB "On The Go" OTG cable. Unfortunately, the S3 Mini does not have the necessary firmware/hardware to support usb hosting. The standard charge cable supplied with the phone will interface with a PC for file sharing and charging only. On the S3 Mini, the RF module OTG cable is not usable nor are any other OTG adaptors.
Even after rooting the phone, the only solution for the S3 mini will be telemetry through Bluetooth. This is my next project. This is also the case for those trying a Samsung Tab 3 7". Luckily these are older Android items and there are plenty of other devices to use.
Another note: Dreamworks is also stocking the correct Xicoy Serial measures telemetry adaptor for V10.0 ECUs. They stock both kinds so be sure you choose the correct one thus:
http://www.dreamworksrc.com/catalog/...asures-Adapter
I attempted to use my Samsung Galaxy S3 Mini with the RF module connected via USB "On The Go" OTG cable. Unfortunately, the S3 Mini does not have the necessary firmware/hardware to support usb hosting. The standard charge cable supplied with the phone will interface with a PC for file sharing and charging only. On the S3 Mini, the RF module OTG cable is not usable nor are any other OTG adaptors.
Even after rooting the phone, the only solution for the S3 mini will be telemetry through Bluetooth. This is my next project. This is also the case for those trying a Samsung Tab 3 7". Luckily these are older Android items and there are plenty of other devices to use.
Another note: Dreamworks is also stocking the correct Xicoy Serial measures telemetry adaptor for V10.0 ECUs. They stock both kinds so be sure you choose the correct one thus:
http://www.dreamworksrc.com/catalog/...asures-Adapter
Last edited by Chris Smith; 08-01-2015 at 05:16 PM.