Varied timing, OCCAM modeling, and hardware-software equivalence in a worked IoT example

CSP-based OCCAM modeling promises to bring great clarity to Internet of Things (IoT) designs that have been made vague by abstract tools. This requires an absoluteness in timing and data access that is more characteristic of the Transputer than of modern systems. However, it turns out some standard C and *n*x library tools can provide it, if human timing suffices. IoT design is strongly dependent on use cases, and we had the fortune of a very definite project use case that drove the small OCCAM-modeled system described in the Reference. Key tools in the design include Unix sockets, ssh, and the kernel-based call select(). This paper will complete that system, begun in the referenced Fringe, and relate it to the general issues to which this technique can be expanded. Its occam modeling will be defended based on timing knowledge, and its hardware-software equivalence (HSE) will be proven. This development must be read in conjunction with the Reference, which see. It de- velops the Reference to allow three or more independent racing systems. It explains the applicability of the revised approach to general IoT.