20.009 (Remote Interface Manual v3.x)
20.009 (Remote Interface Manual v3.x)
20.009 2/14/13
Rev 3.9
Remote Interface User’s Guide
Lanmark Controls Inc. has prepared this document for use by its personnel, licensees, and potential licensees.
Lanmark Controls Inc. reserves the right to change any products described in this document as well as
information included herein without prior notice. Although the information presented in this document has
been tested and reviewed, this document does not convey any license or warrantee beyond the terms and
conditions set forth in the written contracts and license agreements between Lanmark Controls Inc. and its
customers.
The software described in this document is licensed from and is a trade secret of Lanmark Controls Inc. Refer
to your License Agreement for restrictions on use, duplication, or disclosure. Government users and prime
contractors are also governed by the following restricted rights legend:
RESTRICTED RIGHTS LEGEND. Use, duplication, or disclosure by the U.S. Government is subject to the
Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 © (1) (ii) (Oct. 1988) and
FAR 52.227-19 © (June 1987) or other agency provision is as applicable. Copyright Lanmark Controls Inc.
Copyright © 2013 Lanmark Controls Inc. – All rights reserved under the copyright laws of the United States
of America.
WinLase is a registered trademark of Lanmark Controls Inc. in the United States and/or other countries. Other
brands mentioned are trademarks or registered trademarks of their respective holders.
There is no implied warranty of fitness for a particular purpose, and Lanmark Controls Inc. is not responsible
for consequential damages. Individual components and/or software modules manufactured by Lanmark
Controls Inc. or others may be covered by their own warranties. Refer to the appropriate manuals for this
information.
Table of Contents
1. Introduction .............................................................................................................................. 4
1.1 About this Manual ............................................................................................................ 4
1.2 Technical Support............................................................................................................. 4
1.3 Manufacturer .................................................................................................................... 4
2. Principle of Operation .............................................................................................................. 5
2.1 Remote Interface Concept ................................................................................................ 5
2.1.1 RS-232 and TCP/IP Interface Concepts ................................................................... 5
2.1.2 Fieldbus Interface Concepts ..................................................................................... 5
2.2 Configuring the RS-232 Interface .................................................................................... 6
2.3 Configuring the TCP/IP Interface .................................................................................... 8
2.4 Configuring the Fieldbus Interface ................................................................................... 9
2.5 Configuring the Repeat Process and External Start settings .......................................... 10
2.6 Viewing the Host Interface Monitor ............................................................................... 12
2.7 Enabling the Host Mode ................................................................................................. 12
2.8 Tips on using the RS-232 and TCP/IP Remote Interface ............................................... 13
3. Commands and Functions ...................................................................................................... 17
3.1 RS-232 and TCP/IP Interface ......................................................................................... 17
3.1.1 Command Syntax ................................................................................................... 17
3.1.2 Command Set ......................................................................................................... 17
3.1.3 Example Program ................................................................................................... 29
3.1.3.1 C++ Example ...................................................................................................... 29
3.2 Fieldbus Interface ........................................................................................................... 31
3.2.1 Data Structure Overview ........................................................................................ 34
3.2.1.1 Master Output Structure ..................................................................................... 34
3.2.1.2 Master Input Structure ........................................................................................ 37
3.2.2 Processing Example ................................................................................................ 40
4. Warranty ................................................................................................................................. 41
5. Index ....................................................................................................................................... 43
Appendix A – Return codes ........................................................................................................... 45
Appendix B – Object Types ........................................................................................................... 47
Appendix C – TCP/IP Test Client .................................................................................................. 49
TCP/IP Test Client ..................................................................................................................... 49
1. Introduction
Thank you for purchasing the Lanmark Controls Inc. WinLase Professional Laser Marker User Interface. The
following guide will assist you in using the Remote Interface services provided by WinLase Professional; either
with a direct wired RS-232 port connection, through a LAN based TCP/IP socket connection, or a Fieldbus
network connection.
1.3 Manufacturer
2. Principle of Operation
This chapter gives an overview of the Remote Interface services provided by WinLase Professional, and details
on configuring WinLase Professional properly to communicate with your software.
For this reason, WinLase Professional offers the Remote Interface service. This service provides a remote
program, written by the customer, the ability to take control of WinLase. In addition, the Fieldbus interface
provides a means for controlling WinLase, and reading status back from WinLase to the Master controller.
Although TCP/IP, RS-232 and Fieldbus interfaces are supported, only one may be active at a time for Remote
Control.
In operation, the external program takes control of WinLase, but does not initiate the actual marking cycle.
This is done through the START PROCESS input on the Standard I/O card, or the Start Mark input on the
SPC/SPICE series of interface cards. Once the START PROCESS pin is toggled, the mark cycle begins, the
mark completes, and then WinLase Professional returns to wait for the START PROCESS pin to toggle again.
In addition to the control commands available, there are a number of status query commands that can be used
to retrieve the current status of WinLase. These queries can be made even if the remote computer has not
taken control of WinLase.
If an RS-232 COM port has been configured, WinLase will attempt to open the port when the application first
starts. If an error is encountered during startup, an error window will be displayed.
In operation, the external Master initializes WinLase with a startup sequence, and then can go on to take
control and load jobs. Once a job is loaded, the Master initiates the actual marking cycle. This is done through
the StartMark input bit.
The property values listed in the Host Interface page consist of the following:
Make port available to Host Interface – Selecting this check box will make a COM port available to
the Host Interface. When applying this change, the port is not opened, but is only made available to
the Host Interface. This is indicated by a Status of Not Connected. Click on the Host Interface tab to
actually open the port. De-select the box to disable the COM port for the Host Interface.
Port # – The Windows assigned COM port.
Data Bits – COM port setting.
Stop Bits – COM port setting.
Baud Rate – COM port setting.
Parity – COM port setting.
Apply – Click this button to apply any changes made in the Host Interface page.
4. After making changes, click the Apply button. The following window is displayed, and the Status is
updated to Not Connected.
5. Click OK to close the dialog, then select the Host Interface Tab.
6. Click on to display the Host connection types available.
8. Select the Enter Run from Host mode when application starts check box if you want WinLase
Professional to automatically place itself in the Host ready mode when the application first starts.
9. Select the Show Host Monitor when application starts check box if you want WinLase Professional to
automatically show the Host Monitor window when the application first starts.
10. To disable the Remote Interface service, Click on to display the Host connection types available, and
highlight <disabled>.
6. Edit the default values as desired. By default, WinLase Professional has been configured to listen on Port
350. You can change this port if conflicts exist on your network.
7. Select the Enter Run from Host mode when application starts box if you want WinLase Professional to
automatically place itself in the Host ready mode when the application first starts.
8. Select the Show Host Monitor when application starts check box if you want WinLase Professional to
automatically show the Host Monitor window when the application first starts.
9. To disable the Remote Interface service, Click on to display the Host connection types available, and
highlight <disabled>.
Note: This section does not apply to users of the Fieldbus interface. To use the RS-232
or TCP/IP interfaces, you must have either a Standard I/O card or an SPC/SPICE series
scan head card installed in your PC.
To configure WinLase Professional for the Remote Interface, the system must be set to continuously repeat the
job, and to poll the START PROCESS input pin on the Standard I/O card, or the START MARK pin on the
SPC/SPICE card. Note that if you do not select these settings manually, they will be set for you the first time
the Host calls “online”. If the Host calls “run”, these settings are NOT changed from the current values.
To Configure Repeat Process and External Start:
1. In WinLase, on the main menu click Job > Settings. The Job Settings form appears.
2. Select the Repeat Process tab.
3. Select the Do not prompt between cycles and run indefinitely radio button.
6. Click on to display the available I/O ports, and select the desired port. Ports are only available on the
Standard I/O card or the SPC/SPICE series scan head card.
7. Enter a message in the Message edit box. The message appears in the Host Process box while the system
is waiting for the START PROCESS input to toggle.
8. Enter a timeout value in the Timeout edit box. A value of zero will instruct WinLase to wait indefinitely
for a start mark signal.
9. Select the Wait for signal to deassert before triggering radio button to start marking on the trailing edge
of the START PROCESS signal input. Select the Trigger immediately when signal is asserted radio
button to start marking on the leading edge of the START PROCESS signal input.
10. Click OK to close the Job Settings form.
2. To close the Host Monitor, on the main menu click View > Host Monitor. The Host Interface Monitor
form closes.
TCP/IP, on the other hand, is a bit more difficult. It is a networking protocol, and has the ability to
communicate over local area networks (LANs), wide area networks (WANs), and the Internet. In order for one
program to communicate with another on a different computer, the remote program (such as WinLase) needs
to make itself available on a specified Port, and the IP address of the remote computer has to be known.
It is this IP address and Port that ensures any message sent reaches the proper destination. In other words, in
order for you to communicate with WinLase Professional over TCP/IP, you must know the IP address and
Port of the computer running WinLase Professional at your remote computer.
By default, WinLase Professional makes the Remote Interface service available on Port 350. This can be
changed in the Host Interface setup box if Port 350 conflicts with another installed port on your machine.
Determining the IP address of the computer that WinLase Professional is running on depends on how the
TCP/IP stack is configured in Windows NT/2000. Computers can either have a static IP address, or one that is
dynamically allocated when the computer signs on to the network.
6. Internet Protocol (TCP/IP) must appear and be checked in the list of items. If not, install TCP/IP, referring
to the Windows XP documentation as a guide.
7. Highlight Internet Protocol (TCP/IP), and then click the Properties button.
8. If the Use the following IP address radio button is selected, your computer uses a static IP address, which
is shown in the IP Address box.
9. If the Obtain an IP address automatically radio button is selected, your computer is assigned a different
IP address each time it boots up on the network.
If your computer uses a static IP address, you can use this address when communicating with WinLase
Professional over the TCP/IP port. If your computer uses a dynamically assigned address, another method has
Note: WinLase Professional is always listening on Port 350, and will always accept a
connection request on this Port.
HOME
Purpose: Commands all of the motor control axes to Home. This command is valid only if WinLase
has been configured with a compatible motor controller.
MODIFY,buffer,##,******
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: To store the string ‘*****’ in the internal string buffer at index ##. ## must be between 1
and 10. Text objects within the job must have their “Source” set to Get String from Memory
buffer to use the buffer contents. Calling this will clear the previous value stored in buffer.
MODIFY,field,##,******
Purpose: To modify a field of text or barcode where ## is the number of the field (object) to be
modified, and “*****” is the new text string. The field ## corresponds to the position the
object has in the Object List within the job i.e. the first object in the Object List would have
an index value of 1. If the index values are not known at run time, use MODIFY, buffer
instead. The marker must be OFFLINE. If the field does not exist, an error is returned.
MODIFY,position,##,xoffset,yoffset
Purpose: To change the position of a marking object, where ## is the number of the object to be
modified, xoffset is the amount to move the object in bits along the x axis, and yoffset is the
amount to move the object in bits along the y axis. The field ## corresponds to the position
the object has in the Object List within the job i.e. the first object in the Object List would
have an index value of 1.The marker must be OFFLINE. If the field does not exist, an error
is returned.
MODIFY,rotation,##,angle
Purpose: To rotate a marking object about it’s center, where ## is the number of the field (object) to
be modified, and angle is the amount to rotate the object, in units of 0.010 degrees. A
positive angle value rotates the object clockwise. The object ## corresponds to the position
the object has in the Object List within the job i.e. the first object in the Object List would
have an index value of 1.The marker must be OFFLINE. If the field does not exist, an error
is returned.
MODIFY,rotationex,##,angle,xcenter,ycenter
Purpose: To rotate a marking object about an arbitrary center of rotation, where ## is the number of
the object to be modified, angle is the amount to rotate the object, in units of 0.010 degrees,
xcenter is the x-axis center of rotation, in bits and ycenter is the y-axis center of rotation in
bits. A positive angle value rotates the object clockwise. The object ## corresponds to the
position the object has in the Object List within the job i.e. the first object in the Object List
would have an index value of 1.The marker must be OFFLINE. If the field does not exist, an
error is returned.
MODIFY,scale,##,xscale,yscale
Purpose: To scale a marking object from it’s center, where ## is the number of the object to be
modified, xscale is the amount to scale the object in the x-axis, in percent, and yscale is the
amount to scale the object in the y-axis, in percent. For example, to decrease the size of an
object to half it’s current size, use the value 50.00 (%) for both the xscale and yscale values.
The object ## corresponds to the position the object has in the Object List within the job i.e.
the first object in the Object List would have an index value of 1.The marker must be
OFFLINE. If the field does not exist, an error is returned.
OFFLINE
Purpose: Commands the laser to immediately stop marking, and returns the laser to the
MARKER_OFFLINE state.
ONLINE
Purpose: Commands the marker to start the marking process. System will immediately start polling
external start port, and enter MARKER_ONLINE state. This call automatically sets
the external start flag to true, and sets the repeat mode to repeat indefinitely.
OPEN,file,######
Purpose: To open a file where “####” is a text string describing the file to be opened, and must be
a fully qualifed UNF file path. If the file cannot be found, or is corrupt, an error code
is returned.
REQUEST,data,bits_per_mm,c#,h#
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Request WinLase to return the current value for the scan field bits/mm, where c# is the zero
based card index and h# is the zero based scan head index. An example string would be
“REQUEST,data,bits_per_mm,0,0”. The bits/mm value is the ratio of a point coordinate in
bits and the actual position of the point in millimeters.
REQUEST,data,cyclecount
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Request WinLase to return the current cycle count. The cycle count indicates the number of
full cycles, including step and repeat.
REQUEST,data,partcount
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Request WinLase to return the current part count. The part count is the individual marks
within a cycle.
REQUEST,data, cycletime
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Request WinLase to return the current cycle time. The cycle time is defined as the elapsed
time to do all marks within a single cycle.
REQUEST,data, parttime
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Request WinLase to return the current part mark time. The part time is defined as the
elapsed time to do a singlemark within an overall cycle.
REQUEST,data, jobname
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Request WinLase to return the name of the currently loaded job.
REQUEST,data, version
NOTE: WinLase does not need to be under Host control to accept this command
REQUEST,data, user
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Request WinLase to return the User currently logged on to the current Windows NT/2000
session.
REQUEST,field, ##
Purpose: To request data from a field of text, barcode or graphic where ## is the number of the field
to be queried. The marker must be OFFLINE. If the field does not exist, an error is returned.
REQUEST,status,interface
NOTE: WinLase does not need to be under Host control to accept this command
REQUEST,status,lecexecution
NOTE: WinLase does not need to be under Host control to accept this command
Purpose: Returns the current status of the job execution status of the LEC controller.
REQUEST,status,marker
NOTE: WinLase does not need to be under Host control to accept this command
RUN
Purpose: Commands the marker to start the marking process. System will immediately execute the
currently loaded job and enter the MARKER_ONLINE state. This call does not automatically set the external
start flag to true, and does not set the repeat mode to repeat indefinitely. The current job settings will be used
for these two parameters.
SET,control,host
Purpose: Puts WinLase into external control mode. All user input at the console is disabled.
SET,control,local
Purpose: Releases WinLase from the external control mode. Enables user input at the console.
The following pseudo-code uses an application defined function called SendToSocket(), which represents a
method of outputting text from either the RS-232 or TCP/IP ports, and receiving a response as it’s return
value.
//Aquire WinLase
SendToSocket (“SET,control,host”);
//Make sure we have control
if (SendToSocket (“REQUEST,status,interface”)!=” STATUS,512”)
return ERROR;
//Load a job
SendToSocket (“OPEN,file,c:\\test\\job\\test.wlj”);
//Make sure job has loaded properly
if (SendToSocket (“REQUEST,status,marker”)!=” STATUS,2300”)
return ERROR;
//Change the text in the object at index position 2
SendToSocket (“MODIFY,field,2,”Hello World”);
//Put WinLase into the ONLINE mode, waiting for START PROCESS to toggle
SendToSocket (“ONLINE”);
//Verify we are in ONLINE MODE
if (SendToSocket (“REQUEST,status,marker”)!=” STATUS,2301”)
return ERROR;
//Mark some parts
.
.
//Stop polling the START PROCESS input
SendToSocket (“OFFLINE”);
//Release WinLase
SendToSocket (“SET,control,local”);
1. Click on the Fieldbus Tab. If the Fieldbus tab is not visible, try clicking the right or left arrow at the top
right on the row of tabs. If you cannot locate the Fieldbus tab, WinLase does not recognize the Fieldbus
card. Please consult the factory.
2. Click the Properties button. The following window appears:
BYTE44 Function
to
BYTE83
40 Bytes 20 16-bit values Save maximum of 20 Unicode characters to MemoryBuffer2
After WinLase has been notified of a change in data by the slave card, WinLase does a further check on the
data to compare what was received to what WinLase has stored in its local data cache. The data is parsed by
WinLase in the following order:
1. BYTE0, bits 0, 1, 2, and 3 are scanned in order. Once the first change is detected, that change is acted on,
and the system returns without scanning for further changes.
2. If no changes are detected up to this point, BYTE1, bits 0, 1, 2, 3, 4, 5, 6, and 7 are scanned in order.
Once the first change is detected, that change is acted on, and the system returns without scanning for
further changes.
3. If no changes are detected up to this point, BYTE2, BYTE3 and BYTE4 to BYTE 43 and BYTE44 to
BYTE 83 are checked for changes in order. The first change detected is saved to the cache, and the
system returns without scanning for further changes.
4. If no changes are detected up to this point, BYTE84 is scanned, and if a change is detected, the 8-bit value
represented by the individual bits are decoded, and the appropriate job is loaded. The system then returns
without scanning for further changes.
Tips:
If setting a bit flag in BYTE0 or BYTE1 results in an error flag being set, then the same bit flag must be
cleared to clear the error.
When a particular function is set, the programmer should scan the Input structure on the slave to verify
the action has taken place
JobIndex Bit0 through Bit7 (in BYTE84) are treated as a 8-bit value, yielding 256 possible JobIndex
values (0-255). JobIndex must be set to zero (0) first and each subsequent time before a new Job file can
be loaded. The JobIndex value is mapped to a filename on disk in WinLase. See the section on
configuring the Fieldbus card for more details on setting up the job mapping.
BYTE4 to BYTE83 are used to transfer Unicode characters into the WinLase memory buffer system. Text
objects within a job can be configured to extract their string data from one of these memory buffers before
marking the string.
4. Warranty
Lanmark Controls Inc. warrants to the Customer that the product is free from defects in workmanship and
materials for a period of 12 months from the delivery date.
Lanmark Controls Inc. obligation under this warranty is limited to repair, replacement or service, at its option,
any part of the product which, within the warranty period and upon Lanmark Controls Inc. examination shall
disclose to its satisfaction not to have conformed to this Agreement or to have been defective. Defective parts
or products are to be returned to Lanmark Controls Inc. place of shipment.
The above warranties do not apply (i) to defects or failure of product or parts caused by accident, alteration,
abuse, misuse, corrosion or improper installation or operation, or (ii) to alterations or modifications made by
Customer in any way so as in Lanmark Controls Inc. judgment to affect the products reliability, or (iii) to
installation not performed pursuant to Lanmark Controls Inc. factory authorized protocol, or (iv) in the case of
custom software designed to interact with other Customer-supplied software, in the event of any change,
upgrade or reprogramming of such Customer-supplied software so as to create an incompatibility with
Lanmark Controls Inc. software.
Authorization to return products purchased from Lanmark Controls Inc. must be obtained by Customer.
Returns should always be carefully packed and sent freight prepaid. Unless otherwise agreed, return shipment
freight and duty charges shall be borne by Customer. Customer shall bear all charges for freight and handling
of products returned which are not defective.
THIS WARRANTY IS EXPRESSLY MADE IN LIEU OF ANY AND ALL OTHER WARRANTIES
EXPRESSED OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE, EXPRESSED OR IMPLIED.
5. Index
JOB_INDEX_BIT3 · 38
JOB_INDEX_BIT4 · 35
A JOB_INDEX_BIT4 · 38
JOB_INDEX_BIT5 · 35
ABORT_MARK · 34, 37 JOB_INDEX_BIT5 · 38
JOB_INDEX_BIT6 · 35
C JOB_INDEX_BIT6 · 38
JOB_INDEX_BIT7 · 35
Command Set · 17 JOB_INDEX_BIT7 · 38
Command Syntax · 17
L
D
LAN · 13
Descriptive Code · 45 LASER_POWER_CHANGE · 35
E M
INTERLOCK_OPEN · 34, 37
O
J OFFLINE · 21
ONLINE · 21
JOB_INDEX_BIT0 · 35 OPEN,file,###### · 22
JOB_INDEX_BIT0 · 38
JOB_INDEX_BIT1 · 35
JOB_INDEX_BIT1 · 38 P
JOB_INDEX_BIT2 · 35
JOB_INDEX_BIT2 · 38 POWER_OUT_OF_RANGE · 38
JOB_INDEX_BIT3 · 35 Principle of Operation · 5
READY_HOST_CONTROL · 37
T
Remote Interface Concept · 5
Repeat Process · 10
Table of Contents · 3
REQUEST,data, bits_per_mm,c#,h# · 22
TCP/IP · 8, 13
REQUEST,data, cycletime · 23
TCP/IP Test Client · 49
REQUEST,data, jobname · 24
Technical Support · 4
REQUEST,data, parttime · 24
REQUEST,data, user · 25
REQUEST,data, version · 24 U
REQUEST,data,cyclecount · 23
REQUEST,field, ## · 25 USERIN1 · 34
REQUEST,status,interface · 25 USERIN2 · 34
REQUEST,status,lecexecution · 26 USERIN3 · 34
REQUEST,status,marker · 26 USERIN4 · 34
RS-232 · 6, 13 USERIN5 · 34
RS-232 and TCP/IP Interface Concepts · 5 USERIN6 · 34
RUN · 27 USEROUT1 · 37
USEROUT2 · 37
USEROUT3 · 37
S
USEROUT4 · 37
Using the Master Input Data · 39
SET,control,host · 28
SET,control,local · 28
SPEED_OUT_OF_RANGE · 38 W
Standard I/O card · 5, 10
START PROCESS · 5 Warranty · 41
START_MARK · 34 Windows XP · 13
static IP address · 15 WINLASE_NOT_READY · 34, 37
UNKNOWN_VERB 204
UNKNOWN_NOUN 205
UNKNOWN_QUALIFIER 206
INVALID_STRING 209
NO_JOB_LOADED 221
NO_SUCH_OBJECT 231
NO_SUCH_FIELD 233
NO_SUCH_BUFFER 235
NOT_IN_HOST_MODE 236
ALREADY_OFFLINE 240
ALREADY_ONLINE 241
NOT_OFFLINE 242
NOT_ONLINE 243
ALREADY_IN_HOST_MODE 244
ALREADY_IN_LOCAL_MODE 245
SERVER_NOT_READY 250
INTERNAL_ERROR 400
HOST_READY 510
HOST_NOT_READY 511
IN_HOST_MODE 512
FILE_NOT_FOUND 2000
FILE_TYPE_NOT_SUPPORTED 2010
MARKER_OFFLINE 2300
MARKER_ONLINE 2301
LEC_IDLE 2320
LEC_BUSY 2321
NO_MARKER_LIBRARY 2350
INTERLOCKS_OPEN 3000
NO_SCANCARD 3010
NO_HARDLOCK 3011
NO_IOCARD 3012
NO_LASER_INIT 3013
HARDLOCK_NOT_ALLOWED 3014
INVALID_STEP_REPEAT 3020
INVALID_TEXT_SOURCE 3021
TEXTMERGE_ERROR 3022
OBJECT_OUT_OF_BOUNDS 3040
MOTOR_HOME 3050
NO_MOTOR_CONTROLLER 3051
ALIGNMENT_FILE 3052
MOTION_INITIALIZATION_FAIL 3053
NO_DEFAULT_NODE 3054
DEFAULT_NODE_NOT_FOUND 3055
Note: Not all of these Object types are available through the Host Interface. They are
included here for completeness.
MCL Graphic 7
EPS Graphic 8
DXF Graphic 9
System Line 10
System Rectangle 11
System Polygon 12
PLT Graphic 13
EMF Graphic 14
WLO Graphic 15
Text 16
System Drill 17
Barcode 39 18
Barcode CodaBar 19
Barcode 93 20
Barcode 128 21
Barcode 2 of 5 22
Barcode PostNET 23
Barcode UPC 24
Barcode EAN 25
DataMatrix 26
QRCode 27
Bitmap Graphic 28
Wait On Port I/O 29
Set Port I/O 30
Time Delay 31
Message Box 32
Generic Motor Controller 33
XY Table Controller 34
Rotary Indexer Controller 35
Laser Lift Controller 36
2. If the TCP/IP Test Client is running on the same computer as WinLase Professional, enter the following
IP address in the Addr (address) field:
127.0.0.1
If running the TCP/IP Test Client from a remote computer, enter the IP address of the computer running
WinLase Professional in the Addr field.
3. From the Port field, enter the following port:
350
4. Make sure WinLase Professional is running on the local computer or the remote computer.
5. Click the Connect button. The TCP/IP Test Client connects to the WinLase Professional instance. The
Status field updates with Connected to server. The status bar in WinLase Professional updates with
TCP/IP Port: Connected.
6. If the TCP/IP Test Client does not make a connection to the WinLase server, check that the IP address and
the Port is correct, and that WinLase Professional is running.