Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Communication line category: TCP/IP, TCP/IP-TCP Redundant
    Note: a reserved TCP port 4242 is usually used, but any other port can be configured, depending on the settings of communicating device. Line number is not used, it can be set e.g. to 1.
  • Communication line category: Serial and SerialOverUDP Device Redundant (serial communication)
    Note: serial communication was tested only with Saphir ACX32 regulator via its serial port.

Anchor
komunikacna_stanica
komunikacna_stanica
Communication station configuration

...

  • Communication protocol "Siemens SAPHIR".


Station protocol parameters

Dialog window for station configuration - Protocol parameters.
They influence some optional parameters of protocol. Following line protocol parameters can be entered:

Table 1

ParameterMeaningUnitDefault value
Anchor
td
td
Full Debug
Logging is enhanced with listings that enables fast error detection.
 

NO
Anchor
tod
tod
Type of Device
Type of used regulator.
 

ACX32
Anchor
rc
rc
Retry Count
Maximum
count
number of
response
request retries in case of communication error.
 

2
Anchor
rt
rt
Retry Timeout
Timeout
A delay before
retrying
resending a request
, if no response came
in case of communication error.s0,1
Anchor
wft
wft
Wait First Timeout
Timeout between sending a request and first reading of a response.s0,1
Anchor
wt
wt
Wait Timeout
Timeout
Delay between reading the responses.s0,1
Anchor
mwr
mwr
Max. Wait Retry
Maximum
count
number of retries of reading the response.-20

Anchor
merany_bod
merany_bod
I/O tag configuration

...

Possible value types: Ai, Ao, Ci, Co, Di, Dout, TxtI, TxtO, TiA, TiR.


I/O tag address

In Siemens Saphir the I/O tag address is defined as a combination of "Base address", "Data block" and particular element in given data block.

Image Modified

"Base address" is 32-bit number that uses hexadecimal format.

"Data block" is a type of data block located on specified base address. Current implementation supports these data blocks:

  • Message
  • MessageEx
  • SetPointReal
  • SetPointEnum
  • LoopSetPoint
  • MeasureEx
  • SystemClock
  • Diagnostic
  • SwitchCommand
  • LoopController
  • PositioningCommand
  • MBusCounter
  • Counter
  • AlarmList
  • AlarmEntry
  • RCC_Config
  • UnitConfig
  • TimePlanEnumV2_Day
  • TimePlanEnumV2_Week
  • HeatingCurve
  • aoAlarm
  • aoAlarmEntry
  • aoDiagnostic
  • aoSetptValue
  • aoCurveCalc
  • aoAnalogInput
  • aoBinaryInput
  • aoMultistateValue
  • aoLoopController
  • aoAnalogValue
  • aoScheduleWord
  • aoScheduleDayWord
  • PosCommandEx
  • DeviceGroup
  • aoDevice

...

  • Ver. 1.0 - May 28, 2015 - creation of document
  • Ver. 1.1 - July 2, 2015 - implementation of data blocks DeviceGroup and aoDevice

Info
titleRelated pages:

Communication protocols

...