LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error7 occurred

In the attachment you will find the paths.vi

0 Kudos
Message 11 of 23
(274 Views)

I am not seeing that the paths.vi is creating a path for the CRCCOL Calibration global.ini

Is that right?

should I add this to my vi?

Download All
0 Kudos
Message 12 of 23
(274 Views)

You are right, Paths.vi doesn't add the .ini.

 

CRCCOL Shunt Calibration Global.vi, gets the configuration folder path and then adds CRCCOL SHUNT Calibration %d.ini. My guess is that, in Paths.vi you are not getting the right Configuration Path set.

Can you add some indicators on the path flow to check what is coming out.

 

Otherwise, you have a different path on your first and last screen. Do you happen to have the problem with an .exe and not directly in LabVIEW ?

CLAMaxime -- Kudos are a great way to say thank you
0 Kudos
Message 13 of 23
(265 Views)

after I added the question I did add an indicator and the path created was correct in the in CRCCOL calibration global.vi.

 

The thing that is confusing me is that with the executable file that I got from the supplier has no problem with these VI's. everything was running correctly expect the DMM VISA so I changed only the destination global for the DMM and tried to built a new version and from there I started to have this issue

 

0 Kudos
Message 14 of 23
(261 Views)

There's something funky about paths if they are coded explicitly (as you seem to be doing), namely that there's a slightly different Path if you are in Development vs Execution (i.e. a built Application) Mode.  I tend to use Property Nodes of Static VI References to the VI I want to specify, as this works the same for both Development and Execution modes (saving my dwindling Brain Power).

 

Bob Schor

0 Kudos
Message 15 of 23
(258 Views)

I mean if you run the main VI in the development mode no error will show

but after building the excitable and the application and try to run the application I will have this error

0 Kudos
Message 16 of 23
(252 Views)

That's is what Bob is trying to explain : Current VI's Path is different in execution and development.

More about it : https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019NFfSAM

 

It's more than likely that you error comes from the way the path is created in Paths.vi 😉

CLAMaxime -- Kudos are a great way to say thank you
0 Kudos
Message 17 of 23
(248 Views)

ok so is that the same thing that they have been used in my application

Download All
0 Kudos
Message 18 of 23
(244 Views)

From what I see, you used the VI path, not the application folder one.

If you need to know what a VI does, you can use the context help by pressing CTRL + H.

CLAMaxime -- Kudos are a great way to say thank you
0 Kudos
Message 19 of 23
(241 Views)

Hi,

Did you include all dependent files with expected location when you create application?

 

Destination.png

 

 

 

 

 

 

 

 

 

 

Thanks,
Sanad MM

 

0 Kudos
Message 20 of 23
(234 Views)