08-17-2018 01:14 AM - edited 08-17-2018 01:19 AM
I'm at a bit of a loss on this one and I'm in need of some NI TestStand wizardry on how to resolve this problem.
Using the following:
Windows 10
LV 2016
TS 2016
NI WLAN Toolkit 16.0
I've got an issue that I've found in the niWLAN 80211b Generation and Measurements.seq that ships with the toolkit but it's also happening in my code that is derived from that example.
Once I reload the VI prototypes and update the types in that sequence I can run it fine in the LV dev adaptor as well as the LV RTE when I'm in the Sequence Editor.
However, once I switch to the UIs (and I've tried all of them in every language and full-featured as well as simple) and try to run the code with the LV RTE I get the classic error -17600 on the first VI called in the WLAN toolkit. I've tried reordering the sequences within the file and it follows that the first VI found will error out.
To repeat: running the seq in the Sequence Editor with the LV RTE as the adapter works just fine, zero errors. Running the exact same sequence in any UI results in error -17600.
I'm at a loss on how to even troubleshoot this issue and would appreciate any assistance as I've tried iterating as best I can and am at my wits' end.
Solved! Go to Solution.
08-17-2018 01:27 AM
Is your UI built using LV? If so, can you try to build your UI with anything build LV 2016?
Regards
Anand Jain
National Instruments
08-17-2018 01:32 AM
As noted in the post this behavior happens with any shipping UI in any language.
08-17-2018 02:07 AM
Sorry missed that in your previous post.
To help debug this issue further, can you try the following:
1. Restart the Sequence Editor
2. Make sure the adapter is set to execute VIs using the RTE
3. Open your test sequence
4. Execute MainSequence.
Does your sequence run without errors or do you have to reconfigure some steps?
08-17-2018 10:43 AM
The sequence runs fine the Sequence Editor with RTE as the adapter. It throws the error I mentioned in every shipping UI with zero changes to search directories and adapter.
I run though these steps again and I didn't have to reconfigure any steps.
08-17-2018 01:00 PM
A colleague pointed out that you might be hitting a known issue with path lengths.
Can you try to move the UI from the current location to say c:\temp and running your sequence?
08-17-2018 01:05 PM
That fixed it! Is this documented somewhere?
08-17-2018 04:54 PM
Hi Jon,
TestStand R&D is tracking this CAR with ID 430428. We recently found this bug with this specific toolkit in the last month and will update our documentation to reflect this bug.
Thanks!