Dataman 448PRO2AP, User Manual, Page: 113 / 160

PG4UW
113
Default (as preset in software) - the programmer indicates the state when a device is
programmed and the programmer with software wait for inserting a new device as preset in the
software for respective programmer. Multi-sockets programmers (the programmers with more
than one ZIF socket) do not indicate this state; see description for Not indicated (quiet
mode). Single-socket programmers (the programmers with one ZIF socket) indicate this state
by LED Busy blinking; see description for By LED Busy blinking setting.
Not indicated (quiet mode) – the programmer, regardless of the number of ZIF sockets of the
programmer, does not indicate the state when a device is programmed and the programmer
with software wait for inserting a new device. After an operation with a device only one of the
status LEDs Error or OK lights, in dependence on the result of previous operation. This LED
goes off immediately after detecting removal of a device from the ZIF socket.
By LED Busy blinking - the programmer, regardless of the number of ZIF sockets of the
programmer, indicates the state when a device is programmed and the programmer with
software wait for inserting a new device mode by blinking with the LED Busy. After an
operation with a device is done, one of the status LEDs (OK or Error) lights, in dependence on
the result of previous operation and the LED Busy is blinking. If the program detects removal of
a device from ZIF socket, then the status LED goes off, but the LED Busy is still blinking to
indicate readiness of the program to repeat last operation with new device. After the program
indicates one or more pins of (new) device in the ZIF socket, the LED Busy goes light
continually. From this point the program waits a requested time for insertion of the rest pins of
new device. If a requested time (Device insertion complete time) overflows and a device is not
correctly inserted, the program will light the LED Error to indicate this state. When new device
is inserted correctly, the status LED goes off and a new operation with device is started.
Remote control
Remote control of PG4UW control program allows controlling some functions of PG4UW
application by other application. This is very suitable feature for integrating device programmer
to mass-production handler system or other useful application.
Remote application that controls PG4UW acts as Server. Program PG4UW acts as Client.
Communication between PG4UW and remote control program is made via TCP protocol - this
allows the PG4UW to be installed on one computer and remote control application to be
installed on another computer and these computers will be connected together via network.
Default TCP communication settings for remote control are:
Port: telnet Address: 127.0.0.1 or localhost
Address setting applies for PG4UW (Client) only. Port setting applies for PG4UW (Client) and
also for Server application.
Default settings allow using remote control on one computer (address localhost). PG4UW
(Client) and remote control Server have to be installed on the same computer.
Note: If firewall is installed on system, firewall can display warning message when remote
control Server or Client is starting. When firewall is showing warning with question asking to
allow or deny network access for remote Server or Client, please select 'Allow' option,
otherwise remote control will not work. Of course you can specify in firewall options more strict
rights to allow remote Server/Client access on specified address and port only.