Team BlackSheep (TBS) has quietly dropped a full lineup of DroneCAN-ready hardware and, as Painless360 explains in his video briefing, it’s exactly the kind of kit large-model builders have been asking for. If you’re tired of spaghetti wiring in wings and fuselages or you want a cleaner, more reliable way to get sensors and servos around a big airframe, this new TBS range deserves a proper look.
Why DroneCAN matters (and why TBS launching into it is a big deal)
DroneCAN (often just called CAN bus in the automotive world) is a four-wire differential bus — power, ground, CAN high and CAN low — used for reliable distributed communications. It’s been a staple in cars for decades and in large professional RC models for good reason: it gets signals where they need to go without running dozens of individual wires. TBS are now packaging that reliability into consumer-friendly modules so hobbyists can adopt CAN without reinventing the wiring loom.
What TBS released — a whistle-stop tour (specs and practical notes)
Below is a concise, technical summary of the new TBS DroneCAN family. I’ve included the key specs and integration notes so you can decide where each module fits in your build.
TBS DroneCAN Splitter (4A BEC)
This is the simple hub you’ll want inside every wing root.
- Input: 3S–12S
- Output: 5 V @ 4 A total (max ≈1.5 A per connector)
- Connectors: five CAN ports — JST GH 4‑pin 1.25 mm
- Power input: XT30 + solder pads
- Size: 44 × 25 × 8 mm; weight ≈12 g
- Practical note: ideal for powering multiple CAN sensors in a wing; keeps wiring tidy and centrally powered
TBS DroneCAN 20A Power Supply
A beefy power module for larger builds or when you have heavier peripheral power needs.
- Input: 3S–12S
- Outputs: 5 V @ 4 A, 12 V @ 4 A, and 9–16 V @ 20 A
- Integrated voltage sensors and a current sensor
- Interfaces: two CAN ports, one serial, one SWD
- Connectors: JST GH 4‑pin 1.25 mm, XT30, solder pads
- Size: 61 × 40 × 15 mm; weight ≈63 g
- Practical note: you’ll need some ArduPilot config (parameters and sensor mapping) to surface its telemetry — the manual covers setup
TBS DroneCAN 150A Hall-Effect Current Sensor
Non-invasive measurement around the positive lead — perfect for high-current installations.
- Range: 0–150 A
- Input supply for sensor electronics: 4.5–5.5 V (run at 5 V)
- Sensitivity: 12 mV/A
- Interfaces: two CAN ports, serial, SWD
- Size: 35 × 22 × 22 mm; weight ≈7 g
- Practical note: orientation matters — follow the manual so the sensor reports current direction properly
TBS DroneCAN Airspeed Sensor
Lightweight pitot-derived airspeed that reports on CAN and offers I²C as an option.
- Supply: 4.5–5.5 V (nominal 5 V)
- Range: up to 100 m/s (≈360 km/h or 223 mph)
- Accuracy: ±2%
- Weight: ≈4 g
- Interfaces: two CAN, serial, SWD and I²C
- Size: 35 × 22 mm
- Practical note: CAN + I²C support gives installation flexibility — use CAN when you want consolidated wiring and I²C for flight controllers without native DroneCAN
TBS DroneCAN PWM Board
When your servos or ESCs are remote from the flight controller, this board lets you run PWM or DShot over CAN.
- Supply: 4.5–5.5 V
- Outputs: 8 PWM outputs (or 8 DShot), one DShot UART
- Interfaces: two CAN, serial, SWD, I²C
- Size: 40 × 22 × 6 mm; weight ≈4 g
- Practical note: saves long runs of individual servo wires — perfect for wings with many control surfaces or distributed actuators
TBS DroneCAN GPS Module
Standard CAN-connected GPS to reduce cabling and centralise telemetry.
- Connects via CAN to the flight controller
- Installation dramatically simplifies wiring compared to standalone GPS+compass cabling
- Practical note: mount and grounding still matter — refer to existing GPS placement guides when integrating
Integration with ArduPilot and practical setup tips
ArduPilot (ArduPlane, ArduCopter, ArduRover, etc.) already supports many DroneCAN devices. That means TBS hardware is ready to talk to mainstream autopilot stacks — but there are a few gotchas to keep in mind:
- Power budgeting: the more CAN devices you add, the more you must guarantee stable 5 V supply. Use the 4 A splitter for small setups; the 20 A unit is the right choice where higher current rails or additional 9–16 V supplies are required.
- Parameter setup: voltage and current telemetry from the 20 A PSU or the 150 A sensor may need ArduPilot parameter tweaks to map the readings correctly — read the manuals and follow the TBS/ArduPilot docs.
- Daisy-chaining: most modules provide two CAN ports to pass the bus along. Keep wiring topology tidy and mind termination if you go long distances.
- Protocols and alternatives: where I²C is offered (airspeed, PWM board), it provides a fallback for controllers without DroneCAN. But the whole point of these modules is reduced wiring complexity — favour CAN where possible.
Who should care (use cases)
- Modelers building large wings or fuselages with long cable runs — swap dozens of signal wires for a single CAN loop.
- Professional or semi-pro builds that require reliable telemetry for power and airspeed.
- Boat, rover or VTOL projects where distributed sensors and actuators need a robust network.
- Hobbyists moving up to ArduPilot ecosystems — these TBS modules lower the barrier to proper CAN adoption.
Critical analysis
The obvious pros — tidy wiring, standard connectors (JST GH 4‑pin 1.25 mm), clever power options — but practical adoption brings responsibilities:
- Configuration: the hardware reports telemetry, but you still must configure the autopilot to read and display it; this isn’t plug-and-forget for every controller.
- Power distribution design: adding many CAN devices still requires thinking about where the current comes from and where ground returns go — bad decisions here can light up the smoke-LEDs.
- Connector type: JST GH 1.25 mm is tiny — neat and light, but fragile if you’re repeatedly unplugging under strain. Consider strain relief and secure mounting.
Should you start rewiring everything?
Lest be pragmatic: CAN bus isn’t a novelty, it’s the sensible, industrial-strength way to distribute sensors and actuators in big models. TBS’s offering looks well thought-out: a range from the simple 4 A splitter up to a 20 A BEC with telemetry and a high‑current hall sensor, plus sensor modules and a PWM breakout. If you’re building anything larger than a small park flyer, it’s worth planning your next project around a CAN backbone rather than another rat’s nest of servo leads.
Is DroneCAN the same as automotive CAN bus?
DroneCAN is a CAN bus implementation tailored to UAVs and robotics. Technically it runs over the same differential two-wire CAN physical layer (plus power and ground), but the protocol and message sets are optimised for drone sensors, actuators and autopilots.
Do I need special connectors or can I solder the wires directly?
TBS uses JST GH 4-pin 1.25 mm connectors for CAN ports but also provides solder pads. The tiny JSTs are convenient and neat; if you prefer permanence or beefier wiring, solder pads are suitable — just ensure proper strain relief and insulation.
Will my flight controller work with these TBS modules out of the box?
Many modern flight controllers and stacks like ArduPilot already support DroneCAN devices. You may still need to configure parameters to map voltage, current and sensor IDs correctly. Check both the TBS manuals and your autopilot documentation for setup steps.
Which power module should I pick for my wing?
If your CAN devices only need a handful of sensors and a GPS, the 4 A splitter is fine. If you have many servos, heaters, or a need for higher voltage rails (9–16 V), the 20 A power supply provides additional outputs and telemetry to help manage power safely.
This article was created from the video Just released: TBS go big for DroneCAN devices (CANBus).
