PPS Pro version 8.2.pdf - 第176页
User Manual 4022 591 98247 172 PPS-Pro v8.2 05.07 Guidelines for using PPS-Pro SCREEN 86 PPS-Pro H elp C.3 Gather stage If the a ctions d escribed in the ‘pre-gather-sta ge’ d o not l ead t o a solution, all information …
4022 591 98247 User Manual
05.07 PPS-Pro v8.2 171
Guidelines for using PPS-Pro
APPENDIX C What to do in case of a problem
C.1 Survey
To enable Assembléon to find a solution data must be gathered, some checks
can be performed that may lead to a solution right away. These checks are
described in the ‘pre-gather-stage’. If eventually no solution is found, all
information must be gathered. This is described in the ‘gather-stage’. After
this stage, all information can be sent to the local Customer Support
(hereafter CS). This is described in the ‘post-gather-stage’. All three stages are
related to PPS 8.1.
If you are familiar with gathering information, the checklist can directly be
used
(see C.4 on page 178).
C.2 Pre gather stage
Before submitting the information, you can try to find the solution by
yourself. This chapter provides you with some checks which can be performed
in order to attempt this:
■ Check the Release Notes if it is documented and known
■ Use the manual, maybe the solution is already described.
■ Ensure that the latest software version has been installed.
■ Place the project on a local drive if it is not already placed.
■ Check if the length of the total path does not exceed the maximum path-
length which is described in the user manual.
■ Delete all spaces in path and file names.
■ Delete all forbidden characters which are described in the user manual.
■ Use the correct ALE file.
■ Use the correct PSI file.
■ Use the correct aperture files
■ Check that there is enough free diskspace available (20Mb).
■ Check the read/write rights on the involved files and/or directories.
■ Use Help (see SCREEN 86 on page 172).
User Manual 4022 591 98247
172 PPS-Pro v8.2 05.07
Guidelines for using PPS-Pro
SCREEN 86 PPS-Pro Help
C.3 Gather stage
If the actions described in the ‘pre-gather-stage’ do not lead to a solution, all
information must be gathered and send to the local CS provider
(see C.4 on
page 178). The calculation can only be reproduced when they have the same
circumstances and information available. This is very important, it is for the
benefit of all parties that correct and useful and understandable information
is provided. If language is a barrier then ask the local CS provider to translate
the information.
1. Describe the project.
■ Make a screendump of the error or warning which is shown. The
screendump can be made by pressing the Alt+Print Screen keys when the
error or warning is the active window. Further, copy this screendump into
a new file of an image-editor and save it.
4022 591 98247 User Manual
05.07 PPS-Pro v8.2 173
Guidelines for using PPS-Pro
■ Make notes of all steps which were taken before the problem occurred.
2. Describe what has already been investigated.
The checks of the ‘pre-gather-stage’ (see C.2 on page 171) can be used as a
reference for this description.
3. Used Version
For the FCM/ACM optimizer the version of the installed build can be found by
right-click an ‘.exe’ file (for example ‘ale.exe’) of the PPSPro/Bin-directory and
choose the P
roperties menu item (see SCREEN 87 on page 173). Select the
Version tab and select Build version from the Item Name list. The version can
be read from the Value list
(see SCREEN 88 on page 174).
Action: Write down the Build version.
SCREEN 87 PPS Software Version
Some tips w.r.t. this subject:
With the FCM/ACM optimizer add the optimizer version information, in a
default installation these can be found in the properties of the following file:
C:\Assembleon\PPSPro\Bin\Philips\opt_calc.exe
To find the version of the A-Series optimizer, check the first line of any PP
made by the same optimizer.
Always mention this information when communicating with Assembléon
about a your project.