07-07-2021 06:31 PM
Usually with HTML, when you insert an image, the image can be located in the same folder or a sub-folder. Can I use a relative path to insert an image into the TestStand Report file?
After the documentation, it says the images must be in the same folder as the Sequence file. This would make my task very limited since a separate path is needed to put Test Reports.
Plotting the 2D data from Labview using TestStand 2016 has not worked either. Labview and
TestStand 2D arrays are trasposed between the application. Meaning you send a rowXcol array from LV, TestStand sees a colXrow array. This make it impossible to format using Attributes.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Z6fSAE&l=en-US
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kJk0SAE&l=en-US
Solved! Go to Solution.
07-07-2021 07:52 PM
Have you considered just embedding the image directly into the HTML and not having a separate file?
Go look at the mobile device demo that ships with TestStand: C:\Users\Public\Documents\National Instruments\TestStand 2016 (32-bit)\Examples\Demos\Mobile Device Test
On the LCD Video Test and any of the RF LabVIEW steps they are assigning the report text to an image string. Basically inside of the code they are taking an image of the plot and encoding it to Base 64 (which HTML can render). Then just injecting it directly into the report text (which the report doesn't modify). It's pretty slick.
The downside is that it makes your HTML file a little bigger. The upside is you don't have to lug around a bunch of loose images.
I'm not sure why the image should need to reside in the sequence file folder. That seems odd to me. I've never done that, but I used XML.
Hope this helps,
07-08-2021 11:19 AM
You hit the nail on the head. It worked.
Embedding the image is exactly what I wanted to accomplish. I pulled out 2 VIs, "Add Images to Report.vi" and "imageTobase64.vi" from the demo library. The size of the report is not an issue for me.
07-08-2021 12:05 PM
Glad that will work for you. It's very nice.
I started doing that with all of my arrays and LabVIEW graphs. It's so much better than the activex graph they use to display arrays. I'm pushing everything to a database anyway so I don't care about getting the data back out of the report.
Good luck!