spaghetti_developer Posted September 13, 2011 Report Share Posted September 13, 2011 Hi Guys, I'm using the Mean.VI (got from the probability & statistic palette) in the main.vi of my software. Although everything is working properly while I'm in the development enviroment, when I launch the exe of my software the LV-Runtime returns to me an error "the MAIN.VI cannot be loaded". It seems to be a bug of Labview, has someone had the same problem? Why does this? Thank you in advance. Quote Link to comment
mje Posted September 13, 2011 Report Share Posted September 13, 2011 Was lvanlys.dll packaged properly with your executable? The library that mean.vi is a part of requires that dll. Is there any more details about the error message? Quote Link to comment
spaghetti_developer Posted September 13, 2011 Author Report Share Posted September 13, 2011 Hi mje, First of all, thank you for your prompt reply. I'm using the application builder to build my exe. I thought that, as with the other funtions incorporated in LV, It wasn't neccessary to indicate that library to the APP-Builder specifically. Perhaps that was the error! I'm going to try again and if it shows me the error again, I will store the immage of the message and I will post it to you! Thanks. Best reguards. Quote Link to comment
spaghetti_developer Posted September 13, 2011 Author Report Share Posted September 13, 2011 Therefore.... I looked at the package of the exe I've built and I found out that the lvanlys.dll is present on the Data directory of the application. Do I also have to set that dll into the "Always inclue" box of the AB specifically? Quote Link to comment
mje Posted September 13, 2011 Report Share Posted September 13, 2011 In most cases the application builder will be able to determine you need the DLL, and in your case it looks like it has done just that, you shouldn't need to do anything else. I'm sorry, but without a more specific error message I can't offer any more advice, the DLL was just a guess! Quote Link to comment
Saverio Posted September 13, 2011 Report Share Posted September 13, 2011 You initially started off indicating that you suspected the Mean VI. Why? What led you to believe that was the culprit, especially since the error message doesn't really tell you anything. If you remove it from your code does the executable work? Quote Link to comment
asbo Posted September 13, 2011 Report Share Posted September 13, 2011 Make sure you're keeping your EXE next to the data subdirectory the App Builder generates for you. It will have a copy of the lvanlys DLL and this is the first place the EXE will look for the component. I don't know if it fallback to the system copy or not. Quote Link to comment
spaghetti_developer Posted September 14, 2011 Author Report Share Posted September 14, 2011 (edited) Hi Guys, First of all, thank to everyone for the answers and for interesting on my problem. Attached the error messages I received after I had compiled my software with AB. Then, you can also see the code of the main VI. the software is composed only by the main VI. So, why is it having this behaviour? Make sure you're keeping your EXE next to the data subdirectory the App Builder generates for you. It will have a copy of the lvanlys DLL and this is the first place the EXE will look for the component. I don't know if it fallback to the system copy or not. Sorry, I forgot to add that I confirm that the dll is into the data directory and the data directory is into the directory of the exe. Edited September 14, 2011 by spaghetti_developer Quote Link to comment
Saverio Posted September 14, 2011 Report Share Posted September 14, 2011 (edited) If you expand the Dependencies node for the project what do you see? Do you see something like this: If not, try refreshing the Dependencies (right-click on the tree node). How is your build spec set up? Which edition of LabVIEW are you using? I don't mean the version, I mean Full, Professional, etc. Did you install any other software that would have affected the LV2010 Run-Time Engine? This may be a problem with the Run-Time Engine. Perhaps a repair of the installation would fix it? Do you have the correct Run-Time version installed (the standard, and not the minimum version)? Edited September 14, 2011 by Saverio Quote Link to comment
spaghetti_developer Posted September 15, 2011 Author Report Share Posted September 15, 2011 If you expand the Dependencies node for the project what do you see? Do you see something like this: If not, try refreshing the Dependencies (right-click on the tree node). How is your build spec set up? Which edition of LabVIEW are you using? I don't mean the version, I mean Full, Professional, etc. Did you install any other software that would have affected the LV2010 Run-Time Engine? This may be a problem with the Run-Time Engine. Perhaps a repair of the installation would fix it? Do you have the correct Run-Time version installed (the standard, and not the minimum version)? Hi Saverio, thank you for your interest in this matter, here you can see my projects window Such as you can see in the picture I'm having the same situation you are having. My build spec set up is standard set up, the only things I have changed on the AB is that I have inserted the VI in the start up VIs list. The edition of Labview I'm using is the 2010 Professional. I have installed the software on a PC where there aren't other software which can disturb the labview RT, I have already run labview softwares there and I haven't had any problems with them and I'm sure I have installed the right version of the RT. Therefore, what do you think is going on? Quote Link to comment
jgcode Posted September 16, 2011 Report Share Posted September 16, 2011 Have you tried other PCs? - What is the result? I have seen weirder stuff happen before. Also, you could upload your code, so other devs can quickly build the spec and see if they get an error. Quote Link to comment
spaghetti_developer Posted September 16, 2011 Author Report Share Posted September 16, 2011 Also, you could upload your code, so other devs can quickly build the spec and see if they get an error. You are right, here the complite code. meanTester.zip The code is developed by LV2010 Professional version. I want also to remind to everyone that the problem not apeare during the debugging but just when you compile the exe and you try to run it under a 2010 RTE. Thank you for the interest in this matter. Quote Link to comment
jgcode Posted September 16, 2011 Report Share Posted September 16, 2011 The code is developed by LV2010 Professional version. I want also to remind to everyone that the problem not apeare during the debugging but just when you compile the exe and you try to run it under a 2010 RTE. Ok, I built the exe and it ran fine on my PC. Do you want to upload an exe compiled on your PC too, and I will run it here just to check? Quote Link to comment
spaghetti_developer Posted September 16, 2011 Author Report Share Posted September 16, 2011 Yes of course, Here the exe file with all the data it need to work properly. In the folder you can also find the image of the code and the images of the error messages I have already posted. mean_Tester.zip Quote Link to comment
Saverio Posted September 16, 2011 Report Share Posted September 16, 2011 Not sure what to say... I ran the executable and it ran just fine. As asked have you tried this on another PC? Quote Link to comment
asbo Posted September 16, 2011 Report Share Posted September 16, 2011 It runs fine for me as well. I would recommend an uninstall/reinstall or repair of your RTE installation. Quote Link to comment
jgcode Posted September 16, 2011 Report Share Posted September 16, 2011 It runs fine for me as well. I would recommend an uninstall/reinstall or repair of your RTE installation. Yer, I had to format my entire HDD to get this fixed Still didn't know what caused it - but on the upside LabVIEW ran faster Quote Link to comment
spaghetti_developer Posted September 19, 2011 Author Report Share Posted September 19, 2011 Thanks everybody for yours suggestions. Actually I don't know what's happening but, right now I cannot format the PC where the software is working. To solve the problem I simply changed that function in my software with a custom solution (math calculation) to get the AWG and the software began to work properly. This was enough. Thank to everybody for your interest in this matter. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.