** Digitech Central Telemetric Unit for Jeti **
04-06-2018, 10:39 PM
#27
good question..
as we speak i am receiving 10 final prototypes next week.
these will be field tested for a week , none stop in a few different models with different engines.
if those are ok , i am having the first batch made and ready for sale..
for the USA these will be exlusive distributed by Danny at Aeropanda.
at the same time we are still developing , and happy to say we will be supporting officially the new Powerbox Core.
Powerbox Core support will be done in 4 quarter this year.
as we speak i am receiving 10 final prototypes next week.
these will be field tested for a week , none stop in a few different models with different engines.
if those are ok , i am having the first batch made and ready for sale..
for the USA these will be exlusive distributed by Danny at Aeropanda.
at the same time we are still developing , and happy to say we will be supporting officially the new Powerbox Core.
Powerbox Core support will be done in 4 quarter this year.
05-01-2018, 04:56 AM
#29
Twin engines are of course supported by the CTU. When setting one of the CTU as device 1 (device 0 is the "master" CTU) it will only report engine data whereas the "master" CTU will report engine data as well as G force and Altimeter.
06-11-2018, 10:27 PM
#31
Sandro... That’s excellent news... so glad to see Jeti device explorer integrations. Makes adjustments so much easier.. wished you could incorporate a “speed sensor” into the CTU and called it “CTU plus”
David
David
06-11-2018, 11:00 PM
#33
06-11-2018, 11:05 PM
#35
This also makes the CTU much smaller (less thick) to keep the IAS sensor outside. Hope it will do the trick for most, it even lets you place the IAS closer to the Pitot
06-11-2018, 11:06 PM
#36
We selected to make the IAS outside as there are different types of speed versions available, makes it easier to just have one version of the CTU that way. You simply select the max speed by selecting the correct SB-IAS.
This also makes the CTU much smaller (less thick) to keep the IAS sensor outside. Hope it will do the trick for most
This also makes the CTU much smaller (less thick) to keep the IAS sensor outside. Hope it will do the trick for most
yes! what he ^ said ;-)
06-11-2018, 11:19 PM
#37
Got it ... I guess we will stick,the SB-IAS (1280 kph ) on top of the CTU...
Looking forward to install the unit in my next jet ...
Thank you for sharing the good news you got last week
... I guess we will stick,the SB-IAS (1280 kph ) on top of the CTU...Looking forward to install the unit in my next jet ...
Thank you for sharing the good news you got last week
06-11-2018, 11:40 PM
#39
06-12-2018, 10:04 PM
#41
i have looked on the jetcentral webpage bt could not find a manual for their telemetric device.
our CTU has a direct connection to most turbines.
i have written a couple of emails to jetcentral but unfortunately i never got a response back , so at this point we do not support them.
at least not the SE versions , the older ones have a different ECU wich is supported by us.
so at this point you can not enjoy the full intregation our CTU has to offer , where other manufacturers where glad to help.
br Sandor
07-06-2018, 05:08 AM
#44
So, I was doing some more testing of software and system today. During the test, I decided to shoot a small video of a ultimate setup 
It consists of a RSat2 receiver, my SB-EXT2+2 (2 x Expander ports + 2 x Servo outputs), 4 x CTU, 1 x Jeti MAlti, 1 x Jeti MRPM HALL, 1 x Jeti MBar and 2 servos!
All driven by a DC-24. This setup has 68 sensors in the system (you can only show 40 of these simultaneous on the screen, but all can be used from LUA scripts, alarms etc) and delivers data from 4 turbines, G force, Altimeter, Fuel consumption/reserve in tank,
Video is here:
It consists of a RSat2 receiver, my SB-EXT2+2 (2 x Expander ports + 2 x Servo outputs), 4 x CTU, 1 x Jeti MAlti, 1 x Jeti MRPM HALL, 1 x Jeti MBar and 2 servos!
All driven by a DC-24. This setup has 68 sensors in the system (you can only show 40 of these simultaneous on the screen, but all can be used from LUA scripts, alarms etc) and delivers data from 4 turbines, G force, Altimeter, Fuel consumption/reserve in tank,
Video is here:
07-12-2018, 08:19 AM
#49
Sandor,
That is incredibly impressive. The most comprehensive Lua extension I've seen, and some really nice functionality!
It really shows when the devices and the code are done by people who actually fly which is why the user-extenisble systems (like Jeti with Lua) are the only way to go. I hope the other radio manufacturers are paying attention.
I wonder what the PowerBox gang is doing with user extensibility with their new system..
I have my pre-order for the CTU in to Danny at Aeropanda and am excited to get mine :-) And looking forward to reading the lua code to get schooled!
Dave
That is incredibly impressive. The most comprehensive Lua extension I've seen, and some really nice functionality!
It really shows when the devices and the code are done by people who actually fly which is why the user-extenisble systems (like Jeti with Lua) are the only way to go. I hope the other radio manufacturers are paying attention.
I wonder what the PowerBox gang is doing with user extensibility with their new system..
I have my pre-order for the CTU in to Danny at Aeropanda and am excited to get mine :-) And looking forward to reading the lua code to get schooled!
Dave
07-12-2018, 08:34 AM
#50
Sandor,
That is incredibly impressive. The most comprehensive Lua extension I've seen, and some really nice functionality!
It really shows when the devices and the code are done by people who actually fly which is why the user-extenisble systems (like Jeti with Lua) are the only way to go. I hope the other radio manufacturers are paying attention.
I wonder what the PowerBox gang is doing with user extensibility with their new system..
I have my pre-order for the CTU in to Danny at Aeropanda and am excited to get mine :-) And looking forward to reading the lua code to get schooled!
Dave
That is incredibly impressive. The most comprehensive Lua extension I've seen, and some really nice functionality!
It really shows when the devices and the code are done by people who actually fly which is why the user-extenisble systems (like Jeti with Lua) are the only way to go. I hope the other radio manufacturers are paying attention.
I wonder what the PowerBox gang is doing with user extensibility with their new system..
I have my pre-order for the CTU in to Danny at Aeropanda and am excited to get mine :-) And looking forward to reading the lua code to get schooled!
Dave
the Lua was written by Daniel Maiorano (designer of the CG wizard and the Angle & Throw) he flys jets also ;-)
the Code for the CTU , Device Explorer and the Hardware design was Written and designed by Carsten Groen , he did many designs, long time friend and we allready did some stuff together.
and we are doing much more Stay tuned!.
the Design of the CTU box was designed by Lars Nielsen , also a Great Friend , CAD designer and jet jocky.
i am just the guy who comes with the idea , bring them all together have the parts made and maintain contacts.!
we had many more Help from Distributors and Jeti we could not have done the Explorer part without being "supported" by Jeti factory.
Powerbox.
About Powerbox , we have been involved with the Core Telemetric desiogn for some time now , we are working closely with them.
we will do our best to have the same Layout done for the Core , because like you said this is the way it should be.
we are in "talks"with another big company , but we said upfront we want full menu access , and not "emulate"a bunch of sensors..
thanks for the nice words!.
Br Sandor