http://<IP-of-iCSmini>/api/logout/$session-ID TRUE / FALSE
http://<IP-of-iCSmini>/api/getItem/$apikey/$line/$address/$channel/$item JSON Object Returns state of a specific item
of a hardware path
$line, $address, $channel and
$item can be set by wildcard '*'
http://<IP-of-iCSmini>/api/setItem/$apikey/$line/$address/$channel/$item/
$value/[$unit]
TRUE / FALSE Sets state of a specific item of a
hardware path
$line, $address, $channel can
be set by wildcard '*'
http://<IP-of-iCSmini>/api/getUpdate/$apikey/ JSON Object returns all changes collected by
iCSservice since last getUpdate
call for this client session
Use “*” as wildcard, e.g. to set or get items on multiple channels at once.
Use “null” as empty set identifier, e.g. to obtain module specific objects without channel declaration.
EXAMPLES
http://192.168.1.1/api/getItem/123456-321/0/ 1/0/Status.voltageMeasure Returns voltage value, unit and timestamp of
channel 0 of module with address 1 of line 0
http://192.168.1.1/api/ s etItem/123456-321/0/ 1/*/Control.voltageSet/1/kV Set set voltages of all channels of module 1 in
line 0 to 1,000 Volt
http://192.168.1.1/api/ s etItem/123456-321/0/ null/null/Control.power/1 Switch controller of line 0 (master) on
EPICS
For the use of iseg hardware with Experimental Physics and Industrial Control System (EPICS) the iCS comes with a preinstalled
integrated Input-Output-Controller (IOC). This service can be enabled or disabled using the switch „enable EPICS input / output
controller“. To keep things straight-forward the iCS can generate IOC configuration files (.db and .sub), using the current hardware
configuration. Both files can be downloaded to the local computer, be edited manually, e.g. with a text editor and be uploaded
again. This gives a quick start to run an IOC out of the box. To get an overview on all available process variables (PV), which are
generated at the start of IOC, the PV list can be downloaded using the respective button. The IOC script combines a process
variable definition file (.db) with a substitution file (.sub), which contains hardware setup information and placeholders to create
all accessable process-variables at runtime.
File Description Sample content (extraction)
iseg_epics.db Database file with definitions
of PV
#############################
# ### Crate item values ### #
#############################
record( mbbiDirect, "ISEG:${CONTROLLER_SN}:${CAN_LINE}:$
{DEVICE_ID}:StatusLow" ) {
field( DESC, "Lower 16 bit of module status register" )
field( DTYP, "isegHAL" )
field( INP, "@${CAN_LINE}.${DEVICE_ID}.Status" )
field( NOBT, "16" )
field( SHFT, "0" )
field( TSE, "-2" )
}
...
iseg_epics.sub Substitution file contains a
pattern that will be
substituted by the following
lines for each corresponding
channel
{CONTROLLER_SN,CAN_LINE,DEVICE_ID,MODULE_ID,CHANNEL_ID}
{5230003,0,1000,0,0}
{5230003,0,1000,0,1}
{5230003,0,1000,0,2}
...
iseg_epics.pv Text file with list of process
variables generated
ISEG:5230003:0:0:0:CurrentMeasure
ISEG:5230003:0:0:0:CurrentNominal
To Next Page
Loading...
Need help?
General
