Calcul de couple interne TurboLamik : comment le configurer
TurboLamik internal torque calculation is the fallback for builds where the TCU is not being told how much torque the engine makes over CAN. If you are using a standalone ECU, or your car does not send torque over CAN, the TCU needs to work it out from a manifold pressure signal. That means a MAP sensor, either wired to the TCU or sent over CAN, and a base torque table scaled to match your engine.
Get this wrong and everything downstream suffers. The manual states that any problems with rough shifting should start by checking whether that table is correct.
What the TCU actually needs
Before torque calculation matters, the TCU needs four inputs to function properly:
| Input | Notes |
|---|---|
| Throttle position | Analog input or CAN |
| Brake pedal signal | Analog input or CAN |
| RPMs | Analog input or CAN |
| Torque generated by engine | CAN, or calculated internally from MAP |
Torque is the only one of the four that a standalone ECU often cannot provide over CAN. The manual notes that some cars do not support torque by CAN, or the torque resolution is very low. In either case you can try a MAP sensor over CAN, and if that is not available you install a MAP sensor.
Prerequisites: a MAP signal
Make sure a MAP sensor is installed, or that you are receiving MAP over CAN. The manual lists MAP input as input 13 in that context.
Without a reliable manifold pressure signal, the internal torque calculation has nothing to work from. Fix the MAP side before you touch the table.
Setting up torque calculation in TunerPro
The configuration itself is short. The manual lists it as four steps:
- Open "Torque Calculation".
- Enable the flag "Automatic detection of torque calculation input".
- Set "Torque Calculation Input" to 0.
- Select one map, "Base Torque Table RPM/MAP", that uses your desired units of torque.
That last point matters. There is more than one torque map available, and the base table you choose must use the torque units you intend to work in.
What the base torque table does
The base table reflects the torque your engine generates at a given manifold pressure. It is indexed by RPM and MAP. The manual describes the shipped map as a good start point that needs to be adjusted to your engine.
Two maps are involved in the system:
| Map | Role | Should you modify it |
|---|---|---|
| Base Torque Table RPM/MAP | Torque at a given RPM and manifold pressure, referenced to atmospheric | Yes, scale it to your engine |
| Pressure\Torque Multiplier | Boost compensation for turbo cars | Not in most cases |
The base table is capped at 100 kPa, which is atmospheric pressure. For a turbo car, boost is handled by the separate Pressure\Torque Multiplier map, and the manual states it should not be modified in most cases.
Scaling the base table: the multiply method
The manual gives a worked method using a naturally aspirated engine as the example.
Start by finding the peak torque your engine makes. The example uses an N/A M73B54 with a peak of 490 Nm. Then find the peak figure already on the base map, which in that base map is 288. Divide one by the other: 490 divided by 288 is 1.7.
| Step | Value in the manual's example |
|---|---|
| Engine peak torque | 490 Nm |
| Peak value already in the base map | 288 |
| Multiplication factor | 1.7 |
Then select all cells in the map, choose Function Multiply, set the value to the factor you calculated, and press Execute. Save the map and upload it to the TCU.
The result is a starting curve rather than a finished calibration. The multiply approach scales the whole table evenly, which gets you close but not exact.
Verifying the calculation
This is the part that decides whether the setup is usable. The manual gives a specific check.
| Test | Expected result |
|---|---|
| Engine running, idling | Engine TQ (CAN Tq dashboard) should be between 10 and 20 Nm |
| Holding around 3000 RPM | Torque should again be around 10 to 20 Nm |
| Holding around 5000 RPM | Same check at the higher RPM |
| Table graph in 3D | Map should look smooth; adjust if it does not |
| Slow test drive | Gear changes smooth, clutches not slipping extensively |
The manual suggests turning on Data Tracing in TunerPro, which shows you exactly where on the map the engine is operating. That makes it much easier to find which cells need adjustment.
If idle torque reads more or less than 10 to 20 Nm, adjust it slightly along with all the cells around it to bring it to the correct value. The manual notes this may need bigger adjustments with big cams or rotary engines, because those engines produce a less predictable manifold signal at idle.
The same check applies at 3000 RPM and at 5000 RPM, holding the engine speed steady so the reading settles before you judge it. Then press Show Table Graph and confirm the map looks smooth in 3D, adjusting any cells that create a spike or a dip.
Why the 3D graph check matters
A table can read correctly at idle and still be wrong everywhere else. The 3D graph is how you see that. A torque table with a step or a hole in it will command an odd pressure at that operating point, and the driver feels it as a rough or inconsistent shift rather than as a table fault.
Smoothness in the table is the goal. If the graph has a spike, that spike will show up as a shift quality problem later.
The test drive
Finish with a slow test drive. The manual's criteria are that gear changes are smooth and the clutches are not being slipped extensively. That is a practical check rather than a numeric one, and it is the last gate before trusting the setup.
If the shift feel is not right at this stage, go back to the table rather than adjusting shift pressures. The manual's own advice is that rough shifting problems should start with the torque table.
Common mistakes
| Mistake | Why it causes trouble |
|---|---|
| No MAP signal or MAP input not configured | Torque calculation has nothing to reference |
| Wrong base table selected for the torque units in use | Values are scaled incorrectly from the start |
| Forgetting to multiply the whole map | Table sits far from the engine's real torque |
| Modifying Pressure\Torque Multiplier on a turbo car | The manual states it should not be modified in most cases |
| Judging the table from one RPM point | Smooth reading at idle can hide errors at 3000 and 5000 RPM |
| Skipping the 3D graph check | Spikes in the table become shift quality faults |
Frequently asked questions
When do I need internal torque calculation? When the TCU is not being sent torque over CAN. The manual lists this as the case for standalone ECUs, cars that do not send torque by CAN, and cars where the torque resolution is very low.
What MAP input does the TurboLamik use? The manual references MAP input as input 13 when running MAP over CAN.
Which map do I scale to my engine? The Base Torque Table RPM/MAP. Scale the whole table so its values match the torque your engine actually makes. The Pressure\Torque Multiplier map is for boost and should not be modified in most cases.
How do I work out the multiplication factor? Divide your engine's peak torque by the peak value already in the base map. The manual's example is 490 Nm divided by 288, giving a factor of 1.7.
What torque reading should I see at idle? Between 10 and 20 Nm on the Engine TQ (CAN Tq) dashboard. Adjust the surrounding cells if it reads higher or lower.
Does the base table cover boost? No. The base table is capped at 100 kPa, which is atmospheric. Boost is handled by the separate Pressure\Torque Multiplier map.
Next step
If you are setting up torque calculation on a standalone ECU or a car that does not send torque over CAN, tell us the gearbox, engine and controller you are running. We can talk through the MAP side and what the torque table needs to look like for your combination.
Torque calculation steps, the 490 Nm example and the 10 to 20 Nm verification figures in this article are taken from the TurboLamik official manual (manual.turbolamik.eu).
Setting up or buying a TurboLamik controller for a new 8HP build? Start with the TurboLamik 8HP controller buyer guide for the gearbox, ECU, harness and shifter requirements before you order.