Are there any specifications for a IoT device that's targeted for the automotive industry? I refer to a standard that puts constraints on boot and restart times for both the HW and SW?

Let's say I want to build an IoT platform that starts the AC once it's too cold or a device that makes the car horn goes off if it detects a possible collision.

What kind of booting times, restart time or any other requirements I need to take into account.

  • 1
    You need to clarify exactly what you want to attempt here. Very generally, for automotive, you need to demonstrate with a high degree of certainty, how many failures you expect, how you will handle them, and how significant the impact of the ones you miss are. This is also off-topic. Commented Jun 26, 2017 at 23:37
  • 1
    You would not normally use a desktop operating system for this; the primary reason you may see one in some home devices is to speak everyday IP networking protocols, but something in a car would speak CAN or maybe BLE to cooperate with a phone. Arguably, this isn't even an IoT question, but rather an automotive one. Commented Jun 27, 2017 at 3:29
  • 1
    Context is really missing here, are those homework ? University project ? if you work at an automotive design shop they should have better specifications
    – Rsf
    Commented Jun 27, 2017 at 8:46
  • @Rsf it's for a startup I am starting to work on.
    – 0x90
    Commented Jun 27, 2017 at 8:48
  • 3
    I don't understand why some people voted to close this question as off-topic. It's about the design of an IoT device. I voted to close as too broad, because the applicable requirements depend on what the device is used for (critical functionality, interacts with critical components without giving critical output, not connected to the car's main buses, …). Commented Jun 27, 2017 at 21:37

2 Answers 2

  • Yes, there are standards, they are called Automotive safety standards, you can start with ISO26262.
  • Regarding the boot time, this is usually a requirement of the car manufacturer. However this can be determined asking the following question.

In case of fail while driving, how much time the system needs to reach a safety state? This is, speed 0 and out of the way to avoid other cars/trucks that come behind to collide with you. Considering the speed the car is driving and the distance to the obstacle, with this you get the maximum time the system can take to stop the car. Now, in that period the system can fail and restart. Therefore the system recovers insanely quick or there is a redundant service that kicks in when the other is down. The last is the most realistic.

Autonomous driving cars are reaching a safety requirements compare to the airplanes, or even more complex, because the environment they work has many more factors, traffic lights, traffic signs, people, cars, etc.


The IoT devices are normally non real-time machines.

These devices will be connected to the controllers and readers to collect data. And would help with the best route while driving. or control the cooling system wrt the weather forecast(Chuckle).

The functions of the automobile that has to happen in real-time are the operation of auto-brake, airbags etc. (During collision). These are better to have their control system in the vehicle itself, rather than over the internet.

The boot time for a Hard real-time application should be as minimal as possible(in milliseconds). But the IoT system would not be that fast because, it has many functionalities like the Internet Capability, GPS system, etc.

For the AC application that you mentioned, It might be feasible to use an IoT control system!

Hope it helps.

  • this link here could be a reference. Commented Jun 27, 2017 at 7:43
  • IoT endpoints are real-time. Saw one launched last week with flash-based configuration memory (for peripheral state) so it's live from reset. Commented Jun 27, 2017 at 12:02
  • @SeanHoulihane Maybe a very new tech. but even-though it starts immediately, internet takes time to connect... right. Commented Jun 27, 2017 at 12:48
  • it can also be firm or soft real-time but may not be hard real-time. Commented Jun 27, 2017 at 12:50
  • 1
    Sure, the WAN needs to be asynchronous to local operation, but you'd expect fallback/failsafe operation within a few hundred cycles of reset. A few ms at the very most. Commented Jun 27, 2017 at 12:52

Not the answer you're looking for? Browse other questions tagged or ask your own question.