Hottinger Baldwin Messtechnik (HBM)

Overview

The HBM company provides hardware (h/w) and software (s/w) solutions for configuring and reading out sensors of various types.

Sensors are connected to controller boxes of varying capability with respect to number and type of the latter. The controller boxes themselves are typically connected to LAN via ethernet for configuration and data acquisition (DAQ).

../../_images/HBM-MX410B.jpg

Front side of the HBM MX410B controller box with a D-Sub adapter connected to the second input channel.

The Cybus Connectware driver hbmdaq maps the HBM specific DAQ protocol into the standard industry protocol (MQTT).

The configuration interface is not interfaced.

Commissioning file specifics

A typical commissioning file for the HBM protocol looks like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
# ----------------------------------------------------------------------------#
# Commissioning File
# ----------------------------------------------------------------------------#
# Manufacturer: Hottinger Baldwin Messtechnik
# Device: 410B
# Copyright: Cybus GmbH (2017)
# Contact: support@cybus.io
# ----------------------------------------------------------------------------#
# Source Interface Definition - HBM DAQ Streaming
# ----------------------------------------------------------------------------#
source:
  driver: hbmdaq
  connection:
    protocol: hbmdaq
    host: {{IP address}}
  defaults:
    operation: subscribe
# ----------------------------------------------------------------------------#
# Target Interface Definition - MQTT (Cybus Connectware Broker)
# ----------------------------------------------------------------------------#
target:
  driver: mqtt
  defaults:
    operation: write
    topicPrefix: io/cybus/hbm
# ----------------------------------------------------------------------------#
# Mappings: The HBM Box has a set of default signals for each connector
# and may additionally have user-defined signals
# ----------------------------------------------------------------------------#
mappings:
- source:
    signal: AnalogIn_Connector1.Signal1
  target:
    topic: analog1/signal1
- source:
    signal: AnalogIn_Connector2.Signal1
  target:
    topic: analog2/signal1

The HBM controller boxes provide standardized signal names for each available channel. The general structure is:

AnalogIn_Connector<ChannelId>.Signal<SignalId>

Typically each channel has two signals such that for a MX410B controller box with 4 channels we have 8 signals available in total:

  • AnalogIn_Connector1.Signal1
  • AnalogIn_Connector1.Signal2
  • AnalogIn_Connector2.Signal1
  • AnalogIn_Connector2.Signal2
  • AnalogIn_Connector3.Signal1
  • AnalogIn_Connector3.Signal2
  • AnalogIn_Connector4.Signal1
  • AnalogIn_Connector4.Signal2

Using the windows based (HBM-MXAssistant) configuration interface, it is possible to create virtual channels with custom chosen names. Hence, those won’t follow the regular structure and must be added specifically.

Important

The HBM DAQ interface is only able to provide data. Writing to this interface is not foreseen.

It is hence advisory to use the default operation subscribe during the source definition and the default operation write during target definition in the commissioning file (see lines 16-17 and 23-24 of the commissioning file example).

Warning

As data is streamed out in a scheduled push fashion, proper update rates should be configured using the MXAssistant tool.

../../_images/hbm-datarate-adjustment.png

Screenshot showing the data-rate configuration panel.

The HBM DAQ device mapping is resilient against disconnects and will automatically reconnect once possible and continue streaming out data.