06-14-2007 01:12 AM
I am getting a CVI Expired message when I run my code. I was running this with evaluation version of both CVI and LabView but have since replaced these with full versions.
I have gone through all the DLLs I created and re-created them with versions built with the full versions but I still get the message. I am running TestStand version 2.1 as my test executive with CVI, version 7.1, used for DIO and utils. I am also using Labview, version 8.2, to talk to I2C.
So is there anyway to check which DLL is causing this issue? I went through the code and could find no DLLs called that I have no re-built.
Please help as this message and the removal of it is getting very irritating.
Thanks in advance.
.06-15-2007 03:38 AM
Hi,
Can you post a screen shot of the error message that you are seeing?
When does this occur - is it when you load the sequence in TestStand, or does it occur when you are running the sequence files? If its happening during run time, what happens if you slow the execution by enabling tracing in the station options, and slowing down the speed of the execution - can you see which step is causing the error? What if you run using the debugging tools?
Are you able to test this on a another machine with the software installed? Are all your code modules dll's - or are you calling the source files directly?
How do you have the CVI adapter configured? Are you running the CVI steps 'in process' or using an external instance of CVI?
If you can get back to me with this, and some more details of the issue, I'll take a closer look for you
Regards
Hannah
NIUK & Ireland
06-18-2007 05:49 AM
Hannah,
I am unable to post the image of the box but the message says
"The current program has exceeded the maximum time allowed in this Demo of LabWondows CVI"
with an OK button.
In reply to your questions
When does this occur - is it when you load the sequence in TestStand, or does it occur when you are running the sequence files? If its happening during run time, what happens if you slow the execution by enabling tracing in the station options, and slowing down the speed of the execution - can you see which step is causing the error? What if you run using the debugging tools?
This happens after 10 to 15 minutes of the TestStand restarting even if we are not running anything.
Are you able to test this on a another machine with the software installed? Are all your code modules dll's - or are you calling the source files directly?
Cannot get it installed it onto another machine since this is customers software and machine. The CVI is all DLLs, we call ther Labview directly
How do you have the CVI adapter configured? Are you running the CVI steps 'in process' or using an external instance of CVI?
I have tried running the CVI in both modes and still get the message. TS2 shutsdown if I switch between these setting but works OK when I restart this.
Thanks in advance.
06-19-2007 03:27 AM
Hi,
If you look in the NI license manager software - does it show CVI as licensed correctly? Go to 'Start>>All Programs>>National Instruments>>NI License Manager' in the list you should see LabWindows/CVI - and it should have a green square next to one of the development systems listed?
What version was the evaluation software for LabWindows/CVI that you had before you got the fully licensed version? And is this LabWindows/CVI Full or Base development system that you have?
Regards
Hannah
NIUK & Ireland
06-22-2007 02:25 AM
Hanah
The CVI shows up properly on License manager, can you provide an email where I can send a screen dump, but TesStand does not show up at all. The TestStand version is 2.1.
06-22-2007 05:45 AM
06-22-2007 05:54 AM
Hanah,
I have basic support so I am not allowed top use email support, any suggestions on how to proceed?
06-22-2007 06:00 AM
06-25-2007 04:38 AM
06-26-2007 06:24 AM