Dataman 448PRO2, Руководство пользователя, Страница: 153 / 168

Common notes
153
Biannual maintenance
Perform the Selftest for every programmer or programming module.
Annual maintenance
Gently clean the surface of the programmer with isopropyl alcohol or technical alcohol on a
soft cloth. The LCD clean with a soft cloth moistens in water only. Isopropyl alcohol may
damage surface of the LCD.
Perform the calibration test if the programmer supports this feature.
Warning:
The ZIF socket of the programmer and the socket converters are considered as consumables.
The life cycle of the ZIF socket of the programmer' is about 25.000 mechanical cycles. The life
cycle of ZIF sockets of the socket converters is in generally from 5.000 to 10.000 mechanical
cycles, even if the life cycle of some specialized BGA ZIF sockets can be about 500.000
mechanical cycles. Programmed devices, environment and ZIF maintenance have direct
influence to actual electrical lifetime of ZIF socket (it means that ZIF socket does not cause
programming failures yet). Keep fingers away from contacts of ZIF socket, because contacts of
the ZIF socket fouled by smear and grime from fingers may cause the programming failures.
Change the ZIF socket or the socket converter if you noticed increased number of
programming failures.
The warranty does not apply to the ZIF sockets that are wear or grimy and which cause large
amount of failures during working with programmer.
Software
PG4UW is common control program for all of the DATAMAN programmers. Thus, during work
with him it is possible to find some items; those refer not to current selected programmer.
Some special devices (e.g. Philips CoolRunner family) require external DAT files, that aren’t
present in standard PG4UW SW delivery on CD. If you need to program these devices, look at
www.dataman.com , section Download.
Command line parameters
We recommend using special utility pg4uwcmd.exe to make command line parameter control
of PG4UW. For backward compatibility there is possible to use some command line
parameters also directly with
pg4uw.exe , but better way is to use pg4uwcmd.exe , which has
support of more command line commands and also it has capability to return ExitCode (or
ErrorLevel) value indicating success or error result of executing command line parameters. For
more information about using
pg4uwcmd.exe command line controller for PG4UW , please
take a look at Remote command line control of PG4UW .
Command line parameters which can be used directly with pg4uw.exe
/Prj:<file_name> forces project load when program is starting or even if
program is already running, <file_name> means full or
relative project file path and name
/Loadfile:<file_name> forces file load when program is starting or even if program
is already running, <file_name> means full or relative path to
file that has to be loaded, file format is detected
automatically