Choosing your RPM profile, and setting your own LED count
DNR profiles no longer come in fixed layouts like 5-10-5. There is now one profile per middle segment, and you tell the plugin how many LEDs are on your sides.
What changed, and why your old layout is not listed
We used to publish a separate profile for every combination of side and middle LEDs, so 5-10-5, 4-10-4 and 3-9-3 were each their own download. If your wheel had a layout we had not published, there was nothing for you to load.
Now there is one profile per middle segment, written as X-10-X. The X is the part you fill in inside the plugin, so one profile serves every device with that middle.
The short version
Count your middle LEDs and load that profile. Then set your side count in the plugin. Your sides do not need to match anybody else's.
Both of these load X-10-X. Only the side count differs, and that is set in the plugin.
Which LEDs are which
Everything here comes down to telling two groups apart. The middle is the run across the centre of your device. The sides are the columns at either end.
This device loads X-12-X, and its side count is 6. Not 12, because you count one side, not both added together.
Count your middle, and load that profile
Count the LEDs in the run across the centre. That number is the only one that has to match a profile.
We publish middles of 0, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 20 and 21. So a ten LED middle loads X-10-X, and a sixteen loads X-16-X.
No middle at all?
Load X-0-X. Some devices are sides only, with nothing running across the centre, and that is what the zero profile is for. You still set your side count exactly the same way.
Count one side, then set it in the plugin
Count the LEDs running up one side of your device, not both added together. Then open LED Devices, RPM Telemetry, Configuration, and set Number of side LEDs (per side) to that number.
The preview updates as you drag, so you can check it against your wheel before you leave the tab.
That is it. Your sides now light correctly without a bespoke profile.
If a side is split into more than one run
Some wheels split each side into separate runs, for example a layout described as 9/3/10/3/9. Those are still just two sides and a middle.
| Your layout | Middle | Side LEDs per side | Profile to load |
|---|---|---|---|
| 9/3/10/3/9 | 10 | 12, because 9 and 3 are both on the same side | X-10-X |
| 5-10-5 | 10 | 5 | X-10-X |
| 3-9-3 | 9 | 3 | X-9-X |
| Sides only, no centre run | 0 | However many are on one side | X-0-X |
The rule
Add up everything on one side and enter that one number. It does not matter how many separate runs it is split into.
Two runs on each side, but still one side. Load X-10-X and set the side count to 12.
Effects go where you want them too
The same thinking applies to the effects that sit on top of your RPMs, like Marshall Flags and Proximity Spotters. You are not stuck with wherever a profile happens to put them.
In LED Devices, RPM Telemetry, Effects, turn on Use Custom Position for an effect and you get two controls: Start position, which is the LED it begins on, and Number of LEDs, which is how many it uses from there.
Worth knowing
Settings labelled Applies to all Devices, like Edit Universal Flags Settings, change the effect everywhere. The custom position you set here is for this device only, which is what lets a wheel and a DDU show the same effect in different places.
The preview beside the sliders updates live, so you can line an effect up against your own device rather than guessing.
If you have more than one telemetry device
Telemetry profiles are for wheels and DDUs. If you have both, it is tempting to load a telemetry profile onto each of them.
Pick the device you actually look at, usually the wheel, and give it the telemetry profile. For the other one, load DNR Co-Pilot instead. It is built to sit alongside your telemetry device rather than compete with it, so the two stay in step.
| Device | Profile |
|---|---|
| One wheel or DDU, the one you look at | The RPM telemetry profile, X-(middle)-X |
| Any other wheel or DDU | DNR Co-Pilot |
Do not do this
Run one telemetry profile, on one device. A second telemetry profile on another device is the most common cause of LEDs fighting each other, lighting out of step, or not lighting at all.
Still not right?
Three symptoms, and what each one usually means.
If none of those fixes it, open a support ticket and tell us your exact LED layout, counted per group.
- Sides light but the middle does not: you have loaded a profile whose middle does not match your device. Recount the middle and load that profile.
- Middle lights but the sides are short or overrun: the side count in Configuration does not match. Recount one side and set it again.
- LEDs flicker or fight each other: you are almost certainly running two telemetry profiles across a wheel and a DDU.
Related Content
Still need help?
Open a ticket and we'll get back to you with the article context attached.