Verified device applications using Anybus Communicator gateways

Anybus logo Anybus® Communicator™ - Verifed device listing

Product Type:
Drive/Inverter

Brand & Model nr:
Emotron VFB40

Solution Overview:
The example shows how to connect an Emotron VFB40 Inverter to Ethernet. The Anybus Communicator is used to connect between Ethernet and the VFB:s built in ModbusRTU port. The example also contain WEB pages and pre configured emails.

Solution Brief:
The Emotron Drive has to be configured for serial communications as well as the Anybus Communicator. It is assumed that the drive motor data (initial parameters) is set up according to the manual of the VFB.
Configure the Emotron Drive serial communication parameters manually as shown below:
261 Baudrate = 19200
262 Address = 1
263 Interrupt = off
212 Ref Control = Comm
213 Run/Stp Ctrl = Comm

The following ModbusRTU registers are communicated with the drive:
Read:
30029 Control start by / Control mode
30030 Control ref by
30031 Serial comm. unit address
30032 Serial comm. baudrate
30015-30016 Shaft speed (High and low word)
Write:
2 Run / Stop
3 Run Right
4 Run Left
41001 Comm. Ref

Anybus Communicator Ethernet settings:
To set the desired TCP/IP settings use either the Anybus IPconfig utility or the built in settings in ABC Config tool; found under ?Fieldbus?. Plese note: ?TCP/IP Settings? must be DISABLED in ABC Config Tool if Anybus IPconfig utility is used.

Seral cable configuration:
RS232 Wiring between Anybus Communicator and VFB40:
Dsub Communicator -- Dsub VFB40
2 -- 2
3 -- 3
5 ? 5

Comments:
It is possible to have up to 10 user defined email files, ?email_1.cfg?email10.cfg?. If the user would like to receive an e-mail that is event triggered, for example if a motor exceeds 1000 rpm, it is possible to set that up. For further information read the User manual, which can be downloaded from: www.anybus.com

Zip File:
 ABC_Emotron VFB40.zip

Disclaimer
The configuration files shown above are provided as a guide to assist you with your own configuration. HMS takes no responsibility or liability for the usage of these files in your product/network setup.