Named pipes

Named pipes

A named pipe is a conduit created by a user that allows for interprocess communication between multiple processes running on different machines through the network. It is a method for communication between programs, where a pipe server instantiates the pipe and pipe clients connect to it.From: Handbook of Local Area Network Software [1991], An approach to develop a digital twin for industry 4.0 systems: manufacturing automation case studies [2021]

Lan Softwarepotpourri

View Chapter

Purchase Book

Published in Paul J. Fortier, Handbook of Local Area Network Software, 1991

Paul J. Fortier

A key feature of this operating system is its interprocess communications feature. This feature allows users to create named pipes (conduits) through the network so that multiple processes running on various machines can be linked together by interprocess communications. Using this capability, developers can design a wide array of distributed processing applications.

An approach to develop a digital twin for industry 4.0 systems: manufacturing automation case studies

View Article

Journal Information

Published in International Journal of Computer Integrated Manufacturing, 2021

David Guerra-Zubiaga, Vladimir Kuts, Kashif Mahmood, Alex Bondar, Navid Nasajpour-Esfahani, Tauno Otto

Named pipe is a method for communication between programs called a pipe server that instantiates the pipe and pipe clients that connect to the pipe. For this project, a duplex pipe is written since, for the proper implementation of the Digital Twin concept, both applications should be able to send and receive the data. The ControllerAPI application acts as a server; it sets the pipe called ‘digitalTwinPipe’, and the Unity project acts as a client. It is important that the server application is started before the client process attempts to connect to the pipe because, otherwise, the client tries to connect to the pipe that does not exist yet. To coordinate which side has the control over the other and avoid overriding the joint values, the direction of the data flow is specified in the virtual environment using buttons Send and Get from the Digital Twin user interface. Additionally, virtual joystick capabilities are blocked when the virtual model follows the real robot motion.

Explore chapters and articles related to this topic

Lan Softwarepotpourri

An approach to develop a digital twin for industry 4.0 systems: manufacturing automation case studies