In Circuit Test Systems
to create and rate content, and to follow, bookmark, and share content with other members.
log record autofile in 07.2
Question asked by
on Apr 29, 2009
on Jun 8, 2009 by dbailey
Show 0 Likes
It appears that the autofile (fixture id) number does get into the log record using the 'tcm' login on version 07.2 on the 3070. Is this a known issue with 7.2, or with the 'tcm' account login?
No one else has this question
Mark as assumed answered
This content has been marked as final.
Show 2 comments
(Required, will not be published)
Jun 1, 2009 6:18 AM
I discovered the same thing when we attempted to use the autofile ID in logfiles and contacted Agilent about it. It's not just the tcm login, it's a problem that began at a certain software release level. I have found that the autofile ID is available in the testplan, just not in the log file. We print the autofile ID and system hostname out with fail tickets and that works fine still.
I have been told that this WILL be fixed! I think the term I heard from the support engineer on the phone was that they wouuld issue a 'hotfix'.
In the meantime, there is an official workaround (I have not tried this because it seems lame, if our data collection required it, I would.) The workaround is to unlock and lock the fixture inside the testplan, maybe try adding this cycle somewhere during the start up initialization (around version prompting, if you use that). Cycling the fixture is supposed to look up the autofile id and store it. Not sure if it is required per board or per run. Per board would be excruciatingly lame.
Just this morning I got a second, advertisement, response from Agilent informing that this issue will get fixed before the next complete software release is sent out.
So this issue will get fixed. Below is the text of the e-mail I received (note the sales talk!):
This letter is regarding a change request that was generated for an issue you have communicated to us. The reference number for that change request is CR33541 and a brief problem description is as follows:
As of 7.10pc, Log Board does not include the Fixture ID (autofile) in the @Batch log record.
This issue has been carefully reviewed and we have decided to address it appropriately. The change request is scheduled to be available for early distribution in Oct 2009 and for broad distribution in Dec 2009. This release date is only an estimate and is subjected to change without prior notice.
If you need to contact us about your issue, please call Agilent's Customer Support Center. To find the phone number for your location go to the Agilent Contact Us website and select your country:
It is our goal to provide enhancements that best meet the needs of all our system users. In our latest 07.20p software release, we have incorporated enhancements and eliminated defects for more than 69 unique change requests recommended by customers.
We encourage you to update to the 07.20p software release to begin receiving the highest level of support from Agilent and to enjoy the competitive benefits from the latest enhancements.
Please continue to offer your suggestions for improving our products.
For your information, we have introduced our latest In-Circuit Test system - i3070 in Feb 2007 and equipped with the latest software revision 07.20p since Nov 2008.
HP-UX based systems have already crossed our earlier communicated End Of Support. To assist customers with the EOS, we have since launched an exciting UNIX to PC conversion program. We encourage you to contact your sales representative for more details.
Thank you for giving us the opportunity to assist you and for contributing to the quality of our products.
Show 0 Likes
Jun 8, 2009 4:27 AM
I received the hotfix from Agilentand installed it. It works fine on 7.20pc
Show 0 Likes
Retrieving data ...
Oscilloscope’s Frequency Counter Hacked! (kinda)
vrf Linux port
vrf (Interfacing with C DLL)
How do i use 82357b IO Libraries in Borland C++ Builder...
[MP4] C++ Model Builder