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. If you run more than one LED device, only one of them takes the telemetry profile and the rest load DNR Co-Pilot.
First, how many LED devices are you setting up?
If you are setting up one wheel or DDU, carry straight on to the next step. If you have two or more LED devices, there is one rule worth knowing before you start, because getting it wrong is the single most common problem we are asked about.
Co-Pilot is not a fallback or a lesser option. It is what a second device is for. Your rev lights only need to be in one place, so a second device repeating them tells you nothing you were not already being told. Co-Pilot gives that device a job of its own.
There is a mechanical reason too. Number of side LEDs is a single setting shared across your whole rig, and every telemetry profile on every device reads it. Two telemetry profiles wanting different side counts cannot both be right, and fixing one will always break the other.
| Device | Profile to load |
|---|---|
| The one wheel or DDU you actually look at | The RPM telemetry profile, X-(middle)-X |
| Every other LED device, matching layout or not | DNR Co-Pilot |
Only one device runs the telemetry profile
Give the RPM telemetry profile to the device you actually look at, usually the wheel. Every other LED device loads DNR Co-Pilot instead. This applies whether or not your devices share the same layout.
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.
More than one device, in full
This is the rule from step 1, with the reasoning behind it. Telemetry profiles are built for wheels and DDUs, so when you own two it is tempting to load one onto each.
Number of side LEDs lives in the plugin rather than in the profile, and there is only one of it. Every telemetry profile you install reads that same number, so a wheel with 3 either side and a button box with 5 either side can never both be correct. Whichever number you enter, one of them is wrong.
Load DNR Co-Pilot on the second device instead. Co-Pilot never reads the side LED setting, so there is nothing left for the two devices to compete over, and the second one shows you something new rather than repeating the wheel.
Matching layouts are not an exception to this. Two identical rev strips is not what a second device is for, and you would still be tying both devices to a single setting for nothing in return.
- Finding it in the plugin: the product is called RPM - Telemetry Co-Pilot, and it sits in the Co-Pilot LEDs group under LED Devices. Do not confuse it with the Co-Pilot dashboard, which shares the name and is a different product entirely.
- Installing with Download all: a bulk download will not change your side LED count, so a second device can quietly end up running on the first device's number. Install one profile at a time and the plugin asks you before it changes anything.
Do not run two telemetry profiles
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. It is also the most common ticket we answer.
Still not right?
Five 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.
- The LEDs at the ends of one device stay dark, or an effect lands in the wrong place on one device only: you are running a telemetry profile on two devices that need different side counts. Put Co-Pilot on the second one.
- You fix one device and it breaks the other: that is the single side LED setting doing exactly what it does. One of those two devices needs Co-Pilot.
- 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.