Using embedded Anybus Communication modules in a Controller

Industrial controllers mostly need flexible communication interfaces with slave / adapter functionality.

In most industrial applications, a distributed controller is located on a machine site and connected via a fieldbus or industrial Ethernet network to the central automation system (PLC) / IPC). Controllers autonomously regulate a specific task such as position control, vibration control, temperature control or ventilation control. From the network point of view, controllers function as a slave / adapter on the network. In addition to the cyclic control loop data, they often support read and write access to the control parameters (upper and lower limits) or alarm values (over or under temperature). In dependency of the industry branch and cycle time requirements, many different types of industrial networks are used. The networks range from standard fieldbusses such as Profibus to building control systems such as Lonworks.

With the embedded Anybus communication modules, HMS provides ready-to-use connectivity solutions for all types of controllers. The embedded Anybus modules support fast cyclic I/O data exchange (used i.e to transfer set point values) as well as acyclic access to the controller parameters (i.e. temperature of pressure limits). Thanks to the well defined Anybus application software interface, the internal software of the controller can access the cyclic control data and acyclic parameter data in a standardized manner, independent of the selected industrial network.

HMS provides three families of embedded communication modules that fulfill the communication requirements of modern controller:

Anybus-CompactCom (Anybus-CC)
Plug-in communication modules contained in a robust plastic housing with a form factor similar to a compact flash card. Anybus-CC modules feature the latest Anybus technology combining high performance and low prices.
Read more


Credit card sized communication interfaces containing all hardware and software functions needed to build a powerful communication interface for medium and large controllers. Read more

Very small sized communication interfaces that fit into a standard DIL 32 socket. These tiny modules are tailor-made for small drives with limited requirements on performance and data size. Read more

Robot Controllers, a special case
Very specific requirements apply to a robot controller. An industrial robot is normally an integrated cell of a large automation system. The robot controller needs two communication systems, one “uplink” to a PLC and one “downlink” to its own I/O and local devices. Two types of network interfaces are normally required:

1. A network that connects the robot to a supervisory control system (PLC) The robot controller is one of many devices controlled by the PLC and the robot is normally as “slave” on this network. For this kind of communication interface, HMS recommends usage of Anybus-S or Anybus-CC communication modules.

2. The robot cell itself is a small automation system with I/O, feeders, conveyors etc. These devices need to be controlled by the robot itself and the robot controller is normally a “master” in this network. With the range of Anybus-M master/scanner interfaces, HMS provides a range of powerful master interfaces that fulfill the communication requirements of this application.

Regardless which specific Anybus module in used, device manufacturers benefit from the principal advantages of the Anybus technology with up to 70% less development efforts, fast time-to-market, easier certification and continuous technology maintenance by HMS. Read more about the benefits of the Anybus technology. Read more