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 the plugin works out how many LEDs are on your sides. Every LED device keeps its own settings, so you can run a telemetry profile on as many as you like.
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 thing worth knowing before you start, because it used to work the other way round.
This is new. Side LEDs used to be a single setting shared by the whole rig, so two devices needing different counts could never both be right and fixing one always broke the other. Each device now carries its own, and the plugin works the count out from the strip rather than asking you for it.
That means two devices can do genuinely different jobs at the same time. Your wheel can run the rev lights while a DDU shows brake pressure or the fuel gauge, each keeping its own colours and positions.
| Device | Profile to load |
|---|---|
| The wheel or DDU you actually look at | The RPM telemetry profile, X-(middle)-X |
| Every other LED device you want lit | Its own RPM telemetry profile, X-(middle)-X |
Every device keeps its own settings
Load the RPM telemetry profile onto each LED device you want lit. Each one remembers its own side LED count, its own telemetry function, its own effect positions, colours and idle animation, so setting up one can no longer disturb another.
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 whatever your own device leaves over, so one profile serves every device with that middle.
The short version
Count your middle LEDs and load that profile. The plugin works your sides out from there. Your sides do not need to match anybody else's.
Both of these load X-10-X. Only the side count differs, and the plugin works that out per device.
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.
Your side count, which the plugin fills in for you
Open LED Devices, RPM Telemetry, Configuration and look at Number of side LEDs (per side). Installing the profile has already set it for that device, because your strip length and the profile's centre leave only one answer.
The sum is your strip total, minus the profile's centre, halved. That is why the slider is usually greyed out, with the sum written underneath naming your device and the profile doing the deciding.
It stays live only where nothing can be worked out, such as a device that reports no LED total. If you are entering it yourself, count the LEDs up one side, not both added together.
To change your sides, install a profile with a different centre. On a 16 LED strip, X-10-X gives 3 either side and X-8-X gives 4.
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
Everything on one side counts as one side, however many separate runs it is split into. That total is what the plugin arrives at, and what you would enter yourself on a device it cannot work out.
Two runs on each side, but still one side. Load X-10-X, and the side count for that device works out at 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
Telemetry profiles are built for wheels and DDUs, and you can now run one on every LED device you own.
Each device keeps its own side LED count, telemetry function, effect positions, colours, brightness and idle animation. Setting up one cannot disturb another, which is what used to make two telemetry profiles a problem.
Because of that, a second device is worth giving a different job rather than the same one. Leave the rev lights on the wheel you look at, and set the other device to brake pressure, brake and throttle input, or the fuel gauge. All of those live in Telemetry Function on that device's own page.
Devices with different layouts are fine together. A wheel with 3 either side and a button box with 5 either side each keep their own number, and the plugin works each one out from the strip it is on.
- The side LED count is worked out for you: your strip length minus the profile's middle segment, halved. Where that can be calculated the slider is shown greyed with the sum underneath, because there is only one number that fits.
- To change the sides, install a profile with a different middle segment. On a 16 LED strip, X-10-X gives you 3 either side and X-8-X gives you 4.
- Installing with Download all: install one profile at a time if you want to watch what lands where, though a bulk download can no longer put one device's count onto another.
Pick the device at the top of the page first
The RPM Telemetry page has a device picker at the top. Everything below it belongs to whichever device is selected, so check you are looking at the right one before you change anything.
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 the rev bar runs into the side LEDs: the profile's middle segment does not fit that strip. Count the whole strip and load the profile whose middle leaves an equal number either side.
- An effect lands in the wrong place on one device only: check the device picker at the top of the RPM Telemetry page. Effect positions belong to the selected device, so it is easy to set them on the wrong one.
- You change a setting and nothing happens: some wheels and branded DDUs ship a profile that sets its own layout and colours. Where that is the case the page says so and greys the controls it cannot change.
Related Content
Still need help?
Open a ticket and we'll get back to you with the article context attached.