02-21-2013 08:20 AM
Hello,
I've been using the batch model.
I have 3 test sockets that run the same sequence.
I've been using the standard Window from Batch model to accept the entry of UUTs
I've found that the following property:
RunState.Main.Logging.UUT.SerialNumber
Contains the data entered in that window.
Everything was running fine for days on end.
However one of the days the technitian that was running the tests on the test rig came up to me saying that the software starts tossing errors at him stating that the property is not found.
I've checked and when I try to debug the sequence
the Logging component no longer appears ....
When i run the same test sequence on my Laptop the issue doesn't appear.
Any hints why this might be happening would be appreciated.
Regards,
Maciej
Solved! Go to Solution.
02-22-2013 10:02 AM
Do you perhaps have a customized process model? I do not think RunState.Main.Logging.UUT.SerialNumber is a location that normally exists.
I think with the default models you can get the serial number here:
RunState.Root.Locals.UUT.SerialNumber
-Doug
02-25-2013 05:24 AM
I have been using the batch model.
I've started with the BatchUUT.seq file and extended it, as far as I'm aware I'm using a standard Batch process model.
The variable has worked and existed at that location but for some reason ins't availible to me anymore.
I found it by browsing though the watch window ... so I wasn't sure if I can "count" on the presence of the serial number under that address.
Thank you for your suggestion, I'm off-site today and won't be able to check the suggestion you've made directly on the test station but I'll do that Wednesday
Regards,
Maciej
03-01-2013 07:46 AM
well I managed to find
RunState.Root.Locals
but there doesn't seem to be a
UUT.SerialNumber
property where I can find the uut serial number input by the user.
I am using the parallel model.
Where can I find the UUT information?
03-04-2013 09:52 AM
Have you tried looking at that location while at a breakpoint in the execution document? It probably does not exist at edit time, but should exist at runtime.
-Doug