Verified device applications using Anybus Communicator gateways

Anybus logo Anybus® Communicator™ - Verifed device listing

Product Type:
Industrial Sensors

Brand & Model nr:
Sick DME3000

Solution Overview:
The example shows how to connect a Sick DME3000 laser distance reader to Ethernet. The Anybus Communicator is used to connect between Ethernet and the Sick:s serial port. The example also contains a preconfigured WEB page.

Solution Brief:
The Sick DME3000 has to be configured for serial communications as well as the Anybus Communicator. It is assumed that the initial parameters are set up according to the manual of the Sick DME3000.
Configure the Sick DME3000 serial communication parameters manually as shown below:
Baudrate = 9600
Stop bits = 1
Mode = Continuous
Data bits = 7
Parity = Even
Stopbits = 1
Prot = CRLF

The data output from the Sick DME3000, is received by the Anybus Communicator as a variable data object. See below for settings:
Data location: 0x0000
Max.Data length: 0x0024
Byte swap: No swapping
End character value: 0x0A
Fill un-used Bytes: Enable
Filler value: 0x00
Object delimiter: End character visible
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?. Please note: ?TCP/IP Settings? must be DISABLED in ABC Config Tool if Anybus IPconfig utility is used.

RS422 Wiring between Anybus Communicator and Sick DME3000:
Dsub on Anybus Communicator:
1 - +5V Output
5- Ground
6 - RS422 Rx+
7- RS422 Rx-
8- RS422 Tx+
9- RS422 Tx-

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_sick_DME3000.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.