Hard real-time, it's an extension of low level programming, but distinct in that in general it has timing, safety and security requirements religiously applied.
E.g. Aerospace, Automotive, Industrial control systems
My day job is designing and developing websites, but in my off time, I like to build all kinds of things, including Ruby gems, iPhone apps, and Alexa skills.
Would you be willing to write up a quick description of it (nothing to crazy, just a couple sentences) along with a list of five or six key components so I can add it to the list?
Hard real-time, it's an extension of low level programming, but distinct in that in general it has timing, safety and security requirements religiously applied.
E.g. Aerospace, Automotive, Industrial control systems
I like this.
Would you be willing to write up a quick description of it (nothing to crazy, just a couple sentences) along with a list of five or six key components so I can add it to the list?
The fundamental requirement of hard real time is achieving some specific task, in a specific amount of time.
Sometimes this is a repetitive periodic action. E.g. 1ms.
Or a deadline action, event x has happened, complete action y before time z.
All the timings will have a tight tolerance e.g. 1% or 3% of the target time.
This is typically used in control systems or monitoring systems.
Safety is due to the element being controlled. Usually with legal or industry standards to be applied.
Security due to malicious action on those safety systems.