01-04-2011 04:27 PM
Hi All,
I am trying to run Labview VI 2010 in Signal Express. It gives me "version unknown" problem. When I checked the versions for Labview it says 10.0f2 and the Signal Express can read LabView 2010 version. I don't understand this. Isn't 10.0f2 just a patch for 10.0 version ? I will appreciate it if someone can help me out with this.
Regards,
Kanu
Solved! Go to Solution.
01-05-2011 11:28 AM
Hi Kanu,
I tried writing a simple VI and importing it to Signal Express and I had no issues. I am using LV2010f2 32 bit and Signal Express 2010. I have attached the VI that I used so that you can try it yourself. I followed the instructions in this KB to create a source file distribution. If you follow this KB and still can't get it to work, can you please post the VI?
Thanks,
01-05-2011 04:32 PM
Hi Paul,
Thanks a lot. I was trying to directly run the VI without creating LLB and building it. My problem is solved 🙂 .
Kanu
01-05-2011 05:53 PM
Hi Paul,
I have one more question. Is there a way I can import signal express VI into labview VI ? Also, I need to do certain modification to the signal express VI.
Thanks,
Kanu
01-06-2011 09:46 AM
Hi Kanu,
To generate a LabVIEW VI from signal express code, go to Tools » Generate Code » LabVIEW Diagram. You will be prompted to save the VI and then it will be created for you. You can read this KB for some caveats pertaining to VI generation.
03-30-2011 03:37 AM
I have a question here.Could you please help me solve it.It's about importing LabVIEW VIs into LabVIEW SignalExpress as Steps.
I have read Getting Started with LabVIEW SignalExpress ,and I can import Limiter-LV86.vi in the SignalExpress\
Examples\Tutorial into User Step.seproj. But when I build a new VI myself ,the INPUT and OUTPUT is gray.Then I build another file by copying Limiter-LV86.vi,and it shows the same. I dont know why.
Thank you very much for reading this.And I wonder if you could please send me some other examples(I mean some VIs which can be imported into LabVIEW SignalExpress as Steps)
03-31-2011 02:43 PM
Hi!
This KnowledgeBase article should be fairly helpful for your application. It shows you how to configure your VI to work with SignalExpress.
Using a LabVIEW VI with LabVIEW SignalExpress
One thing I noticed when I opened your My File VI is that you did not have your connector wired. This would cause those Input and Output areas to be grayed out.
Also, one thing at the end of that KnowledgeBase that should be noted: You cannot run a VI that was saved for a previous version of LabVIEW using the Run LabVIEW VI step in Signal Express. You must save the VI in the actual version of LabVIEW you specify in the Run LabVIEW VI step.
I hope this helps!
Kim W.
04-21-2011 04:49 AM
Your help is greatly appreciated, and I'm grateful for it.I have solved the problem.
04-28-2011 12:45 AM
I have another problem now. It's about importing LabVIEW VIs into LabVIEW SignalExpress as Steps too. I try to add a Filter in a LabVIEW VI,and the VI can be imported into SignalExpress as Steps. I know we can add a filter :add step-->Processing-->Analog signals-->Filter. However,I want to expand the functions of SignalExpress by importing LabVIEW VIs. I build a new VI myself and it shows:Error occurred in Run LabVIEW 8.6 VI step.
The VI is not executable. Please verify that the VI is not broken and saved as a Source Distribution (which "Includes vi.lib Files") and is within a Linked Library with the ".llb" extension.
I'm a beginner,and I don't know the reason.Could you please help me? I am using LV8.6 32 bit and Signal Express2009.Thank you very much for reading this.And I wonder if you could please send me some other examples(I mean some VIs which can be imported into LabVIEW SignalExpress as Steps) .
04-29-2011 11:32 AM
This could be caused by one of two issues.
1: The
VI that you are trying to open is broken and can not be run. Open the
VI in LabVIEW and verify that it is operational in the LabVIEW
development environment.
2: The VI
isn't built into a source distribution that is compiled as a library
that includes the vi.lib files.
To do this you need to: