Read the right signal
Connect the sensors and define what to sample, how often to sample it and which readings the product needs to keep.
Make your device measure, communicate and respond. Prototyped develops firmware and connected prototypes in Switzerland, linking sensors and hardware to the applications that use their data.
Tell us what you needConnect the sensors and define what to sample, how often to sample it and which readings the product needs to keep.
Build the path from a device to a phone, gateway or backend. Choose the connection around range, power and the place the device will operate.
Exercise the device with its interface and data path. Include connection loss and recovery in the prototype scope where they affect everyday use.
A Bluetooth sensor, a gateway and a cloud-connected device solve different problems. We start with the user interaction, deployment environment and power source, then choose the architecture. That keeps the first version focused on what it needs to prove.
We can work with an existing board or develop firmware alongside new electronics. Board documentation, source-code access and a sample device help us assess an existing design. The agreed handover can include firmware source, build instructions and interface documentation.
A small device worn by a platypus measures temperature and humidity around the animal. A Bluetooth Low Energy gateway receives the readings and relays them to a backend. The case study explains that complete data path.
Explore the case studyYes, subject to reviewing the board and its documentation. Useful starting points are the schematic, component list, connector information, existing source code and the behaviour you want to change.
Not always. A device may connect directly to a compatible phone or computer. A gateway can be useful when readings need to reach a backend without relying on a nearby personal device. We choose this around your use case.
Yes. Firmware, gateways, backends and interfaces can be developed as one project or scoped separately. We agree where the data goes, who uses it and which interactions the first version needs.
Yes. Sampling frequency, wireless communication and component choice all affect power use. We can scope power measurements and duty-cycle changes into the prototype; battery life needs to be checked on the actual hardware.