Device security and OTA updates: designing both in
A device you cannot update safely is one you cannot fix. A device that accepts any firmware is one somebody else can take. Both are decided by choices made before the first board.
Read the article ↗In-depth articles on industrial IoT, embedded engineering, connectivity and product development, written for the engineers and technical buyers who have to make these decisions.
A device you cannot update safely is one you cannot fix. A device that accepts any firmware is one somebody else can take. Both are decided by choices made before the first board.
Read the article ↗Where quiescent current hides, why peak current causes resets rather than flat batteries, what cold really costs you, and how to measure consumption instead of estimating it.
Read the article ↗Sampling, aliasing, conditioning, noise, mounting and calibration. Everything downstream inherits the quality of what you captured, and no processing puts back what was lost.
Read the article ↗Where to take data from, how to design the boundary between plant and business networks, and the timestamp and data quality problems that decide whether any of it is usable later.
Read the article ↗LoRaWAN, NB-IoT, LTE-M, cellular, Wi-Fi and Bluetooth compared on the things that matter: coverage at your sites, power, payload, downlink and cost across the fleet.
Read the article ↗Memory budgets, inference timing, quantisation cost and the power arithmetic that decides whether a model belongs on the device at all.
Read the article ↗Prediction is earned rather than bought. What condition monitoring delivers first, why failure history is the constraint, and how to run a programme people still trust after a year.
Read the article ↗Most of the useful information can be collected without opening the machine. What to measure, how to install it, and how to run the programme so it survives past the pilot.
Read the article ↗They are not really competitors. Understanding what each one is for makes the choice straightforward, and explains why most working systems use more than one.
Read the article ↗