Find Robot Operating System Projects

I'm looking for a senior PCB engineer for an initial paid consultation, with the possibility of a full design engagement.

**The Board**
4-layer, 40×35mm. Components:
- STM32F405 (MCU, SPI DMA at 500Hz)
- ICM-42688-P (6-axis IMU)
- LIS2MDL (magnetometer)
- MS5611 (barometer)
- nRF52840 (BLE module)
- BQ25185 (LiPo charger)
- MicroSD slot

**Consultation Scope (1hr, paid)**
I want your honest assessment of:
- Layout risks on this component combination at 40×35mm
- SPI trace impedance requirements at 500Hz sampling
- nRF52840 antenna keepout strategy at this board size
- Power domain isolation between BLE switching and analog sensor rails
- Realistic hours estimate for schematic + layout

**Full Project (if available)**
Schematic capture + 4-layer KiCad layout, DRC-clean Gerbers + BOM ready for JLCPCB SMT assembly. Fixed-price milestone contract.

**What I'm Looking For**
- Real portfolio of tight mixed-signal or wearable boards — not just large compute/SBC designs
- STM32 + nRF52 experience specifically
- Direct communicator — I need honest assessments, not reassurance
- Availability to review feedback within 48hrs

**About the Project**
This is a real product with a pilot demo scheduled with the Swiss national ski team in October 2026. Rev A is a functional prototype, not production.

• Describe your recent experience with similar projects

Hi Nitish,

I’m looking for someone to work long-term on a LiDAR-based project similar to Leica RTC360.

Before we proceed, I need to confirm your hands-on experience:

1. Have you worked directly with raw LiDAR point cloud data (LAS/LAZ)?
2. Which tools/libraries have you used? (PCL, Open3D, CloudCompare, etc.)
3. Can you process and clean point clouds (noise removal, segmentation, classification)?
4. Have you built or worked on any real LiDAR scanning or mapping systems?

This role requires daily, long-term involvement — not just consulting.

Can you share specific projects related to this?

Thank

I’m building a new robotic platform and need an experienced software engineer who is completely at home in the ROS ecosystem. The mechanical and electronic design are already handled; what I’m missing is someone who can take charge of the software layer, wire the sensors, actuators and high-level behaviours together, and leave me with a clean, well-documented codebase.

Here is where the project currently stands:
• The robot’s compute unit is running Ubuntu, but I haven’t decided whether ROS 1 or ROS 2 will serve us better. I’d like your advice on that choice before development begins.
• Core functionality—navigation, obstacle avoidance and basic manipulation—must be brought online first, followed by a simple REST or gRPC interface so other services can talk to the robot.
• All hardware drivers are available from the manufacturers, yet they still need proper ROS node wrappers and message definitions.

Deliverables
1. Recommendation memo (ROS 1 vs ROS 2) with clear rationale for the final selection.
2. Modular ROS packages for sensor input, motion planning and actuator control, written in clean C++/Python and conforming to ROS coding standards.
3. Launch files, parameter files and a README that makes it easy for another developer to spin the system up from scratch.
4. A brief hand-off session (recorded) walking me through the architecture, build process (catkin/colcon) and any future extension points.

Acceptance criteria
• All nodes compile and run without errors on a fresh Ubuntu install.
• Real-time sensor data is visualised in RViz and fed into navigation successfully.
• Code passes roslaunch tests and cpplint/flake8 with no critical warnings.

If you have 4+ years of hands-on ROS development and can start soon, I’m ready to move quickly. Please mention a project where you integrated multiple sensors in ROS so I know you’ve read the brief.

Skills: Python, Software Architecture, C++ Programming, Robotics, Software Development, Ubuntu, Software Documentation, Robot Operating System (ROS), Software Engineering, REST API

Reference Design:
CM5 RPI card: https://github.com/piecol/CM5_MINIMA_REV3
Pixhawk Standard: https://github.com/pixhawk/Pixhawk-Standards

Please refer to the Pixhawk standard and we need to build a unifed board housing both CM5 and Flight controller. The communication between CM5 and the flight controller shall be through the Pixhawk Standard connector.

Thank you.

Looking for an engineer with experience in flexible heating elements and embedded systems for a single hardware prototype. The project requires designing a thin flexible heating element that distributes heat uniformly across a surface, powered by a long life coin battery, and activated automatically by a temperature sensor when ambient temperature reaches a certain threshold. This is for a single prototype initially with potential for future production

Take a rough PCB layout from alpha phase to finished product. Schematic is and first PCB design iteration is nearly complete. Looking for a PCB designer to look it over before ordering some test units then help improve and and minimize size of design for high volume production readiness

I’m exploring the use of the RK3576 SoC . Could you help evaluate whether this chip can efficiently run a cloud-based OS (thin client / remote desktop setup)? I’m particularly interested in performance, compatibility, and any limitations you foresee. Looking forward to your insights.

The project consists of two separate PCBs:

1. Controller PCB (existing design)

Based on ESP32-S3
Controls a motor and LED lighting system
Includes a 915 MHz RF receiver interface
Schematics and PCB layout are already completed (without the receiver)

Scope for this board:

Review the existing schematic and layout
Identify any issues related to:
Power integrity
Grounding and noise (motor + switching)
RF routing considerations
General layout best practices
Provide recommendations or required corrections prior to manufacturing

2. Remote PCB (new design required)

Based on ESP32-S3
Includes:
915 MHz RF transceiver (SPI)
SPI LCD display (ST7796S or similar)
Capacitive touch controller (I²C)
Battery management (Li-ion charger + fuel gauge e.g. MAX17048)
Schematics are complete
No PCB layout has been done
No antenna matching network has been designed

Scope for this board:

Full PCB layout design from schematics
RF section design including:
915 MHz antenna matching network
Antenna selection (PCB trace, chip antenna, or u.FL depending on constraints) - Signal should reach 25-40metres
Proper partitioning of:
RF section
Digital (ESP32)
Power (battery, charger, regulators)
Routing for:
SPI (LCD + RF)
I²C (shared between touch controller and fuel gauge)
Power integrity and grounding strategy
Preparation for manufacturing (JLCPCB preferred)
Operation of the remote will be through the 3.5 inch ST7796S module

General Requirements

Compact layout suitable for handheld remote form factor
Consideration for EMC and RF performance
Clear documentation of layout decisions
Output: Gerbers, BOM, and assembly files

Please let me know if any additional information is required to proceed.