This is historical information of device classes implemented in Eurotherm2408 device server.

Use this link to find the valid information.

Development status: Released
Information status: New

Contact:



Class Description


Families: Instrumentation

Key words:

Platform: Unix Like

Language: Cpp

License:

Contact:

Hardware


Manufacturer: none

Bus: Not Applicable

Class interface


Attributes:

Name Description
TemperatureScalar: DevDouble The current temperature
SetpointScalar: DevDouble The current temperature setpoint
ManualScalar: DevBoolean Manual mode (true = on, false = off)
ProgramStateScalar: DevString Program state. Possible values: reset / run / hold / complete
CurrentProgramScalar: DevUShort Number of the currently running program.
CurrentSegmentScalar: DevUShort Number of the currently running segment.
RemainingProgramTimeScalar: DevUShort Remaining program time in hours
RemainingSegmentTimeScalar: DevUShort Remaining segment time in seconds
SegmentTypeScalar: DevString The type of segment currently running.
ProgramDirScalar: DevString Path to directory containing controller programs
MaxProgramsScalar: DevUShort Maximum number of programs this controller can store.
AllowedStatesScalar: DevUChar Bitmask to set which bits of the controller status byte should not set the device state to ALARM. The status byte bit meaning is: 0: ALARM1 1: ALARM2 2: ALARM3 3: ALARM4 4: MANUAL MODE 5: SENSOR FAILURE 6: LOOP BREAK 7: HEATER FAILURE So to e.g. not cause an alarm state on ALARM1 and MANUAL MODE set the attribute to 17 ( = binary 00010001, bits 0 and 4 => 1).
HoldBackScalar: DevBoolean Report / set holdback state. true = holdback enabled false = holdback disabled
OutputLevelScalar: DevDouble
OutputLevelMaxScalar: DevDouble
OutputLevelMinScalar: DevDouble

Commands:

Name Description
StateInput: DevVoid
Output: State
State Code
This command gets the device state (stored in its <i>device_state</i> data member) and returns it to the caller.
StatusInput: DevVoid
Output: ConstDevString
Status description
This command gets the device status (stored in its <i>device_status</i> data member) and returns it to the caller.
StartProgramInput: DevUShort
program number
Output: DevVoid
Start a program stored in the controller. The max. program number depends on the hardware, can be 0, 1, 4 or 20. Check with reading attribute MaxPrograms.
StopProgramInput: DevVoid
Output: DevVoid
Stop currently running program
HoldProgramInput: DevVoid
Output: DevVoid
Hold currently running program
LoadProgramInput: DevString
path to program file, either absolute or relative to attribute ProgramDir
Output: DevVoid
Loads a program into controller memory
DeleteProgramInput: DevUShort
Program number
Output: DevVoid
removes program from controller memory

Pipes:

Properties:

Name Description
HostNameDevString Hostname or IP address
PortNumberDevString TCP Port Number.
DeviceAddressDevShort Address of device (adjusted at hardware)
SimulationModeDevShort
LogicOpsDevBoolean true, if the hardware supports logical operations
ConnectTypeDevString connection type, either `serial` or `net`
DeviceFileDevString tty device file name
BaudRateDevLong tty device baud rate

23 Feb 2017, Piotr Goryl
Updated:
The device class has been updated.
You can see previous version here .



19 Jan 2017, Piotr Goryl
Updated:
The device server has been updated.
You are looking at this version now.



2 Jan 2017, Piotr Goryl
Created:
The device server has been added to catalogue.
Added by:pgoryl2 on:19 Jan 2017, 10:54 a.m.