dave_user, Administrators
5,190
edits
Changes
no edit summary
{{InfoBoxTop}}
{{AppliesToAXELULite}}
{{AppliesToAXEL ULite TN}}
{{AppliesToSBCLynx}}
{{AppliesTo SBC Lynx TN}}
{{AppliesToIoT}}
{{AppliesTo IoT TN}}
{{InfoBoxBottom}}
== [[XUELK-AN-005: Implementing an Industrial IoT gateway/supervisor|History]] ==
Nowadays, the need to implement IIoT solutions, associated with machines that are already in operation, is pretty common. This step is usually part of a broader plan that is a migration path toward the Industry 4.0 model. Traditional industrial machines and systems, which were conceived and deployed before the introduction of Industry 4.0 concept, often have no Internet network connectivity. As such, it is usually challenging to find '''non-intrusive retrofitting solutions to connect them to the Internet'''.
This Technical Note describes a real-world example in which the versatility of [[:Category:SBC_Lynx|SBC Lynx]] was leveraged to address this issue. A customized industrial gateway was built on the base of [[XUELK-AN-005:_Implementing_an_Industrial_IoT_gateway/supervisor|this implementation]]. This device, which is able to perform '''non-intrusive data collecting from a legacy industrial machine''', is part of a '''larger data collecting and monitoring system''' that will be illustrated in the following sections as well.
===The legacy industrial machine===
The legacy machine is powered by an embedded system that was designed by DAVE Embedded Systems years ago and that consists of several boards. Two of them are more relevant for the purposes of this discussion. They are named ''Single Board Computer'' and ''I/O board'' as shown in the following picture.
The two boards are connected with an RS485 link on which data are exchanged through a proprietary protocol.
===The industrial gateway===
The gateway is powered by an embedded Linux distribution, which was tailored for such applications. On the legacy machine side, the gateway acts as a traffic sniffer. It is connected to the RS485 link and eavesdrops all the traffic flowing through this channel. As it is aware of the protocol used, it can parse the exchanged packets and extract data from them. On the cloud side, the gateway uploads every extracted piece of data to the NoSQL database, along with an associated timestamp.
It is worth remembering that the '''extraction of data to be uploaded to the cloud is a non-intrusive process''': to implement this solution, '''no hardware/software modifications of the legacy machine were required'''.