Embedded consultant for Development Board and firmware Selection mini cnc with pan tilt (prototype stage) no plc
Budget: ₹1,500 – ₹12,500 INR
I’m finalising the electronics platform for a small CNC-style automation device (XYZ nema motor+ pan/tilt servo motor + 3 DC motors) and need an experienced embedded/firmware engineer to evaluate options, advise on tradeoffs, and map the estimated firmware effort for each choice.
Important: I do not want a PLC or complex industrial control stack. The solution should be simple, reliable, and operate like a 3D-printer — easy to communicate with, easy to operate, and easy to update in the field.
________________________________________
Use case
Automate up to 10 repeatable tasks for non-technical operators. Key product expectations include:
• Start a stored motion path from an RF/wired remote
• Optional scheduling and multi-selection auto-start
• Manual/digital speed control for motors
• Emergency stop, start/pause/stop, error/status LEDs
• Remaining time display, motor/sensor status indicators
All of above shall be subject to Practical discussion of integration, power consumption, failure modes, and alternatives
________________________________________
Project summary
• 3-axis CNC (X/Y/Z steppers) with SD card storage for 10 motion paths (file size not a constraint).
• Pan–tilt mechanism near the tool (2 servos).
• DC motors: 2 auxiliary DC motors + 1 DC tool motor on Z (on/off and optionally PWM speed).
• Motion files will be uploaded by us (SD / Wi-Fi / Bluetooth-anything that’s reliable and doable).
• The remote(wired or RF) is used to select and start one of the 10 stored paths. Pan-tilt moves are executed together with the selected trajectory; DC motors may be started/stopped as defined by the path.
• Optional: user control for DC motor speed and trajectory speed.
I will provide sample RF-remote button layouts (4 variants). Your task includes evaluating firmware impact for each and recommending the least intrusive option.
________________________________________
Scope of work (deliverables)
Please deliver a clear, actionable report that includes:
1. Short comparison matrix of at least three suitable development platforms (e.g., Teensy, ESP32, STM32, Raspberry Pi Pico, etc.) with:
o Key pros/cons for this project
o Estimated difficulty of required firmware customisation (low/medium/high)
2. Your recommended platform and why — include practical notes such as:
o Boot time and startup behaviour
o Low-power / standby options and RF wake strategy
o Field upgrade approach (OTA, SD, USB)
o Peripherals needed (PWM timers, ADC channels, SPI/UART/SPIFfS)
3. Feasibility & effort estimate for firmware customisation:
o Toolchain options (GCC, ESP-IDF, PlatformIO, STM32Cube, etc.)
o Driver maturity and gaps (stepper drivers, servo control, PWM for DC motors, SD/Wi-Fi)
o Rough person-days to reach a production-ready image (prototype → release)
4. Evaluation of the 4 remote designs you’ll receive — which remote requires minimal firmware change and why
5. Open issues & technical questions that must be resolved before final sign-off
6. A concise recommended roadmap and next steps I can hand to my firmware team
________________________________________
Constraints & expectations
• Keep solution non-PLC and 3D-printer style (GRBL/grblHAL/firmware-based; simple UART/serial/G-code or file interface).
• Favor minimal custom core-planner work — prefer plugin/extension approach (grblHAL or similar) where practical.
• Prioritise reliability, low power standby with RF wake, and simple operator UX.
• Deliverables should be concise and actionable — diagrams and a short bullet roadmap are preferred.
________________________________________
Ideal consultant profile
• Proven embedded firmware experience (ESP32/STM32/Teensy or similar)
• Experience with CNC/GRBL/grblHAL, stepper/servo control and PWM/DC motor control
• Experience with SD/Wi-Fi/OTA file handling and low-power RF wake designs
• Comfortable producing architecture diagrams, pinout recommendations, and implementation time estimates
Please feel to apply if you think you can contribute as an expert for any aspect of the project
Important: I do not want a PLC or complex industrial control stack. The solution should be simple, reliable, and operate like a 3D-printer — easy to communicate with, easy to operate, and easy to update in the field.
________________________________________
Use case
Automate up to 10 repeatable tasks for non-technical operators. Key product expectations include:
• Start a stored motion path from an RF/wired remote
• Optional scheduling and multi-selection auto-start
• Manual/digital speed control for motors
• Emergency stop, start/pause/stop, error/status LEDs
• Remaining time display, motor/sensor status indicators
All of above shall be subject to Practical discussion of integration, power consumption, failure modes, and alternatives
________________________________________
Project summary
• 3-axis CNC (X/Y/Z steppers) with SD card storage for 10 motion paths (file size not a constraint).
• Pan–tilt mechanism near the tool (2 servos).
• DC motors: 2 auxiliary DC motors + 1 DC tool motor on Z (on/off and optionally PWM speed).
• Motion files will be uploaded by us (SD / Wi-Fi / Bluetooth-anything that’s reliable and doable).
• The remote(wired or RF) is used to select and start one of the 10 stored paths. Pan-tilt moves are executed together with the selected trajectory; DC motors may be started/stopped as defined by the path.
• Optional: user control for DC motor speed and trajectory speed.
I will provide sample RF-remote button layouts (4 variants). Your task includes evaluating firmware impact for each and recommending the least intrusive option.
________________________________________
Scope of work (deliverables)
Please deliver a clear, actionable report that includes:
1. Short comparison matrix of at least three suitable development platforms (e.g., Teensy, ESP32, STM32, Raspberry Pi Pico, etc.) with:
o Key pros/cons for this project
o Estimated difficulty of required firmware customisation (low/medium/high)
2. Your recommended platform and why — include practical notes such as:
o Boot time and startup behaviour
o Low-power / standby options and RF wake strategy
o Field upgrade approach (OTA, SD, USB)
o Peripherals needed (PWM timers, ADC channels, SPI/UART/SPIFfS)
3. Feasibility & effort estimate for firmware customisation:
o Toolchain options (GCC, ESP-IDF, PlatformIO, STM32Cube, etc.)
o Driver maturity and gaps (stepper drivers, servo control, PWM for DC motors, SD/Wi-Fi)
o Rough person-days to reach a production-ready image (prototype → release)
4. Evaluation of the 4 remote designs you’ll receive — which remote requires minimal firmware change and why
5. Open issues & technical questions that must be resolved before final sign-off
6. A concise recommended roadmap and next steps I can hand to my firmware team
________________________________________
Constraints & expectations
• Keep solution non-PLC and 3D-printer style (GRBL/grblHAL/firmware-based; simple UART/serial/G-code or file interface).
• Favor minimal custom core-planner work — prefer plugin/extension approach (grblHAL or similar) where practical.
• Prioritise reliability, low power standby with RF wake, and simple operator UX.
• Deliverables should be concise and actionable — diagrams and a short bullet roadmap are preferred.
________________________________________
Ideal consultant profile
• Proven embedded firmware experience (ESP32/STM32/Teensy or similar)
• Experience with CNC/GRBL/grblHAL, stepper/servo control and PWM/DC motor control
• Experience with SD/Wi-Fi/OTA file handling and low-power RF wake designs
• Comfortable producing architecture diagrams, pinout recommendations, and implementation time estimates
Please feel to apply if you think you can contribute as an expert for any aspect of the project