** Digitech Central Telemetric Unit for Jeti **
#326
My Feedback: (5)
Thank you very much for the reply. I am using a Mercury and KingTech 210G2
So, I understand about the REX instead of just the R3. If I get a REX Rx, can I still get PowerBox telemetry?
Kind of on the fence about just moving to a CB200 or 210, and Cortex. Bit I already have the PowerBox, and have always like PB products.
V/r
Wayne
So, I understand about the REX instead of just the R3. If I get a REX Rx, can I still get PowerBox telemetry?
Kind of on the fence about just moving to a CB200 or 210, and Cortex. Bit I already have the PowerBox, and have always like PB products.
V/r
Wayne
#327
My Feedback: (6)
Yes.. You just run a servo wire from the telemetry output of the Mercury to a telemetry input of the R3 or a telemetry port you configure on the REX receiver you decide to go with..
Im a powerbox fan.. The primary thing is the power distribution followed a close second by speed compensated gyro gains.....
Chris
Im a powerbox fan.. The primary thing is the power distribution followed a close second by speed compensated gyro gains.....
Chris
#333
Thread Starter
My Feedback: (10)
Release 0.96 Auto Throttle is released!
Principles of operation
The CTU device has an auto-throttle function built in (usage is optional nd at own risk!).
The auto-throttle function’s job is to try and keep the plane flying at a specific IAS.
Basically, the auto-throttle function is a “black box” inside the CTU device and is fed with the current IAS and the IAS it has been set to achieve (setpoint).
The output from this box is a throttle setting.
This setting depends on the error (difference) between the current IAS and the setpoint.
The larger this difference is, the higher the change in throttle setting will be.
To help soften the reaction to the throttle output 3 parameters are also input to the auto-throttle “black box”.
These parameters allow the algorithm to select an optimum throttle output.
The algorithm in use is called a “PID controller”.
The PID controller looks at the difference in the IAS and control the throttle output according to this difference using the 3 parameters (kP, kI and kD).
The parameters are quite sensitive to changes.
The default values in the “CTU Configuration Tool” seems to work well with most JetCat engines, being not too aggressive nor too soft.
Download the Firmware AND bin file here : https://www.digitech-aerosports.nl/product/783681/ctu
look in the list
there are 2 files one is the BIN file for your TX , if you have the latest definitions you do NOT need to update your TX your tx wont report anything .
if you have a old verson (your tx will report on the CTU that there is a newer version).
copy the BIN file in your TX under the map Devices.
upgrade your CTU to 0.96
Please read the Manual for the AT function Carefully.
use at OWN risk.
we tested this in lots of flights without any issues.
please remember for the AT function to work you MUST have a Digitech IAS with special firmware.
if you own a Digitech IAS allready 480kmh version only you can upgrade the Fimrware easy yourself.
otherwise order the IAS for AT at your local dealer.
LUA script
Dave WW2BIRDS will later tell you more about this extreme cool item for your Jeti.
Principles of operation
The CTU device has an auto-throttle function built in (usage is optional nd at own risk!).
The auto-throttle function’s job is to try and keep the plane flying at a specific IAS.
Basically, the auto-throttle function is a “black box” inside the CTU device and is fed with the current IAS and the IAS it has been set to achieve (setpoint).
The output from this box is a throttle setting.
This setting depends on the error (difference) between the current IAS and the setpoint.
The larger this difference is, the higher the change in throttle setting will be.
To help soften the reaction to the throttle output 3 parameters are also input to the auto-throttle “black box”.
These parameters allow the algorithm to select an optimum throttle output.
The algorithm in use is called a “PID controller”.
The PID controller looks at the difference in the IAS and control the throttle output according to this difference using the 3 parameters (kP, kI and kD).
The parameters are quite sensitive to changes.
The default values in the “CTU Configuration Tool” seems to work well with most JetCat engines, being not too aggressive nor too soft.
Download the Firmware AND bin file here : https://www.digitech-aerosports.nl/product/783681/ctu
look in the list
there are 2 files one is the BIN file for your TX , if you have the latest definitions you do NOT need to update your TX your tx wont report anything .
if you have a old verson (your tx will report on the CTU that there is a newer version).
copy the BIN file in your TX under the map Devices.
upgrade your CTU to 0.96
Please read the Manual for the AT function Carefully.
use at OWN risk.
we tested this in lots of flights without any issues.
please remember for the AT function to work you MUST have a Digitech IAS with special firmware.
if you own a Digitech IAS allready 480kmh version only you can upgrade the Fimrware easy yourself.
otherwise order the IAS for AT at your local dealer.
LUA script
Dave WW2BIRDS will later tell you more about this extreme cool item for your Jeti.
#335
#340
#341
My Feedback: (20)
Carston,
I want to use one of my CTUs in a Freewing F-22 EDF foamy turbine conversion. It will be useful nose weight.
Can you tell me if the CTU is powered from the ECU or from the receiver. I have to use a 5 volt BEC to power the receiver, servos, and retracts, but need to power the Kingtech ECU with at least 6v. The CTU connects between the ECU and receiver, so I want to know where the power for the CTU is drawn from. Using Jeti REX12A, DS-24, and K-45G3 ECU.
This would be a good platform to play with Dave's auto throttle also.
Thanks,
Gary
I want to use one of my CTUs in a Freewing F-22 EDF foamy turbine conversion. It will be useful nose weight.
Can you tell me if the CTU is powered from the ECU or from the receiver. I have to use a 5 volt BEC to power the receiver, servos, and retracts, but need to power the Kingtech ECU with at least 6v. The CTU connects between the ECU and receiver, so I want to know where the power for the CTU is drawn from. Using Jeti REX12A, DS-24, and K-45G3 ECU.
This would be a good platform to play with Dave's auto throttle also.
Thanks,
Gary
#344
Carston,
I want to use one of my CTUs in a Freewing F-22 EDF foamy turbine conversion. It will be useful nose weight.
Can you tell me if the CTU is powered from the ECU or from the receiver. I have to use a 5 volt BEC to power the receiver, servos, and retracts, but need to power the Kingtech ECU with at least 6v. The CTU connects between the ECU and receiver, so I want to know where the power for the CTU is drawn from. Using Jeti REX12A, DS-24, and K-45G3 ECU.
This would be a good platform to play with Dave's auto throttle also.
Thanks,
Gary
I want to use one of my CTUs in a Freewing F-22 EDF foamy turbine conversion. It will be useful nose weight.
Can you tell me if the CTU is powered from the ECU or from the receiver. I have to use a 5 volt BEC to power the receiver, servos, and retracts, but need to power the Kingtech ECU with at least 6v. The CTU connects between the ECU and receiver, so I want to know where the power for the CTU is drawn from. Using Jeti REX12A, DS-24, and K-45G3 ECU.
This would be a good platform to play with Dave's auto throttle also.
Thanks,
Gary
The CTU is powered from the receiver. The ECU connection is "data only"
Regards,
CArsten
#345
The SB-IAS can be used as a standalone airspeed sensor, in that case you connect it to EX Bus "as normal". This will give you airspeed and distance travelled on the transmitter.
You can also get the SB-IAS with a special firmware where it will deliver its data as a simple stream of airspeed info, this the plugs into one of the extra ports on the CTU. You then enable the autothrottle function on the CTU. Together with the AT functionality, you will also get the airpseed down on the transmitter (the airspeed is basically sent from the SB-IAS (with the special software in) via the CTU to the transmitter.
Hope this clears it up
And yes, you can update the firmware of the SB-IAS yourself, I have made all my devices so that you just can use the Jeti USB-to-Serial cable to do this along with a small program I made for this (named "Progammer"). The CTU updates via a SD card, or using USB cable).
More info etc at Digitech's homepage
#346
https://www.digitech-aerosports.nl/dealers-distributors
#347
Thread Starter
My Feedback: (10)
here it is , ask them to allready flash it with the CTU-IAS firmware.
#348
Thread Starter
My Feedback: (10)
YAU!
Yet another update.
https://www.digitech-aerosports.nl/product/783681/ctu
we just updated the LUA script
1. changed translation so that each language has its own file (e.g. nl.jsn). Trans.jsn now is just a list of languages. It only reads and loads the one it needs.
2. Replaced kph with kmh everywhere
3. added knots to speed units selection on the menu.
Please be adviced :
Best is first:
1. uninstall CTUautoT from your applications.
2. delete the digitech folder and the CTUautoT.jsn from your TX folder : apps.
3. copy again the latest files back to this folder (apps).
4. reinstall the LUA in applications.
Yet another update.
https://www.digitech-aerosports.nl/product/783681/ctu
we just updated the LUA script
1. changed translation so that each language has its own file (e.g. nl.jsn). Trans.jsn now is just a list of languages. It only reads and loads the one it needs.
2. Replaced kph with kmh everywhere
3. added knots to speed units selection on the menu.
Please be adviced :
Best is first:
1. uninstall CTUautoT from your applications.
2. delete the digitech folder and the CTUautoT.jsn from your TX folder : apps.
3. copy again the latest files back to this folder (apps).
4. reinstall the LUA in applications.
#350
Ravill,
yes! Each CTU can be configured either as a "Master" or "Slave 1" to "Slave 3". The only difference between a CTU that is "Master" or "Slave" is that a master device sends down altitude and G force. The Master also takes care of the Autothrottle function if that is enabled.
All the slaves (up to 3) sends down only engine info and fuel info for the connected turbine.
So yes, you need one CTU for each engine (up to 4) in your plane.
yes! Each CTU can be configured either as a "Master" or "Slave 1" to "Slave 3". The only difference between a CTU that is "Master" or "Slave" is that a master device sends down altitude and G force. The Master also takes care of the Autothrottle function if that is enabled.
All the slaves (up to 3) sends down only engine info and fuel info for the connected turbine.
So yes, you need one CTU for each engine (up to 4) in your plane.