Case Studies
What We Have Done Before...
Embedded Engineering Solutions has been providing quality engineering services to customers for more than 5 years. Past projects and areas of work include the following:
Expertise for Dedicated Engineering Support and Maintenance
We have experience with a wide range of industries, companies, and projects. Some of our past successes include:
- Designed a BLE enabled automated pet door for a startup company including all product hardware and firmware – project features aggressive power management, BLE scanning, variable speed motor control, mobile app and AWS cloud integration.
- Designed Real Time Location Service IoT product for a large medical device company with Azure cloud integration
- Designed a remote monitoring hub for medical devices for a small telemedicine company with AWS cloud integration including all hardware and firmware
- Designed a live fire training tool for a small startup providing products for military and law enforcement training. Work included all hardware, firmware and mobile app development
- Revised and updated the design of a chiropractic adjustment instrument including hardware updates and firmware design – project features LCD user interface, BLE support and magnetic hall effect sensing
- Designed firmware for a specialized sports distance and time tracking tool – project features high accuracy UWB distance measurements and BLE communication with a mobile app
- Developing a 3-phase variable frequency drive designed and optimized for a direct solar DC input for a company that installs remote solar pumping applications
- Developing a ruggedized system that displayed hardwired video output from a specific piece of equipment for a large defense contractor
- Developing multiple hardware and software features for a mid-sized company making medical kiosks including sensing, display and control capabilities
- Developing wireless consumer devices to support telemedicine for a small subsidiary of a large medical device company
- Designed numerous circuit board layouts with up to 8 routing layers for a large supplier of silicon fabrication equipment
- Developed hardware and firmware solutions for a manufacturer of innovative prosthetic controls including BLE communication, power management, analog signal reading and complex mathematical manipulation of control signals
- Developed firmware for a mid-sized manufacturer of inventory control and management products including Zigbee communication and aggressive power management
- Worked with a small medical device startup to design and deploy a battery powered electro-mechanical chest compressor to allow continuous automated CPR for up to 3 hours
- Designed hardware and software for a 3-phase motor soft starter for a small industrial controls company
- Developed firmware to establish remote connectivity to Amazon Web Services for a multi-national corporation using their mobile network and allow them to demonstrate at CES2017
- Developed multiple hardware and firmware solutions to demonstrate various component products including DisplayPort and SoC devices for a large electrical component distributor
- Developed firmware to communicate over BLE to a mobile device app and allow remote control of an embedded LED product
- Developed hardware and software for an LED system that displays complex patterns on a string of multi-color LEDs
FAQs
Can you show examples of engineering firms delivering BLE-connected consumer or industrial products?
Ask for examples that describe the device class, the constraints (power, range, environment), and what was delivered (prototype, pilot, production). Useful proof includes how the wireless link was validated and what was done to make field failures observable. For the capabilities that typically matter in these projects, see Capabilities Overview and Firmware Development.
What should I look for in case studies for IoT or connected embedded devices?
Look for specifics: the problem, key constraints, the architecture choices, what was tested, and the final deliverables handed to manufacturing. Strong case studies also explain tradeoffs and risks, not just outcomes. If you want context for how projects are typically executed, review Our Process.
What counts as "shipped" experience versus a prototype that never went to production?
"Shipped" generally means a design that went through verification, had a manufacturing package, and was built in quantity with a test strategy that worked on the factory floor. Prototypes can be valuable, but they do not prove manufacturability, sourcing resilience, or long-term maintainability. The manufacturing-focused deliverables are covered on Hardware Design and Prototyping.
What past project experience matters most for medical or safety-critical electronics?
Look for experience with disciplined requirements, traceable verification, risk management, and documentation practices that support audits and change control. Ask how hazards and failure modes were handled and what testing was used to prove mitigation. Even when formal regulatory scope varies, the engineering discipline is consistent. Related: Our Process.
What experience should a firm have before designing motor control or power electronics products?
Motor control and power electronics work is driven by safety margins, thermal design, EMI, and failure containment, not just basic functionality. Look for experience with bring-up and measurement on real loads, fault handling strategy, and how the design was validated under worst-case conditions. Hardware-centric considerations are outlined in Hardware Design and system tradeoffs in Embedded Systems Design.
How do firms typically support manufacturing handoff and production ramp for embedded devices?
A strong handoff includes complete design files, a sourceable BOM with alternates, programming and test workflows, and documentation that a CM can build without guesswork. Production ramp is usually where missing test points, unclear requirements, or weak documentation becomes expensive. The expected handoff artifacts are described on Hardware Design and Our Process.
How can I tell if a firm can take over a troubled embedded project and get it stable?
Look for a structured stabilization approach: reproduce the issue, establish a baseline build and test setup, instrument the system, then isolate root cause across hardware and firmware. Be cautious of teams that jump straight to rewriting without measurement. A takeover often starts with a discovery phase, which is outlined on Getting Started, and then routes into Firmware Development or Hardware Design.