LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Solutions for these 'OCR' error codes:

Hi,
 
I have a labview application, but it doesn't work properly because it has errors (see nierror.doc)
 
If anybody knows how to solve these problems, we will be gratefull, becuase we can not solving them.
 
Thanks
0 Kudos
Message 1 of 7
(3,729 Views)

Hello,

The first says:

 IMAQ Vision: (Hex 0xBFF604A5) File not found. So some file it's missing. Simple, no? Smiley Happy

But you don't wanna post the .vi? And say what's your labview version.


Software developer
www.mcm-electronics.com





PORTUGAL
0 Kudos
Message 2 of 7
(3,726 Views)

Hi,

Ok, but the file exits and it is in the correct place. Because it appears on the front pnel, I mean the same name that the file that vision builder has done in the migration.

My aplication is migrated from vision builder to labview. It doen´t run poperly when I build an aplication. But it does when I run my main.vi. It only does not work when I use it like an aplication.

I have done everything that I was supposed to do to build it, but the OCR does not find a file and does not open the session.

I post some pictures that explain the error, I´m sorry because it is in spanish, but you can see where the problem is.

Thanks

0 Kudos
Message 3 of 7
(3,719 Views)

Hai sioux,

See this error code image. Try to solve it out.

"You might have wired a number that is not an error code to the error code input".

0 Kudos
Message 4 of 7
(3,717 Views)
It's much more difficult to see your doc. I can only see the code. If you don't wanna show all the code. Cut to the essencial.
Software developer
www.mcm-electronics.com





PORTUGAL
0 Kudos
Message 5 of 7
(3,705 Views)
Hi Sioux,

"It doen´t run poperly when I build an aplication. But it does when I run my main.vi"

This is most often a problem of not correctly building path to files as in an executable the base path changes! When you use "path to vi" you have to strip one more folder from the path as the executable acts as an additional folder in the vi path... There are lots of threads explaining this behaviour!
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 7
(3,703 Views)
Hi Jorge,

see this screenshot for this behaviour... On the right side you have the exe and on the left the VI. As you see the paths are diffrent.

Greetings


Message Edited by RMathews on 04-02-2008 09:14 AM
Ramona Lombardo
Applications Engineer, NI Germany
Certified LabVIEW Developer
Message 7 of 7
(3,667 Views)