Porovnávané verzie

Stará verzia 1

changes.mady.by.user D2000 Dev Team

Uložené

porovnané s

Nová verzia Aktuálny

changes.mady.by.user D2000 Dev Team

Uložené

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Siemens SAPHIR is used to configure and monitor the regulators controllers of Saphir and Climatix product lines produced by Siemens. Supported regulatorscontrollers: Saphir ACX32/ACX34 (via TCP/IP as well as via serial interface) and Climatix POL63x (specifically POL638 via TCP/IP).

...

  • 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 The 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 the Saphir ACX32 regulator ACX32 controller via its serial port.

Kotva
komunikacna_stanica
komunikacna_stanica
Communication station configuration

...

  • Communication protocol "Siemens SAPHIR".


Station protocol parameters

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

Table 1

ParameterMeaningUnitDefault value
Kotva
td
td
Full Debug
Logging
is enhanced with listings that enables fast error detection.  
of detailed debug information about communication in the line log.
NO
Kotva
tod
tod
Type of Device
Type of used regulator.
 

ACX32
Kotva
rc
rc
Retry Count
Maximum count of
response retries. 
request retries. If no response returns after a request had been sent, the station's status will change to a communication error.
2
Kotva
rt
rt
Retry Timeout
Timeout before
retrying
resending a request
, if no response came
if no response has been received.s0,1
Kotva
wft
wft
Wait First Timeout
Timeout between sending a
The delay after sending the request and
first
before reading
of
the response.s0,1
Kotva
wt
wt
Wait Timeout
Timeout
The delay between
reading
the
responses
response readings.s0,1
Kotva
mwr
mwr
Max. Wait Retry
Maximum count
The maximum number of retries of
reading
the response reading.-20

Kotva
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 a particular element in a given data block.

Image Modified

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

"Data block" is a type of data block located on a specified base address. Current The 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


Each data block is an N-tuple (different for every type of data block) of primitive data types. Supported primitive types:

...

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

Info
titleRelated pages:

Communication protocols

...