ibaBM-DDCS can access the service channel (CH3) of the ABB drives and query parameters there, independent from a communication connection to a controller. ibaBM-DDCS acts here as master and reads the current parameter values of the drives.

ibaBM-DDCS is directly connected to the CH3 port of a drive or to the master port of the NDBU-95, which is connected to the drives (CH3).

Note
	The parameter channel is only for acquiring supplementary information from drives or slow values, e.g. temperatures. We recommend acquiring data via the data set channel for typical application.

Note

Since every parameter is requested via handshake (request – response) by the drive, the access cycle depends directly on the number of requested values. Typical request requires approx. 2ms per analog value and approx. 2 ms per 16 digital bits. Request times become very high when many drives are connected. In order to improve this behavior, iba recommends using several ibaBM-DDCS devices, see tip in chapter Time response.

The desired Parameter are selected with ibaPDA as follows:

• Node number (drive)

• Parameter group

• Parameter number

Like in DriveWindow, the parameters can be selected in ibaPDA with a symbolic browser, where the user can see the node names, the parameter groups and the parameters as text.

If DriveWindow and ibaPDA shall be operated in parallel, DriveWindow is connected to the X34 (RX/TX) port of ibaBM-DDCS. The accesses to the drives are looped through ibaBM-DDCS. In contrast to DriveWindow, ibaPDA can only read the parameters.

ibaPDA only supports the acquisition of analog parameter values in 32-bit IEEE-Float format and digital parameter values.

Note
	Analog parameters in other data formats, such as DINT, are displayed incorrectly in ibaPDA.

When there is only one drive, ibaBM-DDCS can be connected directly to the CH3 port (service channel) of the drive. When there are several drives, the communication can be established using a NDBU-95 in star or ring topology.