AnsweredAssumed Answered

Testjet failure

Question asked by Carol on Oct 16, 2011
Latest reply on Oct 20, 2011 by adrianc

Like • Show 0 Likes0
Comment • 7

Hello,
I got an ICT fixture and program transferred from another site. It worked fine there, but failed TestJet here.
It failed everything tested by TestJet indicating that this test doesn't work.
I checked the board config file. It matches with the tester's config file.
I run the same test software both on Windows and Unix. The failures are the same: TestJet doesn't work. Everything else passes.
Can some one give me some clue what else I should check? Thanks in advance.

No one else has this question

Outcomes

7 Replies

Carol Oct 17, 2011 8:02 AM
Mark Correct
Correct Answer
Hello,

I double checked the board config file. I found it enabled advanced fixturing for which my tester doesn't have this feature. Also, when I recompile the "fixture" file, I got a lot of errors. Is this the reason that causes the TestJet failure? Thanks.
Like • Show 0 Likes0
Actions
adrianc Oct 17, 2011 8:17 AM
Mark Correct
Correct Answer
Carol,
It should not be because of the enable advanced fixturing statement in the config file. But it is curious that the config file compile fails.
Could you send the board and system config files?

Also, please state what version software are you running now that is seeing the problem, as well as the previous software revision when it was working.
Like • Show 0 Likes0
Actions
adrianc Oct 17, 2011 8:33 AM
Mark Correct
Correct Answer
Carol,
Something that I missed out earlier ...
The "enable advanced fixture" means that you are using "custom probes" for this fixture. It is possible that the custom probes defined are not found in the system that you are using right now.

The directory containing the "custom probes" are
1) C:\Agilent_ICT\standard\fixture\components or
2) your board directory ... <board directory>/custom_fix

To be sure that the fixture source file is correct, in the BTBasic window ... list object "fixture/fixture.o" over "fixture/fixture"

Are you able to send the listing of the compile of the fixture file? From BTBasic window, ... compile "fixture/fixture";list ... then send the file "fixture.l"
Like • Show 0 Likes0
Actions
Carol Oct 17, 2011 10:47 AM
Mark Correct
Correct Answer
Hi Andrian,

Thanks for your reply.
The below is the typical error in my "fixture.l" and there are 100 similare errors is the file.
There is "39MilProbe" file in my "custom_fix" folder.

NODE GEN_BUSY
      PINS
        20443;
      PROBES
        P1282     75450,   61640 39MIL;
                                      ^
This parameter value is not recognized. (ERROR FDF4)

                                      ^
This parameter value is not recognized. (ERROR FDF4)

                                      ^
The sequence of keywords and values does not make sense. (ERROR FDF19)[/code][/code]
Like • Show 0 Likes0
Actions
adrianc Oct 18, 2011 3:17 AM
Mark Correct
Correct Answer
Carol,
This looks suspiciously that the 39mil code is not recognized by the test software.
Could you tell me what software release version you are using?
Type in korn shell window ... "version".
If you are using a software version earlier than 05.00p to run your test programs, you could get the errors because the system does not recognise the new syntax.
Like • Show 0 Likes0
Actions
Carol Oct 18, 2011 6:01 AM
Mark Correct
Correct Answer
Hi Andrian,

I'm using 5.21pb 0103UX and 8.2.0p Windows. Thanks.
Like • Show 0 Likes0
Actions
adrianc Oct 20, 2011 7:35 PM
Mark Correct
Correct Answer
Carol,
From what I can see from our records, that 05.21pb supports "advanced fixturing". It is supported since 05.00p.

Just to clarify, what do you mean by "5.21pb 0103UX and 8.2.0p Windows". Are you running "5.21pb 0103UX" on windows?
Like • Show 0 Likes0
Actions

Testjet failure

Outcomes

Related Content

Recommended Content