If more than 2 DI sensors on an ibaCMU‑S device are used, there are three optional proceedings possible for migrating to ibaDAQ. Be sure to save the current ibaCMC configuration before making any changes. Note down the DI-RPS sensors which are currently connected to ibaCMU-S, e.g. by means of a screenshot of the current configuration.

Option 1: Add another ibaMS16xDI‑24V module and rewire sensors

Prerequisite: At least one free slot is available on the backplane of ibaCMU-S.

Proceeding (before migration)

  1. Unlink the DI-RPS sensors, which are connected to the ibaCMU-S module.

    The first two sensors may remain connected to the ibaCMU-S if you plan to use the first two digital inputs on the ibaDAQ device for the same purpose.

  2. Continue the migration.

Proceeding (after migration)

  1. Add a hardware module ibaMS16xDI 24V to ibaDAQ in ibaCMC.

  2. Connect the digital sensors with the new module.

  3. Assemble the additional hardware module device and connect the digital sensors as configured in ibaCMC.

  4. Update the snapshot settings in ibaCMC to grant the correct recording of the sensors.

  5. Finally, load the configuration onto the ibaDAQ device.
Option 2: Keep first two DI-sensors on the module, get more speed information via TCP receive telegram from ibaPDA

In the following, it is assumed that ibaPDA is the data source of process data.

Prerequisites:

  • One license ibaPDA-Interface-Generic-TCP is enabled for both ibaDAQ and ibaPDA.

  • ibaDAQ and ibaPDA are connected via network.

Proceeding

  1. Configure or extend a TCP receive telegram by the required speed signals in ibaCMC.

  2. Replace the DI-RPS sensors in the component groups by TCP channels.

    Do not remove the DI-RPS sensors from the configuration in order to preserve the formerly recorded speed data.

  3. To make sure that the correct speed signal is used for the condition and for recording, update the snapshot settings in ibaCMC.

  4. Disconnect the DI-RPS sensors, which are supposed to be transferred to TCP telegrams, from the ibaCMU-S device.

  5. Connect the DI-RPS sensors, which are still needed, with the ibaDAQ.

  6. Configure the TCP telegram with the required data in ibaPDA.

  7. Continue the migration, see Migration from ibaCMU-S to ibaDAQ with migration wizard.
Option 3: Keep first two DI-sensors on the module, get speed information by process signal integration via an ibaPDA interface

Prerequisites:

  • An interface to an external system is available on ibaDAQ, which transmits the speed signals. This could be any of the available ibaPDA interfaces (e.g. OPC UA).

  • A license for the corresponding ibaPDA interface is enabled.

    Note: The license ibaCMS-One-Sensor already contains 2 OPC UA client interfaces, which can transmit process data from an ibaPDA system via its integrated OPC UA server.

  • All DI-RPS sensors, which are supposed to be replaced by process signals, are disconnected from ibaCMU-S. The first two sensors can remain connected for further use in ibaDAQ.

Proceeding (after migration)

  1. Configure a new process signal module in ibaCMC below ibaDAQ.

  2. Replace the DI-RPS sensors in the component groups by process signals.

  3. To make sure that the correct speed signal is used for the condition and for recording, update the snapshot settings in ibaCMC.

  4. Disconnect all DI-RPS sensors from the ibaCMU-S module and replace the module by the ibaDAQ module.

  5. Connect the DI-RPS sensors to be kept to the ibaDAQ.

  6. Configure a timebase of 50 ms in ibaPDA for the transmission of the speed signals via the integrated OPC UA server.

  7. Configure the OPC UA client on ibaDAQ and select the required signals from the OPC UA server.