LabVIEW
Error 200477
The code uses cDAQ3, your MAX has cDAQ1 ... Change either one (or even better move the configuration to an .ini-file).
So I did a Mass Compile of the LabVIEW Project on one of them. NO I have and Error shown below.. I have attached the Project File as well.
@mjhartwig wrote:
Sorry I am a extreme nubie to LabVIEW how would I move the Configuration file to an .ini-file?
The idea is to have this channel info in an .ini-file instead of as a constant, which make it easier to adapt to the environment.
How to use ini-files is shown well in the two examples in this project.
Help --> Find Examples
So, instead of having that cDAQ3Mod1-constant, you have that information in a simple text file e.g. config.ini that sits along with your .exe
The file (depending on your naming choices) will look something like:
[System]
MainSwitch=cDAQ3Mod1/do1
You should fix your problem before you try updating the code to use configuration files.
As I suspected and Crossrulz mentioned, you are using the wrong DAQ Device Name. This is exactly what the error message has been saying from the start.
I can't see your code, but your screenshot shows the device is called "cDAQ3":
BUT, your actual device is called "cDAQ1" as seen by NI-MAX:
Open NI-MAX again, right-click on the name cDAQ1, and select "Rename". Change it to "cDAQ3". All 4 sub-modules will probably change to. If they don't, rename them as well.
@mjhartwig wrote:
So I did a Mass Compile of the LabVIEW Project on one of them. NO I have and Error shown below.. I have attached the Project File as well.
This is why I said you shouldn't just try things randomly. You updated the LabVIEW code and now it's confusing the calls to old MS Excel functions used in the Report Generator Toolkit.
Try going to those places where the Error List has a red X like the broken VI you are showing below. Right-click on the name of the function (circled red) and click Select Method >. Now you need to pick the correct method from the list. Look for the exact same name and hope it's there. So, in this case you look for "SaveAs". Hopefully, that will update the function. Keep doing that for every VI on the Error List with a red X and keep your fingers crossed...
The DAQ names were part of my Issue. I also had to relink my Microsoft Library in code in order to compile it successfully. I can Run the code and test using LabVIEW. I am struggling to create exe files for the production level. Or I get and error when I Run the EXE File that the file path for the toolkit I need to generate a report is too long.
