| T O P I C R E V I E W |
| DaveLangstaff |
Posted - 09/21/2006 : 12:24:22 PM
Hi,
Since upgrading my copy of Labview from 6.1 to 8.0.1, the Labview browser in OriginPro (v7.5) no longer works.
When selecting from the menu (Tools|Labview Vi browser...) I get
an alert box (Labview Import Dialog) saying Labview not available.
Does anyone know if Origin works with Labview 8 and is there a way of re-establishing contact between the two programs ?
I know I can write my labview Vi to call origin, but that's a bit long winded for the one off application I'm using.
regards
dave L
|
| 9 L A T E S T R E P L I E S (Newest First) |
| zachary_origin |
Posted - 10/09/2006 : 05:53:30 AM
Hi dave L,
Yes, I have the same problem as you. It seems it is really the reason you mentioned: the VI path name for LabVIEW.GetVIReference is not absolute path. This is indeed a bug in Origin connecting with LabVIEW 8.0. Later we will fix this bug and we will inform you if it is fine. Thanks for your time and effort.
Zachary
OriginLab Technical Services.
Edited by - zachary_origin on 10/09/2006 05:56:32 AM |
| DaveLangstaff |
Posted - 10/02/2006 : 07:14:38 AM
Hi Zachary,
Thanks for that, unfortunately, we've still got a way to go.
I've checked that "Origin Automation Server.llb" is in the <labview>/user.lib directory and have mass compiled it to ensure it is good for labview 8.0
The symptoms seem to be that if labview is not running, or if only the opening screen is open, I get a dialog box asking to pick a vi to browse. I can then navigate to pick a vi, another dialog box (Labview Vi Import) then shows the name of the vi, with full pathname and a tree of sub-vis below it. Thus far so good, unfortunately there aren't any controls shown on the right hand side of the dialog box and both the import buttons are greyed out.
If I have any vi's open in labview when I attempt the import, I get a 'Labview not available' message.
regards
dave L
|
| zachary_origin |
Posted - 09/30/2006 : 02:02:49 AM
Hi dave L,
That is great to know your progress on this.
Regarding fails in Labview.GetVIReference() method, I think of something maybe more common, which is you need manually copy the VI library in Origin (Origin Automation Server.llb) to the \user.lib subfolder of the LabVIEW installation folder so that LabVIEW can find the VIs.(see Origin:Help, Interfacing With Other Applications> LabVIEW> Origin VIs for LabVIEW for detailed operation.) This problem usually occurs when LabVIEW is installed after Origin. From the "symptome" you mentioned, it is most likely this problem. Now it fails only because LabVIEW can not find the needed VIs in its folder.
Maybe I have made the simple thing a little more complicated before. Would you give a try and tell the results? Hope it works now.
Zachary
OriginLab Technical Services.
Edited by - zachary_origin on 09/30/2006 02:04:25 AM |
| DaveLangstaff |
Posted - 09/29/2006 : 12:13:38 PM
Hi Zachary,
Just to let you know how I've been getting on...
The method Labview.GetLVExportedVIs() seems to work ok, returning a list of the names of all labview vi's in memory at the time.
Problems seem to come when Labview.GetVIReference() is called, this
routine returns false, whatever name of Vi is given to it.
Looking at the macro in FreqResp.xls and also other bits of example code from the NI web site, it appears that GetVIReference() is usually called with the full path to the VI, rather than just the name - its possible this may be the problem.
Hopefully I may be able to look at the problem a bit more next week.
regards
dave Langstaff |
| zachary_origin |
Posted - 09/28/2006 : 10:34:48 PM
Now it seems the problem is in Origin.
Yes, you can debug it in code builder. The corresponding file is OriginInstallation\OriginC\OriginLab\LabViewImport.c. Frankly, we have not tested LabVIEW8 in Origin75 because LabVIEW has not released V8 before the release of Origin75. So it is great appreciated that you will try to find what is the problem in your case.
You can reference Progamming Guide: Calling Other Applications from Origin: COM Client Programming in Origin:Help. This may do some helps.
Any problem during debugging, please let me know.
Zachary
OriginLab Technical Services. |
| DaveLangstaff |
Posted - 09/28/2006 : 08:48:07 AM
Hi Zachary,
Starting to get somewhere, but we're not there yet...
I managed to get the freqresp.xls example you mentioned working ok,
so it would appear that Labview is working as an ActiveX server. I can get labview to do some calculations and post the results back into an excel graph, so comms look to be there.
However the Tools|Labview Vi browser... menu item from Origin still gives the Labview not available response.
I'm not sure how to proceed now, is there any way I can debug the Vi browser to try and find out at what point things are going wrong ?
regards
dave L |
| zachary_origin |
Posted - 09/22/2006 : 11:03:38 AM
Hi dave L,
Here is a link from NI about using ActiveX with LabVIEW.
http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/using_activex_with_labview/
In the LabVIEW as an ActiveX Server section, it is mentioned that there is an example about using LabVIEW in excel (labview\examples\comm\freqresp.xls). You can try this example to see if it is the problem of LabVIEW ActiveX server.
Zachary
OriginLab GZ Office |
| DaveLangstaff |
Posted - 09/22/2006 : 06:10:31 AM
Hi Zachary,
Many thanks for looking into this...
I've tried that and still get the same repsonse. The Labview ActiveX
checkbox was already checked when I looked.
I've also tried running the repair option from the Origin installation routine.
Have you any ideas on how I might split the problem down? ie. is it labview not serving the activeX or is it origin not finding it ?
regards
dave L
|
| zachary_origin |
Posted - 09/21/2006 : 11:07:00 PM
Hi Dave L,
It seems that LabVIEW ActiveX server is not available. You should activate it. On how to activate it, you can see LabView Help > Fundamentals > Windows Connectivity > ActiveX > Activating LabVIEW as ActiveX Server.
I installed Labview 8.0.1 Evaluation version and it works well. But if I uncheck the ActiveX checkbox in LabVIEW, I got the same information like you. So I think it is just the problem that you met.
Hope it helps,
Any questions, feel free to contact us.
Zachary
OriginLab GZ Office |
