IQlab / Engineering
Controllers & firmware
Device logic, sensor interfaces and communication. Hardware and firmware developed together.
Discuss a project ↗
IQlab / FIRMWARE
Controllers for the application
We develop control and data acquisition devices, defining inputs, outputs, event responses and behavior when communication or power is lost.
What the work covers
01
Firmware as part of the system
We implement peripherals, signal processing and communication with external equipment. Interfaces and protocols are selected for the project requirements.
02
Validation on real hardware
We check startup, normal operation and error handling on the target board. Agreed interfaces and configuration procedures are documented to support future maintenance.
03
Interfaces & requirements
Agree on connections, constraints and expected system behavior.
Firmware as part of the complete system
Firmware connects electronics to the application: it samples inputs, drives outputs, processes commands and reports device state. We define operating sequences, acceptable delays and error behaviour at the start. Integrators benefit from a clear protocol and predictable handling of repeated commands.
Communication, diagnostics and maintenance
Message formats, responses, timeouts and error codes are specified together. Diagnostic information helps distinguish missing peripherals from protocol or power problems. Updates through a single-board computer are designed for the selected controller, including the loading method, version checks and recovery procedure.
Testing with actual peripherals
Assessment includes cable removal, restart, invalid responses and reconnection as well as normal operation. For cash-handling terminals, operation acknowledgement and prevention of duplicate execution need explicit rules. Firmware can be developed for a new board or adapted alongside existing equipment.
Before we begin
Can we start from an existing board or system?
Yes. Send a description, available schematics, files and photos. We first determine what can be retained and what needs to change.
How are cost and timing defined?
After discussing the problem, constraints and expected outcome. Scope and milestones are agreed for the individual project.
What do you need for an initial discussion?
A brief description, the existing equipment and essential functions. If you already have a specification, attach it to your email.
UART / I²C / SPI / GPIO
Universal peripheral controller
A ready hardware platform for software teams. Connect peripherals to a single-board computer and build standalone automation without a conventional PC.
Everest controllers and readers have been proven through several years of round-the-clock operation in deployed systems.