Date: Fri, 29 Mar 2024 09:46:06 +0100 (CET) Message-ID: <2068713977.111596.1711701966188@srvdoc.doc.ipesoft.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_111595_1796705806.1711701966187" ------=_Part_111595_1796705806.1711701966187 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Supported device types and versions
Communication line configuration
Communication =
station configuration
I/O tag configuration
Literature
Changes and modifications
Document revisions
The protocol supports data transmission from/to the SCI (Supervisory Com= puter Interface) interface of the Fisher-Rosemount RS3 control system.
For the correct communication of a Rosemount RS3 SCI device, these SCI p= arameters must be set:
Table 1
Parameter | Value |
---|---|
Comm Port Baud Rate | 9.2 kbs or 38.4 kbs |
Checksum | Yes |
Data Bits and Parity | 8N |
XON/XOFF Control | Off |
EIA Option | None |
Reply Header String in Hex format | 00 00 00 00 |
Reply Trailer String in Hex format | 00 00 00 00 |
Mode | Async Length LSB |
Data Format | IEEE |
TX Gap | 100 ms |
SCI allows configuring acquisition of 1500 system values into its table = (Table entry) with different parameters (Scaling, Update interval). Table e= ntries are allocated to individual I/O tags starting with the First= index value. The station represents a logical set of tags wi= th the same Update Interval parameter. Update In= terval is a time period with which the SCI acquires new values from the Ros= emount S3 system.
Note: As the SCI configuration allows to define the par= ameter Update Interval up to 300 seconds (5 min.), this setting is used for= station polling periods of 15 and 60 minutes.
The following station protocol parameters can be defined:
Table 2
Keyword | Full name | Meaning | Unit | Default value |
---|---|---|---|---|
RC
|
Retry Count | Request repetition count in case of a communicat= ion error. | - | 2 |
RT
|
Retry Timeout | The delay between request repetitions in case of= a communication error. | ms | 200 |
WFT
|
Wait First Timeout | The delay after transmitting the request and bef= ore reading the response. | ms | 60 |
WT
|
Wait Timeout | Delay between response readings until its finali= zation. | ms | 200 |
MWR
|
Max Wait Retry | Repetition count of response readings until its = finalization. | - | 15 |
DEBUG
|
Debug Mode | If the value of the parameter is YES, the tables=
on the side of the SCI device are not configured during communication (del=
etion from tables + initialization of individual points). The parameter is used only for debugging purposes.= td> | YES/NO | NO |
SW
|
Send Weak | If the value is YES - if a new I/O tag value wit=
h an error attribute is acquired, the error number will be sent to the I/O =
tag value and the value is marked by the WEAK attribute. It is used for |
YES/NO | NO |
A string containing the protocol parameters is being defined as follows:=
Keyword=3Dvalue;Keyword=3Dvalue; ...
Example:
SW=3DYES;WFT=3D300;
If a keyword with an invalid value in the initialization string is used,= the corresponding default value according to the table 2 will be used.
Possible I/O tag types: Ai, Ao, Di, Dout
Communication supports value acquisition of I/O tags of the following ty= pes:
Further, it allows to write new values of I/O tags of the following type= s:
Note:
-
Related pages: