Mitsubishi FR-A5ND, Инструкция по эксплуатации

Страница: 19 / 78

FR-A5ND
DeviceNet
™
Communications Option Unit
13
VFD has recognized the FR-A5ND Option Unit, the VFD configuration data
may be re-entered either via the parameter unit or the network.
3.1.1.3. To use the DeviceNetManager™ software, you will need to acquire
the DeviceNet Electronic Data Sheet (EDS) file. The EDS file is a standard
DeviceNet file which defines the configurable parameters of a field device and
facilitates the network configuration software’s ability to recognize a specific
field device. Please refer to the configuration software tool instruction manual
for more information about the installation and use of EDS files.
The most recent revision of the A500(L) EDS file is available on the Internet
as well as a separate item from Mitsubishi Electric Automation, Inc. See
Appendix A for details on acquiring this file.
3.2. Basic Configuration
3.2.1 Set Baud Rate:
The baud rate must be consistent throughout the network in order to estab-
lish communication and allow configuration via the network. Therefore, this
step is critical to the success of the FR-A5ND Option Unit’s configuration.
3.2.1.1. Upon power-up, the FR-A5ND DeviceNet Option Unit will default to a
communication speed of 125 Kbps.
3.2.1.2. The baud rate may be set via the network using “Baud Rate,” at-
tribute 2 of DeviceNet Class 0x03, instance 1. See section 6.2.3 for further
information.
3.2.1.3. The baud rate may be set manually via the parameter unit by chang-
ing Pr345. See section 5.1 for further information.
3.2.1.4. Set Node Address: The station number assigned to the FR-A5ND
Option Unit in section 2.3 will determine the default node address upon VFD
power-up. If, upon network configuration, an address conflict is found, the
Node Address may be set via the using “Node Address,” attribute1 of the
DeviceNet Class 0x03, instance 1. See section 6.2.3 for further information.
3.2.2. DeviceNet I/O Assembly:
Communication between a master device and a slave device on the network
requires that the DeviceNet Class 0x04 – “Assembly Object” in both devices
be the same.