AnsweredAssumed Answered

Using Custom Testplans in 7.10p

Question asked by AaronM on Jul 21, 2008
Latest reply on May 11, 2009 by dbailey

Like • Show 0 Likes0
Comment • 9

We are using a customized testplan currently in 5.x. We have recently setup a dual-boot machine to work on upgrading to 7.10p. So far we have ran into a major stumbling block with 7.10p. Our testplans ask for operator input. However, we could use some advice on how to handle this in the GUI since there is only an output window for BT-basic.

1. Is it possible to create a msgbox asking for operator input?
2. I noticed that the migration presentation had a slide about running in a classic mode. I do not have audio capability, and was wondering how to set this up. Thanks

No one else has this question

Outcomes

9 Replies

bodaiji Jul 21, 2008 11:17 PM
Mark Correct
Correct Answer
Hi,

I think 7.10p support the softkeys like what we used to have when running in the BT Basic window. Maybe that can help?

For classic mode, it is basically the BT-Basic mode. I think you can simply launch a BT-Basic window load in the testplan (get "testplan") and run it like what you do with 5.x software. Just don't launch the GUI.

But then, you lose the features that you get in the GUI like the Optimiser, Board browser, AutoDebug etc.
Like • Show 0 Likes0
Actions
alfred_poelderl Jul 22, 2008 2:19 PM
Mark Correct
Correct Answer
If you are interested to create a window which will pop up and will offer some user input this should be possible by creating a perl script.

Here an extremly simple script, asking a question and expecting an yes/no :

use Win32;
$result = Win32::MsgBox('Do you want to stop?', 16+4);
print $result;

You should be able to call this script with the bt-basic enter instruction and get the result to a variable.
Like • Show 0 Likes0
Actions
AaronM Jul 25, 2008 2:23 PM
Mark Correct
Correct Answer
Thanks for the response, I will let my guys know.
Like • Show 0 Likes0
Actions
daICThack Aug 14, 2008 1:08 PM
Mark Correct
Correct Answer
If you login as tcm instead of operator you will get a operator interface like older versions...

da Hackerz
Like • Show 0 Likes0
Actions
dbailey Oct 21, 2008 6:21 AM
Mark Correct
Correct Answer
How about operator input. I'll need the operators to hand enter bar codes that cannot be read by fix mounted scanners on the fixture.

Does anyone know if there is an inputbox function that will work?
Like • Show 0 Likes0
Actions
oconnellj Oct 31, 2008 5:32 AM
Mark Correct
Correct Answer
for the new operator interface, you can have a operator prompt by using the bt basic command 'input prompt'

with the new operator interface this will open a new window and prompt them to enter either a barcode or a version label for instance. With this command you specify both the title of the question box and the string holder to capture the return from the entry, it works in exactly the way you have described and syntax definition is detailed within the new manuals.

if you need any examples let me know and i can send to you
Like • Show 0 Likes0
Actions
wangside1 Dec 8, 2008 11:35 AM
Mark Correct
Correct Answer
How would you call a sub routine in Vee Pro, using a perl script?

ex:
//perl
hellow_world();

// Vee pro
module hello_world();
print "hello world";
end
Like • Show 0 Likes0
Actions
aakkoc May 11, 2009 2:07 AM
Mark Correct
Correct Answer
Hello, I have a question and I didn't know how to ask so I did here. We have an HP3070 sistem and we have just upgraded it to the windows. And we now have thre problem:
1. We use custom testplan to test, print and logs. Now on windows it cannot create new file and write to it because of the permission problem. How do we get this problem?
2. It cannot print directly, we can solve this by printing the logs afterwards, but is it possible to print the test resul directly?
3. On windows, how do we use the control card RS232 interface?

I will be very pleased to get any answer to my questions. Thank you very much
Like • Show 0 Likes0
Actions
dbailey May 11, 2009 4:46 AM
Mark Correct
Correct Answer
I'm not sure, exactly, what you are describing. But...

When transferring a UNIX testplan to a Windows machine, the rs232 oti initialization commands changed.

Permissions will need to bee set up by some kind of IT person, make sure that the any users that use the folders have persmission to access, write or read to them. We found that even the most basic persmission needs to run tests were NOT set up by the install program.

If you have code in the testplans that include directory paths, you'll need to make sure that they match the new paths in the Windows hard drive. AND, if you upgrade from 5.42 to 7.XX, the paths change again (from .../Agilent3070/... to .../Agilent_ICT/...)

Even though you are now in the Windows envionment, the back slash, forward slash usage in paths remains the way they are used in the UNIX environment - c:/Agilent_ICT/boards
Like • Show 0 Likes0
Actions

Using Custom Testplans in 7.10p

Outcomes

Related Content

Recommended Content