LabVIEW Error 'Type' 4E340

[The_Seeker]

Greetings List Readers,

After building an application from an otherwise perfectly good VI, I have run across an odd (and apparently undocumented) error message in the executable version.

Oddly the VI runs prefectly inside the development system. However, when I generate an executable and attempt to run it, the LabVIEW run-time pops up a message indicating that an "error of type 4E340 has occured". The message also says that I will need to correct this using the full development version. However, in the development version, there is no problem whatsoever.

Does anyone know what "error type 4E340" is indicating? There doesn't appear to be any reference to this in any of the documentation, and a search of the NI site also produced no results.

The VI itself is quite simple. It captures images (using a triggered acquisition), and saves the captured images to disk. Nothing too fancy here, just a few IMAQ VIs, and file I/O -- although, I should mention that it also uses the new shared variable, which is linked to an RT application running on a PXI chassis. (The shared variable itself doesn't  seem to be the source of the problem -- I have had no problems linking to it from other compiled applications on the same PC.)

Can anyone shed some light on this mysterious error message, and/or the reason why the LV run-time is having problems with a VI that works perfectly well in the development system environment?

Thanks in advance.

-- D.

[Ankita]

Hi,

Curiously enough, even Google search does not turn up anything for this error.

Please try and see if you can reproduce the error on  another machine. Also please post your VI so we can try and reproduce the problem.

Regards,

Ankita 

[The_Seeker]

Well, after some trial and error -- and the better part of a day -- I think I discovered the source of the problem. I'll post it here in case someone else experiences the same cryptic error message.

After posting my previous message, I decided to narrow the scope of my search. First, I deleted all references to shared varibles. No luck there. Apparently, the shared variables were NOT the source of the error.

Next I shifted my focus to the IMAQ functions. This turned out to be the source of the problems.I believe it has something to do with a version conflict between the most recent version of the IMAQ libraries, and the previous version. (Or perhaps it has something to do with the license manager..)

Anyway, to summarize, here are the steps that led to this error:

1) I downloaded and installed the IMAQ Vision 8.0 from the NI web site, and installed it on my desktop PC. Since we are working on a PXI-based vision application, I also updated the PXI. However, after installing it, I soon discovered that our previous registraion code was not valid.

2) After contacting my local NI rep and discovering the (surprisingly high) cost of this upgrade, and discussing it with my supervisor, questions soon arose as to how critical this upgrade would be to our project. Given that the new version only adds incrementally to the functionality, and that the existing version has been working just fine, my manger didn't see any immediate need and opted to give it a pass for the time being.

3) At this point, I removed the upgrade and reverted the previous version. Everything appeared to be working fine in the development system, and indeed, I almost forgot that the newer IMAQ was once installed.

4) After two or three weeks of succcessfully building RT vision applications for the PXI without any difficulties, I assumed that everything was fine. However, when I attempted to build this small vision app on the desktop PC, the ghost of the ill-fated upgrade installation appeared.

The moral of the story:
Check the price of the upgrade BEFORE you download and install it -- and get the go-ahead from the boss first. Reverting back to the previous version may not be a seamless as you might hope. 

In closing, I must say, the oddest part in all of this had to be the undocumented error message. If a developer goes to the trouble of throwing up a dialog to inform the user of a difficulty, doesn't it make sense to provide the details somewhere in the documentation so the user knows what action to take next...?

Anyway, that summarizes my experience with this peculiar error. 

-- D