auto ref/keratometer model ark-530a/ark-510a · 2016. 7. 5. · when the ark-530a/510a receives the...
TRANSCRIPT
September 2009Pages in total - 52
XRK8A*RTZ001B/E
INTERFACE MANUALINTERFACE MANUAL
ARK-530A/ARK-510AARK-530A/ARK-510AAUTO REF/KERATOMETERAUTO REF/KERATOMETER
MoModel
NIDEK CO., LTD. : 34-14, Maehama, Hiroishi-cho, Gamagori, Aichi 443-0038, Japan(Manufacturer) Telephone: +81-533-67-6611
Facsimile: +81-533-67-6610NIDEK CO., LTD : 3F Sumitomo Fudosan Hongo Bldg., 3-22-5, Hongo,(Tokyo Office) Bunkyo-Ku, Tokyo 113-0033, Japan
Telephone: +81-3-5844-2641Facsimile: +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-5750NIDEK 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
1. OUTLINE OF COMMUNICATION. . . . . . . . . . . . . . . . . . . . 31.1 Interface Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2. RS-232C COMMUNICATION . . . . . . . . . . . . . . . . . . . . . . . 52.1 Outline of RS-232C Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
2.1.1 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
2.2 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.2.1 Command format (with “NIDEK”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.2.2 Data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.2.3 CR (Carriage Return) Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2.3 Communication Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192.3.1 Interface between the ARK-530A/510A and external PC . . . . . . . . . . . . . . . . . . . .192.3.2 Flow of sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202.3.3 Sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3. LAN COMMUNICATION . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1 Outline of LAN Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.1.1 Outline of communication function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273.1.2 Reception structure of measurement data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
3.2 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293.2.1 Folder configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293.2.2 Measurement data (image data) output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293.2.3 Response to data acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303.2.4 XML file configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313.2.5 Style sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313.2.6 XML file sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
4. EXAMPLE OF RECEIVED DATA . . . . . . . . . . . . . . . . . . . 374.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
2
:
3
1
1. OUTLINE OF COMMUNICATION
1.1 Interface Type
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/510Ausing the RS-232C interface in Chapter 2 and the LAN interface in Chapter 3.
4
OUTLINE OF COMMUNICATION: Interface Type
5
2
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/510Acomes 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.
This chapter describes the specifications for the interface for data transmission between the ARK-530A/510A and a personal computer, etc.
Basic interface specifications
As the Transmission system, Parity check, and Stop bit length are fixed as above, it is necessary forthe external computer to conform to these 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)
6
RS-232C COMMUNICATION: Outline of RS-232C Communication
Cable connection
Connect the ARK-530A/510A interface port and the serial communication port (RS-232C) ofthe 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 aconversion adapter.
1
2
3
45
67
8
1
9
5
6
External computerSerial communicationport(RS-232C)
ARK-530A/510AInterface connector
D-sub 9P (female) DIN 8P
7
RS-232C COMMUNICATION: Outline of RS-232C Communication
2
2.1.1 Communication sequenceTwo types of the transmission sequences, “NIDEK” and “NCP10”, can be selected by setting the “71.I/F MODE” parameter.
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 complicatedcontrols such as the DTR control, DSR control, RS command control, SD command control, etc., itallows easier communication compared with “NIDEK”. However, with “NCP10”, data transmission inresponse to a request from the personal computer is not available. Select a transmission sequencethat suits your needs or purposes.
When the I/F MODE parameter is set to NIDEK
DTR/DSR control:
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.
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 PC
Possible Not possible
Checksum data Not present Present
Data
Data
Same timing
Same timing
Sending end
Receivingend
8
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 lowstate on a line. The DTR signal of the external computer does not affect the transmission under eithercondition.In addition, since the RS/SD command control is not performed, pressing the print button ( )sends the data directly.
9
RS-232C COMMUNICATION: Data Format
2
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 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:
2) For requesting KM measurement data:
3) For requesting AR and KM measurement data:
3 CL command
Sends a request to clear measurement data to the ARK-530A/510A from the external com-puter.
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 thenext patient is measured.
H: HEX (Hexadecimal)
SOH C * * STX R S ETB EOT
01H 43H 2AH 2AH 12H 52H 53H 17H 04H
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
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
10
RS-232C COMMUNICATION: Data Format
2.2.2 Data format
Basic format
1) AR measurement data:
2) KM measurement data:
3) AR and KM measurement data:
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 areadded after “EOT” in each data format.
Data transmitted from the ARK-530A/510A
SOH D R M STX Data ETB Data ETB Data ETB EOT
SOH D K M STX Data ETB Data ETB Data ETB EOT
SOH D R M STX Data ETB Data ETB Data ETB
SOH D K M STX Data ETB Data ETB EOT
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
11
RS-232C COMMUNICATION: Data Format
2
Data
The number inside the parentheses indicates the number of characters transmitted.
1 Company name / Model name
When the “72. I/F FORMAT” parameter is set to “SHORT” and a request for KM data only issent (see “2 SD Command” of 2.1), the company name and model name are not transmitted.
2 Patient number
3 Patient ID
Transfer the data when the patient ID is inputted by the bar code reader.
4 Date and time of measurementWhen the time format is set to “AM/PM”
1) When the “38. DATE FORMAT” parameter is set to “Y/M/D”:
2) When the “38. DATE FORMAT” parameter is set to “M/D/Y”:
3) When the “38. DATE FORMAT” parameter is set to “D/M/Y”:
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
ID code Company name Model name (ARK-510A)
N O 0 1 2 3
No. code Patient number (4)
I P 0 1 2 3 4 5 6 7 • • • 27 28 29 30
IP code Patient ID Transfer the number of inputted letters (maximum 31 letters). (20 letters for printing)
D A 2 0 0 6 . 0 5 . 1 2 . 0 1 : 2 3 P M
Date code Year (4) Month
(2) Date (2) Hour (2) Minute (2)
AM/PM (2)
D A M A Y / 1 2 / 2 0 0 6 . 0 1 : 2 3 P M
Date code Month (3) Date (2) Year (4) Hour (2) Minute
(2)AM/PM
(2)
D A 1 2 / M A Y / 2 0 0 6 . 0 1 : 2 3 P M
Date code Date (2) Month (3) Year (4) Hour (2) Minute
(2)AM/PM
(2)
12
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”:
2) When the “38. DATE FORMAT” parameter is set to “M/D/Y”:
3) When the “38. DATE FORMAT” parameter is set to “D/M/Y”:
5 Vertex distance
6 Near working distance
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 thedata to indicate it was measured by the AR with the CAT measurement mode icon ( ) displayed.
1) Left eye data
2) Right eye data
D A 2 0 0 6 . 0 5 . 1 2 . 0 1 : 2 3
Date code Year (4) Month
(2) Date (2) Hour (2) Minute (2)
D A M A Y / 1 2 / 2 0 0 6 . 0 1 : 2 3
Date code Month (3) Date (2) Year (4) Hour (2) Minute
(2)
D A 1 2 / M A Y / 2 0 0 6 . 0 1 : 2 3
Date code Date (2) Month (3) Year (4) Hour (2) Minute
(2)
V D 1 2 . 0 0
VD code Vertex distance (5)
W D 4 0
WD codeWorking distance
(2)
O L - 0 5 . 2 5 - 0 0 . 7 5 1 0 9 9 *
R/L code (2) SPH (6) CYL (6) AXIS (3) Confidence
code (1)CAT mark
(1)
O R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4 8 *
R/L code (2) SPH (6) CYL (6) AXIS (3) Confidence
code (1)CAT mark
(1)
13
RS-232C COMMUNICATION: Data Format
2
3) Reference value (Confidence index is "E”.)
When “44. ERROR DATA” is set to “YES”, the data whose confidence index (indicates thedegree of reliance) is under 5, can be measure as a reference value. In this case, “E” isadded to the end of the transmitted data.
4) Error data
When “46. ERROR PRINT” is set to “YES”, the measurement errors are stored in memoryand transmitted together with AR measurement data.
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 confidenceindex 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.
O R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4 E *
R/L code (2) SPH (6) CYL (6) AXIS (3) Confidence
E code (1)CAT mark
(1)
E R + 0
ERROR code
Type of error (2)
Type of error Content
+O Positive SPH range over error
-O Negative SPH range over error
CO CYL range over error
14
RS-232C COMMUNICATION: Data Format
8 Contact lens conversion data1) Left eye data
2) Right eye data
When “54. CL PRINT” is set to “NO”, contact lens conversion data is not transmitted.
9 Optimum trial lens data1) Left eye data
2) Right eye data
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, thedata is not transmitted.
10 PD measurement1) When both right and left PD values are measured:
2) When the distance PD value only is measured: ie
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/FFORMAT” parameter is set to “SHORT”, only the latest PD value is transmitted.
C L - 0 5 . 2 5 - 0 0 . 7 5 1 0 9
R/L code (2) SPH (6) CYL (6) AXIS (3)
C R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4
R/L code (2) SPH (6) CYL (6) AXIS (3)
T L - 0 5 . 2 5 - 0 0 . 7 5 1 0 9
R/L code (2) SPH (6) CYL (6) AXIS (3)
T R - 0 5 . 0 0 - 0 0 . 5 0 0 3 4
R/L code (2) SPH (6) CYL (6) AXIS (3)
P D 6 8 3 5 3 3 6 3
PD code (2) PD (2) RPD (2) LPD (2)
N. PD (2)(Near point
PD)
P D 6 8 ? ? ? ? ? ?
PD code (2) PD (2) RPD (2) LPD (2)
N. PD (2)(Near point
PD)
15
RS-232C COMMUNICATION: Data Format
2
11 KM measurements
When median values have been obtained after three or more measurements, the medianvalues are transmitted first and then respective items of data are transmitted (in order ofacquisition 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)
1) Left eye (mm) data
2) Left eye (D) data
3) Right eye (mm) data
4) Right eye (D) data
L 0 7 . 9 5 0 7 . 7 1 1 7 6 0 7 . 8 3
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
D L 4 2 . 4 5 4 3 . 7 7 1 7 6 4 3 . 1 1
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
- 0 1 . 3 2
CYL (6)
R 0 7 . 8 6 0 7 . 5 3 1 7 5 0 7 . 7 0
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
D R 4 2 . 9 4 4 4 . 8 2 1 7 5 4 3 . 8 8
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
- 0 1 . 8 8
CYL (6)
16
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
2) Left eye (D) data
3) Right eye (mm) data
4) Right eye (D) data
E L 0 7 . 9 8 0 7 . 9 6 1 7 4 0 7 . 9 7
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
H L 4 2 . 2 5 4 2 . 5 0 1 7 4 4 2 . 3 8
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
- 0 0 . 2 5
CYL (6)
E R 0 7 . 9 3 0 7 . 9 1 1 7 5 0 7 . 9 2
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
H R 4 2 . 5 0 4 2 . 7 5 1 7 5 4 2 . 6 3
R/L code (2) R1 (5) R2 (5) AXIS (3) AVE (5)
- 0 0 . 2 5
CYL (6)
17
RS-232C COMMUNICATION: Data Format
2
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
2) Right eye data
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
2) Right eye data
“Target lamp” transfers the state of the target lamp during the PS measurement.
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.
The checksum is represented by four hexadecimal digits. The value of the checksum is thesimple sum of “SOH” to “EOT” in the data format. However, the “CR” code is not includedinto the calculation of the checksum when the “CR” code is added.
S L 1 1 . 5
R/L code (2) CS (4)
S R 1 1 . 0
R/L code (2) CS (4)
P L 0 6 . 0 F
R/L code (2) PS (4)
Target lamp (1)
P R 0 6 . 0 N
R/L code (2) PS (4)
Target lamp (1)
N Target lamp ON
F Target lamp OFF
SOH ・・・ ETB EOT 3 2 C F
Data Checksum (4)
CAUTION • Set the “74. BIT LENGTH” parameter to 8.When the parameter is set to 7, the codes that correspond to kana-characters are notexported successfully.
18
RS-232C COMMUNICATION: Data Format
2.2.3 CR (Carriage Return) CodeWhen 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 youto 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
“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”)
“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”)
“CR” code is added to the end of the “ETB” code and the end of data.
SOH C * * STX R S ETB EOT CR
0DH
SOH D R M STX Data ETB CR Data ETB CR Data
ETB CR EOT CR
SOH D R M STX Data ETB CR Data ETB CR Data
ETB CR EOT C1 C2 C3 C4 CR
Checksum
19
RS-232C COMMUNICATION: Communication Program
2
2.3 Communication Program
2.3.1 Interface between the ARK-530A/510A and external PCActual 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 andserial communication port (RS-232C) of the external computer with an interfacecable (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:
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 thesample program is running.
When data is transmitted successfully, measurement data is displayed on the monitor of thecomputer.
ARK-530A
I/F MODE Depending of the sample program
BAUD-RATE 9600
BIT LENGTH 8
CR CODE YES
When the I/F MODE parameter is set to NIDEK When the I/F MODE parameter is set to NCP10
20
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
21
RS-232C COMMUNICATION: Communication Program
2
When the I/F MODE parameter is set to NCP10:
External computer
ARK-530A/510A
22
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 IntegerDim 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
23
RS-232C COMMUNICATION: Communication Program
2
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 Else Label3.Caption = "RS Command Error (Terminated)" & vbNewLine & "Push Start Button" End If If MSComm1.PortOpen = True Then MSComm1.PortOpen = False End IfEnd 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 SelectEnd Sub
Private Sub Form_Unload(Cancel As Integer) If MSComm1.PortOpen = True Then MSComm1.PortOpen = False End IfEnd Sub
Private Sub Timer1_Timer() TimeupFlag = True Timer1.Enabled = FalseEnd Sub
24
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 IntegerDim 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 IfEnd 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
25
RS-232C COMMUNICATION: Communication Program
2
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 SelectEnd Sub
Private Sub Form_Unload(Cancel As Integer) If MSComm1.PortOpen = True Then MSComm1.PortOpen = False End IfEnd Sub
Private Sub Timer1_Timer() TimeupFlag = True Timer1.Enabled = FalseEnd Sub
26
RS-232C COMMUNICATION: Communication Program
27
3
3. LAN COMMUNICATION
3.1 Outline of LAN Communication
3.1.1 Outline of communication functionThe ARK-530A/510A creates XML (measurement results and information) and JPEG (measurementring 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 inexternal computers using CIFS (Common Internet File System). Chapter 3 explains the method ofreceiving measurement data from the ARK-530A/510A using this LAN interface.
Basic communication specifications
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.
1 Basic specifications CIFS
2 Connector RJ-45
3 Standard 10/100Base-TX
4 Cable Straight
5 Compatible OS Windows 2000, XP, Vista
CAUTION• Be sure to connect to the PC via a network hub.Do not connect to the PC directly. Connection failure may occur.
ARK-530A/510A Receiver PC
LAN cable
Network hub
28
LAN COMMUNICATION: Outline of LAN Communication
3.1.2 Reception structure of measurement dataMeasurement data transmitted from the ARK-530A/510A is captured by the receiver PC as shown inthe illustration below.
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 formatfiles are written in the shared folder. Then, measurement data is extracted by filing software and savedin the database.
LMX GPJ
Transmission of measured
data from the device via LAN
Receiver PC
Filing software
Database
Shared folder
Measured data
Extraction and storage of
measured data
29
LAN COMMUNICATION: Data Format
3
3.2 Data Format
3.2.1 Folder configurationTransmitted 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 folderbelow including device error code.
When captured properly, transmitted measurement data is erased by the receiver software.Therefore, it cannot be checked.
3.2.2 Measurement data (image data) output fileThere are two types of output files normally produced: measurement data and image data (AR ringimage).
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.
RKT TXT
JPG
Shared folder Measurement data(XML file)
Image data(JPEG file)
Measurement dataOne file for one patientAll sets of data such as right and left eyes, AR, and KM are output to one XML file.
Image data(AR ring image)
One file for each eye, 2 files480×480 8-bit gray scale JPEG compression 75
30
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)
Image data (JPEG file)
3.2.3 Response to data acquisitionThere are two device modes. One is to write data to the shared folder and the other is to confirm datareception.Data acquisition is checked by the device monitoring that the XML file of measurement data is nolonger present. On the receiving end, after a data file is produced, the existing data is read out anddeleted or renamed.The device indicates an error if the XML file remains present after 5 seconds of file writing (JPEG filesare not monitored.)
ARK ABCDEFGHIJKLMN 20071109103057 . xml
Delimiter (underbar)
Header 3 characters fixed ARK
ID14 characters fixed(If no characters, space is entered.)
Date and time 14 characters fixed(YYYYMMDDHHMMSS)
XML extension(3 characters fixed)
ARK ABCDEFGHIJKLMN 20071109103057RA1 . jpg
Delimiter (underbar)
ID14 characters fixed(If no characters, space is entered.)
Date and time 14 characters fixed(YYYYMMDDHHMMSS)
JPEG extension(3 characters fixed)
Type (A = AR ring image)Right of left eye (R/L) Unit (1 fixed)
Header 3 characters fixedARK
31
LAN COMMUNICATION: Data Format
3
3.2.4 XML file configurationTags for data which have not been measured are not output. For example, when only the right eye ismeasured, there are no left-eye tags. Regardless of the print format and communication format of theparameter, all output-enabled data are output.
3.2.5 Style sheetXML files are supported by a style sheet. They cannot be displayed in Internet Explorer without stylesheet 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 measurementdata 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 thenew 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.
Common data(No tags)
Version, date and time, or suchPatient dataMeasurement conditions
Right eye data AR data Measurement data (1 to 10)Median valueTrial lens dataContact lens data
KM data Measurement data (1 to 10)Median valueSagittal measurement dataKM peripheryMeasurement data (1 to 10)Median value
CS (Corneal Size) dataPS (Pupil Size) data
Left eye data Same as right eyePD (Pupillary Distance) data
32
LAN COMMUNICATION: Data Format
3.2.6 XML file sampleThis is not a collection of actual measurement data but is only a sample for explanation.
<?xml version="1.0" encoding="UTF-16"?><?xml-stylesheet type="text/xsl" href="RKT_style.xsl"?>
XML headerStyle sheet
<Data><Company>NIDEK</Company><ModelName>ARK-530A</ModelName><ROMVersion>9.99 /1.03</ROMVersion><Version>1.00</Version><Date>2008/03/28</Date><Time>14:20:52</Time>
Data tagCompany nameModel nameROM version (software/FPGA)Format version (differs from software version)Date (Y/M/D)Time (H/M/S)
<Patient><No.>0193</No.><ID>ABCDEFGHIJKLMN</ID>
</Patient>
Patient tagPatient No.Patient ID
<Comment>========================</Comment><VD>0.00 mm</VD><WorkingDistance>28 inch</WorkingDistance><DiopterStep>0.25D</DiopterStep><AxisStep>1º</AxisStep><CylinderMode>+</CylinderMode><RefractiveIndex>1.3375</RefractiveIndex>
CommentsVDWorking distanceDiopter stepAxis stepCylinder mode (-, +, MIX)Refractive index (ARK only)
<R><AR>
<ARList No = "1"><Sphere>-9.25</Sphere><Cylinder>+3.25</Cylinder><Axis>4</Axis><CataractMode>ON</CataractMode><ConfidenceIndex>9</ConfidenceIndex><SE>-8.25</SE>
Tag for right eyeAR data tag
Measurement data tag (1 to 10)SPH valueCYL valueAxisCAT mode (does not exist for OFF)
Confidence index (9 to 5, E)SE value
</ARList><ARList No = "2">
<Error>COVR </Error></ARList>
Error
(Repeated in accordance with the number of measurements)
<ARMedian><Sphere>-10.25</Sphere><Cylinder>+4.00</Cylinder><Axis>4</Axis><SE>-8.25</SE>
</ARMedian>
Median value tagSPH valueCYL valueAxisSE value
<TrialLens><Sphere>-6.25</Sphere><Cylinder>- 4.00</Cylinder><Axis> 94</Axis>
</TrialLens>
Trial lens tagSPH valueCYL valueAxis
33
LAN COMMUNICATION: Data Format
3
<ContactLens><Sphere>-10.25</Sphere><Cylinder>+4.00</Cylinder><Axis>4</Axis><SE>- 8.25</SE>
</ContactLens>
Contact lens tagSPH valueCYL valueAxisSE value
<RingImage>ARK 20080328142052RA1.jpg
</RingImage>
AR ring image file name
</AR><KM>
<LMList No = "1"><R1>
<Radius>8.01</Radius><Power>42.25</Power><Axis>0</Axis>
</R1>
KM data tagMeasurement data tag (1 to 10)R1 data tagmm dataDiopter dataAxis
<R2><Radius>8.01</Radius> <Powe >42.25</Power><Axis> 90</Axis>
</R2>
R2 data tagmm dataDiopter dataAxis
<Average><Radius>8.01</Radius><Power>42.25</Power>
</Average>
Average data tagmm dataDiopter data
<KMCylinder><Power>+ 0.00</Power><Axis>0</Axis>
</KMCylinder></KMList>
Cylinder tagDiopter dataAxis
(Repeated in accordance with the number of measurements)
<KMMedian><R1>
<Radius>8.01</Radius><Power>42.25</Power><Axis>0</Axis>
</R1>
Median value tagR1 data tag
mm dataDiopter dataAxis
<R2><Radius>8.01</Radius><Power>42.25</Power><Axis> 90</Axis>
</R2>
R2 data tagmm dataD iopter dataAxis
<Average><Radius>8.01</Radius><Power>42.25</Power>
</Average>
Average data tagmm tagDiopter tag
34
LAN COMMUNICATION: Data Format
<KMCylinder><Power>+0.00</Power><Axis>0</Axis>
</KMCylinder></KMMedian>
Cylinder tagDiopter dataAxis
<Sagittal><FixationAngle>25<FixationAngle><SagittalAxis>25<SagittalAxis><SUP>8.02</SUP><INF>8.02</INF><TEM>8.00</TEM><NAS>7.98</NAS><Topometry>
<SUP>8.02</SUP><INF>8.02</INF><TEM>8.00</TEM><NAS>7.98</NAS><Rh>8.00</Rh><Rv>8.02</Rv><Ro>8.01</Ro><ASTc>+0.00</ASTc><dRo>+0.00</dRo><ASTp>+0.16</ASTp><dAST>-0.16</dAST>
</Topometry><Eccentricity>
<SUP>+0.11</SUP><INF>+0.11</INF><TEM>-0.11</TEM><NAS>-0.20</NAS><eh>-0.16</eh><ev>+0.11</ev><E>-0.08</E>
</Eccentricity></Sagittal>
Sagittal tagFixation angleSagittal axisSuperior sideInferior sideTemporal sideNasal side
Superior sideInferior sideTemporal sideNasal sideAverage of corneal curvature on horizontal meridian
Average of corneal curvature on vertical meridian
Average of corneal curvature at the center
Corneal cylinder at the centerDifference of corneal curvature between R1 and R2
Corneal cylinder at the peripheryDifference of corneal cylinder between the center and peripheral
Superior sideInferior sideTemporal sideNasal sideEccentricity on horizontal meridianEccentricity on vertical meridianTotal Eccentricity
<NAS>-0.20</NAS><eh>-0.16</eh><ev>+0.11</ev><E>-0.08</E>
</Eccentricity></Sagittal><Peripheral>
<KMList No = "1"><R1>
<Radius>7.95</Radius><Power>42.50</Power><Axis>0</Axis>
</R1>
KM peripheral tagMeasurement data tag (1 to 10)
R1 data tagmm dataDiopter dataAxis
35
LAN COMMUNICATION: Data Format
3
<R2><Radius>7.94</Radius><Power>42.50</Power><Axis>90</Axis>
</R2>
R2 data tagmm dataDiopter dataAxis
<Average><Radius>7.95</Radius><Power>42.50</Power>
</Average>
Average data tagmm dataDiopter data
<KMCylinder><Power>+0.00</Power><Axis>0</Axis>
</KMCylinder>
Cylinder tagDiopter dataAxis
</KMList>(Repeated in accordance with the number of measurements)
<KMMedian><R1>
<Radius>7.95</Radius><Power>42.50</Power><Axis>0</Axis>
</R1>
Median value tagR1 data tag
mm dataDiopter dataAxis
<R2><Radius>7.94</Radius><Power>42.50</Power><Axis>90</Axis>
</R2>
R2 data tagmm dataDiopter dataAxis
<Average><Radiu>7.95</Radius><Power>42.50</Power>
</Average>
Average data tagmm dataDiopter data
<KMCylinder><Power>+0.00</Power><Axis>0</Axis>
</KMCylinder></KMMedian>
</Peripheral></KM>
Cylinder tagDiopter tagAxis
<CS><CSList No = "1">
<Size>12.1</Size></CSList>
</CS>
CS (corneal size) tagList tag (currently fixed at 1)
Corneal size
<PS><PSList No = "1">
<Size>4.7</Size><Lamp>ON</Lamp>
</PSList></PS>
PS (pupil size) tagList tag (currently fixed at 1)
SizeLamp (ON, OFF)
</R>
36
LAN COMMUNICATION: Data Format
<L>
</L>
Tag for left eye
(Same as right eye)
<PD><PDList No = "1">
<FarPD>26</FarPD><RPD>8</RPD><LPD>18</LPD><NearPD>26</NearPD>
</PDList >
</PD>
PD tagMeasurement data tag (1 to 5)
Distance visionDistance vision for right eyeDistance vision for left eyeNear vision
(Repeated in accordance with the number of measurements)
</Data>
37
4
4. EXAMPLE OF RECEIVED DATA
4.1 Example of Measurement Data Received by PC
Sample printout
Patient numberPatient IDName and sexData and time of measurementVertex distanceNear working distance
Right eye: 1st, Normal dataRight eye: 2nd, Error (CYL range over error)Right eye: 3rd, Normal dataRight eye: 4th, Normal dataRight eye: 5th, Normal dataRight eye: Median values
Right eye: Trial lens dataRight eye: CL conversion dataRight 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 measurementRight eye: 1st, KM data (P)
Right eye: KM median values (P)
Right eye: Corneal size measurement and pupil size measure-ment
38
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC
Left eye: 1st, Normal dataLeft eye: 2nd, Normal dataLeft eye: 3rd, Error (Negative SPH range over error)Left eye: 4th, Normal dataLeft eye: Median values
Left eye: Trial lens dataLeft eye: CL conversion dataLeft 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 measurementLeft 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 distancesPupillary distance: Distance and near pupillary distances(with monocular PD)Comment
39
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC
4
Data to be transmitted for producing the above sample printout
(1) RS-232C communicationDRM
IDNIDEK/ARK-530ANO0006IP012345678901234567890DA2006/01/09.10:50AMVD12.00WD40OL-04.25-00.25093OL-04.37-00.370909EL-OOL-04.25-00.250939OL-04.12-00.000008OR+00.25-00.37084OR+00.25-00.370869OR+00.25-00.500958OR+00.25-00.500848ERCOOR+00.25-00.370839CL-04.00-00.75095CR+00.25-00.25085TL-04.00-00.75095TR+00.00+00.25175PD68353363PD67????62
DKM L07.9507.7117607.83DL42.4543.7717643.11-01.32 L07.9507.7117607.83DL42.4543.7717643.11-01.32 L07.9507.7117607.83DL42.4543.7717643.11-01.32 L07.9607.7417707.85DL42.4043.6017743.00-01.20EL07.9607.7517607.86HL42.5043.5417643.02-01.04EL07.9707.7417607.84HL42.3843.6017642.99-01.22EL07.9607.8017607.88HL42.5043.2517642.88-00.75EL07.9507.7117607.83HL42.4543.7717643.11-01.32 R07.8607.5317507.70DR42.9444.8217543.88-01.88 R07.8707.5317407.70DR42.8844.8217443.85-01.94 R07.8607.5317507.70DL42.9444.8217543.88-01.88 L07.8607.5317507.70DL42.9444.8217543.88-01.88
Header for AR measurement dataCompany name and model namePatient numberPatient IDData and time of measurementVertex distanceNear working distanceLeft eye: AR median values
4th, Normal data3rd, Error (Negative SPH range over error)2nd, Normal data1st, Normal data
Right eye: AR median values5th, Normal data4th, Normal data3rd, Normal data2nd, Error (CYL range over error)1st, Normal data
Left eye: CL conversion dataRight eye: CL conversion dataLeft eye: Trial lens dataRight eye: Trial lens dataPupillary distance: Distance PD (with monocular PD) and near PDPupillary distance: Distance PD and near PDHeader for KM measurement dataLeft eye: KM median values (mm)
KM median values (D)3rd, KM data (mm)
KM data (D)2nd, KM data (mm)
KM data (D)1st, KM data (mm)
KM data (D)Left eye: KM median values (mm)
KM median values (D)3rd, KM data (mm)
KM data (D)2nd, KM data (mm)
KM data (D)1st, KM data (mm)
KM data (D)Right eye: KM median values (mm)
KM selected data (D)3rd, KM data (mm)
KM data (D)2nd, KM data (mm)
KM data (D)1st, KM data (mm)
KM data (D)
KM measurement(center)
KM peripheralmeasurement
KM measurement(center)
40
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC
ER07.9707.9117407.94 . . . . . . . . . . . .HR42.3342.7517442.54-00.42 . . . . . .ER07.9807.9617407.97 . . . . . . . . . . .HR42.2542.5017442.83-01.25 . . . . . .ER07.9607.8017407.88 . . . . . . . . . . .HR42.5043.2517442.88-00.75 . . . . . .ER07.9807.9617407.97 . . . . . . . . . . .HR42.2542.5017442.38-00.25 . . . . . .SL11.5 . . . . . . . . . . . . . . . . . . . . . . . . .PL06.0F . . . . . . . . . . . . . . . . . . . . . . . .SR11.0 . . . . . . . . . . . . . . . . . . . . . . . . .PR06.0N . . . . . . . . . . . . . . . . . . . . .
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 thedata after .
Left eye: KM median values (mm)KM selected data (D)3rd, KM data (mm)
KM data (D)2nd, KM data (mm)
KM data (D)1st, KM data (mm)
KM data (D)Left eye: Corneal size measurementLeft eye: Pupil size measurementRight eye: Corneal size measurementRight eye: Pupil size measurement
KM peripheralmeasurement
41
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC
4
(2) LAN communication
<?xml version="1.0" encoding="UTF-16"?><?xml-stylesheet type="text/xsl" href="RKT_style.xsl"?>
XML headerStyle sheet
<Data><Company>NIDEK</Company><ModelName>ARK-530A</ModelName><ROMVersion>9.99 /1.03</ROMVersion><Version>1.00</Version><Date>2006/01/09</Date><Time>10:50:52</Time>
Data tagCompany nameModel nameROM version (software/FPGA)Format version (differs from software version)Date (Y/M/D)Time (H/M/S)
<Patient><No.>00006</No.><ID>012345678901234</ID>
</Patient>
Patient tagPatient No.Patient ID
<Comment>========================</Comment><VD>12.00 mm</VD><WorkingDistance>40 cm</WorkingDistance><DiopterStep>0.25D</DiopterStep><AxisStep>1º</AxisStep><CylinderMode>MIX</CylinderMode><RefractiveIndex>1.3375</RefractiveIndex>
CommentsVDWorking distanceDiopter stepAxis stepCylinder mode (-, +, MIX)Refractive index (ARK only)
<R><AR>
<ARList No = "1"><Sphere>+0.25</Sphere><Cylinder>-0.37</Cylinder><Axis>83</Axis><CataractMode>ON</CataractMode><ConfidenceIndex>9</ConfidenceIndex><SE>+0.00</SE>
</ARList>
Tag for right eyeAR data tag
Measurement data tag (1)SPH valueCYL valueAxisCAT mode (does not exist when set to OFF) modeConfidence index (9 to 5, E)SE value
<ARList No = "2"><Error>COVR </Error>
</ARList>
Measurement data tag (2)Error
(Repeated in accordance with the number of measurements, maximum of five measurements)
<ARMedian><Sphere>-0.25</Sphere><Cylinder>-0.37</Cylinder><Axis>84</Axis><SE>+0.00</SE>
</ARMedian>
Median value tagSPH valueCYL valueAxisSE value
<TrialLens><Sphere>+0.00</Sphere><Cylinder>+0.25</Cylinder><Axis> 175</Axis>
</TrialLens>
Trial lens tagSPH valueCYL valueAxis
<ContactLens><Sphere>+0.25</Sphere><Cylinder>-0.25</Cylinder><Axis>85</Axis><SE>+ 0.00</SE>
</ContactLens>
Contact lens tagSPH valueCYL valueAxisSE value
42
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC
<RingImage>ARK 20060109105052RA1.jpg
</RingImage></AR>
AR ring image file name
<KM><LMList No = "1">
<R1><Radius>7.88</Radius><Power>42.94</Power><Axis>175</Axis>
</R1>
KM data tagMeasurement data tag (1)
R1 data tagmm dataDiopter dataAxis
<R2><Radius>7.53</Radius> <Powe >44.82</Power><Axis> 85</Axis>
</R2>
R2 data tagmm dataDiopter dataAxis
<Average><Radius>7.70</Radius><Power>43.88</Power>
</Average>
Average data tagmm dataDiopter data
<KMCylinder><Power>-1.88</Power><Axis>175</Axis>
</KMCylinder></KMList>
Cylinder tagDiopter dataAxis
(Repeated in accordance with the number of measurements, maximum of three measurements)
<KMMedian><R1>
<Radius>7.86</Radius><Power>42.94</Power><Axis>175</Axis>
</R1>
Median value tagR1 data tag
mm dataDiopter dataAxis
<R2><Radius>7.53</Radius><Power>44.82</Power><Axis> 85</Axis>
</R2>
R2 data tagmm dataDiopter dataAxis
<Average><Radius>7.70</Radius><Power>43.88</Power>
</Average>
Average data tagmm dataDiopter data
<KMCylinder><Power>-1.88</Power><Axis>175</Axis>
</KMCylinder></KMMedian>
Cylinder tagDiopter dataAxis
43
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC
4
<Sagittal><FixationAngle>25<FixationAngle><SagittalAxis>25<SagittalAxis><SUP>8.02</SUP><INF>8.02</INF><TEM>8.00</TEM><NAS>7.98</NAS><Topometry>
<SUP>8.02</SUP><INF>8.02</INF><TEM>8.00</TEM><NAS>7.98</NAS><Rh>8.00</Rh><Rv>8.02</Rv><Ro>8.01</Ro><ASTc>+0.00</ASTc><dRo>+0.00</dRo><ASTp>+0.16</ASTp><dAST>-0.16</dAST>
</Topometry><Eccentricity>
<SUP>+0.11</SUP><INF>+0.11</INF><TEM>-0.11</TEM><NAS>-0.20</NAS><eh>-0.16</eh><ev>+0.11</ev><E>-0.08</E>
</Eccentricity></Sagittal>
Sagittal tagFixation angleSagittal axisSuperior sideInferior sideTemporal sideNasal side
Superior sideInferior sideTemporal sideNasal sideAverage of corneal curvature on horizontal meridian
Average of corneal curvature on vertical meridian
Average of corneal curvature at the center
Corneal cylinder at the centerDifference of corneal curvature between R1 and R2
Corneal cylinder at the peripheryDifference of corneal cylinder between the center and peripheral
Superior sideInferior sideTemporal sideNasal sideEccentricity on horizontal meridianEccentricity on vertical meridianTotal Eccentricity
<Peripheral><KMList No = "1">
<R1><Radius>7.98</Radius><Power>42.25</Power><Axis>174</Axis>
</R1>
KM peripheral tagMeasurement data tag (1)
R1 data tagmm dataDiopter dataAxis
<R2><Radius>7.96</Radius><Power>42.50</Power><Axis>84</Axis>
</R2>
R2 data tagmm dataDiopter dataAxis
<Average><Radius>7.97</Radius><Power>42.38</Power>
</Average>
Average data tagmm dataDiopter data
<KMCylinder><Power>-0.25</Power><Axis>174</Axis>
</KMCylinder>
Cylinder tagDiopter dataAxis
</KMList>(Repeated in accordance with the number of measurements, maximum of three measurements)
44
EXAMPLE OF RECEIVED DATA: Example of Measurement Data Received by PC
<KMMedian><R1>
<Radius>7.95</Radius><Power>42.50</Power><Axis>0</Axis>
</R1>
Median tagR1 data tag
mm dataDiopter dataAxis
<R2><Radius>7.94</Radius><Power>42.50</Power><Axis>90</Axis>
</R2>
R2 data tagmm dataDiopter dataAxis
<Average><Radiu>7.95</Radius><Power>42.50</Power>
</Average>
Average data tagmm dataDiopter data
<KMCylinder><Power>+0.00</Power><Axis>0</Axis>
</KMCylinder></KMMedian>
</Peripheral></KM>
Cylinder tagDiopter dataAxis
<CS><CSList No = "1">
<Size>11.0</Size></CSList>
</CS>
CS (corneal size) tagList tag (currently fixed at 1)Corneal size
<PS><PSList No = "1">
<Size>6.0</Size><Lamp>ON</Lamp>
</PSList></PS>
PS (pupil size) tagList tag (currently fixed at 1)SizeLamp (ON, OFF)
</R><L>
</L>
Tag for left eye
(Same as right eye)
<PD><PDList No = "1">
<FarPD>67</FarPD><NearPD>62</NearPD>
</PDList >
PD tagMeasurement data tag (1)
Distance visionNear vision
<PDList No = "2"><FarPD>68</FarPD><RPD>35</RPD><LPD>33</LPD><NearPD>63</NearPD>
</PDList >
</PD>
Measurement data tag (2)Distance visionRight eye for distance visionLeft eye for distance visionNear vision
(Repeated in accordance with the number of measurements)
</Data>
45
EXAMPLE OF RECEIVED DATA: Sample Printout of KM Data when the I/F FORMAT Parameter is Set to Short
4
4.2 Sample Printout of KM Data when the I/F FORMAT Parameter is Set to Short
Sample printout
Data to be transmitted for producing the above sample printout
DKM . . . . . . . . . . . . . . . . . . . . . . . . .NO0006 . . . . . . . . . . . . . . . . . . . . . . .DA2006/01/09.10:50AM . . . . . . . . . . . L07.9507.7117607.83 . . . . . . . . . . . .EL07.9507.7117607.83 . . . . . . . . . . . . R07.8607.5317507.70 . . . . . . . . . . .ER07.9507.7117607.83 . . . . . . . . .
The above sample example is produced when the SD command is CKM. (See (2) SD commandof 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.
Patient numberName and sexData and time of measurement
Right eye: KM median values; KM measurement (center)
Right eye: KM median values; KM peripheral measurement
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
Header for KM measurement dataPatient numberData and time of measurementLeft eye: KM median values (mm); KM measurement (center)Left eye: KM median values (mm); KM peripheral measurementRight eye: KM median values (mm); KM measurement (center)Right eye: KM median values (mm); KM peripheral measurement
46
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 KMmeasurement data. Basic transmitting and receiving sequences are stipulated in the aforemen-tioned “1 OUTLINE OF COMMUNICATION” (Page 3).
DKM NO.0001 DAMAY/18/2006.10:50AM L08.5107.8410008.18 DL39.6643.0510041.36-03.39 FA25 LS07.8608.53+0.16A LI07.8608.53+0.16A LT08.5507.87+0.24A LN08.5507.87+0.24A LE+0.24+0.16+0.20 LR07.8708.5208.18+0.67 LA-03.39-03.26-00.13
= 01H SOH = 02H STX = 17H ETB = 04H EOT = 0DH is added in accodance with setting.
Printed data by ARK-530A Transmission format
47
EXAMPLE OF RECEIVED DATA: Transmission of Sagittal Measurement Data
4
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 valueSAGIT2 : Measurement value including dROECC : Each eccentricityA/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 diopterbetween 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.
48
EXAMPLE OF RECEIVED DATA: Interface Error Messages
4.4 Interface Error Messages
If any error occurs during communications with the external computer, the corresponding errormessage is displayed on the LCD screen.
Error code table
ERROR CODE
Display Description Symptom
11 ERR011 Time-out error (OUT) in characters Communication breaks during data reception.
12 ERR012Time-out error (OUT) for receiving data
Time-out after the DTR-DSR is effected
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
21 ERR021 Time-out error (IN) in charactersDSR is not flagged while SD command is 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) -
49
EXAMPLE OF RECEIVED DATA: Interface Error Messages
4
LAN communication error codes
ERROR CODE
Display Description Symptom
700 ERR700 • File sharing error
Windows file sharing error
• Check the LAN cable connection. • Check that the IP address or subnet mask is
correct on the NETWORK setting screen.
703 ERR703 • Hardware error
IC error • Replace BA01.
704 ERR704 • DHCP error
The IP address cannot be obtained. • There is no DHCP server. Check the DHCP
server.
750 ERR750 • Network access error
Access to the network is not allowed.
• Check the LAN cable connection. • Check that the IP address or subnet mask is
correct on the NETWORK setting screen.
751 ERR751 • Network writing error
Writing to the PC is not allowed.
• Check that the PC folder specified as the place in which data is saved is a shared folder or that free space is left.
754 ERR754 • PC name error
The specified PC name does not exist.
• Check that the computer name specified by the PC NAME parameter on the NETWORK setting screen is correct or that LAN is properly connected.
755 ERR755 • Read-only folder error
The folder in which data is saved is read-only attribute.
• The folder of the connected PC is write-protected. Disable the write-protect.
756 ERR756
• Log-on errorLogging on the PC is not possible (The user name or password is incorrect.)
• Entry in the user name or password field on the NETWORK setting screen is incorrect.
757 ERR757 • Shared folder error
The shared folder does not exist. (The shared folder name is incorrect.)
• Check the folder name or whether the folder is set to share.
758 ERR758 • Time-out error
Timeout (The PC did not finish the process in a specified time.)
• Reduce the PC processing load. (Reduce the resident software).
759 ERR759 • Delete error
PC data cannot be deleted. • The folder of the connected PC is write-protected.
Disable the write-protect.
760 ERR760
• Error during initializationThe network is undergoing initialization (requires a certain amount of time).
• Wait and try again.
761 ERR761 • Access authority error
File sharing setting is improper. • Check the file sharing setting of the shared folder
of the connected PC.
762 ERR762 • Account error
The account is disabled. (The user setting is improper.)
• Enable the account of the connected PC.
771 ERR771 • Cable connection error
The LAN cable is not connected. • Check the LAN cable connection.
50
EXAMPLE OF RECEIVED DATA: Interface Error Messages
772 ERR772 • ACK error
There is no response from the PC.
• The deleting process of measurement data files by the receiver software did not finish within the specified time. Check that the software operates properly. If it occurs frequently, retry connection after setting the NETWORK parameter from ACK to YES.
ERROR CODE
Display Description Symptom