10-14-2015 04:30 AM
Firstly, my development PC is on a network. I deployed a Teststand sequence to another PC that is on a network without the development environment and the test sequence worked perfectly. I then deployed the same sequence to a PC that is not on a network (standalone PC) and also do not have the development environment installed. The sequence runs perfectly with the exception that the Test reports is not displaying and is also not saved anywhere.
Has anyone encountered similar problems?
I have a suspicion its something to do with network/internet connection. Can someone assist?
10-15-2015 10:24 AM - edited 10-15-2015 10:24 AM
Hello Riaan,
It shouldn't have anything to do with the network connection. Did you build your own user interface or did you use one of the examples we made? We have a simple user interface and a full-featured one. Was it one of these?
10-15-2015 11:53 PM
Hi John,
I used the simple interface.
I added a callback - ReportOptions, I am getting a report now but a cannot get the name of the Report saved correctly. It either gives me only .html or I can give it a physical name such as report1.html. I need the report name to have a unique serial number (as entered by the operator), with date and time.
Regards,
10-16-2015 05:30 AM
Hi,
I manage to get it working - I copied the .cfg content to my deployed PC and everything worked.
Thanks
10-16-2015 09:25 AM
Hi Riaan1
I'm having troubles getting the report options callback to work.
I my case the file name is missing. I just get the extension as report name ".xml"....
could you upload a seq. where e.g. the $UUT macro is working ?
10-22-2015 12:03 AM
Hi NikolajEgeskov,
I removed the callback.
I used the Configure-Result Processing option in Teststand and did the setup as per the attached.
Regards,
10-22-2015 02:00 AM
Hi Riaan1
The point was not to use the Configure-result processing option.
I have several test stations serving different purposes.
I would like to be able to deploy my image, without having to setup Configure-result processing option on each station every time I deploy a new version.
The only solution to this in my opinion is to use the report options callback in each sequence, making sure that each sequence takes care of where the reporting is done, and not some station config.
Sometimes the cfg files included in my workspace are deployed correctly but often they are not. I have no clue why this happens, but it just highlights the impotance of the above.
br
Nikolaj