Software Turbo Speed Reader Download [BETTER]
Manuel Medina
I hope that you are fine and having a nice last morning of the week. Today, I got strange numbers on my Task Manager CPU performance information. I was working on data modelling using 8 cores for the modelling and one more core for the whole code. Suddenly, I saw that the speed is reaching sometimes the speed of 3.66 GHz. Why does my cpu reach speed higher than the max turbo speed given that:
I searched the web, most of the cases are focusing on speed when it is higher the Base speed, where the reasonable answers to such cases are about the fact that the cpu uses the Max Turbo. However, in my case, my cpu is reaching speed more than not only the Base, but also the Max Turbo Frequency with having the intel Turbo Boost Max Technology 3.0 disabled. Could you please answer my question? Thank you very much.
Does the increase in clock frequency above the base clock is the only way this gadget shows the turbo boost?If yes then again they are showing the single textual increase in frequency value as turbo boost.
According to my monitoring program, the cores in my CPU have independant clock frequencies of eachother. This is probably intel speed-step working [Citation needed], (since naturally you cannot set individual clocks for your cores). The cores throttle based on system load, as clearly seen in the first screenshot:
Q2. Does the increase in clock frequency above the base clock is the only way this gadget shows the turbo boost? If yes then again they are showing the single textual increase in frequency value as turbo boost.
Hello all! I have a Garrett GTX3582R Gen II turbo with a 10 blade compressor wheel. According to Garrett, their turbospeed sensor outputs at 1/8th input frequency. Using the Link provided equation, I set my calibration to 7500 and now turbospeed reads extra high on our AIM Dash, for example 93 rpmx1000 at idle. I've checked my CAN multipliers and everything is set to 1. Seems like everything should be right, what am I doing wrong here?
We've switched and not getting any reading from either DI 15+ or DI 16+. We switched back to DI 3 and it worked as expected. We've ensured we turned on the new DI to Turbospeed and disabled DI 3. Any thoughts?
We updated the firmware and the turbo speed would read for a few seconds and then go to zero. We grounded the DI- and no luck, same issue. By happenstance, our mechanic held the DI- wire in his hand and all of a sudden the turbo speed started to read properly. After talking with an electrical engineer friend, we decided to try the smallest capacitor we had, 104 picofarad, from DI- to ground and now the turbo speed reads properly. Thoughts?
@Adamw, I'm the mechanic that was working on the car with defjux. The turbo speed works fine on DI15 with DI- grounded through the capacitor. I have no problem leaving it this way if it's working, I just want to make sure it isn't an indication of something wrong with the wiring in general, whether that be poor grounds, power supply issue etc (all have been checked to the best of my ability). To reiterate, the same wire going into DI15+ was working fine on one of the lower speed DIs, but would overrun the frequency limit around 57k turbo speed. The rpm reading at idle is the same on the high speed input as it was with the low, so for now it seems to be functioning.
I dont see any harm in leaving the cap there. I dont know enough about how the differential DI circuit works to offer an explanation of the cause. Just I have seen turbo speed connected to those DI's in the past with nothing special required. But if it works and continues to work under normal operating conditions that I would be happy.
This speed limit programmer is designed to allow the user to set a speed limit of their choosing. User may adjust the speed block down if they choose to limit the mph of the vehicle for safety reasons. User may also correct the speed reading for bigger or smaller tire sizes. Includes complete installation instructions. This product is 100% plug and play with minimal installation and setup time.
*This speed limit programmer locks out the speedometer on the Wildcat XX at 70mph. While the speedometer will read approximately 70mph, the vehicle will continue to accelerate beyond 70mph for competition use with proper training and safety equipment.
I have similar issue. I use a Tacx Turbo and set up sessions using the Tacx Desktop app. The turbo emits Bluetooth and Ant+ signals. My bike is fitted with a Garmin speed and cadence sensors which emit Ant +. I Use the Bluetooth feed for Power on he Taxc app and Ant+ from my Garmin sensors for speed and cadence. The app tracks speed and cadence correctly. However, I also track the turbo sessions on my Fenix 5 and although the Power readings are the same as the app I consistently get readings at 150% higher for Speed and Cadence (and by default the distance is also way up as well. This is simply because my Fenix is reading both the Ant+ signals. Now the killer, you can't do anything about it. You can't instruct the Fenix to ignore one of the feeds and you can't tell the Tacx turbo to not send Ant+ signals.
But even with 15,34 it was a bit low so I adjusted by myself the rear wheel circumference in order to obtain a speed that I used to have when I ride my bike on the road with the same power and cadence.
Thanks for this. I've read the article and checked out the equivalent Elite turbo against my Tacx Vortex. (So many variations!!) It looks as though the speed (and therefore distance) is related to the drum size of the Tacx turbo and a calculation linked to its radial velocity. (The give away is that the use Pi in the equations). I've also had a reply suggesting that I divide my actual wheel circumference by 1.57 which is roughly Pi/2. and as an aside was also the answer to lots of questions my old professor used to set 46 years ago when I was studying telecommunications principles. Just goes to show that what goes around comes around.
Thanks again Patrick. I adjusted my watch for a turbo ride today and it has worked. MIne is a Tacx trainer so I had to tinker with the adjustment factor until it matched the reading on the app but it's all good now.
Standard's Turbo Speed Sensors are engineered to accurately detect turbocharger operating speed and reduce exhaust temperatures. These direct-fit replacements are extensively tested to OE specifications to ensure superior performance and long service life.
Hello i have a weird problem with icue.When it's open my 13900k will always maintain 5.5ghz which is the turbo clocks,even on idle.When i close iCue software clocks go at 800mhz as they are supposed to on idle.I'm running 4 LL fans,vengeange rgb ram and Corsair h150i elite lcd xt connected to a commander pro.
The other variable is how you've set up your BIOS. Some MB makers turn off limits out of the box and that can cause aggressive behavior, like clocking all cores up to turbo max when any one core is loaded. This varies. Even at default Auto everything, the CPU behavior may not always be as expected and a subtle change to the Vcore mechanics can shift idle power consumption from 20 to 50W.
Most speed sensors are hall effect or reluctor style. Optical require a Light to strike a sensor which is interrupted via a trigger disc or blade. So in order to use an optical you would need the compressor blade to interrupt an LED - trigger.
On a compressor map there is "turbo speed lines" these lines show at what RPM the turbo is operating at X pressure ratio and/or mass air flow. It will help you determine when your are starting to reach the choke line and over spin the turbo.
Thanks for your answer, I understand that the sensor is used to figure out where on the compressor map you are, but I don't understand what the limiting factors are - I have only seen turbo speed sensors on top end drag cars, and from what I know about compressor sizing, the peak compressor efficiency "island" at the centre of the map is targeted towards peak power, rather than running the turbo hard up against the right hand side "choked" region... In any case, you'd know when the turbo is up against the choke line anyway, even without a speed sensor, since power would flat line on the dyno..
Out of interest, I saw that some Garrett turbos now have a factory speed sensor port (such as the new version of the GTX42) which I think is cool! The idea of monitoring turbo RPM seems to be catching on!
There's a few uses for a turbo speed sensor. As has already been mentioned, between turbo speed and pressure ratio you can pin point where in the compressor map you're operating. This can be useful in validating turbo selection. You can also utilise turbo speed in the ECU control algorithms - Say for example in some cases you could use turbo speed as an input to boost control or as a safety parameter to prevent over speeding the turbo.
I am running an EFR 7064 turbo myself with the speed sensor. Really nice feature to have. Not exactly necessary for most use cases but I like seeing the turbo RPM to assess the effect of certain changes on spool time for example.
df19127ead