03-07-2006 04:59 PM
03-09-2006 01:55 PM
Hi Ron,
Are you able to see any of your cards under devices and interfaces? I would suggest reformating again and then start out with only putting LabVIEW RT 7.0 on your PXI system and see if you are able to identify the chassis. After that add drivers one by one until everything is working correctly or you run into the same issue. If the serial driver was the newest driver save this driver for last.
Regards,
Bassett
03-09-2006 02:39 PM
03-13-2006 01:33 PM
Hi RonC,
You might check to make sure that your controller is not booting up in install mode and is booting up into Real-Time. Also check to make sure your VISA settings and VISA Server settings are correct. The document linked will explain how to setup NI-VISA for remote systems.
Accessing PXI Instruments with NI-VISA in LabVIEW RT
http://digital.ni.com/public.nsf/websearch/01F9536A7A1D12A486256FF000561DA6?OpenDocument
Let me know if either of these help out.
Regards,
S. Bassett
03-16-2006 06:01 PM
03-20-2006 04:30 PM
Hi RonC,
Without installing the NI-Serial Drivers the ports will not be visable. After installing NI-Serial for RT they shoud be accessible under devices and Interfaces as normal. If the registry key was not removed you may have to remove it manually. PXI Services should be installed when MAX was installed. Just so we are on the same page, when you said you have gotten everything back to normal this means you are able to identify your PXI chassis in MAX. If this is true there may be an issue with MAX 4.0 and LabVIEW RT 7.0.
I have a PXI-8176 and will install LabVIEW RT 7.0 on it to see if it exhibits the same behavior and will let you know the results.
Thanks,
S. Bassett
03-20-2006 07:18 PM
Hi S. Bassett
Yes, in answer to your question -- the PXI system showed up in MAX, as PXI System (Unidentified), and I was able to identify the controller and chassis, and this information persists between restarts. Other than the serial driver, everything has been returned to where it was before I attempted the NI-VISA 3.4.1 upgrade. I thought this NI-VISA install would be safe, because the original recommendation came from a thread discussing a problem with LV 7.0 and not being able to get an RS-485 device into 2-wire mode. This was the exact problem I was having.
I am still stuck on the serial driver. I deleted the only registry key I can find related to NI-Serial, but this has made no difference. MAX does not recognize any serial software as being present, either on the host or the target. The Windows Add/Remove Programs control panel shows an item in the National Instruments software list; "NI-Serial for LabVIEW RT". Attempting to remove this item fails -- NI-IRDA gets removed, then the process chokes on NI-SERIAL -- get Error 1638 (unexplained). The "NI-Serial for LabVIEW RT" does not get removed from the list. NI serial driver installation, attempting to re-install the NI-SERIAL v2.5.3 (the version on my LV 7.0 CDs) fails because the installer says a newer version is already installed (it isn't) The installer for NI-SERIAL v 2.5.5 that I downloaded, which is actually only an updater, will not run because it reports a "different" version is already installed. So the NI installer for 2.5.3 reports a "newer" version, the updater for 2.5.5 reports a "different" version. The highest previously-installed version is 2.5.5, the pre-upgrade version was 2.5.3. The uninstaller reports a driver that does not exist, and then chokes trying to "uninstall" it, but without explaining what the error is.
So, I am stuck right now on this issue. Obviously there is persistent information retained somewhere that is confusing the installers/uninstallers but I cannot find where this is.
Thank you for your continuing interest and help on this.
RonC
03-20-2006 07:49 PM
03-21-2006 08:11 PM
03-23-2006 01:57 PM
RonC,
After investigating futher and doing several installs, it does look like there may be an issue with the PXI Chassis being recognized on a RT System with LabVIEW Real-Time 7.0 and MAX 4.0. I will need to investigate a little further to try if there is a work around for this issue. I'll let you know what I find out.
Regards,
Steven B.