Toshiba G7 - Manual (Page 22)

G7 ASD Multi-Protocol Communication Option and PG Feedback Option Manual 15
8. Network Configuration Parameters
This section applies to ASD-MULTICOM-A option boards only.
Because the Multicom interface supports several different fieldbus physical layers and protocols, some
configuration must be performed prior to inclusion on the network to inform the Multicom interface
which network it is being asked to communication via, and what the characteristics of that network are.
This configuration is performed by setting ASD parameters F890 ~ F894, which are collectively known
as the “Network Configuration Parameters”.
Note that the values of these 5 Network Configuration Parameters are only read by the Multicom
interface upon initialization after a drive reset or power-up condition. Therefore, if any of these
parameters are changed, be sure to reset the drive to enable the changes (as will be explained later, this
may actually involve resetting the drive twice: once when changing the “Network Selection” parameter
to validate the chosen network, and then once more when changing any of the configuration items
associated with the chosen network). Also note that although parameters F890 ~ F894 are always
available, whether or not all of these configuration parameters are actually used by the Multicom
interface will depend on the Multicom interface’s firmware version and the selected network.
The primary network selection is chosen by parameter F890 (refer to Table 4).
Table 4: Network Selection
Parameter Function Settings Default Value
F890
Network
Selection
0: Profibus DP
1: Modbus RTU
2: DeviceNet
0
The function and adjustment ranges assigned to parameter F890 are fixed; that is to say that parameter
F890 is always the “Network Selection” parameter. The functions and adjustment ranges of the
remaining network configuration parameters (F891 ~ F894), however, will vary based on the setting of
parameter F890. For example, when parameter F890 is configured for Profibus DP communications,
then parameter F891 is unused, and its upper and lower adjustment limits will both be “0”. When
parameter F890 is configured for Modbus RTU communications, however, then parameter F891 is used
to select the Modbus network baud rate, and its adjustment range then becomes 0 ~ 7.
As previously mentioned, the values of the Network Configuration Parameters are validated by the
Multicom interface only during a drive initialization procedure. Therefore, when the drive and the
Multicom interface are initializing, the settings of the Network Configuration Parameters are read and
internally saved by the Multicom interface. These internally-saved values
will not change until the next
initialization procedure. For this reason, two drive resets may be required when modifying the Network
Configuration Parameters: one to change and validate the network selection (parameter F890), and
another one to change and validate the remaining Network Configuration Parameters (parameters F891
~ F894) if necessary.
This behavior may best be explained through the use of an example. Say, for instance, that the
Multicom interface is currently configured for Profibus DP communications (parameter F890 = 0).
Let’s also say that we would like to reconfigure the Multicom interface to communicate via Modbus
RTU at 38.4kbaud with even parity, and that all configuration parameters are currently at their factory-
default values:
1. Apply power to the drive. The drive and Multicom interface initialize. Parameter F890 is set
to 0, so the Multicom interface internally configures itself for Profibus DP communications.