
Floating hub
stef1029/trilab-floating-platform
Head-fixed floating platform for studying sensory-guided spatial orienting in mice — hardware, firmware and control software.

Head-fixed floating platform for studying sensory-guided spatial orienting in mice — hardware, firmware and control software.
Reward port is an open-source printed circuit board by stef1029, from the stef1029/trilab-floating-platform repository on GitHub. It is a 4-layer board of 30 × 21 mm with 60 parts on 59 nets, routed with 747 tracks and 79 vias.
It is built around the STM32G071GBU6, RS485 and DRV8837DSG, with the PAM8302AASCR, 2N7002PW and SM02B-GHS-TB among its other parts. Its parts include 24 resistors, 18 capacitors, 7 connectors, 5 ICs and 4 transistors. It belongs with the STM32 boards of this library.
Central nRF52840-based hub board for the behavioural rig. Korora provides:
The current controller module is the BMD-340-A-R, based on the nRF52840.
The current power-management assumption is an nPM1300-class Nordic PMIC. Exact PMIC variant, battery connector, thermistor arrangement, charge current, and rail configuration must be finalized against the selected battery before schematic release.
Korora is the system master.
The hub:
Initial high-level architecture:
+----------------------+
5V BENCH INPUT --------->| |
| nPM PMIC |
LiPo BATTERY ----------->| charger / fuel gauge|
| power-path / bucks |
+----+-------------+---+
| |
3V3 VSYS
| |
| +---------- VLOAD
| |
+-------------------------+--> JST-GH
|
+---------+---------+
| BMD-340-A-R |
| nRF52840 |
+----+----+----+----+
| | |
UART GPIO I2C/SPI
| | |
| | +----> IMU
| | +----> magnetometer
| | +----> PMIC telemetry
| |Korora is designed to connect directly to peripheral boards using the common 10-pin JST-GH bus.
Korora is the RS-485 bus master and the source of the differential SYNC pulse. Peripheral boards are expected to:
The initial Reward Port design assumes a 500000 baud, 8-N-1, half-duplex RS-485 link and an initially 4 Hz SYNC pulse.
These values are initial protocol parameters rather than permanent electrical limitations.
Korora has two power sources:
The PMIC provides charging and power-path control between them.
The earlier system requirement described the battery as approximately 4.3 V.
Do not set the PMIC charge termination voltage from that description alone. The final battery datasheet controls:
Provide a 2-pin header for development power:
| Pin | Signal |
|---|---|
| 1 | +5V_BENCH |
| 2 | GND |
The bench input feeds the PMIC input rather than directly feeding the battery rail.
Intended behaviour:
5 V bench present
|
v
PMIC
/ \
/ +----> system load
|
+---------> battery chargingThe bench supply must be current limited during initial bring-up.
Korora distributes two positive rails to the peripheral connector.
3V3 is the regulated digital rail.
Expected loads include:
The total required 3V3 current is TBD.
Before finalizing the PMIC configuration, calculate:
hub local 3V3 load
+
maximum number of peripheral boards
x
maximum peripheral 3V3 load
=
required regulated 3V3 currentIf this exceeds the useful continuous current available from the selected PMIC regulator configuration, Korora requires an external 3V3 regulator or a revised power architecture.
VLOAD is currently defined as the PMIC system / VSYS rail.
VLOAD is not assumed to be a precision regulated 5 V rail.
Conceptually:
battery operation:
battery -> PMIC power path -> VSYS -> VLOAD
bench operation:
5 V input -> PMIC power path -> VSYS -> VLOADTherefore VLOAD may vary with power-source state and battery condition.
Peripheral loads must be designed for the specified VLOAD operating range.
The final VLOAD voltage range and current limit must be documented after the PMIC and battery design are finalized.
Korora should provide a digital control / telemetry link between the PMIC and the nRF52840.
Current intended interface:
BMD-340 SDA <------> PMIC SDA
BMD-340 SCL -------> PMIC SCL
PMIC IRQ ----------> BMD-340 GPIOThe firmware should be able to query and log, where supported by the selected PMIC configuration:
Exact registers and reported metrics depend on the final PMIC implementation.
Controller module:
BMD-340-A-R
nRF52840Korora uses the nRF52840 for:
Physical BMD-340 pin numbers are not yet frozen.
Reserve logical functions for:
| Function | Peripheral / type | Notes |
|---|---|---|
| RS-485 transmit | UARTE TX | Main peripheral bus |
| RS-485 receive | UARTE RX | Main peripheral bus |
| RS-485 driver enable | GPIO or UARTE DE strategy | Must default bus-safe |
| SYNC output | GPIO / timer-driven output | Feeds second RS-485 driver |
| PMIC SDA | TWIM / I2C | Shared bus possible |
| PMIC SCL | TWIM / I2C | Shared bus possible |
| PMIC interrupt | GPIO input | Optional but recommended |
| IMU bus | SPI or I2C | Final choice TBD |
| IMU interrupt 1 | GPIO input | Data-ready / FIFO event |
| IMU interrupt 2 | GPIO input | Optional |
| Magnetometer bus | I2C or SPI | Final choice TBD |
| Magnetometer DRDY | GPIO input | Optional but recommended |
| SWDIO | SWD | Debug |
| SWDCLK | SWD | Debug |
| RESET | reset | Debug / recovery |
The final pin assignment should be chosen only after confirming:
Korora uses one SN65HVD75DGKR for the main half-duplex RS-485 bus.
Logical connections:
BMD UARTE_TX ---------> SN65HVD75 D
BMD UARTE_RX <--------- SN65HVD75 R
BMD RS485_DE ---------> SN65HVD75 DE
SN65HVD75 /RE
|
+---- RS485_P
+---- RS485_NExact DE and /RE wiring is TBD.
The design must guarantee that Korora does not unintentionally drive the bus during reset or boot.
Initial protocol configuration inherited from the first Reward Port:
500000 baud
8 data bits
no parity
1 stop bit
half duplex
hub master polling
peripherals transmit only when addressedKorora is the only normal bus master.
Korora uses a second SN65HVD75DGKR as a dedicated differential digital-output driver.
Concept:
BMD SYNC GPIO --------> SN65HVD75 D
|
+---- SYNC_P
+---- SYNC_NKorora is the source of SYNC.
Peripheral boards receive the differential pair and convert it back to a local logic signal for hardware timer capture.
Initial SYNC frequency:
4 HzThe exact pulse width is TBD.
The SYNC waveform should be generated from a hardware timer or hardware-timed GPIO mechanism where practical so that edge timing does not depend on normal firmware scheduling latency.
SYNC_P / SYNC_N provide differential signalling and noise immunity.
They do not by themselves provide authentication or cryptographic security.
Korora is the system time authority.
The design currently assumes:
Korora should maintain a monotonic high-resolution local clock suitable for:
Korora uses the same 10-pin JST-GH pinout as the peripheral boards.
| Pin | Signal |
|---|---|
| 1 | RS485_P |
| 2 | RS485_N |
| 3 | SYNC_P |
| 4 | SYNC_N |
| 5 | 3V3 |
| 6 | GND |
| 7 | VLOAD |
| 8 | GND |
| 9 | VLOAD |
| 10 | GND |
Pins 7 and 9 are the same VLOAD net.
Pins 6, 8, and 10 join the same ground system.
Korora will normally be one physical end of both differential buses.
Therefore the hub should include termination provisions for:
Preferred implementation:
optional 120 ohm RS-485 termination
optional 120 ohm SYNC terminationusing solder jumpers or clearly defined assembly options.
Only the physical ends of each differential bus should be terminated.
The duplicated VLOAD and GND pins are intended to reduce harness resistance and increase available load-current capacity.
Before schematic release, define:
Do not use connector nominal current ratings alone as the system current budget.
The complete cable and connector chain must be checked.
Korora contains:
6-axis IMU:
STEVAL-MKI240KA during development
LSM6DSV32X sensor
3-axis magnetometer:
MMC5983MA / MMC5983MA-B development hardwareCombined measurements:
accelerometer: X Y Z
gyroscope: X Y Z
magnetometer: X Y Z
total: 9 axesInitial requested fused update rate:
20 Hz to 100 HzThis is the output / processing rate target, not necessarily the raw sensor sampling rate.
Raw accelerometer and gyroscope data may be sampled faster and decimated or fused into a 20-100 Hz application output.
Final electrical bus allocation is TBD.
Two reasonable starting configurations are:
Option A:
IMU -> SPI
magnetometer -> I2C
PMIC -> I2C
Option B:
IMU -> I2C
magnetometer -> I2C
PMIC -> I2COption A gives the IMU a dedicated high-throughput bus.
Option B minimizes routing and is likely sufficient for the initial 20-100 Hz application rate.
During prototype bring-up, use the interfaces exposed by the available evaluation boards.
The final integrated PCB should use the sensor IC interfaces directly unless there is a deliberate reason to retain plug-in modules.
Prefer hardware data-ready interrupts rather than polling for timing-sensitive sensor acquisition.
Recommended signals:
IMU INT1 -------> BMD GPIO
IMU INT2 -------> BMD GPIO optional
MAG DRDY -------> BMD GPIO if available / usefulFirmware should timestamp sensor-ready events against the same hub timebase used for the rest of the system.
The initial 9-DoF processing goal is orientation tracking.
Expected outputs may include:
Candidate fusion approaches include:
The exact algorithm is TBD.
The first implementation should prioritize:
The 9-DoF sensor stack does not by itself provide stable long-term absolute XYZ position.
Double integration of accelerometer error causes position drift.
Therefore the current hub requirements should distinguish between:
orientation / motion trackingand:
absolute or long-term XYZ position trackingIf absolute position is later required, Korora will need an external position reference such as:
This is a system-level requirement and should be resolved before relying on the IMU as a position sensor.
The IMU and magnetometer require deliberate PCB placement.
Place the IMU:
Mark the sensor axes in the schematic notes and PCB documentation.
The magnetometer is sensitive to local magnetic fields.
Keep it as far as practical from:
The preferred magnetometer location is likely near a PCB edge with a controlled keepout from magnetic / high-current components.
Final placement should be validated experimentally.
The BMD-340-A-R antenna area must be treated as an RF keepout.
Final PCB layout must follow the module manufacturer's antenna-placement requirements.
In particular, do not allow the power section, battery, magnetometer, high-current harness routing, or large copper structures to compromise the antenna region.
Place the BMD-340 near a suitable board edge unless the final RF design intentionally uses a different approved arrangement.
Provide access to at least:
SWDIO
SWDCLK
RESET
3V3 reference
GNDPreferred implementation is a compact Tag-Connect footprint, pogo-pad pattern, or small debug header.
Also provide useful test points for:
Korora firmware is responsible for:
Initial bus behaviour:
The protocol still needs definitions for:
Initial sequence:
The first peripheral README assumes an initial 4 Hz SYNC rate.
The final rate should be chosen from measured oscillator drift, event-timing requirements, bus traffic, and desired recovery time after connection.
Low-battery policy is TBD.
Firmware should eventually define thresholds for:
Do not allow an uncontrolled battery collapse to be the normal session-ending mechanism.
Korora should detect and log at least:
Where useful, store reset cause and fault state across reboot.
Recommended initial startup order:
The system must not allow accidental RS-485 transmission while the nRF52840 pins are still in reset/default state.
Recommended controlled shutdown sequence:
Exact behaviour is TBD.
The following items are not yet frozen:
| Qty | Value | Footprint | References |
|---|---|---|---|
| 7 | 100k | Resistor_SMD:R_0402_1005Metric | R7, R8, R9, R18, R20, R21, R22 |
| 6 | 100nF | Capacitor_SMD:C_0402_1005Metric | C3, C4, C14, C15, C16, C20 |
| 4 | 100 | Resistor_SMD:R_0402_1005Metric | R10, R11, R12, R19 |
| 4 | 10k | Resistor_SMD:R_0402_1005Metric | R3, R15, R23, R24 |
| 4 | 2N7002PW | Package_TO_SOT_SMD:SOT-323_SC-70 | Q1, Q2, Q3, Q4 |
| 3 | 330 | Resistor_SMD:R_0402_1005Metric | R4, R5, R6 |
| 2 | 100nf | Capacitor_SMD:C_0402_1005Metric | C8, C9 |
| 2 | 10uF | Capacitor_SMD:C_0603_1608Metric | C1, C19 |
| 2 | 120 | Resistor_SMD:R_0603_1608Metric | R1, R2 |
| 2 | 1k | Resistor_SMD:R_0402_1005Metric | R16, R17 |
| 2 | 220pF | Capacitor_SMD:C_0402_1005Metric | C11, C12 |
| 2 | RS485 | Jumper:SolderJumper-2_P1.3mm_Open_RoundedPad1.0x1.5mm | JP1, JP2 |
| 2 | SM02B-GHS-TB | Connector_JST:JST_GH_SM02B-GHS-TB_1x02-1MP_P1.25mm_Horizontal | J6, J7 |
| 2 | SM04B-GHS-TB | Connector_JST:JST_GH_SM04B-GHS-TB_1x04-1MP_P1.25mm_Horizontal | J1, J4 |
| 2 | SM10B-GHS-TB | Connector_JST:JST_GH_SM10B-GHS-TB_1x10-1MP_P1.25mm_Horizontal | J2, J3 |
| 2 | THVD1410DGKR | Package_SO:VSSOP-8_3x3mm_P0.65mm | U1, U2 |
| 1 | 100 | Resistor_SMD:R_0603_1608Metric | R14 |
| 1 | 10uF | Capacitor_SMD:C_0805_2012Metric | C13 |
| 1 | 1uF | Capacitor_SMD:C_0402_1005Metric | C10 |
| 1 | 33 | Resistor_SMD:R_0402_1005Metric | R13 |
| 1 | 4.7nF | Capacitor_SMD:C_0402_1005Metric | C7 |
| 1 | 4.7uF | Capacitor_SMD:C_0603_1608Metric | C17 |
| 1 | 470pF | Capacitor_SMD:C_0402_1005Metric | C5 |
| 1 | 470uF | Capacitor_Tantalum_SMD:CP_EIA-7343-43_Kemet-X | C18 |
| 1 | Conn_SWD | Connector:Tag-Connect_TC2030-IDC-NL_2x03_P1.27mm_Vertical | J5 |
| 1 | DRV8837 | Package_SON:WSON-8-1EP_2x2mm_P0.5mm_EP0.9x1.6mm | U5 |
| 1 | PAM8302AASCR | footprints:PAM8302AASCR_DIO | U3 |
| 1 | STM32G071GBU6 | Package_DFN_QFN:QFN-28_4x4mm_P0.5mm | U4 |

stef1029/trilab-floating-platform
Head-fixed floating platform for studying sensory-guided spatial orienting in mice — hardware, firmware and control software.

stef1029/trilab-floating-platform
Head-fixed floating platform for studying sensory-guided spatial orienting in mice — hardware, firmware and control software.

axpaul/KinetiCoreDC
Compact STM32G0-based DC motor controller board featuring TI DRV8874 H-bridge drivers, RS485 communication, optoisolated I/O, and hardware power protection.

UofA-SPEAR/pcb_designs_2026
Repository for SPEAR 2026 PCB designs. PCB design software is KiCad.

Stab-Rabbit-coding/Serenity-UAV
A functional, security conscious, Unmanned Aerial Vehicle based on the Firefly Class spacecraft Serenity from the 2002 show..

nickraymond/nereus_Pi_shield_ADIN2111
A Raspberry Pi Zero 2W shield built from a copy of the Sofar Bristlemouth mote: ADIN2111 two-port 10BASE-T1L with PoDL, powered from the bus, 5 V for the Pi, a 24 V payload port, and the Sofar mote's power path…

kanha2907/Gps-using-neom9n-
Compact GPS breakout board based on the u-blox NEO-M9N module. Includes support circuitry for battery-backed operation, LEDs, and passives—designed for low-power embedded GPS applications.

misko/prompt2device
The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.

askiiart/thrustmaster-ferrari-challenge-wheel-translator
This is a little microcontroller used to adjust pedals for the Thrustmaster Ferrari GT/Challenge wheel. It takes the potentiometer values, adjusts them to match that the controller expects, and outputs the values…

It measures 30 × 21 mm and has 4 copper layers, 0.8 mm thick.
60 parts, built around the STM32G071GBU6, RS485, DRV8837DSG and PAM8302AASCR. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
From the stef1029/trilab-floating-platform repository on GitHub, at the commit this page was made from: the board is electronics/reward_port_2_sided_nonlatching_solenoid/kicad/reward_port.kicad_pcb and its schematic electronics/floating_hub/floating_hub.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Its repository states no licence, so its author keeps all rights: ask stef1029 before reusing the design.