Anybus Communicator CAN

AAnnyybbuuss®® CCoommmmuunniiccaattoorr™™ CCAANNIIIIooTT

USER MANUALSCM-1202-116 1.0 en-US ENGLISH

Important User InformationLiabilityEvery care has been taken in the preparation of this document. Please inform HMS Industrial Networks AB of anyinaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS IndustrialNetworks AB, reserve the right to modify our products in line with our policy of continuous product development.The information in this document is subject to change without notice and should not be considered as acommitment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errorsthat may appear in this document.

There are many applications of this product. Those responsible for the use of this device must ensure that all thenecessary steps have been taken to verify that the applications meet all performance and safety requirementsincluding any applicable laws, regulations, codes, and standards.

HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that mayarise as a result from the use of undocumented features, timing, or functional side effects found outside thedocumented scope of this product. The effects caused by any direct or indirect use of such aspects of the productare undefined, and may include e.g. compatibility issues and stability issues.

The examples and illustrations in this document are included solely for illustrative purposes. Because of the manyvariables and requirements associated with any particular implementation, HMS Industrial Networks AB cannotassume responsibility for actual use based on these examples and illustrations.

Intellectual Property RightsHMS Industrial Networks AB has intellectual property rights relating to technology embodied in the productdescribed in this document. These intellectual property rights may include patents and pending patent applicationsin the USA and other countries.

Anybus® Communicator™ CAN IIoT User Manual SCM-1202-116 1.0 en-US


Table of Contents Page

1 Preface ................................................................................................................................. 31.1 About This Document .......................................................................................................3

1.2 Document history ............................................................................................................3

1.3 Document Conventions .....................................................................................................4

2 Description .......................................................................................................................... 52.1 Introduction....................................................................................................................5

2.2 Data Exchange Model .......................................................................................................6

2.3 CAN Network Protocol ......................................................................................................7

3 Installation......................................................................................................................... 103.1 Installation Overview ...................................................................................................... 10

3.2 External Parts ................................................................................................................ 11

3.3 DIN Rail Mounting.......................................................................................................... 11

3.4 Connectors and Indicators ............................................................................................... 12

3.5 LED Indicators ............................................................................................................... 13

4 Configuration..................................................................................................................... 144.1 Configuration Overview................................................................................................... 14

4.2 Basic TCP/IP Concepts..................................................................................................... 15

4.3 TCP/IP Configuration ...................................................................................................... 16

4.4 Anybus Configuration Manager - Communicator CAN........................................................... 19

4.5 Anybus Configuration Manager - IIoT................................................................................. 23

4.6 Web Interface ............................................................................................................... 25

5 Technical Data ................................................................................................................... 275.1 General Specifications..................................................................................................... 27

5.2 CAN Interface................................................................................................................ 27

5.3 IIoT Interface................................................................................................................. 27

This page intentionally left blank

Preface 3 (28)

1 Preface1.1 About This Document

This document describes how to configure and use the Anybus Communicator CAN IIoT.

The use of this product requires a basic knowledge of industrial network technology and of theMQTT and OPC UA protocols.

For additional documentation and software downloads, FAQs, troubleshooting guides andtechnical support, please visit www.anybus.com/support.

1.2 Document historyVersion Date Description

1.0 2019-02-11 First release


http://www.anybus.com/support

Preface 4 (28)

1.3 Document ConventionsOrdered lists are used for instructions that must be carried out in sequence:

1. First do this

2. Then do this

Unordered (bulleted) lists are used for:

• Itemized information

• Instructions that can be carried out in any order

...and for action-result type instructions:

► This action...

→ leads to this result

Bold typeface indicates interactive parts such as connectors and switches on the hardware, ormenus and buttons in a graphical user interface.

Monospaced text is used to indicate program code and otherkinds of data input/output such as configuration scripts.

This is a cross-reference within this document: Document Conventions, p. 4

This is an external link (URL): www.hms-networks.com

This is additional information which may facilitate installation and/or operation.

This instruction must be followed to avoid a risk of reduced functionality and/or damageto the equipment, or to avoid a network security risk.

CautionThis instruction must be followed to avoid a risk of personal injury.

WARNINGThis instruction must be followed to avoid a risk of death or serious injury.


http://www.hms-networks.com

Description 5 (28)

2 Description2.1 Introduction

Anybus Communicator CAN IIoT is intended for connecting a CAN subnetwork to Ethernetnetworks using the MQTT and OPC UA protocols for IIoT services. The gateway can supply datato the IIoT service but cannot be controlled by it, which means that data flows only from the CANside to the Ethernet (IT) side.

The Anybus Communicator gateways are configured using Anybus Configuration Manager, a suiteof configuration tools with easy to use graphical interfaces that do not require programmingskills.

Anybus Configuration Manager and additional related software and documentation are availableat www.anybus.com/support.

Fig. 1 Anybus Configuration Manager



Description 6 (28)

2.2 Data Exchange Model2.2.1 Overview

The data exchanged on the CAN subnetwork and on the higher level (IT) network reside in ashared memory buffer in the Anybus Communicator CAN. The IT network can read data from thememory locations specified in Anybus Configuration Manager - Communicator CAN.

Fig. 2 Memory buffer structure

The internal memory buffer is divided into three areas based on their function:

Input Data (512 bytes) This area can be read by the higher level (IT) network.

A maximum of 256 data point tags can be defined for MQTT.

A maximum of 80 data point tags can be defined for OPC UA.

Output Data (512 bytes) This area cannot be accessed by the IT network but can be used for setting staticvalues on the subnetwork.

General Data(max. 1024 bytes)

This area cannot be accessed by the IT network but can be used for transfersbetween individual nodes on the subnetwork or as a general “scratch pad” fordata.

The size of the General Data area is 1024 bytes. How much of that area that willbe used for communication depends on the configuration.

2.2.2 Memory MapWhen building the subnetwork configuration in Anybus Configuration Manager - CommunicatorCAN the areas in the memory buffer will be mapped to the following memory locations:

Fig. 3 Memory Map


Description 7 (28)

2.3 CAN Network Protocol2.3.1 General

The CAN protocol is message-based and can exchange up to 8 bytes of data in each message.The protocol only acts as a data carrier, it is up to each application to define and interpret thedata content of the messages.

Data is exchanged using frames. Each frame has a unique identifier for the data it exchanges,which also represents the message priority. Anybus Communicator CAN supports both 11-bit(CAN 2.0A) and 29-bit (CAN 2.0B) identifiers, selected in the configuration.

CAN is essentially a produce-consume protocol, where all nodes listen to all messages. Thedevices recognize what data to collect by the identifier in the CAN frame. Anybus CommunicatorCAN is also able to act as a network master and issue queries that demand responses. Bothmethods can be used within the same configuration.

2.3.2 Message TypesAnybus Communicator CAN features three CAN message types: Query-Response, Produce, andConsume. These message types only specify the basic communication model, not the actual CANprotocol. All three message types can be used in the same configuration.

Query-Response

The Anybus Communicator CAN here acts as a master on the CAN subnetwork, andcommunication takes place in a query-response fashion. The gateway sends a query and expectsa response within a specified timeout.

Fig. 4 Query-Response messaging

Produce and Consume

Here there is no master-slave relationship between the Anybus Communicator CAN and thesubnetwork nodes. Any node, including the gateway, may both produce and consume messages.Nodes do not have to respond to messages, or wait for a query in order to send one. Theconsumed data can be accessed from the higher level network, and vice versa.


Description 8 (28)

Fig. 5 Produce and Consume messages


Description 9 (28)

2.3.3 Protocol Building BlocksThe following building blocks are used in Anybus Configuration Manager - Communicator CAN todescribe the subnetwork communication.

Group A group does not represent any specific device on the CAN subnetwork, it is only ameans to structure the transactions that have been defined for the gateway in AnybusConfiguration Manager - Communicator CAN.

Each group can be associated with any number of transactions, however the totalnumber of transactions in a configuration is limited to 128.

Transaction A transaction consists of one or more CAN frames. Each transaction is associated with aset of parameters controlling how and when to use it on the subnetwork. There are 5transaction types: produce, consume, query-response, dynamic produce and dynamicconsume. A group can contain transactions of all three types simultaneously.

A total of 128 transactions can be configured.

Dynamic Transaction A dynamic transaction makes it possible for a network master to change selectedparameters during runtime. The parameters are mapped to the Output or General Dataareas and cannot be changed using Anybus Configuration Manager - Communicator CAN.

A dynamic transaction can only consist of a single CAN frame which in turn can only holdone data object.

Only one dynamic produce transaction and one dynamic consume transaction can beconfigured.

CAN Frames CAN frames are low level entities used to compose transactions. Each frame carries an11-bit or 29-bit identifier and can hold up to 8 bytes of data.

A total of 256 CAN frames can be configured.

2.3.4 Transaction Live ListThe optional Transaction Live List consists of a bit array where each bit corresponds to atransaction on the CAN subnetwork (bit 0 corresponds to transaction 1 etc.). A set bit indicatesnormal functionality. The bit is not set if the transaction is non-working or non-existent.

The live list is mapped in the Input data area of the memory, either at the start of the area ordirectly after the Status word. From 8 transactions up to 128 transactions in steps of 8 can bemonitored using the live list. This means that up to 16 bytes of the input data area of thememory can be occupied by the live list.

The latest live list can always be accessed in Anybus Configuration Manager - CommunicatorCAN, regardless of whether the live list is mapped in the input data area or not.


Installation 10 (28)

3 Installation

This product contains parts that can be damaged by electrostatic discharge (ESD). UseESD prevention measures to avoid damage.

3.1 Installation OverviewPrerequisites

The following items are required for installation and basic configuration:

• USB type B cable

• CAN cable

• Ethernet cable

• Anybus Configuration Manager - Communicator CAN

• Anybus Configuration Manager - IIoT

• IPconfig (3.2.1.1 or later)

The Anybus Configuration Manager and IPconfig applications can be downloaded fromwww.anybus.com/support.

Basic installation steps

1. Download and install the required configuration software on a PC (see Prerequisites)

2. Mount the Anybus Communicator CAN on the DIN rail.

3. Connect the CAN and IIoT network interfaces.

4. Connect the USB cable between the gateway and the PC.

5. Connect the power cable and apply power.

6. Check the LED indicators to verify that the gateway is running and that the serial and ITnetworks are connected. See LED Indicators, p. 13.

7. Use Anybus Configuration Manager - Communicator CAN to set up the data exchangeconfiguration in the Anybus Communicator CAN.

8. Use IPconfig to configure the TCP/IP settings for the Anybus Communicator CAN.

9. Use Anybus Configuration Manager - IIoT to create a tag configuration and transfer it to theAnybus Communicator CAN IIoT interface.

10. Connect to the web interface of the Anybus Communicator CAN and configureMQTT/OPC UA communication.




3.2 External Parts

Fig. 6 Overview

1 LED indicators2 DIN rail mount3 Power connector4 CAN connector5 USB connector6 IIoT network interface

3.3 DIN Rail Mounting

The unit must be electrically grounded through the DIN rail for EMC compliance.

Fig. 7 DIN rail mounting

Push the unit gently downwards on the DIN rail to attach or relase it from the rail.



3.4 Connectors and Indicators3.4.1 Power Connector (2 pin)

Connecting power with reverse polarity or using the wrong type of power supply maydamage the equipment. Make sure that the power supply is connected correctly and ofthe recommended type.

Pin Signal1 +24 VDC2 Power Ground

3.4.2 CAN Interface (DE-9M)Pin Signal Description

2 CAN_L CAN low

3 CAN_GND CAN ground

5 Shield Cable shield6 CAN_GND CAN ground

7 CAN_H CAN high

1, 4, 8, 9 - (reserved)

3.4.3 USB Connector (Type B)The USB port is used when connecting the Anybus Communicator CAN to a computer forconfiguration. The USB cable should be removed when not in use.

Pin Signal

1 +5 V input

2 USBDM (USB communication)

3 USBDP (USB communication)

4 Signal ground

Housing Cable shield

3.4.4 Ethernet Connector (RJ45)Pin Signal Description

1 TD+ Transmit data +2 TD- Transmit data -3 RD+ Receive data +6 RD- Receive data -4,5,7,8 - (reserved)



3.5 LED IndicatorsLED 1 to 4 IIoT interface statusLED 5 CAN statusLED 6 Device status

LED Indication Meaning

1 - Network Status

Off Offline or no power

Green Online, IP address assigned

Green, flashing No IP address assigned or no link

Red Fatal error, IP address conflict

Alternating Red/Green Firmware update in progress

2 - Module Status

Off No power or IP address conflict

Green Normal operation

Red Fatal error

Alternating red/green Firmware update in progress

3 - Link/Activity 14 - Link/Activity 2

Off Link not detected or no power

Green Link established (100 Mbit/s)

Green, flickering Link activity (100 Mbit/s)

Red Link established (10 Mbit/s)

Red, flickering Link activity (10 Mbit/s)

5 - CAN Status Off No power or no CAN communication

Green Running, no errors or timeout

Red. flashing Transaction error, timeout, or CAN subnet stopped

Red Fatal error6 - Device Status Off No power or initializing

Green Running

Green, flashing Idle

Red Fatal error

Alternating red/green Configuration error

The Link/Activity LED indicators will show a red light for 10 Mbit/s connections. This is normaland does not indicate an error.


Configuration 14 (28)

4 Configuration4.1 Configuration Overview4.1.1 Data Exchange Settings

The data exchange options and subnetwork protocol settings must be configured beforecommunication can be set up. The configuration is created and downloaded to the AnybusCommunicator CAN IIoT using Anybus Configuration Manager - Communicator CAN.

See Anybus Configuration Manager - Communicator CAN, p. 19.

4.1.2 Network Communication SettingsTo be able to communicate over Ethernet the IIoT interface needs a valid TCP/IP networkconfiguration. TCP/IP settings can be configured from the IT network or locally using the IPconfigconfiguration tool.

TCP/IP settings can be set automatically from a DHCP or BootP server. If no DHCP server is found,the module will fall back on its current settings. If no current settings are available the modulewill halt and the status LED will indicate a network configuration error. The networkconfiguration may still be accessed using IPconfig.

See TCP/IP Configuration, p. 16.

4.1.3 IIoT ConfigurationThe MQTT and OPC UA data and communication options are configured using AnybusConfiguration Manager - IIoT and the web interface of the Anybus Communicator CAN IIoT.

See Anybus Configuration Manager - IIoT, p. 23 and Web Interface, p. 25



4.2 Basic TCP/IP ConceptsIP Address

The IP address is used to identify each node on a TCP/IP network. IP addresses are written asfour decimal integers (0–255) separated by dots, where each integer represents the binary valueof one byte of the IP address. This is known as dot-decimal notation.

Example: 10000000 00001010 00000010 00011110 is written as 128.10.2.30

The following IP addresses are reserved for special purposes and cannot be used:

0.n.n.n First byte zero — used for broadcast messages

127.n.n.n First byte 127 — used for loopback addresses to the local host

n.n.n.0 Last byte zero — identifies a whole network/subnet

n.n.n.255 Last byte 255 — used for broadcast messages

Subnet Mask

The IP address is divided into three parts: Net ID, Subnet ID and Host ID. A subnet mask is a 32-bit binary pattern, where a set bit allocates a bit for Network/Subnet ID, and a cleared bitallocates a bit for the Host ID. The subnet mask is usually written in dot-decimal notation.

Example: To make the IP address 128.10.2.30 belong to subnet 128.10.2, the subnetmask must be 255.255.255.0.

Default Gateway

For devices to be able to communicate over Ethernet they must either belong to the samesubnet or communicate via a gateway or router.

A gateway or router routes communication between networks, i.e. it enables the nodes on onenetwork to access the nodes on another. The default gateway address in the TCP/IP settings ofyour product specifies the IP address of the gateway or router on the local network.



4.3 TCP/IP Configuration4.3.1 Installing the IPconfig Utility

IPconfig is a Windows-based tool for configuration of TCP/IP settings in HMS devices. The toolwill detect all compatible and active HMS devices on the local network.

1. Download IPconfig from www.anybus.com/support.

2. Unpack the contents of the zip archive and run the installer program.

4.3.2 Scanning for Connected DevicesWhen IPconfig is started it will automatically scan all available local networks for HMS devices.Detected devices will be listed in the main window. To refresh the list, click on Scan.

Fig. 8 IPconfig main window

IP IP address of the deviceSN Subnet maskGW Default gateway

DHCP Automatically managed IP configuration

Version Firmware versionType Product name

MAC Ethernet MAC address (System ID)




4.3.3 Ethernet ConfigurationTo change the IP settings for a device, double-click on the entry in the main window or right-clickon it and select Configuration.

Fig. 9 Ethernet configuration

Enter static IP settings as required, or select DHCP if using dynamic IP addressing.

Do not enable DHCP if there is no DHCP server available on the network.

You can add a name for the device in the Hostname field. Only characters a–z, A–Z, 0–9 and _(underscore) are allowed.

The default password for changing IP settings is blank (no password). If a password has been setfor the device you must enter it to be able to change the settings.

To set a new password, check the Change password box and enter the current password in thePassword field, then enter the new password in the New password field.

For security reasons the default password should always be changed.

Click on Set to save the new settings. The device will reboot automatically.



4.3.4 IPconfig SettingsAdditional settings for IPconfig can be accessed by clicking on Settings.

Fig. 10 IPconfig settings

Network Interface

Check this option to select a specific network interface to use when scanning for devices from acomputer which has more than one interface. If this option is left unchecked, all availablenetworks will be scanned.

Internal DHCP Server

If a device has been set to use DHCP but there is no DHCP server on the network, the device maynot be detected by IPconfig. To recover access to the device an internal DHCP server in IPconfigcan be temporarily activated:

1. Click the checkbox for Internal DHCP Server, then click OK. IPconfig will automaticallyrefresh the scan and list the missing device in the main window.

2. Select the device and configure it to use static IP addressing instead of DHCP.

3. Disable the internal DHCP server.

Do not enable the internal DHCP server if there is already an active DHCP server on thenetwork.



4.4 Anybus Configuration Manager - Communicator CAN4.4.1 Basic Settings

The main window in Anybus Configuration Manager is divided into 4 parts:

Fig. 11 Anybus Configuration Manager - Communicator CAN

1. Menus and Toolbar

2. Parameter List

3. Information Window

4. Navigation Tree

Menus and Toolbar

The menus contain commands for creating and saving configurations and connecting to thegateway. Most menu commands can also be carried out by clicking on a button in the toolbar.

Parameter List

Lists the parameters or options related to the currently selected entry in the Navigation Tree.

Values can be selected from a dropdown menu or entered manually depending on parametertype. Values can be specified in either decimal or hexadecimal format.

Example: The decimal value 42 can also be entered as 0x2A.

Moving the mouse cursor over a parameter in this window will show a help text in theInformation Window that explains how to use the parameter.

Information Window

Displays a help text describing the currently selected parameter setting.



Navigation Tree

Presents the different parts of the configuration in a tree structure.

Communicator (top level)

Additional settings for the Anybus Communicator CAN gateway.

Fig. 12 Communicator settings

GeneralParameter Comment

Control/Status Word If enabled, the Control/Status Word will occupy the first two bytes of the Output/Inputareas of the memory.To avoid memory address collisions this parameter should be enabled before addingframes to the configuration.

Start-up Operation Mode Decides the start-up mode of the CAN subnetwork if the Control Word is enabled.

Transaction Live List If the Transaction Live List is enabled it is mapped from the beginning of the input areaor, if the Control/Status Word is enabled, after the Status Word. It is possible to mapfrom 8 to 128 transactions, in steps of 8. Each transaction is represented by a bit thattells the system whether the transaction is alive or not.

StatisticsParameter CommentCounters The receive counter and the transmit counter count successful CAN messages on the

subnetwork. If enabled, the counters can be mapped to the input data area. The firstfree address in the input data area is selected by default. The counters can be disabledand enabled separately.To avoid memory address collisions this parameter should be enabled before addingframes to the configuration.The messages are counted only if they have been configured in Anybus ConfigurationManager - Communicator CAN.

Receive Counter Address Enter the address in the input data area where the receive counter shall be mapped. Thereceive counter occupies 2 bytes.

Transmit Counter Address Enter the address in the input data area where the transmit counter shall be mapped.The transmit counter occupies 2 bytes.

Fatal EventParameter Values CommentAction Stay in Safe-State In case of a fatal software event, the Anybus Communicator

CAN will be locked in the safe state.Software Reset In case of a fatal software event, the software will be reset and

the Anybus Communicator CAN will be restarted.



Communicator : Project

Used to store project information such as project name, project creator, version and description.

Fig. 13 Project settings

Communicator : Network

The higher level network type must be selected here to create a valid configuration. Whichparameter settings are available depends on the selected network type.

Moving the mouse cursor over a parameter setting will show a help text in the informationwindow. Additional help may be found at www.anybus.com/support.

Fig. 14 Network settings (example)




Communicator : Subnetwork

Contains settings for the CAN subnetwork.

Fig. 15 Subnetwork settings

GeneralParameter Values CommentBit Rate 20 kbit/s

50 kbit/s100 kbit/s125 kbit/s200 kbit/s250 kbit/s500 kbit/s800 kbit/s1000 kbit/s

Select the bit rate on the CAN subnetwork.

Bus Off Action No ActionAutomatic Reset

Select what will happen to the CAN controller when the CANsubnetwork goes bus off.When the Control/Status Word is enabled this parameter willbe disabled (No Action).

11/29-bit CAN Identifier 11 bit29 bit

Select CAN identifier size on the subnetworkIf there are configured transactions when this parameter ischanged, the following will happen:

• A change from 11 bit to 29 bit identifier will cause theidentifier to be padded with zeroes up to 29 bits, keepingthe 11 bits at the same location.

• A change from 29 bit to 11 bit identifier will cause theupper 18 bits to be deleted and the lower 11 bits kept.This may cause faulty CAN identifiers.

Silence Time (ms) 0 - 65535 Default = 0 (disabled)The minimum time that must elapse between the end of amessage and the beginning of the next message. If a device onthe CAN subnetwork is slow and/or does not have a messagequeue, it may be necessary to enter a delay between themessages to ensure that they are handled correctly. The delayis set in milliseconds.

Clear Buffer in Error Passive Disabled/Enabled Disabled: All CAN frames that are not successfully transmittedwill be buffered. The size of the buffer is 255 frames. If thebuffer is full, new frames will be discarded.Enabled: While the CAN state is Error Passive, all CAN framesthat are not successfully transmitted will be discarded.The usual reason for Error Passive state is disconnection of theCAN cable.



4.5 Anybus Configuration Manager - IIoTThe Anybus Communicator CAN is configured using Anybus Configuration Manager - IIoT, whichcan be downloaded from www.anybus.com/support.

Fig. 16 Anybus Configuration Manager - IIoT

Setting up the IIoT tags

1. Select either OPC UA or MQTT as communication protocol.

For OPC UA you must also specify a Namespace URI. If this field is left empty a default valuewill be used.

2. Click on Add to add IIoT tags as required. The data types and addresses of the tags mustmatch the IO data mapping set up with Anybus Configuration Manager - Communicator CAN.

Fig. 17 Adding tags

3. Optionally, select File ► Save to save the current configuration project.

Note: The project file saves the current settings in Anybus Configuration Manager - IIoT and canbe used as a starting point when creating configurations. It cannot be used as a configuration fileby the Anybus Communicator CAN IIoT.

When you have finished setting up the IIoT tags you must generate a configuration and apply itto the Anybus Communicator CAN IIoT. This can be done directly from Anybus ConfigurationManager - IIoT or by saving a configuration file and using an external FTP client.




Applying the configuration from Anybus Configuration Manager - IIoT

1. Select File ► Generate and send....

Fig. 18 Sending the configuration

2. Enter the IP address and the FTP username and password for the Anybus CommunicatorCAN.

The default username is ABX and the password is FTPAccess.

3. Click on Send to transfer the configuration to the Anybus Communicator CAN.

When the transfer is finished, click on OK to close the confirmation dialog.

The X-gateway will apply the new configuration and restart automatically.

Generating a configuration file and applying it using an external FTP client

1. Select File ► Generate configuration....

2. Save the generated configuration file to your computer.

3. Open an FTP client and connect to the IP address of the Anybus Communicator CAN.

The default username is ABX and the password is FTPAccess.

4. Transfer the saved configuration file from your computer to the Anybus Communicator CAN.

5. Power cycle the X-gateway to apply the new configuration.



4.6 Web InterfaceThe web interface of the Anybus Communicator CAN IIoT provides additional configurationsettings and status information. The web interface is accessed by entering the IP address of theAnybus Communicator CAN IIoT in a web browser. The computer used for access must be in thesame Ethernet subnet as the Anybus Communicator CAN.

Overview

Fig. 19 Overview page

This page provides basic information about the Anybus Communicator CAN including the serialnumber and the installed firmware version.

Parameters

Fig. 20 Parameter page

This page shows the current data values for the configured IIoT tags.

Network Status

Fig. 21 Status page

This page shows the current network settings and communication status. This information ismainly intended for troubleshooting.



Network Configuration

Fig. 22 Configuration page

IP Configuration

TCP/IP network settings. These parameters can also be configured using IPconfig.

Ethernet Configuration

Port 1/2 10 HDX = 10 Mbit/s half duplex

10 FDX = 10 Mbit/s full duplex

100 HDX = 100 Mbit/s half duplex

100 FDX = 10 Mbit/s full duplex

Auto = Automatic mode (default)

MQTT Configuration

Broker URL The URL of the MQTT broker.

Client identifier The MQTT ClientID of the Anybus Communicator CAN IIoT.

Keep alive time (s) The time interval in seconds between the keep alive messages sent from the client tothe broker.

Broker username/password Authentication to send to the MQTT broker (if required).

Base topic The base topic name to use in MQTT messages.

Quality of service The MQTT QoS level to use.

OPC UA Configuration

TCP port The TCP port to use for OPC UA. Default = 4840.

Discovery server URL The URL of the OPC UA discovery server (required for timestamp information).


Technical Data 27 (28)

5 Technical Data5.1 General Specifications

Model name Anybus Communicator CAN IIoT

Order code AB7330

Dimensions (L x W x H) 120 x 75 x 27 mm

Weight 150 g

Operating temperature -25 to +55 °C (IEC 60068-2-1 and IEC 60068-2-2)

Storage temperature -40 to +85 °C (IEC 60068-2-1 and IEC 60068-2-2)

Humidity range 5–95 % RH, non-condensing (IEC 60068-2-30)

Power supply 24 V ±10 % DC regulated power source

Current consumption Typical: 100 mA @ 24 VDCMaximum: 250 mA @ 24 VDC

Galvanic isolation Yes, on both network sides

Mechanical rating IP20, NEMA rating 1

Mounting DIN rail (EN 50022)Network shield conductance via DIN rail

Certifications See datasheet at www.anybus.com/support

5.2 CAN InterfaceCAN specification CAN 1.0, 2.0A and 2.0B

Maximum baud rate 1 Mbit/s

CAN connector DE-9M

5.3 IIoT Interface

OPC UA functionality • Support for micro-embedded profile

• Supports Discovery Services

• Timestamp supported via discovery server

• User name and password authentication

• Supports DataChange Subscription

• Maximum 80 data point tags

(max. 2 clients with up to 40 tags per client)

MQTT functionality • MQTT client acting as publisher

• MQTT version 3.1.1 supported

• Json data encoding supported

• QoS 0-2 supported

• User name and password authentication

• Maximum 256 data point tags

Ethernet • 100 Mbit/s, full duplex (fixed)

• Dual port cut-through switch, RJ45 connectors



last page

© 2019 HMS Industrial NetworksBox 4126300 04 Halmstad, Sweden

[email protected] SCM-1202-116 1.0 en-US / 2019-02-13 / 11689

Documents

Anybus Communicator CAN