07-13-2018 01:10 PM
I have sent the DAQmx drivers to the shop to manually install.
07-14-2018 10:07 AM
Tell me this may be the problem. The software now runs but there is no communication to the data acquisition front end. I had a similar problem when computer manufacturers starting cutting back on the voltage outputs to save money on power supplies. The last system I put together before retiring had it's own power supply (picture attached). The system I am having problems with never had a power supple and was on a very old computer running XP. Could it need a power supply?
07-15-2018 11:37 AM
This is very frustrating. Is there anyone at NI that knows how to 'integrate' a system???!!! I grant it that my hardware is not that new, but a simple question concerning how to ascertain if the front end is communicating with the computer should be an easy thing. I used to run into this type of situation all the time when asked to troubleshoot an electric motor being driven by a variable speed drive. There were people that would test the motor by itself and bless it as good. There were people that would bless the drive and bless it as good. There is usually NO ONE that knows how to look at both of them as a system and solve the problem For example, a back feedback signal or tach would drive the system crazy with very high vibration levels, yet it was overlooked frequently.
My problem. I have time tested code. It requires the RunTime Engine and the DAQmx drivers for a PCI 6221 data acquisition board. The front end is a 12 year old M series 2345 front end with ACC modules and one Analog module for a tach input. This is difficult stuff people, and I really appreciate the help from the forum. You folks are head and shoulders above NI tech support.
My end user called and they looked up my license and said it expired in 2015!!! First of all, didn't know they 'expire' and second of all, that's the year I bought it to transfer the vi's to Windows 7!!!!!!
So, anyone that can answer my question about needing to power the front end with a separate power supply or not would be greatly appreciated.
Regards,
Ron
07-16-2018 03:10 AM
@Coryman wrote:
I have sent the DAQmx drivers to the shop to manually install.
Not the drivers, the MAX configuration. You can export the configuration on the development system, and import it on the destination system. Or include it in the installation.
Can you access the hardware from MAX? (You probably get a (erroneous) warning that it's not licensed). If not, I'd say there's no way it will work from LabVIEW.
07-16-2018 05:32 AM
Thank you. I'll try that today.
07-16-2018 05:53 AM
Are you saying to include the configuration in the Installer? I can't find any option to include it in the application builder to build the application.
Ron
07-16-2018 06:00 AM
I found the export configuration section in the 'build new install'. It doesn't give me what I need to export. I am assuming this is because the system I built all of these programs for is at my old work site. I don't have the PCI 6221 or the M series 2345 front end or the ACC cards. All I have is the licensed LabVIEW and all of my vi code.
07-16-2018 06:01 AM
I have my license serial numbers and codes. Can the end user use them to run the DAQmx configuration on his computer?
07-16-2018 06:21 AM
@Coryman wrote:
I have my license serial numbers and codes. Can the end user use them to run the DAQmx configuration on his computer?
AFAIK, MAX can be used without license, although it complains (or used to complain) about a valid license if there is no registered LabVIEW version. You should be able to include MAX in the installer.
07-16-2018 06:27 AM
@Coryman wrote:
I found the export configuration section in the 'build new install'. It doesn't give me what I need to export. I am assuming this is because the system I built all of these programs for is at my old work site. I don't have the PCI 6221 or the M series 2345 front end or the ACC cards. All I have is the licensed LabVIEW and all of my vi code.
In the hardware configuration tab of the installer, there are fields to include the MAX configuration.
If you don't have a MAX configuration, I guess it's kind of useless. But if your application depends on it (it might not), it needs to be there. Either copy it from the old system or add it manually in MAX.