 Error message |
|
|
|
|
Related links
Check out our General Code Repository Files. Also, before posting here, check to see if your post doesn't fit into another subforum by category.
Tags |
(This content has not been tagged yet)
|
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 |
 Nov 23 2004, 07:33 AM
Post
#1
|
|||
 Very Active  Member Posts: 216 Joined: 6-August 04 From: Sachsenheim D-74343 Germany Member No.: 582 LV:7.1.1 
 |
Hi!
I can't run LV, I get everytime thins error: Compiler error. Report this problem to ni tech support. copy cvt str/pict/tag, csrc=0x40 
--------------------
|
||
 |
 
|
||
| Ad |
Nov 23 2004, 07:33 AM
Post
#
|
||
|
|
|
||
|
|
|
||
|
Nov 23 2004, 09:05 AM
Post
#2
|
|||
|
Active Member Posts: 24 Joined: 5-August 04 From: Kopenhagen DeŽnmark Member No.: 577 LV:7.0 
|
QUOTE (Sarah83 @ Nov 23 2004, 09:33 AM) Hi! I can't run LV, I get everytime thins error: Compiler error. Report this problem to ni tech support. copy cvt str/pict/tag, csrc=0x40  Hi Sarah have you reported error to NI Support ? try shortlink http://forums.ni.com/ni/board/message?boar....id=3313#M76428 which brings to NI board messages. You might have to log on! Chow Xseadog
|
||
|
|
|
||
|
Nov 23 2004, 03:41 PM
Post
#3
|
|||
|
Very Active Member Posts: 216 Joined: 6-August 04 From: Sachsenheim D-74343 Germany Member No.: 582 LV:7.1.1
|
QUOTE (xseadog @ Nov 23 2004, 11:05 AM) Hi Sarah have you reported error to NI Support ? try shortlink http://forums.ni.com/ni/board/message?boar....id=3313#M76428 which brings to NI board messages. You might have to log on! Chow Xseadog Thanks, now I wrote in every forum... but there came no answer  And I can't do something... I sent an email to .ni --------------------
|
||
|
|
|
||
|
Nov 24 2004, 05:50 AM
Post
#4
|
|||
 Very Active Member Posts: 116 Joined: 9-June 03 From: Perth, Western Australia Member No.: 111 Using LabVIEW Since:2006 LV:6.0.2 ,. ,. 
|
QUOTE (Sarah83 @ Nov 23 2004, 03:33 PM) copy cvt str/pict/tag, csrc=0x40 Is is in a particular VI or when you do something? It might be a corrupt VI and deleting the offender might solve the problem. Sometimes deleting theoffending object from the VI can fix these sort of problems. cheers, Alex. -------------------- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning." Robert Cringley.
|
||
|
|
|
||
|
Nov 24 2004, 07:41 AM
Post
#5
|
|||
|
Very Active Member Posts: 216 Joined: 6-August 04 From: Sachsenheim D-74343 Germany Member No.: 582 LV:7.1.1
|
QUOTE (aledain @ Nov 24 2004, 07:50 AM) Is is in a particular VI or when you do something? It might be a corrupt VI and deleting the offender might solve the problem. Sometimes deleting theoffending object from the VI can fix these sort of problems. cheers, Alex. I created an .llb It seems that only my main .vi create this error. I opend some sub.vi's and they run without this error message. I opend an older version of my main .vi, too and this works. But in this corrupt vi are many changes of some days Edit: With LabVIEW I'm working on a local pc, withaout network... maybe my admin should install LabVIEW at this pc... so I can save every version in Star Team Client and I have a backup on the server. This post has been edited by Sarah83: Nov 24 2004, 07:43 AM --------------------
|
||
|
|
|
||
|
Nov 29 2004, 12:40 PM
Post
#6
|
|||
|
Very Active Member Posts: 216 Joined: 6-August 04 From: Sachsenheim D-74343 Germany Member No.: 582 LV:7.1.1
|
Now I programmed my main .vi new. I click on the run button and - the error is back again
I can't do something. The German support from ni said, I should wait, he forwarded my request to the USA.
--------------------
|
||
|
|
|
||
|
Nov 30 2004, 06:07 AM
Post
#7
|
|||
|
Very Active Member Posts: 116 Joined: 9-June 03 From: Perth, Western Australia Member No.: 111 Using LabVIEW Since:2006 LV:6.0.2 ,. ,.
|
Try deleting bits of the diagram one at a time (or adding bits of your code one at a time) until the error disappears/appears.
Are you calling any DLL's? They can be nasty if you do not have the correct data structures passed to them? -------------------- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning." Robert Cringley.
|
||
|
|
|
||
|
Dec 1 2004, 02:20 PM
Post
#8
|
|||
|
Very Active Member Posts: 216 Joined: 6-August 04 From: Sachsenheim D-74343 Germany Member No.: 582 LV:7.1.1
|
QUOTE (aledain @ Nov 30 2004, 08:07 AM) Are you calling any DLL's? They can be nasty if you do not have the correct data structures passed to them? Yes, e.g winmm.dll for sound. --------------------
|
||
|
|
|
||
|
Dec 2 2004, 09:07 AM
Post
#9
|
|||
|
Very Active Member Posts: 216 Joined: 6-August 04 From: Sachsenheim D-74343 Germany Member No.: 582 LV:7.1.1
|
QUOTE (aledain @ Nov 30 2004, 08:07 AM) Try deleting bits of the diagram one at a time (or adding bits of your code one at a time) until the error disappears/appears. Now I created the "test" case and the "do nothing" case. Until I wired a tunnel, there was no error message. I wired a tunnel to the case with a false constant and get the compiler error again
--------------------
|
||
|
|
|
||
|
| Time is now: 22nd November 2008 - 02:07 AM |