Average: 0
Rating Count: 0

Development status: Released, Release: release_1_1_7
Information status: Updated
Repository: http://svn.code.sf.net/p/tango-ds/code/DeviceClasses/SampleEnvironment/CellCouette

Class Description

this device is used to control a specific sample environnement called Cell Couette.

This equipement is consisted of 3 parts: - the motor controller - the torque controller - temperature controller

the multiplexage is ensured by a multipoint link RS-485. but sometime theses controllers can be in concurrency. To improve the communication, THE STATE COMMAND MUST BE POLLED BY THE USER (under JIVE application). The other attributes which read on the hardware are polled by default.

Moreover, to ensure the communication , the elapsed time between 2 RS232 requests is at least 500 ms

The device communicates with controllers by using the Serial Device (RS232 communication) the communication parameters of the associated proxy device server called Serial are: Baudrate = 19200; Charlength = 8; Newline = none; Serialline = COMx; stopbits = 0; Timeout = 2000

3 modes are available: CONTINUOUS: the rotor rotates continuously OSCILLATION: the rotor oscilates RAMP: the rotor rotates continuously by speed steady period

Families: SampleEnvironment

Key words:

Language: Cpp



Class interface


Name Description
viscosityScalar: DevDouble
motorResolutionScalar: DevUShort
temperatureScalar: DevDouble
stressScalar: DevDouble
torqueScalar: DevDouble
cellHeightScalar: DevDouble
weightScalar: DevDouble
weightOffsetScalar: DevDouble
speedMaxRampScalar: DevLong
timeRampScalar: DevDouble
deformationScalar: DevDouble
frequencyScalar: DevDouble
halfAngularAmplitudeScalar: DevLong
speedScalar: DevDouble
isPositiveRotationScalar: DevBoolean
speedMaxScalar: DevDouble
speedUnityScalar: DevUShort
positionScalar: DevDouble
positionUnityScalar: DevUShort
cellGapScalar: DevDouble
cellRadiusScalar: DevDouble
modeScalar: DevUShort


Name Description
GetMotorStateInput: DevVoid
Output: DevString
return a message which inform you on the motor state
GetMotorParamInput: DevVoid
Output: DevString
get motor parameters
SetMotorParamInput: DevVoid
Output: DevVoid
Once you have written new values of speedMax, motorResolution, timeRamp attributes you must call setMotorParam(), thus new motor parameters are sent to the motorController
SendCommandInput: DevString
Output: DevString
send a specifc command to the specified controller. You must specify the controller adress in the string to send. adress list: 15: motor controller 03: temperature controller 02: torque controller ex: "15QX" where: 15 : the adress of the motor controller (2 bytes) QX: is the command (N bytes)
PowerOFFInput: DevVoid
Output: DevVoid
cut the motor power
StopInput: DevVoid
Output: DevVoid
stop the motor motion
StartInput: DevVoid
Output: DevVoid
start the motor motion according to the operating mode selected (either CONTINUOUS or OSCILLATIONS) - CONTINOUS MODE: this is the write part of speed attribute which define the rotor speed once you push on start comand - OSCILLATIONS MODE: execute a sequence memorized in the controller (already programmed in the firmware)
StatusInput: DevVoid
Output: DevString
This command gets the device status (stored in its device_status data member) and returns it to the caller.
StateInput: DevVoid
Output: State
This command gets the device state (stored in its device_state data member) and returns it to the caller.
ResetInput: DevVoid
Output: DevVoid
the rotor returns to the default state (note that the encoder position is set to 0)



Name Description
TorqueCalibrationCoefficientDevDouble TorqueCalibrationCoefficient
SerialProxyNameDevString name of the serial device proxy

Please log in to comment.

20 Apr 2017, Piotr Goryl
The device class has been updated.
You can see previous version here .

23 Feb 2017, Piotr Goryl
The device class has been added to catalogue.
Added by:pgoryl2 on:23 Feb 2017, 12:10 p.m.