The circuit board is the part of a light nobody photographs and the part that decides what the light can do. Almost every meaningful difference between a Rhino product and a commodity one traces back to a decision made on a board layout, so it is worth explaining what those decisions are — in plain terms, without needing to read a schematic.
The short version
The commodity model buys a finished LED module and fits it into whatever housing it will go in. We draw the board for the product it goes in. That difference decides how much current the light can carry, where the wire comes out, how heat leaves the emitter, what protection is on board, and whether the product can be changed next year.
What "designing the board" actually means
A light board is a small circuit that takes twelve-ish volts from a vehicle and turns it into precisely controlled current through some LEDs, usually with a microcontroller deciding what those LEDs do. Designing it means choosing the parts, drawing how they connect, and then laying out the physical copper: where each component sits, how wide every trace is, and how the whole thing fits the housing it has to live in.
Buying a module means somebody else made all of those choices, for a generic enclosure, before they knew what you were going to do with it.
The six things a board decides
1. How much current the light can carry
Trace width and copper weight set how much current the board can move without heating up. Get that wrong and the board becomes the hottest thing in the product. A board designed for the actual load of the actual light is sized for it; a generic module is sized for the load its designer assumed.
The measured numbers on our own products are the same fact from the other end. A pod draws a measured 2.5 A at 14.4 V, which derives to 36 W. An Axion rock light draws a measured 1.4 A at 14.3 V, deriving to 20 W. Those are input figures read at the finished product, and they are what the board and the wiring were designed around.
2. Where the wire comes out
Connector placement sounds trivial until you are installing. It decides whether the pigtail exits somewhere that can be sealed, whether the wire has a strain path that is not the solder joint, and whether the light can sit flush against a wheel well without kinking anything. On a bought-in module the connector is where it is, and the housing has to be designed around a decision somebody else made.
3. How heat gets out
An LED converts a good part of its input power to heat, and that heat has to reach the aluminium to go anywhere. The path runs from the emitter, through the board, into the housing. Where the copper pour sits, how the emitter is mounted and how the board meets the housing are all layout decisions, and they set the ceiling on how hard the light can be driven for how long.
This is also why the housing and the board have to be designed together. Our RGB+W housing took several revisions specifically because the housing has to pull heat away from the emitters as fast as they make it, and every revision was a trade between output and thermal headroom. That trade is only available to you if you own both parts.
4. What protection is on the board
Vehicles are electrically hostile: voltage swings with engine speed, wiring gets connected backwards, connectors get wet. Protection against those conditions is components on a board. If you did not design the board, you did not choose them, and you generally cannot find out what is there.
5. How it fits the housing
Board outline, mounting hole positions, component height, where the emitters sit relative to the optic. A board drawn for a specific housing can use the whole internal volume and put the emitter exactly where the optic wants it. A module fitted into a housing has to be accommodated, and the compromises show up as wasted space, awkward wiring or a light face that is not quite where it should be.
6. What the firmware can do
The board decides what the software can even ask about. If there is no temperature sense on the board, firmware cannot manage heat. If the microcontroller has no spare inputs, the product can never learn to read a vehicle signal. If there is no way to update the firmware, the product is finished the day it ships.
What the firmware in a light actually does.
Revisions are the real payoff
A board you own is a board you can change, and our history is mostly a list of changes.
- The pod board went through a first prototype, then a revision to make it brighter using fewer components, then a third revision that went bigger on the centre emitter — and, in the same design pass, gained the ability to link pods together into a bar.
- The RGB+W rock light board went from a first prototype that tried to run six large RGBW packages in one housing, through a second board drawn specifically to fix problems the first one exposed, to a third that we could test properly.
- The Bluetooth control board went through eleven numbered revisions. Version six is the one where Bluetooth finally worked; every version before it taught us something about the one before that.
None of those are things you can do to somebody else's module. They are the difference between a product line and a catalog.
What this means when you own one
- The light is sized for its own load, not for a generic assumption about what somebody might do with the module.
- A fault can be diagnosed, because there is a schematic and someone in the building can read it. That is the precondition for every repair.
- The product can improve after you buy it. Firmware and hardware revisions come from the same people who answer the phone.
- Nothing about the product depends on a supplier's roadmap. If a module vendor discontinues a part, a company built on that module has a problem. A company with a schematic has a component substitution.
The honest limits
Designing the board does not mean making everything on it. The emitters are Cree parts; the microcontroller, the passives and the connectors are all bought in. What we own is the design, the layout and the choice of every part on it — and naming a good emitter is not the same as having measured what the finished light does with it, which is why our published performance figures come off a meter rather than off a datasheet.