03-05-2007 03:55 PM
03-06-2007
09:22 AM
- last edited on
07-08-2025
09:32 AM
by
Content Cleaner
Howdy kgtang,
First off since you are using the PXI 2503, you need to download (which you may or may not have done already) the latest NI-Switch driver found here. If you open up the readme for that driver, you will notice it indicates where the installed files (drivers and examples) will be installed to. For CVI, you will need to navigate to the C:\Program Files\IVI\Drivers\niSwitch\ directory. In that directory, you can navigate to the Examples\CVI folder to check out the CVI examples. To add the NI-Switch instrument driver to your CVI project so you can use the Swtich functions, select Edit >> Add Files to Project >> Instruments (*.fp) and then add the niSwitch.fp file located in the C:\Program Files\IVI\Drivers\niSwitch\ directory. Then your Library Tre should look like the attached "Switch Libraries.jpg" snapshot.
Hope this helps!
Best Regards,
03-06-2007 04:51 PM
Thanks Jonathan,
I followed your instructions and now have lots of stuff in my "Instruments" folder. That gets me to the next question.
Am I going to need actual hardware connected to my development PC to develop the hardware control?
The life test we inherited is being used and cycling motors. However, it's functionality is extremely limited and does very little of what we need it to do. The system was developed with Labview and is next to impossible to follow. The hardware includes one PC (operator interface), a PXI system that controls 2503 switches and 1102 TC amplifiers (for volts, amps and thermocouples readings), and a PXI that controls SCSI 1100 multiplexers (controls the main power relays).
Things are cycling and scanning everywhere but that just about it. I believe the existing hardware will do what we need. It's probably a major overkill. Beings the system contains approximately 17 miles of wire, were going to try leave the hardware as is. However, it's been decided were going to have to restart the software from scratch.
I've developed new control software and GUI using CVI. The new software is to the stage where it needs to actuate relays and acquire readings rather than simply printing messages to stdout. This is new territory for me.
It would be great to have a couple of phone calls with an expert and get an informed opinion as to whether or not we are on the right track and what we are facing.
Thanks,
kgtang
715 675-3359 ext 4292
03-06-2007
05:42 PM
- last edited on
07-08-2025
09:33 AM
by
Content Cleaner
Hi kgtang,
At design and compile time you don't need your hardware hooked up. You will only receive errors when you actually run your application and try to call those hardware functions on a device that isn't connected. Errors in this case make sense because you don't have any hardware connected.
Honestly, what I would do is create "code" placeholders in your code of where you are going to implement certain hardware features. Inside those placeholders, place simply printf and MessagePopup statements to indicate that those pieces of code are being called. This simulates your applicaiton and just verifies that the flow of your program works fine. Then start implementing the actual hardware code. It might be best to hook up the hardware at that time and start with functions like initializing and shutting down your hardware.
If you are having trouble getting started, contact an NI Support Engineer either by phone or email and they can help you out live.
Best Regards,