Roche Urisys 1100 Urine Analyzer

US Supplement

US Supplement The contents of this manual, including all graphics and photographs, are the property of Roche Diagnostics. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Roche Diagnostics. Roche Diagnostics has made every reasonable effort to ensure that all the information contained in this manual is correct at the time of printing. However, Roche Diagnostics reserves the right to make any changes changes necessary without notice as part of ongoing product development. The US Supplement is intended for the US Market only.

US Supplement Revision History Revisions to Revisions to this documen documentt are provide provided d by Roche Roche Diagno Diagnostics stics when neces necessary sary.. No part part of this this may be reproduced in any form or by any means without prior written consent.

Publication Reference Number

2653-00-1208 version 1.0

Date

December 2008

Revision purpose

entire document

document docum ent

Technical Product Information & Serial Interface Description Description of Urisys 1100 Software Version 5.x & 6.x Contents 1 Interfac Int erfac e Descr ipti ip ti on ............... ...................... ............... ............... ............... ................ ............... ............... ............... ............... ............... ............... .............. ............. .......... ...2

1.1 Serial Connection ....................................................... .......................... ............................. .............................. ............................2 1.2 Barcode Barcode Reader, AT/PC Keyboard Keyboard port .......................................................... ........................... ............................... .....................3 .....................3 1.3 Barcode Reader....................................................................................................................3 2 Host Interf ace Descrip tio n, Unidir ectio nal and Bid irect ion al......... al............. ....... ....... ........ ........ ....... ....... ........ ....... ....... ....... ...4 4

2.1 Introduction ............................. .............................. ............................. ...................................4 2.1.1 Document Purpose 4 2.1.2 Document Conventions 4 2.2 Analyzer overview.................................................................................................................4 2.2.1 Analyzer Description 4 2.2.2 Operation Modes 4 2.3 Protocols Protocols Bidirectional Bidirectional and and Unidirectional Unidirectional .................................................... ........................ ............................ ........................5 ........................5 2.3.1 Bidirectional case: 5 2.3.2 Timing and Handshaking 6 2.4 Results Report Structure .............................. ............................. .............................. .............8 2.5 Interface Parameter ....................................................... ......................... .............................. ............................. ........................10 10 2.6 Checksum Calculation......................... Calculation ....................................................... .............................. ............................. ....................11 11 2.7 Unidir Unidir sample outputs byte-to-byte ............................. ............................. ...........................14 ...........................14 3 ASTM pr otoc ot oc ol ............... ....................... ............... ............... ............... ............... ................ ............... ............... ............... ............... ............... ............... .............. ............. .......... ...17

3.1 General ............................ .............................. ............................. ........................................17 17 3.2 Sending normal measurement data....................................................................................19 data....................................................................................19 3.3 Requesting operator ID list download.................................................................................20 download.................................................................................20 3.4 Operator identifier list download ........................................................ ........................... ............................. .............................. ...21 21 3.5 Sending LOG data ........................................................ ........................... ............................. .............................. ........................22 22 3.6 Abbreviations in result tables..............................................................................................23 tables..............................................................................................23 3.7 Parameter Parameter names and codes (RNN) ............................ .............................. ........................25 ........................25

Technical Product Information & Serial Interface Description Description of Urisys 1100 Software Version 5.x & 6.x

1 Interface Description 1.1 Serial Connection At the rear, URISYS 1100 Urine Analyzer has has a serial interface connector, through which it can be connected to a PC or central host computer. Upon request, Roche Diagnostics can supply a suitable standard data cable (REF 11 906 186 001) . The connected PC must satisfy the requirements with regard to electrical safety listed in EN 60950. The interface can be used for unidir ectional, bidirectional or ASTM communication, selectable via the menu. When the interface is set for unidirectional communication, the data are sent as an ASCII file and can be received via a terminal program. There is not any control of connection. In bidirectional and ASTM mode, the device waits for defined messages from the host, checking the connection. In bidirectional mode there can be two Patient ID lengths. The entered Patient ID appears in the URISYS 1100 Urine Analyzer display window and is also printed and/or sent to the PC/Host with the test results. If bidirectional communication with a PC or host computer has been selected, the maximum length of the Patient ID used (either 10 or 13 characters) must be preprogrammed via the display message “INTERFACE: BIDIR” and the function “10/13” to ensure that the correct data is sent.


1.2 1.2 Barc ode Reader, Reader, AT/PC T/PC Keyboard por t Operator IDs and corresponding passwords, Sample or Patient IDs I Ds (to each sample sequence number number displayed on the LCD), can be entered entered either via a barcode reader (see recommended reader) or via an AT/PC keyboard (e.g., the Reflotron keyboard from Roche Diagnostics). Power is supplied by the barcode reader interface. Interface specification: 5-pin DIN socket, female Pin out:

1 2 3

4 5

clock data n/c GND +5V

1.3 1.3 Barc ode Reader Reader Barcode Readers suitable for use with URISYS 1100 Urine Analyzer with SW Version 5.0 and above must meet the t he following specifications: - Radio frequency interface class B according to EN 61326-1 - Electromagnetic interference immunity requirements for industrial locations according to EN 61326-1


2 Host Host Interface Descript Descript ion, ion , Unid Unidirectio irectio nal and Bid irection al 2.1 Introduction 2.1.1 Document Purpose

This document provides the specifications for data transmission of results from a URISYS 1100 Urine Analyzer to an external laboratory host computer via an asynchronous serial connection. This document defines the so called Unidirectional and Bidirectional type connections. 2.1. 2.1.2 2 Document Conv ention s

All example data streams are represented represented as follows: STX ; E

1234567001 ETX 99

CR

Space characters (ASCII 32) are represented by the symbol. All ASCII values are represented in decimal base. STX, ETX, and CR are the only control characters used, and will be represented by standard standard acronyms, as shown above. above. Each field is contained within a box.


2.3 2.3 Protocols Bidirectional and Unidirectional Overview

According to setting, the interface is a unidirectional unidirectional or bidirectional serial interface. All communications originate at the analyzer. analyzer. When using of bidirectional communication the host needs to: Send a packet (MOR) to tell the analyzer whether it is ready to receive when the analyzer requests attention. Send a packet (MOR) to tell the analyzer that the last result packet was good and please send another. Send a packet (REP) to tell the analyzer that the last received packet had an error, so please send it again. Handle two possible Patient ID lengths – Pat.ID can be 10 or 13 characters in length. 2.3. 2.3.1 1 Bi-dir ection al case: Packet Types

The URISYS 1100 Urine Analyzer uses different packets to determine the operation of the host interface and transfer results. The types of packets are:


2.3. 2.3.2 2 Timing and Handshaking Description

The URISYS 1100 Urine Analyzer always acts as the “master” in communicating with the host. As the master, the URISYS 1100 Urine Analyzer Analyzer always always initiates conversations. The following diagrams and tables describe normal and abnormal communication exchanges. Normal Operation

After a series of strips are processed, the operator operator can send results to the host. The following diagram and table shows the t he sequence of events:

Max 15 seconds

1 Urisys1100

3 SPE + Data1

SPM

Max 15 seconds

Max 15 seconds

MOR

MOR

2

4

5

7

SPE + Data2

END

MOR

Host

Normal Handshaking

6


Ab no r mal Oper ati on

After a series of strips are processed, the operator operator can send them to the host. The following diagram and table shows the sequence of events when trouble occurs, and only one sample is being sent. Max 15 seconds

1 Urisys1100

Max 15 seconds

3 SPE + Data1

SP M

MOR

REP

2

4

Max 15 seconds

5

7

SPE + Data1

EN D

MOR

Host

6

Ab no rm al H an ds ha kin g

Event  

Description

The URISYS 1100 Urine Analyzer sends the SPM message to the host, requesting permission to send results. The host responds with the MOR message, giving the URISYS 1100 Urine Analyzer permission permission to send a result. result. The host must respond respond within 15


2.4 2.4 Results Results Repor Repor t Stru ctu re The results packet has a structure as shown below: Units Settings ConvenSI tional + + Arbitrary Ar bi tr ary Example 1 Example 2

Start Stop Len

Content

Comment

1 2 3 4 5

1 2 3 4 17

1 1 1 1 13

STX ; E Space Chars

Start of Text (ASCII 02) STX Frame ID (ASCII 59) ; Function Code (ASCII 69) E

18 19 24 25

18 23 24 26

1 5 1 2

Space nnnnn Space nn

27 28 30 31 33 34 36 37 39 40

27 29 30 32 33 35 36 38 39 41

1 2 1 2 1 2 1 2 1 2

42

46

5

Sample ID

Example 3

STX ; E

5462145698 54621456980 546214569801 012 12 2

Sequence Number

Measurement Day of Month Separator . (ASCII 46) nn Measurement Month Separator . (ASCII 46) nn Year Space nn Measurement Hour Separator : (ASCII 58) nn Measurement Minute Space SG Specific Gravity Test Name nnnnn Specific Gravity Result

STX ; E

Ar bi tr ary

1

1

1

12

12

12

. 01 . 98

. 01 . 98

. 01 . 98

11 : 58

11 : 58

11 : 58

SG

SG

SG

1.020

1.020

Technical Product Information & Serial Interface Description Description of Urisys 1100 Software Version 5.x & 6.x 170 175 176 179 190 195 196 199 210 215 216 221 222

174 175 178 189 194 195 198 209 214 215 220 221 233

5 1 3 11 5 1 3 11 5 1 5 1 12

Chars Space BIL Chars Chars Space BLD Chars Chars Space Chars Space Chars

234 235 236 237 239

234 235 236 238 239

1 1 1 2 1

Space Not Used ETX Chars CR

Urobilinogen Arbitrary

neg

neg

neg

Bilirubin Test Name Bilirubin Results Bilirubin Arbitrary

BIL neg neg

BIL neg neg

BIL neg neg

Blood Test Name Blood Results Blood Arbitrary

ERY ERY 50 Ery/ul 50 Ery/ul

ERY

Operator identifier

Davidoff

Davidoff

Davidoff

Not Used End of Text ETX Checksum Carriage Return (213)

ETX Nn CR

ETX Nn CR

ETX nn CR

Instrument identifier

Remark:

All result-packet-structures are as follows: follows: first 4 digits: numbers, 5th digit: space, last 6 digits: Units (right hand orientated). Checksum in this example are not calculated (nn)! Units Settings

The URISYS 1100 Urine Analyzer has flexible unit settings that include the following: (all examples are taken from the Result Packet Structure table on the previous pages, using the Protein test).


2.5 2.5 Interf ace Parameter Parameter Cable Cable Connection s

The table below summarizes the connections needed for host communication. URISYS 1100 URISYS DTE 9 Pin Signal Signal Female Direction

RxD TxD GND DTR



2 3 5 4

  

9 Pin Male

Host 25 Pin Male

DCE Signal

3 2 7 20

TxD RxD GND DTR

2 3 5 4

Communication Parameters

The required serial interface parameters are listed in the table below.

Parameter

Baud Rate Word Length Parity

Value

9600 8 bits None


2.6 2.6 Checks Checks um Calcul Calcul ation Overview

All of the messages require dynamic dynamic verification of checksums utilizing utilizing two different possible of calculations (Algorithm “a” and Algorithm “b”). The analyzer analyzes the received checksum, checksum, and it will compare it with ”Algorithm a” or with ”Algorithm b”. Thus the Algorithm with positive check results remains as active calculation Algorithm (see Auto adaptation). The host needs only to send send the required packets along with the known known checksums. checksums. The host can also check the REP, SPM, and END messages against the stored messages to ensure integrity. For the results packets (SPE) however, Roche highly recommends that the host interface program uses the checksum checksum to ensure data integrity of the result result packets. This section describes how the checksum works. Au to adapt adap t io n

URISYS 1100 Urine Analyzer is in a position to adapt itself automatically to the procedure used by the host (checksum a or b). If an error is discovered when checking the test bytes of the used protocol, the check continues using the algorithm of the alternative procedure. If, using the alternative test procedure, the test bytes are recognized as correct, this procedure is used for all protocols in future. This new setting is retained even after the power has been switched off. If the alternative procedure does not recognize any correct test bytes either, an REP protocol is transmitted and there is no change of test procedure.


LRC-Byte =

Byte1 XOR Byte2 XOR Byte3 ........ XOR Byte last LRC1-Byte = high-Nibble high-Nibble (shifted by 4 bits) of the LRC-Byte OR 3016 LRC2-Byte = low-Nibble low-Nibble of the LRC-Byte OR 30 16 Example: Bit-No. 8 7 6 5 4 3 2 1 1 0 1 1 0 0 0 1 0 2 0 0 0 0 0 0 1 1 Byte-No. 3 0 0 1 1 0 1 1 0 4 0 0 1 1 1 0 1 0 5 0 0 1 1 1 1 1 0 ---------------------------------LRC-Byte 0 1 0 1 0 0 1 1 ---------------------------------high-Nibble low-Nibble

0 1 0 1 0 0 1 1

LRC 1 - Byte = OR

0 0 1 1 0 0 0 0 /* 3016 */ 0 0 0 0 0 1 0 1 /* high-Nibble high-Nibble */ ---------------------------0 0 1 1 0 1 0 1 ============================

LRC 2 - Byte =

0 0 1 1 0 0 0 0

/* 3016 */


Al go ri th m b

This check sum is calculated by adding together the bytes to be transferred, the individual bytes being interpreted as positive and, whole numbers. STX, the checksum, ETX and CR are not included in the addition. The result of the addition is taken as modulo 256. The resulting number can be represented by a single byte. The two half-bytes of this number are represented as hexadecimal figures (”0”..”9”, ”A”..”F”). Leading zeros are included.

CS = (Byte2 + Byte3 + ... + ByteLength-4) modulo 256 If your software does not have a decimal-hexadecimal routine or function that can return a leading zero, the below algorithms may be helpful. CS1-Byte

= INT ((CS / 16)) + 48 for INT ((CS / 16)) = INT ((CS / 16)) + 55 for INT INT ((CS / 16))

CS2-Byte

= (CS modulo 16) + 48 for (CS modulo 16) = (CS modulo 16) + 55 for (CS modulo 16)

Example: MOR-Protocol STX,'>', ETX,'3E', CR 0216 3E16 0316 3316 4516 0D16 Further examples:

with

MOR-Protocol:☺> 3E

9 10 9 10

CS = 62 = 3E16

Technical Product Information for Urisys 1100 Urine Analyzer Software Version 5.x & 6.x

2.7 2.7 Unid Unid irectio nal sample outp uts byt e-to-byte e-to-byte Unidirectional Data description of URISYS 1100 Urine Analyzer Interface Single Unit results Bits line

1

2

3

4

5

6

7

8

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

U S P x O D x x x x x x x x x x x x

R e a x p e

I q t x . v

L . . x

U N I x I c

X r D x D e

. : x :

S

i

x I

9

x D

10

11

12

13

14

15

16

17

18

19

20

U

R x

I x x

N x x

A

N

A

L

Y

S

E

x

x x

x x

x x x x

x x x x

x x x x

x x x

x x x

x x x

x :

21

22

23

24

x x x

x x x

x x x

x x x

(15(15-24 24:Date/ :Date/Time) Time) (9-24 (9-24 operator i dentifier) (13-17 Device identifier) (1 Changed Changed limi t flag)

x

S p L N P G K U B E x

G H E I R L E B I R x

U T O U T G L Y x

x

x

x

x x x x x x x x x x x





x

x

x

x

x



x x x x x x x x x x .




(19(19-24 24:: Unit) (19(19-24 24:: Unit) (19(19-24: 24: Unit) (19(19-24: 24: Unit) (19(19-24 24:: Unit) (19(19-24 24:: Unit) (19-2 (19-24: 4: Unit) (19(19-24 24:: Unit) (20(20-24 24:: Unit) (19(19-24 24:: Unit) (1-20 (1-20 calibration warni ng)

Interface Setti Setti ng: ng : 9600 9600 Baud, Baud , 8 Bit, 1 Stop Bi t, NO NO Pari Parity ty Explanation: x = variable Output (coul d be space in som e cases) Remark: Remark: all Data Data transm itted in ASCII, ASCII, if applic ation runn ing wit h wind ows, data has to be transf ormed in ANSI. ANSI.

URISYS 1100 Urine Analyzer Host Interface Document Version 1.0

Page 14/28


Unidirectional Data description of Urisys 1100 Urine Analyzer Interface Combined Unit results Bits line

1

2

3

4

5

6

7

8

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

U S P x O D x x x x x x x x x x x x

R e a x p e

I q t x . v

L . . x

U N I x I c

X r D x D e

. : x :

S

i

x I

9

x D

10

11

12

13

14

15

16

17

U

R x

I x x

N x x

A

N

A

L

Y

S

E

x

x x

x x

x x x x

x x x x

x x x x

x x x

x x x

x x x

x :

18 19

20

21

22

23

24

x x x

x x x

x x x

x x x

(15(15-24 24:Date/ :Date/Time) Time) (9-24 (9-24 operator i dentifier) (13-17 Device identifier) (1 Changed Changed limi t flag)

x

S p L N P G K U B E x

G H E I R L E B I R x

U T O U T G L Y x

x

x

x






x





x x x x X x x x X x x


.

.



(15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (15-20 (15-20 uni t1, 23-24 unit2) (1-20 (1-20 calibration w arning)

Interface Settin Settin g: 9600 9600 Baud, 8 Bit , 1 Stop Bit , NO Pari Parity ty Explanation: x = variable Output (coul d be space in som e cases) Remark: Remark: all Data Data transm itted in ASCII, ASCII, if applic ation runn ing wit h wind ows, data has to be transf ormed in ANSI. ANSI.


Page 15/28


Unidirectional Log data output of URISYS 1100 Urine Analyzer Bits line

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

1 2 3 4

U D

R e

I v

L i

U c

X e

-

S I

U :

R

I

N x

A x

N x

A x

L x

Y

S

E

D

x

x

x

x

x

x

x

x

x

x

x

5 6 7 8

O P

p a

. s

s

I w

D o

: r

d

:

x

x

x

x

x

x

x

x

x

9 10 11 12

O P

p a

. s

s

I w

D o

: r

d

:

x

x

x

x

x

x

x

x

x

13 14 15 16

O P

p a

. s

s

I w

D o

: r

d

:

x

x

x

x

x

x

x

x

x

17 18

O P

p a

. s

s

I w

D o

: r

d

:

x

x

x

x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x

x x x

x

x x

x x x

x

x x

x x

x x

x x

x x

x x

x x

x x x

x x

x x

x x

x x

22

23

24

(13-17 Device identifier)

x x x

21

x x

x x

x

x

x

x

x

x x

x x

x x

x x

x x

x

x

x

x

x

x x

x x

x x

x x

x x

x

x

x

x

x

x x

x x

x x

x x

x x

x

x

x

x

x

x x

x x

x x

x x

x x

(1-12:Date/Time, 20-24 action: On, Off or Login) (13-24 operator identifier) (13-24 password)

(1-12:Date/Time, 20-24 action: On, Off or Login) (13-24 operator identifier) (13-24 password) (1-12:Date/Time, 20-24 action: On, Off or Login) (13-24 operator identifier) (13-24 password) (1-12:Date/Time, 20-24 action: On, Off or Login) (13-24 operator identifier) (13-24 password)

*The last 20 Log event printed and sent out in Unidir.


Page 16/28


3 ASTM ASTM protocol proto col 3.1 General General The ASTM ASTM proto col o f " URISY URISYS S 1100 1100 cobas" device

The URISYS 1100 device can output data in four ways: printing data on built-in printer as 24 ASCII character long messages sending data in Unidir mode to host, format is the same as in printing sending data in Bidir mode to host sending data to host in "cobas" mode, using the so called ASTM protocol. E 1394-91 standard requirements). Device implements the Profile 1 of EN ISO 18812:2003 to send results to host PC (so this protocol fulfils the ASTM E1394-91 The only used message type is i s the M1. In this type of data transmission always the UX3 device is the master. In this protocol the result message must contain the following records: H 1x P 1x O 1x R nx C mx L 1x

n>=1 0<=m<=n

Header of the message (Patient data, not used; empty record). Order - definition of the test and the sample Result numerical data and units one record – one parameter The flag of the previous result as comment, if there is a flag Message terminator

One message can contain one test result. One test result is: all the data for one sample measurement. Ad di ti on all y d evice evi ce c an as k and receive operator name list from host

Asking: H 1x M 1x L 1x

Header of the message Request for operator identifiers and their passwords lists Message terminator

Answer: H 1x M nx L 1x

n>=1


Header of the message Names and passwords of n (max 300) operators Message terminator

Page 17/28

Technical Product Information for Urisys 1100 Urine Analyzer Software Version 5.x & 6.x Data flow in the different cases

Normal result send

OpID list request

OpID OpID list do wnload

Log d ata send send

Device sends --(ENQ)




Host sends --(ACK)

"H" record

Host sends --(ACK)

"H" record (ACK)

"P" record (ACK) "O" record (ACK) "R" record (ACK) "C" record

(ACK) "M" record RQO (ACK) "L" record (ACK) (EOT) -----

(ACK) (more "R"-s and "R + C"-s) (ACK) "L" record (ACK) (EOT) -----


Host sends --(ACK)

"H" record

Host sends --(ACK)

"H" record (ACK)

"M" record OL (ACK) "M" record OL (ACK) (more "M” records) (ACK) "L" record (ACK) (EOT) -----

(ACK) "M" record LOG (ACK) "L" record (ACK) (EOT) -----

Page 18/28


3.2 3.2 Sendi Sendi ng nor mal measurement d ata


Page 19/28


3.3 3.3 Requesting Requesting o perator ID list do wnlo ad


Page 20/28


3.4 3.4 Operator Operator id entifier list d ownl oad


Page 21/28


3.5 3.5 Send Sendin ing g L OG data


Page 22/28


3.6 3.6 Abbreviation s in resul t tables Ab br ev. Con ten t (s amp le)

CHS DTC DTM DTS FL LOG LGDat NOL OI_N OL OpID PW RES RESC RESR RN

Meani ng

Plac e

(CheckSum) 20070321 20070322154726 20070322154726 *^M

Checksum of the record** x18 Date of last menu calibration R10 Date/Time of the test O15 Date/time of the message H14 * (the flag of not-normal range, if result is not neg/norm) and M (limit modification mark, if one or C4 more limits for this parameter are modified - limit table is INTUSER.) See SM M3 LOG 20070322154726ÔN^L Date/time of log event, the event (On, Off, Login), the used OpID, the used password (LOG)M4 .Normann^Heureka 11 Number of OpIDs in the valid authentication list (min 1, max 300) (OL)M7 1 Place number in OpID authentication list (1…NOL) (OL)M2 OL See SM M3 L. NormanÂ Name or code of the operator (max 12 chars), code of authentication (A,N)*** R11, (OL)M4 Petike Password to the operator name or code before (12 chars) (OL)M5 25^1+ Result in setted system (SI or CONV or ARB) + result in ARB system * R4 375^315 Compensated and raw results in (R%) x10 (SM)M5 587 Reference pad raw results in (R%) x10 (SM)M6 3 Record serial number, generaly the same as parameter ser.no. in cases of normal or CheckMode R2, C2, (SM)M2, results, and 0...99 in case of LOG data. data . (LOG)M2

RNN RQO S_ID SM(R)

3^LEU RQO Kovacs Janos SM

Parameter serial number, see parameter code list See SM Patient identifier (max 13 characters) Record sub_ID: Service Mode (CheckMode) Reference result (SMR), (SMR), or measuring pad result(SM), or request for OpID list (RQO), or OpID List (OL), or Log data (LOG);

R3, (SM)M4 M3 O3 M3

S_NO

187^008^C10

O4

SEN

URISYS1100^75943^S W1.2ÛSA

MeasNo (1…65535); SerNo (1…100), within the given series; strip type setting (C5, C7, C10); MeasNo is an independent serial no of the test, automaticaly restarts, can not be set or clear. Device type, device ID, sw version, limit table type (INT/USA/INTUSER)


H5

Page 23/28

Technical Product Information for Urisys 1100 Urine Analyzer Software Version 5.x & 6.x SID

UrinalysisÎncubated

Type of measurement; fixed text: UrinalysisÎncubated, or Urinalysis^Fast, or CheckMode MeasÎncubated, or CheckMode Meas^Fast

O5

SV SZIN UNI

User Orange Leu/ul

code of rights (SV=supervisor, User=not supervisor) Color of test, in CheckMode (Orange, Green) for each parameter The setted result unit (ARB has no unit)

(OL)M6 (SM)M6 R5

*Param names, result values and units correspond to valid vali d limit table (INT or USA) This check sum is calculated by adding together the bytes to be transferred, the individual bytes being interpreted as **Calculation of positive, whole numbers. CR and ETX are included in the addition, STX Not. The result of the addition is taken as modulo checksum: 256. The resulting number can be represented by a single byte. The two half-bytes of this number are represented as hexadecimal figures (”0”..”9”, ”A”..”F”). Leading zeros are included.

***Authentication code

Byte0=(STX) CHS = (Byte1 + Byte2 + ... + ByteLength-1) modulo 256 A=authentic OpID; N=not authentic ID or not ID used


Page 24/28


3.7 3.7 Parameter Parameter names an d c odes od es (RNN) (RNN)


Page 25/28


3.8 3.8 ASTM Commu nic ation sampl es of URIS URISYS YS 110 1100 0 Urine Anal yzer Normal measurement result send

*

17:50:24,405 Urisys 1100 - ASTM Host Simulator [V 6.8d]

U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100

17:56:22,233 [ENQ] 17:56:22,233 [ACK] 17:56:22,280 [STX]1H|\^&|||URISYS1100^99305^SW5.31ÎNT|||||||P||20090116184200[C [STX]1H|\^&|||URISY S1100^99305^SW5.31ÎNT|||||||P||20090116184200[CR][ETX]F8[CR][ R][ETX]F8[CR][LF] LF] 17:56:22,280 [ACK] 17:56:22,296 17: 56:22,296 [STX]2P|1[CR][ETX]3F[CR][LF] [STX]2P|1[CR][ETX] 3F[CR][LF] 17:56:22,311 [ACK] 17:56:22,358 17:56: 22,358 [STX]3O|1||001^00036^C10|UrinalysisÎncubated|R||||||X|||20090 116184100[CR][ETX]00[CR 116184100[CR][ETX]00[CR][LF] ][LF] 17:56:22,358 [ACK] 17:56:22,389 [STX]4R|01|01^·SG|1.020|g/cm3| [STX]4R|01|01^·SG|1.020|g/cm3|||||20090116|LNormanÂ[CR][ ||||20090116|LNormanÂ[CR][ETX]BB[CR][LF] ETX]BB[CR][LF] 17:56:22,405 [ACK] 17:56:22,436 [STX]5R|02|02^·pH|····7||||||20090116|LNormanÂ[CR][E [STX]5R|02|02^·pH|···· 7||||||20090116|LNormanÂ[CR][ETX]09[CR][LF] TX]09[CR][LF] 17:56:22,436 [ACK] 17:56:22,483 [STX]6R|03|03^LEU|··neg^·· [STX]6R|03|03^LEU|··neg^··neg|·Leu/ul|||||20090116|LNormanÂ[CR neg|·Leu/ul|||||20090116|LNormanÂ[CR][ETX]0B[CR][LF ][ETX]0B[CR][LF]] 17:56:22,483 [ACK] 17:56:22,530 [STX]7R|04|04^NIT|··neg^··neg||||||20090116|LNormanÂ[CR] [STX]7R|04|04^NIT|·· neg^··neg||||||20090116|LNormanÂ[CR][ETX]BD[CR][LF [ETX]BD[CR][LF]] 17:56:22,530 [ACK] 17:56:22,577 [STX]0R|05|05^PRO|··neg [STX]0R|05|05^PRO|··neg^··neg|·mg/dl·|||||20090116|LNormanÂ[ ^··neg|·mg/dl·|||||20090116|LNormanÂ[CR][ETX]D1[CR] CR][ETX]D1[CR][LF] [LF] 17:56:22,577 [ACK] 17:56:22,624 [STX]1R|06|06^GLU|·norm^· [STX]1R|06|06^GLU|·norm^··neg|·mg/dl·|||||20090116|LNormanÂ[ ·neg|·mg/dl·|||||20090116|LNormanÂ[CR][ETX]2D[CR] CR][ETX]2D[CR][LF] [LF] 17:56:22,624 [ACK] 17:56:22,671 [STX]2R|07|07^KET|··neg^· [STX]2R|07|07^KET|··neg^··neg|·mg/dl·|||||20090116|LNormanÂ[C ·neg|·mg/dl·|||||20090116|LNormanÂ[CR][ETX]CA[CR][ R][ETX]CA[CR][LF] LF] 17:56:22,671 [ACK] 17:56:22,717 [STX]3R|08|08ÛBG|·norm^· [STX]3R|08|08ÛBG|·norm^··neg|·mg/dl·|||||20090116|LNorman ·neg|·mg/dl·|||||20090116|LNormanÂ[CR][ETX]29[CR] Â[CR][ETX]29[CR][LF] [LF] 17:56:22,717 [ACK] 17:56:22,764 [STX]4R|09|09^BIL|··neg^·· [STX]4R|09|09^BIL|··neg^··neg|·mg/dl·|||||20090116|LNormanÂ[C neg|·mg/dl·|||||20090116|LNormanÂ[CR][ETX]C3[CR][ R][ETX]C3[CR][LF] LF] 17:56:22,764 [ACK] 17:56:22,811 [STX]5R|10|10ÊRY|··· [STX]5R|10|10ÊRY|···50^···3+|·Ery/ul|||||20090116|LNormanÂ[C 50^···3+|·Ery/ul|||||20090116|LNormanÂ[CR][ETX]A9[CR][LF R][ETX]A9[CR][LF]] 17:56:22,811 [ACK] 17:56:22,827 17: 56:22,827 [STX]6C|10|I|*|I[CR][ETX]96[CR][LF [STX]6C|10|I|*|I[CR] [ETX]96[CR][LF]]


Page 26/28


HOST U1100 HOST U1100

17:56:22,827 [ACK] 17:56:22,842 [STX]7L|1|N[CR][ETX]0A[CR][LF] [STX]7L|1|N[CR][ET X]0A[CR][LF] 17:56:22,858 [ACK] 17:56:22,858 [EOT]

OpID OpID list request request and download

*


Request

U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100

17:49:45,561 [ENQ] 17:49:45,561 [ACK] 17:49:45,608 [STX]1H|\^&|||URISYS1100^99305^SW5.31ÎNT|||||||P||20090116183500[C [STX]1H|\^&|||URISY S1100^99305^SW5.31ÎNT|||||||P||20090116183500[CR][ETX]FA[CR][ R][ETX]FA[CR][LF] LF] 17:49:45,624 [ACK] 17:49:45,639 17: 49:45,639 [STX]2M|1|RQO[CR][ET [STX]2M|1|RQO[CR][ETX]AA[CR][LF] X]AA[CR][LF] 17:49:45,639 [ACK] 17:49:45,655 [STX]3L|1|N[CR][ETX]06[CR][LF] [STX]3L|1|N[CR][ET X]06[CR][LF] 17:49:45,655 [ACK] 17:49:45,671 [EOT]

Download

HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST

17:49:47,686 [ENQ] 17:49:47,686 [ACK] 17:49:47,733 [STX]1H|\^&|||Host|||||||P||2008120817494 [STX]1H|\^&|||Host|||||||P||20081208174945[CR][ETX]76[CR] 5[CR][ETX]76[CR][LF] [LF] 17:49:47,733 [ACK] 17:49:47,764 [STX]2M|1|OL|LNorman|Pass|SV|3[CR [STX]2M|1|OL|LNorman|Pass|SV|3[CR][ETX]6D[CR][L ][ETX]6D[CR][LF] F] 17:49:47,780 [ACK] 17:49:47,811 [STX]3M|2|OL|123456789012|Password9012|SV|3[CR] [STX]3M|2|OL|123456789012|Password9012|SV|3[CR][ETX]B0[CR][LF] [ETX]B0[CR][LF] 17:49:47,811 [ACK] 17:49:47,842 [STX]4M|3|OL|UserName|UserPW [STX]4M|3|OL|UserName|UserPW|User|3[CR][ETX]7F[CR] |User|3[CR][ETX]7F[CR][LF] [LF] 17:49:47,858 [ACK] 17:49:47,889 [STX]5L|1[CR][ETX]3E[CR][LF] [STX]5L|1[CR][ETX]3 E[CR][LF] 17:49:50,374 [ACK] 17:49:50,389 [EOT]


Page 27/28

Technical Product Information for Urisys 1100 Urine Analyzer Software Version 5.x & 6.x Log data send

*


U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100 HOST U1100

17:48:54,780 [ENQ] 17:48:54,780 [ACK] 17:48:54,827 [STX]1H|\^&|||URISYS1100^99305^SW5.31ÎNT|||||||P||20090116183400[C [STX]1H|\^&|||URISY S1100^99305^SW5.31ÎNT|||||||P||20090116183400[CR][ETX]F9[CR][ R][ETX]F9[CR][LF] LF] 17:48:54,842 [ACK] 17:48:54,874 [STX]2M|0|LOG|20090116183300^Login^LNorman [STX]2M|0|LOG|20090116183300^Login^LNorman^PASS[CR][ETX]D8[C ^PASS[CR][ETX]D8[CR][LF] R][LF] 17:48:54,874 [ACK] 17:48:54,905 17:48: 54,905 [STX]3M|1|LOG|20090116183300^Login^LNorman [STX]3M|1|LOG|20090116183300^Login^LNorman^Pass[CR][ETX]3A[CR][ ^Pass[CR][ETX]3A[CR][LF] LF] 17:48:54,921 [ACK] 17:48:54,936 [STX]4L|1|N[CR][ETX]07[CR][LF] [STX]4L|1|N[CR][ET X]07[CR][LF] 17:48:54,936 [ACK] 17:48:54,952 [EOT]


Page 28/28

Roche Urisys 1100 Urine Analyzer

Recommend Documents