The DeviceNet protocol firmware provides the DeviceNet Slave
mechanism by the Predefined Master/Slave Connection Set. The virtual slave
would always wait for the request command from the master. The DeviceNet
communication protocol can be clarify as two forms: One is the Explicit
Message and others are I/O Messages. Here, we only provide one explicit
message connection and four I/O connections as depicted in Figure 1.4.2.
Figure 1.4.2 DeviceNet Messaging
The DeviceNet Communication Protocol is based on the concept of
connections method. Master would create connections with slave devices
based on the command of exchanging information and I/O data. The slave
should provide at least one I/O connection to establish the communication with
the master. There are four main steps to create a new virtual slave device in
the PISO-DNS100(U). Figure 1.4.3 demonstrates the main process for creating
the DeviceNet virtual slave below.
Figure 1.4.3 Four steps to establish the DeviceNet connection
PISO-DNS100(U) DeviceNet Slave API functions User’s Manual (Ver: 1.1) 2010/01/07
9
ГК
Атлант
Инжиниринг
–
официальный
представитель
в
РФ
и
СНГ
+7(495)109-02-08 [email protected] www.bbrc.ru