Вы находитесь на странице: 1из 52

AUTO REF/KERATOMETER

Model
Mo ARK-530A/ARK-510A
INTERFACE MANUAL

September 2009
Pages in total - 52
XRK8A*RTZ001B/E
NIDEK CO., LTD. : 34-14, Maehama, Hiroishi-cho, Gamagori, Aichi 443-0038, Japan
(Manufacturer) Telephone: +81-533-67-6611
Facsimile: +81-533-67-6610
NIDEK CO., LTD : 3F Sumitomo Fudosan Hongo Bldg., 3-22-5, Hongo,
(Tokyo Office) Bunkyo-Ku, Tokyo 113-0033, Japan
Telephone: +81-3-5844-2641
Facsimile: +81-3-5844-2642
NIDEK INCORPORATED : 47651 Westinghouse Drive, Fremont, California 94539, U. S. A.
(United States Agent) Telephone: +1-510-226-5700
Facsimile: +1-510-226-5750
NIDEK SOCIETE ANONYME : Europarc 13, rue Auguste Perret, 94042 CRETEIL, France
(EU Authorized Representative) Telephone: +33-1-49 80 97 97
Facsimile: +33-1-49 80 32 08
Table of Contents

1. OUTLINE OF COMMUNICATION. . . . . . . . . . . . . . . . . . . . 3
1.1 Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2. RS-232C COMMUNICATION . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Outline of RS-232C Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
2.1.1 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
2.2 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
2.2.1 Command format (with “NIDEK”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
2.2.2 Data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
2.2.3 CR (Carriage Return) Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2.3 Communication Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
2.3.1 Interface between the ARK-530A/510A and external PC . . . . . . . . . . . . . . . . . . . .19
2.3.2 Flow of sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
2.3.3 Sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

3. LAN COMMUNICATION . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1 Outline of LAN Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.1.1 Outline of communication function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.1.2 Reception structure of measurement data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
3.2 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.2.1 Folder configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.2.2 Measurement data (image data) output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.2.3 Response to data acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
3.2.4 XML file configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
3.2.5 Style sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
3.2.6 XML file sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

4. EXAMPLE OF RECEIVED DATA . . . . . . . . . . . . . . . . . . . 37


4.1 Example of Measurement Data Received by PC. . . . . . . . . . . . . . . . . . . . . . . . .37
4.2 Sample Printout of KM Data when the I/F FORMAT Parameter is Set to Short45
4.3 Transmission of Sagittal Measurement Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
4.4 Interface Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

1
:

2
1. OUTLINE OF COMMUNICATION

1.1 Interface Type


1

The ARK-530A/510A comes equipped with the following two types of interface to transfer measure-
ment data to external computers:
• RS-232C interface
• LAN interface

This interface manual describes the method of receiving measurement data from the ARK-530A/510A
using the RS-232C interface in Chapter 2 and the LAN interface in Chapter 3.

3
OUTLINE OF COMMUNICATION: Interface Type

4
2. RS-232C COMMUNICATION

2.1 Outline of RS-232C Communication

To transmit data measured by the ARK-530A/510A to an external computer, the ARK-530A/510A


comes equipped with an RS-232C interface. This manual provides the method of receiving the mea-
surement data from the ARK-530A/510A through this interface. 2

This chapter describes the specifications for the interface for data transmission between the ARK-
530A/510A and a personal computer, etc.

{ Basic interface specifications

1 Basic spec In accordance with RS-232C standards

2 Connector DIN 8-pin

3 Transmission method Asynchronous

4 Transmission system Half duplex

5 Baud rate 9600/4800/2400/1200 bit/sec

6 Bit length 8/7 bit

7 Parity check Odd parity

8 Stop bit 1 bit

9 Data code ASCII code

10 CR code YES (added)/ NO (Not added)

As the Transmission system, Parity check, and Stop bit length are fixed as above, it is necessary for
the external computer to conform to these specifications.

5
RS-232C COMMUNICATION: Outline of RS-232C Communication

{ Cable connection

㧝 㧝
4'& 4'&
4:& 㧞 㧞 6:&
140 140
6:& 㧟 㧟 4:&
$.7 ;'.
&64 㧠 㧠 465
External computer $.74'&
ARK-530A/510A
5)0& 㧡 㧡 %65
Serial communication Interface connector
)4; $.7
&54 㧢 㧢 &54
port
;'. $.74'&
(RS-232C) 465 㧣 㧣 5)0&
)4;
%65 㧤 㧤 &64

㧥 㧱 ()0&

()0& 㧱

D-sub 9P (female) DIN 8P

5 1 2
5 4

8
3 1

7 6
9 6

Connect the ARK-530A/510A interface port and the serial communication port (RS-232C) of
the external computer with the above interface cable (Model: OPIF-15).
This interface cable allows the “71. I/F MODE” parameter to be set either to “Nidek” or “NCP10”.

Connection to the external computer by any means other than that specified above (Dsub 9P) needs a
conversion adapter.

6
RS-232C COMMUNICATION: Outline of RS-232C Communication

2.1.1 Communication sequence


Two types of the transmission sequences, “NIDEK” and “NCP10”, can be selected by setting the “71.
I/F MODE” parameter.

COMMUNICATION SEQUENCE NIDEK NCP10

DTR/DSR control Performed Not performed

RS/SD command control Performed Not performed

Data transmission in response to a request from the


Possible Not possible 2
PC

Checksum data Not present Present

With “NIDEK”, the transmission sequence is the same as the conventional transmission sequence.
With “NCP10”, press the button to transmit data. Because “NCP10” does not need complicated
controls such as the DTR control, DSR control, RS command control, SD command control, etc., it
allows easier communication compared with “NIDEK”. However, with “NCP10”, data transmission in
response to a request from the personal computer is not available. Select a transmission sequence
that suits your needs or purposes.

{ When the I/F MODE parameter is set to NIDEK


DTR/DSR control:

Data

Sending
end Same timing

Data

Same timing

Receiving
end

T1, T2 = 0.1 sec.


(Time-out period: T1, T2 > 0.1 sec.)
Disable DTR as soon as possible after the transmission and reception of EOT.

7
RS-232C COMMUNICATION: Outline of RS-232C Communication

{ RS/SD command control:


[When the print button ( ) is pressed:]

[When a data send request is sent from the external computer:]

{ When the “I/F MODE” parameter is set to NCP10


The DTR/DSR control is not performed. The DTR signal of the ARK-530A/510A is constantly at a low
state on a line. The DTR signal of the external computer does not affect the transmission under either
condition.
In addition, since the RS/SD command control is not performed, pressing the print button ( )
sends the data directly.

8
RS-232C COMMUNICATION: Data Format

2.2 Data Format

2.2.1 Command format (with “NIDEK”)


ASCII characters are used for data transmission and reception.

1 RS command
Sends a request for 2 SD command to the external computer from the ARK-530A/510A. 2
SOH C * * STX R S ETB EOT

01H 43H 2AH 2AH 12H 52H 53H 17H 04H H: HEX (Hexadecimal)

2 SD command
Sends a request for measurement data transmission to the ARK-530A/510A from the exter-
nal computer.
1) For requesting AR measurement data:

SOH C R M STX S D ETB EOT

2) For requesting KM measurement data:

SOH C K M STX S D ETB EOT

3) For requesting AR and KM measurement data:

SOH C R K STX S D ETB EOT


3 CL command
Sends a request to clear measurement data to the ARK-530A/510A from the external com-
puter.

SOH C R M STX S D ETB EOT

SOH C K M STX S D ETB EOT

SOH C R K STX S D ETB EOT

This process clears the above commands. This is the equivalent of pressing the print button
( ), after which preparations for the next measurement are made.
When the measurement is started after preparation, the previous data is cleared and the
next patient is measured.

9
RS-232C COMMUNICATION: Data Format

2.2.2 Data format

{ Basic format
1) AR measurement data:

SOH D R M STX Data ETB Data ETB Data ETB EOT

2) KM measurement data:

SOH D K M STX Data ETB Data ETB Data ETB EOT

3) AR and KM measurement data:

SOH D R M STX Data ETB Data ETB Data ETB

SOH D K M STX Data ETB Data ETB EOT

When the ARK-530A/510A receives the SD command, data transmission is started in this format.
When the “71. I/F MODE (Interface Mode)” parameter is set to “NCP10”, four digits of checksum are
added after “EOT” in each data format.

{ Data transmitted from the ARK-530A/510A

1) Company name / Model name 2) Patient number

3) Patient ID 4) Date and time of measurement

5) Vertex distance 6) Near working distance

7) Objectively measurement data 8) Contact lens conversion data

9) Optimum trial lens data 10) Pupillary distance

11) KM measurements 12) Corneal size measurements

13) Pupil size measurements 14) Checksum

10
RS-232C COMMUNICATION: Data Format

{ Data
The number inside the parentheses indicates the number of characters transmitted.

1 Company name / Model name

I D N I D E K / A R K - 5 3 0 A

ID code Company name Model name (ARK-530A)

I D N I D E K / A R K - 5 1 0 A
2
ID code Company name Model name (ARK-510A)

When the “72. I/F FORMAT” parameter is set to “SHORT” and a request for KM data only is
sent (see “2 SD Command” of 2.1), the company name and model name are not transmitted.
2 Patient number

N O 0 1 2 3

No. code Patient number (4)

3 Patient ID
Transfer the data when the patient ID is inputted by the bar code reader.

I P 0 1 2 3 4 5 6 7 ••• 27 28 29 30

Patient ID Transfer the number of inputted letters (maximum 31 letters).


IP code
(20 letters for printing)

4 Date and time of measurement


When the time format is set to “AM/PM”

1) When the “38. DATE FORMAT” parameter is set to “Y/M/D”:

D A 2 0 0 6 . 0 5 . 1 2 . 0 1 : 2 3 P M

Date Year (4) Month Date (2) Hour (2) Minute AM/PM
code (2) (2) (2)

2) When the “38. DATE FORMAT” parameter is set to “M/D/Y”:

D A M A Y / 1 2 / 2 0 0 6 . 0 1 : 2 3 P M

Date Month (3) Date (2) Year (4) Hour (2) Minute AM/PM
code (2) (2)

3) When the “38. DATE FORMAT” parameter is set to “D/M/Y”:

D A 1 2 / M A Y / 2 0 0 6 . 0 1 : 2 3 P M

Date Date (2) Month (3) Year (4) Hour (2) Minute AM/PM
code (2) (2)

11
RS-232C COMMUNICATION: Data Format

When the time format is set to “24H”


1) When the “38. DATE FORMAT” parameter is set to “Y/M/D”:

D A 2 0 0 6 . 0 5 . 1 2 . 0 1 : 2 3

Date Year (4) Month Date (2) Hour (2) Minute


code (2) (2)

2) When the “38. DATE FORMAT” parameter is set to “M/D/Y”:

D A M A Y / 1 2 / 2 0 0 6 . 0 1 : 2 3

Date Month (3) Date (2) Year (4) Hour (2) Minute
code (2)

3) When the “38. DATE FORMAT” parameter is set to “D/M/Y”:

D A 1 2 / M A Y / 2 0 0 6 . 0 1 : 2 3

Date Date (2) Month (3) Year (4) Hour (2) Minute
code (2)

5 Vertex distance

V D 1 2 . 0 0

VD code Vertex distance (5)

6 Near working distance

W D 4 0

Working
WD code distance
(2)

7 Objectively measurement data


After median values have been obtained after three or more measurements, the median val-
ues are transmitted first and then respective items of data are transmitted (in order of acqui-
sition time with the latest data first). Order of R/L: L Æ R.
When the “45. CAT MARK” parameter is set to “YES”, a CAT measurement mark “*” is added to the
data to indicate it was measured by the AR with the CAT measurement mode icon ( ) displayed.

1) Left eye data

O L - 0 5 . 2 5 - 0 0 . 7 5 1 0 9 9 *

R/L code Confidence CAT mark


SPH (6) CYL (6) AXIS (3)
(2) code (1) (1)

2) Right eye data

O R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4 8 *

R/L code Confidence CAT mark


SPH (6) CYL (6) AXIS (3)
(2) code (1) (1)

12
RS-232C COMMUNICATION: Data Format

3) Reference value (Confidence index is "E”.)


When “44. ERROR DATA” is set to “YES”, the data whose confidence index (indicates the
degree of reliance) is under 5, can be measure as a reference value. In this case, “E” is
added to the end of the transmitted data.

O R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4 E *

R/L code Confidence CAT mark


SPH (6) CYL (6) AXIS (3)
(2) E code (1) (1)

4) Error data
2
When “46. ERROR PRINT” is set to “YES”, the measurement errors are stored in memory
and transmitted together with AR measurement data.

E R + 0

ERROR Type of
code error (2)

Type of error Content

+O Positive SPH range over error

-O Negative SPH range over error

CO CYL range over error

When the “72. I/F FORMAT” parameter is set to “SHORT”:


• Only median values are transmitted as objectively measurement data.
• When the median value could not be obtained, only the last one in the values whose confidence
index is not under 5 is transmitted.
• When only the reference value is existed, only the latest data in the reference vales is transmitted.
• The error data is not transmitted.

13
RS-232C COMMUNICATION: Data Format

8 Contact lens conversion data


1) Left eye data

C L - 0 5 . 2 5 - 0 0 . 7 5 1 0 9

R/L code SPH (6) CYL (6) AXIS (3)


(2)

2) Right eye data

C R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4

R/L code SPH (6) CYL (6) AXIS (3)


(2)

When “54. CL PRINT” is set to “NO”, contact lens conversion data is not transmitted.
9 Optimum trial lens data
1) Left eye data

T L - 0 5 . 2 5 - 0 0 . 7 5 1 0 9

R/L code SPH (6) CYL (6) AXIS (3)


(2)

2) Right eye data

T R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4

R/L code SPH (6) CYL (6) AXIS (3)


(2)

When the “53. TL PRINT” parameter is set to “NO”, trial lens data is not transmitted.
When the median value could not be obtained from the objectively measurement result, the
data is not transmitted.
10 PD measurement
1) When both right and left PD values are measured:

P D 6 8 3 5 3 3 6 3

N. PD (2)
PD code PD (2) RPD (2) LPD (2) (Near point
(2) PD)

2) When the distance PD value only is measured:


ie

P D 6 8 ? ? ? ? ? ?

N. PD (2)
PD code PD (2) RPD (2) LPD (2) (Near point
(2) PD)

When the “55. NEAR PD PRINT” parameter is set to “NO”, only “??” in N.PD is transmitted.
When the PD values are measured more than one time, the measurement PD data is trans-
mitted in order of acquisition time with the latest PD data first. However, when the “72. I/F
FORMAT” parameter is set to “SHORT”, only the latest PD value is transmitted.

14
RS-232C COMMUNICATION: Data Format

11 KM measurements
When median values have been obtained after three or more measurements, the median
values are transmitted first and then respective items of data are transmitted (in order of
acquisition time with the latest data first). Order of R/L: L Æ R.
When the “72 I/F FORMAT” parameter is set to “SHORT”:
• Only KM median values are transmitted.
• When median values could not be obtained, only the latest KM measurement data is transmitted.
• Data (D: in diopter) is not transmitted.

KM measurement (center) 2
1) Left eye (mm) data

L 0 7 . 9 5 0 7 . 7 1 1 7 6 0 7 . 8 3

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

2) Left eye (D) data

D L 4 2 . 4 5 4 3 . 7 7 1 7 6 4 3 . 1 1

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

- 0 1 . 3 2

CYL (6)

3) Right eye (mm) data

R 0 7 . 8 6 0 7 . 5 3 1 7 5 0 7 . 7 0

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

4) Right eye (D) data

D R 4 2 . 9 4 4 4 . 8 2 1 7 5 4 3 . 8 8

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

- 0 1 . 8 8

CYL (6)

15
RS-232C COMMUNICATION: Data Format

KM peripheral measurement

When KM peripheral measurement is not performed, the data is not transmitted.

1) Left eye (mm) data

E L 0 7 . 9 8 0 7 . 9 6 1 7 4 0 7 . 9 7

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

2) Left eye (D) data

H L 4 2 . 2 5 4 2 . 5 0 1 7 4 4 2 . 3 8

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

- 0 0 . 2 5

CYL (6)

3) Right eye (mm) data

E R 0 7 . 9 3 0 7 . 9 1 1 7 5 0 7 . 9 2

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

4) Right eye (D) data

H R 4 2 . 5 0 4 2 . 7 5 1 7 5 4 2 . 6 3

R/L code R1 (5) R2 (5) AXIS (3) AVE (5)


(2)

- 0 0 . 2 5

CYL (6)

16
RS-232C COMMUNICATION: Data Format

12 Corneal size (CS) measurement


When the “72. I/F FORMAT” parameter is set to “SHORT”, the data is not transmitted.
1) Left eye data

S L 1 1 . 5

R/L code CS (4)


(2)

2) Right eye data


2
S R 1 1 . 0

R/L code CS (4)


(2)

13 Pupil size (PS) measurements


When the “72. I/F FORMAT” parameter is set to “SHORT”, the data is not transmitted.
1) Left eye data

P L 0 6 . 0 F

R/L code Target


PS (4)
(2) lamp (1)

2) Right eye data

P R 0 6 . 0 N

R/L code Target


PS (4)
(2) lamp (1)

“Target lamp” transfers the state of the target lamp during the PS measurement.

N Target lamp ON

F Target lamp OFF

14 Checksum
When the “71. I/F MODE” parameter is set to “NCP10”, a checksum is added to the data for-
mat. It is added after “EOT” of each data format.

SOH ・・・ ETB EOT 3 2 C F

Data Checksum (4)

The checksum is represented by four hexadecimal digits. The value of the checksum is the
simple sum of “SOH” to “EOT” in the data format. However, the “CR” code is not included
into the calculation of the checksum when the “CR” code is added.

CAUTION • Set the “74. BIT LENGTH” parameter to 8.


When the parameter is set to 7, the codes that correspond to kana-characters are not
exported successfully.

17
RS-232C COMMUNICATION: Data Format

2.2.3 CR (Carriage Return) Code


When a personal computer is used as the external computer for receiving the data, it may be neces-
sary to add “CR” code to the end of data to be transmitted in one line. The ARK-530A/510A allows you
to select whether or not to add “CR” code to the end of data.
See Step 3 of “2.3.1. Interface between the ARK-530A/510A and external PC” (page 19)
The data to be transmitted when “CR” code is added:

1 RS command with “CR” code added

SOH C * * STX R S ETB EOT CR

0DH

“CR” code is added to the end of a command statement.


2 Data with “CR” code (When the “71. I/F MODE” parameter is set to “NIDEK”)

SOH D R M STX Data ETB CR Data ETB CR Data

ETB CR EOT CR

“CR” code is added to the end of the “ETB” code and the end of data.
3 Data with “CR” code (When the “71. I/F MODE” parameter is set to “NCP10”)

SOH D R M STX Data ETB CR Data ETB CR Data

ETB CR EOT C1 C2 C3 C4 CR

Checksum

“CR” code is added to the end of the “ETB” code and the end of data.

18
RS-232C COMMUNICATION: Communication Program

2.3 Communication Program

2.3.1 Interface between the ARK-530A/510A and external PC


Actual transmission method is explained using the attached sample program in this section.
As the external computer, an IBM PC compatible (IBM100% COMPATIBLE) is used.

1 Connect between the port of the ARK-530A/510A interface connector and 2


serial communication port (RS-232C) of the external computer with an interface
cable (OPIF-15).

2 Enter a sample program of one of transmission sequences to the external com-


puter.
Visual Basic is used as a BASIC application.

3 Set the ARK-530A/510A as specified:


I/F MODE Depending of the sample program
BAUD-RATE 9600
BIT LENGTH 8
CR CODE YES

See “2.12 Parameter Settings” in the operator’s manual for the method of setting parame-
ters.

4 Measure eyes with the ARK-530A/510A and press the print button when the
sample program is running.
When data is transmitted successfully, measurement data is displayed on the monitor of the
computer.
ARK-530A

When the I/F MODE parameter is set to NIDEK When the I/F MODE parameter is set to NCP10

19
RS-232C COMMUNICATION: Communication Program

2.3.2 Flow of sample program

{ When the I/F MODE parameter is set to NIDEK:

External computer

ARK-530A/510A

20
RS-232C COMMUNICATION: Communication Program

{ When the I/F MODE parameter is set to NCP10:

External computer

ARK-530A/510A

21
RS-232C COMMUNICATION: Communication Program

2.3.3 Sample program

{ When the I/F MODE parameter is set to NIDEK:

'****************************************************
' Input DATA from ARK/AR for PC/AT
' Sample Program for I/F Mode = NIDEK
' (Visual Basic Ver6.0)
'****************************************************
' Setting of ARK
' I/F Mode = NIDEK
' Baud-Rate = 9600
' Bit Length = 8
' CR Code = YES
'
Dim TimeupFlag, RecEotFlag As Integer
Dim Buf, L_Buf As String

Private Sub Form_Load()


' Initialize Display Message
Text1.Text = ""
Label1.Caption = "Receive Data"
Label2.Caption = "Communication with AR/ARK"
Label3.Caption = "Push Start Button"
Command1.Caption = "Start"
' Initialize MSComm Control
MSComm1.CommPort = 1
MSComm1.Settings = "9600,o,8,1"
MSComm1.RThreshold = 1

End Sub

Private Sub Command1_Click()


CRM_SD = Chr(1) + "CRM" + Chr(2) + "SD" + Chr(23) + Chr(4) ' SD command for AR
CRK_SD = Chr(1) + "CRK" + Chr(2) + "SD" + Chr(23) + Chr(4) ' SD command for ARK
CXX_RS = Chr(1) + "C**" + Chr(2) + "RS" + Chr(23) + Chr(4) ' RS Command

Text1.Text = ""
Label3.Caption = "Initializing..."
' Open COM1 Port
If MSComm1.PortOpen = False Then
MSComm1.PortOpen = True
MSComm1.DTREnable = False
Timer1.Enabled = False
Timer1.Interval = 2000
Timer1.Enabled = True: TimeupFlag = False
Do ' Waiting for DSR turn off
DoEvents
Loop Until TimeupFlag = True
End If
Label3.Caption = "Waiting for RS command (DSR)"
L_Buf = "": RecEotFlag = False
Do ' Check DSR
DoEvents
Loop Until MSComm1.DSRHolding = True
Label3.Caption = "Waiting for RS command (Text)"
Timer1.Interval = 5000
Timer1.Enabled = True: TimeupFlag = False
MSComm1.DTREnable = True
Do ' Waiting for RS command
DoEvents
If TimeupFlag = True Then
Exit Do
End If
Loop Until RecEotFlag = True
If L_Buf = CXX_RS Then
Label3.Caption = "Waiting for SD command transmitting (DSR)"
L_Buf = "": RecEotFlag = False
Do ' Check DSR
DoEvents

22
RS-232C COMMUNICATION: Communication Program

Loop Until MSComm1.DSRHolding = True


MSComm1.Output = CRN_SD ' Send SD command for ARK
Label3.Caption = "Waiting for DATA (TEXT)"
Timer1.Interval = 5000
Timer1.Enabled = True: TimeupFlag = False
Do ' Waiting for Data
DoEvents
If TimeupFlag = True Then
Exit Do
End If
Loop Until RecEotFlag = True
If RecEotFlag = True Then
Label3.Caption = "Finished DATA receiving" & vbNewLine & "Push Start Button"
Else
Label3.Caption = "EOT Error!!" & vbNewLine & "Push Start Button"
End If 2
Else
Label3.Caption = "RS Command Error (Terminated)" & vbNewLine & "Push Start Button"
End If
If MSComm1.PortOpen = True Then
MSComm1.PortOpen = False
End If
End Sub

Private Sub MSComm1_OnComm()


Select Case MSComm1.CommEvent ' Receive
Case comEvReceive
Buf = MSComm1.Input
L_Buf = L_Buf + Buf
Text1.Text = Text1.Text + Buf
If Right$(L_Buf, 1) = Chr(4) Then ' Check end of data
RecEotFlag = True
Text1.Text = Text1.Text + vbNewLine
End If
Case comEvCTS
Case comEvDSR
Case comEvCD
Case comEvRing
Case comEvEOF
Case Else
MsgBox "Error", vbCritical
End Select
End Sub

Private Sub Form_Unload(Cancel As Integer)


If MSComm1.PortOpen = True Then
MSComm1.PortOpen = False
End If
End Sub

Private Sub Timer1_Timer()


TimeupFlag = True
Timer1.Enabled = False
End Sub

23
RS-232C COMMUNICATION: Communication Program

{ When the “I/F (Interface) MODE” parameter is set to “NCP10”:

'******************************************************
' Input DATA from ARK/AR for PC/AT
' Sample Program for I/F Mode = NCP10
' (Visual Basic Ver6.0)
'******************************************************
' Setting of ARK
' I/F Mode = NCP10
' Baud-Rate = 9600
' Bit Length = 8
' CR Code = YES
'
Dim TimeupFlag, RecEotFlag As Integer
Dim Buf, L_Buf As String

Private Sub Form_Load()


' Initialize Display Message
Text1.Text = ""
Label1.Caption = "Receive Data"
Label2.Caption = "Communication with AR/ARK"
Label3.Caption = "Push Start Button"
Command1.Caption = "Start"
' Initialize MSComm Control
MSComm1.CommPort = 1
MSComm1.Settings = "9600,o,8,1"
MSComm1.RThreshold = 1

End Sub

Private Sub Command1_Click()

Text1.Text = ""
Label3.Caption = "Initializing..."
' Open COM1 Port
If MSComm1.PortOpen = False Then
MSComm1.PortOpen = True
End If
L_Buf = ""
RecEotFlag = False
TimeupFlag = False
Timer1.Enabled = False
Label3.Caption = "Waiting for DATA receiving"
Do ' Waiting for Data
DoEvents
If RecEotFlag = True Then
Exit Do
End If
Loop Until TimeupFlag = True

If RecEotFlag = True Then


Label3.Caption = "Finished DATA receiving" & vbNewLine & "Push Start Button"
Else
Label3.Caption = "EOT Error!!" & vbNewLine & "Push Start Button"
End If
If MSComm1.PortOpen = True Then
MSComm1.PortOpen = False
End If
End Sub

Private Sub MSComm1_OnComm()


Select Case MSComm1.CommEvent
Case comEvReceive ' Receive Data
Buf = MSComm1.Input
L_Buf = L_Buf + Buf
Text1.Text = Text1.Text + Buf
If TimeoutFlag = False Then
Timer1.Enabled = True ' Timer Start
End If
Timer1.Interval = 1000 ' Set interval time

24
RS-232C COMMUNICATION: Communication Program

s = Len(L_Buf)
If s > 4 Then
If Mid$(L_Buf, s - 4, 1) = Chr(4) Then ' Search EOT before checksum
RecEotFlag = True
Timer1.Enabled = False
End If
End If
Case comEvCTS
Case comEvDSR
Case comEvCD
Case comEvRing
Case comEvEOF
Case Else
MsgBox "Error", vbCritical
End Select
End Sub 2

Private Sub Form_Unload(Cancel As Integer)


If MSComm1.PortOpen = True Then
MSComm1.PortOpen = False
End If
End Sub

Private Sub Timer1_Timer()


TimeupFlag = True
Timer1.Enabled = False
End Sub

25
RS-232C COMMUNICATION: Communication Program

26
3. LAN COMMUNICATION

3.1 Outline of LAN Communication

3.1.1 Outline of communication function


The ARK-530A/510A creates XML (measurement results and information) and JPEG (measurement
ring image) files of the measurement data to be used in electronic filing systems for ophthalmology,
and it comes equipped with the LAN interface that outputs those created files to shared folders in
external computers using CIFS (Common Internet File System). Chapter 3 explains the method of
3
receiving measurement data from the ARK-530A/510A using this LAN interface.

{ Basic communication specifications

1 Basic specifications CIFS


2 Connector RJ-45
3 Standard 10/100Base-TX
4 Cable Straight
5 Compatible OS Windows 2000, XP, Vista

Network settings such as the IP address and file share of external computers need to be specified accord-
ing to the network setting manual of the AR-310A, AR-330A, AR-360A, ARK-510A, ARK-530A, ARK-560A.

{ Cable connection
Connect the LAN cable to the LAN connector on the underside of the device.
Connect the other end of the LAN cable to the hub to which the receiver PC is connected.

CAUTION • Be sure to connect to the PC via a network hub.


Do not connect to the PC directly. Connection failure may occur.

Network hub

LAN cable

ARK-530A/510A Receiver PC

27
LAN COMMUNICATION: Outline of LAN Communication

3.1.2 Reception structure of measurement data


Measurement data transmitted from the ARK-530A/510A is captured by the receiver PC as shown in
the illustration below.

Receiver PC

Filing software
Transmission of measured
data from the device via LAN
Database

Shared folder

XM L JPG Extraction and storage of


measured data
Measured data

Measurement data transmitted via LAN are written in the shared folder set in the receiver PC. Mea-
surement data is written in XML format in the shared folder. When there is image data, JPEG format
files are written in the shared folder. Then, measurement data is extracted by filing software and saved
in the database.

28
LAN COMMUNICATION: Data Format

3.2 Data Format

3.2.1 Folder configuration


Transmitted data is saved in the shared folder and lower levels in the folder structure shown below.
If data has not been captured in the receiver software, check whether data is written in any folder
below including device error code.
When captured properly, transmitted measurement data is erased by the receiver software.
Therefore, it cannot be checked.

Shared folder RKT Measurement data


TXT
(XML file) 3

JPG Image data


(JPEG file)

3.2.2 Measurement data (image data) output file


There are two types of output files normally produced: measurement data and image data (AR ring
image).

One file for one patient


Measurement data
All sets of data such as right and left eyes, AR, and KM are output to one XML file.
Image data One file for each eye, 2 files
(AR ring image) 480×480 8-bit gray scale JPEG compression 75

When no style sheet file (RKT_style.xsl) is found in the TXT folder, a style sheet file is also output.
When a style sheet file exists, a new file is not ouput.

29
LAN COMMUNICATION: Data Format

{ File name
File names of measurement data (image data) transmitted from the device to the receiver PC are as fol-
lows:
ID characters that cannot be used for file names are all converted to tilde (∼).

Measurement data (XML file)


Delimiter (underbar)

ARK ABCDEFGHIJKLMN 20071109103057 . xml

XML extension
Header 3 characters fixed ID14 characters fixed Date and time 14 characters fixed (3 characters fixed)
ARK (If no characters, space is entered.) (YYYYMMDDHHMMSS)

Image data (JPEG file)


Type (A = AR ring image)
Delimiter (underbar) Right of left eye (R/L) Unit (1 fixed)

ARK ABCDEFGHIJKLMN 20071109103057RA1 . jpg

Header 3 characters fixed ID14 characters fixed Date and time 14 characters fixed JPEG extension
ARK (If no characters, space is entered.) (YYYYMMDDHHMMSS) (3 characters fixed)

3.2.3 Response to data acquisition


There are two device modes. One is to write data to the shared folder and the other is to confirm data
reception.
Data acquisition is checked by the device monitoring that the XML file of measurement data is no
longer present. On the receiving end, after a data file is produced, the existing data is read out and
deleted or renamed.
The device indicates an error if the XML file remains present after 5 seconds of file writing (JPEG files
are not monitored.)

30
LAN COMMUNICATION: Data Format

3.2.4 XML file configuration


Tags for data which have not been measured are not output. For example, when only the right eye is
measured, there are no left-eye tags. Regardless of the print format and communication format of the
parameter, all output-enabled data are output.

Common data Version, date and time, or such


(No tags) Patient data
Measurement conditions
Right eye data AR data Measurement data (1 to 10)
Median value
Trial lens data
Contact lens data
KM data Measurement data (1 to 10)
Median value 3
Sagittal measurement data
KM periphery
Measurement data (1 to 10)
Median value
CS (Corneal Size) data
PS (Pupil Size) data
Left eye data Same as right eye
PD (Pupillary Distance)
data

3.2.5 Style sheet


XML files are supported by a style sheet. They cannot be displayed in Internet Explorer without style
sheet files (RKT_style.xsl) in the TXT folder. (Use a text editor to check the contents.)
When there is no RKT_style.xsl file in the TXT folder, it is automatically produced when measurement
data is received. An existing RKT_style.xsl file is not overwritten.
Please note that when the program is changed using the device, that style sheet does not become the
new style sheet unless the existing RKT_style.xsl file is manually deleted.
Creating a unique style sheet in the TXT folder allows data to be displayed in the unique format.

31
LAN COMMUNICATION: Data Format

3.2.6 XML file sample


This is not a collection of actual measurement data but is only a sample for explanation.

<?xml version="1.0" encoding="UTF-16"?> XML header


<?xml-stylesheet type="text/xsl" href="RKT_style.xsl"?> Style sheet
<Data> Data tag
<Company>NIDEK</Company> Company name
<ModelName>ARK-530A</ModelName> Model name
<ROMVersion>9.99 /1.03</ROMVersion> ROM version (software/FPGA)
<Version>1.00</Version> Format version (differs from software version)
<Date>2008/03/28</Date> Date (Y/M/D)
<Time>14:20:52</Time> Time (H/M/S)
<Patient> Patient tag
<No.>0193</No.> Patient No.
<ID>ABCDEFGHIJKLMN</ID> Patient ID
</Patient>
<Comment>========================</Comment> Comments
<VD>0.00 mm</VD> VD
<WorkingDistance>28 inch</WorkingDistance> Working distance
<DiopterStep>0.25D</DiopterStep> Diopter step
<AxisStep>1º</AxisStep> Axis step
<CylinderMode>+</CylinderMode> Cylinder mode (-, +, MIX)
<RefractiveIndex>1.3375</RefractiveIndex> Refractive index (ARK only)
<R> Tag for right eye
<AR> AR data tag
<ARList No = "1"> Measurement data tag (1 to 10)
<Sphere>-9.25</Sphere> SPH value
<Cylinder>+3.25</Cylinder> CYL value
<Axis>4</Axis> Axis
<CataractMode>ON</CataractMode> CAT mode (does not exist for OFF)
<ConfidenceIndex>9</ConfidenceIndex> Confidence index (9 to 5, E)
<SE>-8.25</SE> SE value
</ARList>
<ARList No = "2">
<Error>COVR </Error> Error
</ARList>
(Repeated in accordance with the number
of measurements)
<ARMedian> Median value tag
<Sphere>-10.25</Sphere> SPH value
<Cylinder>+4.00</Cylinder> CYL value
<Axis>4</Axis> Axis
<SE>-8.25</SE> SE value
</ARMedian>
<TrialLens> Trial lens tag
<Sphere>-6.25</Sphere> SPH value
<Cylinder>- 4.00</Cylinder> CYL value
<Axis> 94</Axis> Axis
</TrialLens>

32
LAN COMMUNICATION: Data Format

<ContactLens> Contact lens tag


<Sphere>-10.25</Sphere> SPH value
<Cylinder>+4.00</Cylinder> CYL value
<Axis>4</Axis> Axis
<SE>- 8.25</SE> SE value
</ContactLens>
<RingImage> AR ring image file name
ARK 20080328142052RA1.jpg
</RingImage>
</AR>
<KM> KM data tag
<LMList No = "1"> Measurement data tag (1 to 10)
<R1> R1 data tag
<Radius>8.01</Radius> mm data
<Power>42.25</Power> Diopter data 3
<Axis>0</Axis> Axis
</R1>
<R2> R2 data tag
<Radius>8.01</Radius> mm data
<Powe >42.25</Power> Diopter data
<Axis> 90</Axis> Axis
</R2>
<Average> Average data tag
<Radius>8.01</Radius> mm data
<Power>42.25</Power> Diopter data
</Average>
<KMCylinder> Cylinder tag
<Power>+ 0.00</Power> Diopter data
<Axis>0</Axis> Axis
</KMCylinder>
</KMList>
(Repeated in accordance with the number
of measurements)
<KMMedian> Median value tag
<R1> R1 data tag
<Radius>8.01</Radius> mm data
<Power>42.25</Power> Diopter data
<Axis>0</Axis> Axis
</R1>
<R2> R2 data tag
<Radius>8.01</Radius> mm data
<Power>42.25</Power> D iopter data
<Axis> 90</Axis> Axis
</R2>
<Average> Average data tag
<Radius>8.01</Radius> mm tag
<Power>42.25</Power> Diopter tag
</Average>

33
LAN COMMUNICATION: Data Format

<KMCylinder> Cylinder tag


<Power>+0.00</Power> Diopter data
<Axis>0</Axis> Axis
</KMCylinder>
</KMMedian>
<Sagittal> Sagittal tag
<FixationAngle>25<FixationAngle> Fixation angle
<SagittalAxis>25<SagittalAxis> Sagittal axis
<SUP>8.02</SUP> Superior side
<INF>8.02</INF> Inferior side
<TEM>8.00</TEM> Temporal side
<NAS>7.98</NAS> Nasal side
<Topometry>
<SUP>8.02</SUP> Superior side
<INF>8.02</INF> Inferior side
<TEM>8.00</TEM> Temporal side
<NAS>7.98</NAS> Nasal side
<Rh>8.00</Rh> Average of corneal curvature on horizontal meridian

<Rv>8.02</Rv> Average of corneal curvature on vertical meridian

<Ro>8.01</Ro> Average of corneal curvature at the center


<ASTc>+0.00</ASTc> Corneal cylinder at the center
<dRo>+0.00</dRo> Difference of corneal curvature between R1 and R2

<ASTp>+0.16</ASTp> Corneal cylinder at the periphery


<dAST>-0.16</dAST> Difference of corneal cylinder
</Topometry> between the center and peripheral
<Eccentricity>
<SUP>+0.11</SUP> Superior side
<INF>+0.11</INF> Inferior side
<TEM>-0.11</TEM> Temporal side
<NAS>-0.20</NAS> Nasal side
<eh>-0.16</eh> Eccentricity on horizontal meridian
<ev>+0.11</ev> Eccentricity on vertical meridian
<E>-0.08</E> Total Eccentricity
</Eccentricity>
</Sagittal>
<NAS>-0.20</NAS>
<eh>-0.16</eh>
<ev>+0.11</ev>
<E>-0.08</E>
</Eccentricity>
</Sagittal>
<Peripheral> KM peripheral tag
<KMList No = "1"> Measurement data tag (1 to 10)
<R1> R1 data tag
<Radius>7.95</Radius> mm data
<Power>42.50</Power> Diopter data
<Axis>0</Axis> Axis
</R1>

34
LAN COMMUNICATION: Data Format

<R2> R2 data tag


<Radius>7.94</Radius> mm data
<Power>42.50</Power> Diopter data
<Axis>90</Axis> Axis
</R2>
<Average> Average data tag
<Radius>7.95</Radius> mm data
<Power>42.50</Power> Diopter data
</Average>
<KMCylinder> Cylinder tag
<Power>+0.00</Power> Diopter data
<Axis>0</Axis> Axis
</KMCylinder>
</KMList>
(Repeated in accordance with the number
of measurements)
3
<KMMedian> Median value tag
<R1> R1 data tag
<Radius>7.95</Radius> mm data
<Power>42.50</Power> Diopter data
<Axis>0</Axis> Axis
</R1>
<R2> R2 data tag
<Radius>7.94</Radius> mm data
<Power>42.50</Power> Diopter data
<Axis>90</Axis> Axis
</R2>
<Average> Average data tag
<Radiu>7.95</Radius> mm data
<Power>42.50</Power> Diopter data
</Average>
<KMCylinder> Cylinder tag
<Power>+0.00</Power> Diopter tag
<Axis>0</Axis> Axis
</KMCylinder>
</KMMedian>
</Peripheral>
</KM>
<CS> CS (corneal size) tag
<CSList No = "1"> List tag (currently fixed at 1)
<Size>12.1</Size> Corneal size
</CSList>
</CS>
<PS> PS (pupil size) tag
<PSList No = "1"> List tag (currently fixed at 1)
<Size>4.7</Size> Size
<Lamp>ON</Lamp> Lamp (ON, OFF)
</PSList>
</PS>
</R>

35
LAN COMMUNICATION: Data Format

<L> Tag for left eye

(Same as right eye)


</L>
PD tag
<PD>
Measurement data tag (1 to 5)
<PDList No = "1">
Distance vision
<FarPD>26</FarPD>
Distance vision for right eye
<RPD>8</RPD>
Distance vision for left eye
<LPD>18</LPD>
Near vision
<NearPD>26</NearPD>
</PDList >
(Repeated in accordance with the number
of measurements)

</PD>

</Data>

36
4. EXAMPLE OF RECEIVED DATA

4.1 Example of Measurement Data Received by PC

{ Sample printout

Patient number
Patient ID
Name and sex
Data and time of measurement
Vertex distance
Near working distance

Right eye: 1st, Normal data


Right eye: 2nd, Error (CYL range over error)
Right eye: 3rd, Normal data 4
Right eye: 4th, Normal data
Right eye: 5th, Normal data
Right eye: Median values

Right eye: Trial lens data


Right eye: CL conversion data
Right eye: SE value data for contact lens

KM measurement (center)
Right eye: 1st, KM data

Right eye: 2nd, KM data

Right eye: 3rd, KM data

Right eye: KM median values

KM peripheral measurement
Right eye: 1st, KM data (P)

Right eye: KM median values (P)

Right eye: Corneal size measurement and pupil size measure-


ment

37
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC

Left eye: 1st, Normal data


Left eye: 2nd, Normal data
Left eye: 3rd, Error (Negative SPH range over error)
Left eye: 4th, Normal data
Left eye: Median values

Left eye: Trial lens data


Left eye: CL conversion data
Left eye: SE value data for contact lens

KM measurement (center)
Left eye: 1st, KM measurement data

Left eye: 2nd, KM measurement data

Left eye: 3rd, KM measurement data

Left eye: KM median values

KM peripheral measurement
Left eye: 1st, KM data (P)

Left eye: KM median values (P)

Left eye: Corneal size measurement and pupil size measurement

Pupillary distance: Distance and near pupillary distances


Pupillary distance: Distance and near pupillary distances
(with monocular PD)
Comment

38
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC

{ Data to be transmitted for producing the above sample printout


(1) RS-232C communication
DRM
Header for AR measurement data
IDNIDEK/ARK-530A
Company name and model name
NO0006
Patient number
IP012345678901234567890
Patient ID
DA2006/01/09.10:50AM
Data and time of measurement
VD12.00
Vertex distance
WD40
Near working distance
OL-04.25-00.25093
Left eye: AR median values
OL-04.37-00.370909
4th, Normal data
EL-O
3rd, Error (Negative SPH range over error)
OL-04.25-00.250939
2nd, Normal data
OL-04.12-00.000008
1st, Normal data
OR+00.25-00.37084
Right eye: AR median values
OR+00.25-00.370869
5th, Normal data
OR+00.25-00.500958
4th, Normal data
OR+00.25-00.500848
3rd, Normal data
ERCO
2nd, Error (CYL range over error)
OR+00.25-00.370839 4
1st, Normal data
CL-04.00-00.75095
Left eye: CL conversion data
CR+00.25-00.25085
Right eye: CL conversion data
TL-04.00-00.75095
Left eye: Trial lens data
TR+00.00+00.25175
Right eye: Trial lens data
PD68353363
Pupillary distance: Distance PD (with monocular PD) and near PD
PD67????62
Pupillary distance: Distance PD and near PD
DKM
Header for KM measurement data
L07.9507.7117607.83
Left eye: KM median values (mm)
DL42.4543.7717643.11-01.32
KM median values (D)
L07.9507.7117607.83
3rd, KM data (mm) KM measurement
DL42.4543.7717643.11-01.32 (center)
KM data (D)
L07.9507.7117607.83
2nd, KM data (mm)
DL42.4543.7717643.11-01.32
KM data (D)
L07.9607.7417707.85
1st, KM data (mm)
DL42.4043.6017743.00-01.20
KM data (D)
EL07.9607.7517607.86
Left eye: KM median values (mm)
HL42.5043.5417643.02-01.04
KM median values (D)
EL07.9707.7417607.84
3rd, KM data (mm)
HL42.3843.6017642.99-01.22 KM peripheral
KM data (D) measurement
EL07.9607.8017607.88
2nd, KM data (mm)
HL42.5043.2517642.88-00.75
KM data (D)
EL07.9507.7117607.83
1st, KM data (mm)
HL42.4543.7717643.11-01.32
KM data (D)
R07.8607.5317507.70
Right eye: KM median values (mm)
DR42.9444.8217543.88-01.88
KM selected data (D)
R07.8707.5317407.70
3rd, KM data (mm)
DR42.8844.8217443.85-01.94 KM measurement
KM data (D)
R07.8607.5317507.70 (center)
2nd, KM data (mm)
DL42.9444.8217543.88-01.88
KM data (D)
L07.8607.5317507.70
1st, KM data (mm)
DL42.9444.8217543.88-01.88
KM data (D)

39
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC

ER07.9707.9117407.94 . . . . . . . . . . . . Left eye: KM median values (mm)


HR42.3342.7517442.54-00.42 . . . . . . KM selected data (D)
ER07.9807.9617407.97 . . . . . . . . . . . 3rd, KM data (mm)
HR42.2542.5017442.83-01.25 . . . . . . KM data (D) KM peripheral
ER07.9607.8017407.88 . . . . . . . . . . . measurement
2nd, KM data (mm)
HR42.5043.2517442.88-00.75 . . . . . . KM data (D)
ER07.9807.9617407.97 . . . . . . . . . . . 1st, KM data (mm)
HR42.2542.5017442.38-00.25 . . . . . . KM data (D)
SL11.5 . . . . . . . . . . . . . . . . . . . . . . . . . Left eye: Corneal size measurement
PL06.0F . . . . . . . . . . . . . . . . . . . . . . . . Left eye: Pupil size measurement
SR11.0 . . . . . . . . . . . . . . . . . . . . . . . . . Right eye: Corneal size measurement
PR06.0N ..................... Right eye: Pupil size measurement

The following marks represent the following control codes:


= SOH 01H = ETB 17H = STX 02H = EOT 04H
When the CR CODE parameter is set to YES, the CR is added after ETB.
When the “71. I/F MODE” parameter is set to “NCP10”, four digits of checksum are added to the
data after .

40
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC

(2) LAN communication

<?xml version="1.0" encoding="UTF-16"?> XML header


<?xml-stylesheet type="text/xsl" href="RKT_style.xsl"?> Style sheet
<Data> Data tag
<Company>NIDEK</Company> Company name
<ModelName>ARK-530A</ModelName> Model name
<ROMVersion>9.99 /1.03</ROMVersion> ROM version (software/FPGA)
<Version>1.00</Version> Format version (differs from software version)
<Date>2006/01/09</Date> Date (Y/M/D)
<Time>10:50:52</Time> Time (H/M/S)
<Patient> Patient tag
<No.>00006</No.> Patient No.
<ID>012345678901234</ID> Patient ID
</Patient>
<Comment>========================</Comment> Comments
<VD>12.00 mm</VD> VD
<WorkingDistance>40 cm</WorkingDistance> Working distance
<DiopterStep>0.25D</DiopterStep> Diopter step
<AxisStep>1º</AxisStep> Axis step
<CylinderMode>MIX</CylinderMode> Cylinder mode (-, +, MIX)
<RefractiveIndex>1.3375</RefractiveIndex> Refractive index (ARK only) 4
<R> Tag for right eye
<AR> AR data tag
<ARList No = "1"> Measurement data tag (1)
<Sphere>+0.25</Sphere> SPH value
<Cylinder>-0.37</Cylinder> CYL value
<Axis>83</Axis> Axis
<CataractMode>ON</CataractMode> CAT mode (does not exist when set
<ConfidenceIndex>9</ConfidenceIndex> to OFF) mode
<SE>+0.00</SE> Confidence index (9 to 5, E)
</ARList> SE value
<ARList No = "2"> Measurement data tag (2)
<Error>COVR </Error> Error
</ARList>
(Repeated in accordance with the number
of measurements, maximum of five
measurements)

<ARMedian> Median value tag


<Sphere>-0.25</Sphere> SPH value
<Cylinder>-0.37</Cylinder> CYL value
<Axis>84</Axis> Axis
<SE>+0.00</SE> SE value
</ARMedian>
<TrialLens> Trial lens tag
<Sphere>+0.00</Sphere> SPH value
<Cylinder>+0.25</Cylinder> CYL value
<Axis> 175</Axis> Axis
</TrialLens>
<ContactLens> Contact lens tag
<Sphere>+0.25</Sphere> SPH value
<Cylinder>-0.25</Cylinder> CYL value
<Axis>85</Axis> Axis
<SE>+ 0.00</SE> SE value
</ContactLens>

41
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC

<RingImage> AR ring image file name


ARK 20060109105052RA1.jpg
</RingImage>
</AR>
<KM> KM data tag
<LMList No = "1"> Measurement data tag (1)
<R1> R1 data tag
<Radius>7.88</Radius> mm data
<Power>42.94</Power> Diopter data
<Axis>175</Axis> Axis
</R1>
<R2> R2 data tag
<Radius>7.53</Radius> mm data
<Powe >44.82</Power> Diopter data
<Axis> 85</Axis> Axis
</R2>
<Average> Average data tag
<Radius>7.70</Radius> mm data
<Power>43.88</Power> Diopter data
</Average>
<KMCylinder> Cylinder tag
<Power>-1.88</Power> Diopter data
<Axis>175</Axis> Axis
</KMCylinder>
</KMList>
(Repeated in accordance with the number
of measurements, maximum of three
measurements)
<KMMedian> Median value tag
<R1> R1 data tag
<Radius>7.86</Radius> mm data
<Power>42.94</Power> Diopter data
<Axis>175</Axis> Axis
</R1>
<R2> R2 data tag
<Radius>7.53</Radius> mm data
<Power>44.82</Power> Diopter data
<Axis> 85</Axis> Axis
</R2>
<Average> Average data tag
<Radius>7.70</Radius> mm data
<Power>43.88</Power> Diopter data
</Average>
<KMCylinder> Cylinder tag
<Power>-1.88</Power> Diopter data
<Axis>175</Axis> Axis
</KMCylinder>
</KMMedian>

42
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC

<Sagittal> Sagittal tag


<FixationAngle>25<FixationAngle> Fixation angle
<SagittalAxis>25<SagittalAxis> Sagittal axis
<SUP>8.02</SUP> Superior side
<INF>8.02</INF> Inferior side
<TEM>8.00</TEM> Temporal side
<NAS>7.98</NAS> Nasal side
<Topometry>
<SUP>8.02</SUP> Superior side
<INF>8.02</INF> Inferior side
<TEM>8.00</TEM> Temporal side
<NAS>7.98</NAS> Nasal side
<Rh>8.00</Rh> Average of corneal curvature on horizontal meridian

<Rv>8.02</Rv> Average of corneal curvature on vertical meridian

<Ro>8.01</Ro> Average of corneal curvature at the center


<ASTc>+0.00</ASTc> Corneal cylinder at the center
<dRo>+0.00</dRo> Difference of corneal curvature between R1 and R2

<ASTp>+0.16</ASTp> Corneal cylinder at the periphery


<dAST>-0.16</dAST> Difference of corneal cylinder
</Topometry> between the center and peripheral
4
<Eccentricity>
<SUP>+0.11</SUP> Superior side
<INF>+0.11</INF> Inferior side
<TEM>-0.11</TEM> Temporal side
<NAS>-0.20</NAS> Nasal side
<eh>-0.16</eh> Eccentricity on horizontal meridian
<ev>+0.11</ev> Eccentricity on vertical meridian
<E>-0.08</E> Total Eccentricity
</Eccentricity>
</Sagittal>
<Peripheral> KM peripheral tag
<KMList No = "1"> Measurement data tag (1)
<R1> R1 data tag
<Radius>7.98</Radius> mm data
<Power>42.25</Power> Diopter data
<Axis>174</Axis> Axis
</R1>
<R2> R2 data tag
<Radius>7.96</Radius> mm data
<Power>42.50</Power> Diopter data
<Axis>84</Axis> Axis
</R2>
<Average> Average data tag
<Radius>7.97</Radius> mm data
<Power>42.38</Power> Diopter data
</Average>
<KMCylinder> Cylinder tag
<Power>-0.25</Power> Diopter data
<Axis>174</Axis> Axis
</KMCylinder>
</KMList>
(Repeated in accordance with the number
of measurements, maximum of three
measurements)

43
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC

<KMMedian> Median tag


<R1> R1 data tag
<Radius>7.95</Radius> mm data
<Power>42.50</Power> Diopter data
<Axis>0</Axis> Axis
</R1>
<R2> R2 data tag
<Radius>7.94</Radius> mm data
<Power>42.50</Power> Diopter data
<Axis>90</Axis> Axis
</R2>
<Average> Average data tag
<Radiu>7.95</Radius> mm data
<Power>42.50</Power> Diopter data
</Average>
<KMCylinder> Cylinder tag
<Power>+0.00</Power> Diopter data
<Axis>0</Axis> Axis
</KMCylinder>
</KMMedian>
</Peripheral>
</KM>
<CS> CS (corneal size) tag
<CSList No = "1"> List tag (currently fixed at 1)
<Size>11.0</Size> Corneal size
</CSList>
</CS>
<PS> PS (pupil size) tag
<PSList No = "1"> List tag (currently fixed at 1)
<Size>6.0</Size> Size
<Lamp>ON</Lamp> Lamp (ON, OFF)
</PSList>
</PS>
</R>
<L> Tag for left eye

(Same as right eye)


</L>
<PD> PD tag
<PDList No = "1"> Measurement data tag (1)
<FarPD>67</FarPD> Distance vision
<NearPD>62</NearPD> Near vision
</PDList >
<PDList No = "2"> Measurement data tag (2)
<FarPD>68</FarPD> Distance vision
<RPD>35</RPD> Right eye for distance vision
<LPD>33</LPD> Left eye for distance vision
<NearPD>63</NearPD> Near vision
</PDList >

(Repeated in accordance with the number


</PD> of measurements)
</Data>

44
EXAMPLE OF RECEIVED DATA: Sample Printout of KM Data when the I/F FORMAT Parameter is Set to Short

4.2 Sample Printout of KM Data when the I/F FORMAT Parameter


is Set to Short

{ Sample printout
Patient number
Name and sex
Data and time of measurement

Right eye: KM median values; KM measurement (center)

Right eye: KM median values; KM peripheral measurement

4
Right eye: Corneal size and pupil size measurements

Left eye: KM median values; KM measurement (center)

Left eye: KM median values; KM peripheral measurement

Left eye: Corneal size and pupil size measurements

Comments

{ Data to be transmitted for producing the above sample printout


DKM . . . . . . . . . . . . . . . . . . . . . . . . . Header for KM measurement data
NO0006 ....................... Patient number
DA2006/01/09.10:50AM . . . . . . . . . . . Data and time of measurement
L07.9507.7117607.83 . . . . . . . . . . . . Left eye: KM median values (mm); KM measurement (center)
EL07.9507.7117607.83 . . . . . . . . . . . . Left eye: KM median values (mm); KM peripheral measurement
R07.8607.5317507.70 . . . . . . . . . . . Right eye: KM median values (mm); KM measurement (center)
ER07.9507.7117607.83 ......... Right eye: KM median values (mm); KM peripheral measurement

The above sample example is produced when the SD command is CKM. (See (2) SD command
of 2.1.) Because the “72. I/F FORMAT” parameter is set to “SHORT”, only KM median values
(mm) are transmitted.
The company name, model name, corneal size and pupil size data are not transmitted.

45
EXAMPLE OF RECEIVED DATA: Transmission of Sagittal Measurement Data

4.3 Transmission of Sagittal Measurement Data

The transmission format of each data of Sagittal measurement is described hereunder.


Sagittal measurement data are shown in the print out sample as below from following to KM
measurement data. Basic transmitting and receiving sequences are stipulated in the aforemen-
tioned “1 OUTLINE OF COMMUNICATION” (Page 3).

Printed data by ARK-530A Transmission format

DKM
NO.0001 %4

DAMAY/18/2006.10:50AM %4

L08.5107.8410008.18 % 4

DL39.6643.0510041.36-03.39 %4

FA25 %4

LS07.8608.53+0.16A %4

LI07.8608.53+0.16A % 4

LT08.5507.87+0.24A %4

LN08.5507.87+0.24A %4

LE+0.24+0.16+0.20 % 4

LR07.8708.5208.18+0.67 %4

LA-03.39-03.26-00.13 %4 %4

= 01H SOH
= 02H STX
= 17H ETB
= 04H EOT
%4 = 0DH % 4 is added in accodance with setting.

46
EXAMPLE OF RECEIVED DATA: Transmission of Sagittal Measurement Data

Header : This signifies KM measurement data to be transmitted.


Patient number
Measurement date and time
KM measurement (mm) data : R1(5), RS(5), AXIS(3), AVE(5)
KM measurement (D) data : R1(5), AXIS(3), AVE(5), CYL(6)
Fixed angle in Sagittal measurement : FIXED ANGLE(2)
Sagittal value for SUP. direction : SAGIT1(5), SAGIT2(5), ECC(5), A/F(1)
Sagittal value for INF. direction : SAGIT1(5), SAGIT2(5), ECC(5), A/F(1)
Sagittal value for TEM. direction : SAGIT1(5), SAGIT2(5), ECC(5), A/F(1)
Sagittal value for NAS. direction : SAGIT1(5), SAGIT2(5), ECC(5), A/F(1)

Among the each Sagittal values from to their meanings are :


SAGIT1 : Measurement value
SAGIT2 : Measurement value including dRO
ECC : Each eccentricity 4
A/F : Whether calculation for conversion axis is made or not.
(A : Conversion of axis is made.)
Horizontal, Vertical and Total eccentricity : eh(5), ev(5), E(5)
Each corneal radius values : Rh(5), Rv(5), Ro(t), dRo(5)
Horizontal corneal radius average value : (Rh)
Vertical corneal radius average value : (Rv)
Central corneal radius average value : (Ro)
Central corneal radius differences : (dRo)

Cylindrical diopters and its differences at center and peripheral : ASTc(6), ASTp(6), dAST(6)
Central corneal cylinder diopter : (ASTc)
Peripheral corneal cylinder diopter : (ASTp)
Difference of corneal cylinder diopter
between center and peripheral : (dAST)

* Values in the parentheses ( ) show the data length.

* When data are output, all data are printed out with the above format regardless the Sagittal printing
format.

47
EXAMPLE OF RECEIVED DATA: Interface Error Messages

4.4 Interface Error Messages

If any error occurs during communications with the external computer, the corresponding error
message is displayed on the LCD screen.

{ Error code table

ERROR
Display Description Symptom
CODE

11 ERR011 Time-out error (OUT) in characters Communication breaks during data reception.

Time-out error (OUT) for receiving


12 ERR012 Time-out after the DTR-DSR is effected
data

13 ERR013 Receiving error (OUT) Parity and flaming error

14 ERR014 Receiving code error (OUT) Received code is defective.


15 ERR015 Reply time-out (OUT) Time-out error between sending and receiving

16 ERR016 DTR-DSR error (OUT) Time-out between DTR and DSR

17 ERR017 Data error (OUT) Data error (Improper received data)

18 ERR018 Command error (OUT) Command error (Improper command)

- NO DAT Data empty (OUT) No measurement data

DSR is not flagged while SD command is


21 ERR021 Time-out error (IN) in characters
received.

22 ERR022 Time-out error (IN) for receiving data DSR is not flagged while SD command is sent.

23 ERR023 Receiving error (IN) Received data does not come.

24 ERR024 Receiving code error (IN) Receiving buffer is full.

25 ERR025 Reply time-out (IN) Unreadable command was entered.

26 ERR026 DTR-DSR error (IN) -

27 ERR027 Data error (IN) -

28 ERR028 Command error (IN) -

48
EXAMPLE OF RECEIVED DATA: Interface Error Messages

{ LAN communication error codes

ERROR
Display Description Symptom
CODE
• Check the LAN cable connection.
• File sharing error
700 ERR700 • Check that the IP address or subnet mask is
Windows file sharing error
correct on the NETWORK setting screen.

• Hardware error
703 ERR703 • Replace BA01.
IC error

• DHCP error • There is no DHCP server. Check the DHCP


704 ERR704
The IP address cannot be obtained. server.

• Check the LAN cable connection.


• Network access error
750 ERR750 • Check that the IP address or subnet mask is
Access to the network is not allowed.
correct on the NETWORK setting screen.

• Check that the PC folder specified as the place in


• Network writing error
751 ERR751 which data is saved is a shared folder or that free
Writing to the PC is not allowed.
space is left.

• PC name error
• Check that the computer name specified by the 4
PC NAME parameter on the NETWORK setting
754 ERR754 The specified PC name does not
screen is correct or that LAN is properly
exist.
connected.

• Read-only folder error


• The folder of the connected PC is write-protected.
755 ERR755 The folder in which data is saved is
Disable the write-protect.
read-only attribute.

• Log-on error
Logging on the PC is not possible • Entry in the user name or password field on the
756 ERR756
(The user name or password is NETWORK setting screen is incorrect.
incorrect.)

• Shared folder error


• Check the folder name or whether the folder is set
757 ERR757 The shared folder does not exist.
to share.
(The shared folder name is incorrect.)

• Time-out error
• Reduce the PC processing load. (Reduce the
758 ERR758 Timeout (The PC did not finish the
resident software).
process in a specified time.)

• Delete error • The folder of the connected PC is write-protected.


759 ERR759
PC data cannot be deleted. Disable the write-protect.

• Error during initialization


The network is undergoing
760 ERR760 • Wait and try again.
initialization (requires a certain
amount of time).

• Access authority error • Check the file sharing setting of the shared folder
761 ERR761
File sharing setting is improper. of the connected PC.

• Account error
762 ERR762 The account is disabled. (The user • Enable the account of the connected PC.
setting is improper.)

• Cable connection error


771 ERR771 • Check the LAN cable connection.
The LAN cable is not connected.

49
EXAMPLE OF RECEIVED DATA: Interface Error Messages

ERROR
Display Description Symptom
CODE
• The deleting process of measurement data files
by the receiver software did not finish within the
• ACK error specified time. Check that the software operates
772 ERR772
There is no response from the PC. properly. If it occurs frequently, retry connection
after setting the NETWORK parameter from ACK
to YES.

50

Вам также может понравиться