Global Sources
EE Times-Asia
Stay in touch with EE Times Asia
EE Times-Asia > Networks

Developing IoT for industrial control (Part 2)

Posted: 11 Feb 2014 ?? ?Print Version ?Bookmark and Share

Keywords:IPv6? 6LoWPAN? Internet Protocol? IP? Internet of Things?

While most of the building blocks required to build a viable Industrial Internet of Things (IIoT) with the features described in Part 1 are widely available, bringing all the elements together will be a challenge even for experienced embedded developers.

To simplify the process, we have developed the IzoT stack (figure 1), available as a free software download. It is a set of higher-level protocol services that can run on top of any IPv4 or IPv6 UDP socket interface and is designed to meet the communication needs of the peer-to-peer IIoT. When running on top of IPv4, the features of IPv6 such as stateless auto-configuration and neighbour discovery are not available. If possible, use IPv6 for its ease of installation.

Figure 1: IzoT features.

A version of the IzoT stack runs on the Raspberry Pi platform and allows developers to prototype on the Pi using either the Ethernet or Wi-Fi interface for the communications.

Rapid detection of packet failures
The IzoT stack supports end-to-end acknowledgements and responses so that if a packet is lost in traversing the network across multiple links, the loss is discovered and the packet is retransmitted. This feature is available with both unicast and multi-cast services.

When using acknowledged multi-cast or request/response multi-cast services, retry messages are encoded with only the nodes that must respond. This limits congestion by informing the nodes whose responses or acknowledgements have already been received by the sender.

No single point of failure
The IzoT platform supports multiple PHYs that, if they fail, only the node connected to the PHY will fail. For example, twisted-pair PHYs are transformer-coupled, so if the drivers fail in a state where they are stuck high or low, it will have no effect on the other nodes on the link. The twisted-pair PHYs are true multi-drop so there are no single components that could fail and take down the link.

In the case where IzoT uses Ethernet, this level of reliability may be achieved with redundant switches. When using IEEE 802.15.4 or IEEE 802.11 b/g/n, the PHY protects itself from denial of service attacks via a process of white listing MAC IDs. When using Power Line communications, the interfaces may be transformer-coupled and a watchdog timer can protect a node from having the transmitter constantly energized.

In the IzoT network, the devices are all autonomous with no central controller dictating their actions. Fully distributed systems, such as the IzoT network, can survive multiple, individual node outages and still operate, or gracefully shut down with operator notification. A system consisting of clients and a server does not have this property, because when the server goes down, the entire system fails.

Duplicate detection
When an IzoT packet is sent, it is assigned a transaction ID number. Nodes that receive the packet create a record of the communications transaction based upon the source, destination, priority attribute, and transaction ID. At the time of initial creation of the record, a timer for the maximum time of the transaction is started. This timer is based on information encoded in the packet or provisioned in the receiver node.

If a subsequent packet is received that matches this record, that packet is detected as a duplicate, and the previously sent response gets re-sent. If a new packet arrives with a transaction ID greater than the currently active transaction, but matching in all the address and priority attributes, the receiver assumes that a new transaction has begun and re-initializes the receive timer.

A packet that arrives with a previously used transaction ID C a smaller value than the currently active transaction, but matching in the address and priority attributesis considered stale and is discarded.

Priority messaging
A sender of an IzoT packet can mark the packet as high priority. This can give it priority at the MAC layer if that feature is supported, and will also give it priority through any intervening routers to its destination. This allows emergency messages to be propagated through the network ahead of non-emergency messages in router queues.

Multiple simultaneous communications transactions
Nodes with more memory can use a version of the IzoT stack with the ability to support many outgoing transactions and correlate the responses. This is done by having a larger outgoing transaction record memory pool, and with some additional logic to correlate responses to the correct initial transaction.

Multiple link support per network
The IzoT stack has been proven on many different links: low-power wireless (IEEE 802.15.4)/ 6LoWPAN, Wi-Fi, Ethernet, multi-drop, free topology twisted-pair (ISO/IEC 149082), consumer band power line (ISO/IEC 14908-3), a new standard for power line communications (IEEE P1901.2), and can be ported to any MAC/PHY that supports a UDP socket. IzoT routers can seamlessly route packets between these links to create a network spanning multiple physical media.

1???2???3???4?Next Page?Last Page

Article Comments - Developing IoT for industrial contro...
*? You can enter [0] more charecters.
*Verify code:


Visit Asia Webinars to learn about the latest in technology and get practical design tips.

Back to Top