Check out the related Code Repository Files or visit the LabVIEW Wiki Development Environment Portal
Tags |
(This content has not been tagged yet)
|
![]() |
May 21 2004, 02:21 PM
Post
#1
|
|||
|
Active Member Posts: 22 Joined: 21-May 04 From: Fort Belvoir, VA Member No.: 423 LV:7.0 |
I am new to labview and I had a question to ask.
-------------------- Thank You
Paul F.
|
||
|
|
|||
| Ad |
May 21 2004, 02:21 PM
Post
#
|
||
|
|
|
||
|
|
|||
May 24 2004, 06:18 AM
Post
#2
|
|||
|
Extremely Active Member Posts: 391 Joined: 6-February 04 From: switzerland Member No.: 253 Using LabVIEW Since:1997 LV:7.1.1 ,6.1 ,.
|
Paul,
Did you try to install the 6i Version of your DSC-package on LV7? It might work, I didn't do it. Just by copying the files wouldn't work because the DSC has a whole engine (with a database) running in the background. It is based as a client-server system. At least you'll need the whole client part (if the server with the database is running on an other machine). Didier
|
||
|
|
|||
May 24 2004, 04:45 PM
Post
#3
|
|||
|
Active Member Posts: 22 Joined: 21-May 04 From: Fort Belvoir, VA Member No.: 423 LV:7.0 |
That sounded like a good idea to me too. I asked my superiors and unfortunately they can't locate the dsc library CD because it was purchased such a long time ago and no one knows where it is
-------------------- Thank You
Paul F.
|
||
|
|
|||
Jun 7 2004, 04:13 AM
Post
#4
|
|||
![]() Confucius say: Crowded elevator always smell different to midget Admin ![]() Posts: 2402 Joined: 13-October 02 From: Planet Earth Member No.: 2 Using LabVIEW Since:1994 LV:8.5 ,8.2.1 ,7.1.1
My Blog
My Gallery
|
QUOTE (Paul @ May 21 2004, 10:21 AM) I went ahead and opened the directory in the old machine and tried saving those 3 vi's and trasnfering over, but the block diagram was protected and 7 would not read it. Are you sure you did this correctly? Even if the block diagram is password protected, LabVIEW should still be able to load the VI and recompile it for the new version. I think it's more likely that the 3 VI's are calling other subVI's that you didn't bring along to the new machine. It could even be a DLL call that cannot be made because the DLL's are missing. Who knows? Create and save new blank (Untitled) VI in 6i and plop the 3 VI's on the diagram of this new VI. Now from the menu select File>>Save With Options. Make sure you select Save entire hierarchy in the dialog box. Also select include vi.lib files and external subroutines. Save to a different directory and then try opening this Untitled.vi in 7.0
Attached image(s)
-------------------- Thank You
Michael Aivaliotis - Follow me on Twitter - My Personal Blog Search the LabVIEW Web - Build the LabVIEW Web - Got VIPM? ![]()
|
||
|
|
|||
Jun 12 2004, 08:34 PM
Post
#5
|
|||
|
Very Active Member Posts: 164 Joined: 18-March 04 From: Canada Member No.: 311 Using LabVIEW Since:1995 LV:8.20 ,7.1.1 ,.
|
Hello Paul,
Looks like you first had LabVIEW 6.1 and DSC 6.1. Then you moved to a different machine with only LabVIEW 7.0 (but no DSC). And you want to run those VIs. I am afraid this won't work. Even if you find and get all the VIs and the DLLs, there are other things in DSC like the DSC Engine, the Citadel database, system services, built-in servers and proxies, third-party servers, etc., which would make it impossible for you to run the DSC-created application on just pure LabVIEW (assuming your app does indeed use the DSC features). At the minimum, you would need a Run Time System of DSC (different from the LabVIEW Run Time Engine). What you can however do is, install the DSC 6.1 on LabVIEW 7.0. This combination will work fine. If the DSC 6.1 CD is missing, you may want to contact your NI Sales person to get it replaced. I am sure they have your purchase records. Finally, another option is -- depending on what your app did -- you can try to make it a non-DSC, pure-LV app. Hope this was helpful. Regards, Khalid Ansari
|
||
|
|
|||
![]() ![]() |
| Time is now: 8th January 2009 - 07:36 PM |