07-16-2009 05:53 AM
Hi,
I have a problem similar to one previously reported - but that only got sorted by buying/using a newer GPIB card, which is not an (good) option for me! After I upgraded to Labview 8.6.1, I found I could no longer communicate with a Xantrex XFR DC power supply. In MAX I get 'instrument not found'. I checked the GPIB address (though there was no reason why it should have changed) and I changed the cable today, but this did not resolve the problem. Then searched online. I have NI488.2 version 2.60 loaded on the machine now. the S/no of my GPIB card (an old one - date not known) 00BC65B0. I attach an NI spy output (seen request for such on a previous message). Any suggestions? (other than buy a new GPIB card!). I guess I could just install the older version of NI488.2, but have not yet tried this option?
Roger
07-16-2009 09:01 AM
07-16-2009 09:18 AM
07-16-2009 09:46 AM
07-16-2009 10:13 AM
The plot thickens! I dont have the 'NI488.2 Getting started wizard' as an option from any of the routes to launch it that are suggested! (I get the GPIB troublshooting option which say pass for software and hardware every time I run it). I don't have add GPIB hardware option also (but it does say 'add GPIB ENET hardware' - which I don't have). What have I loaded in/not loaded in correctly?
Roger
07-16-2009 10:32 AM
I'm not sure if the wizard is part of the latest version. It did the hardware and software intallation verification and you've done that. You won't have a add GPIB hardware because the USB/PCI/PXI controllers are plug and play and will be automatically added. If the controller is listed in MAX and it passes all tests, you probably have everything installed.
Have you tried connecting a different instrument just to see if there might be something wrong with the Xantrex?
07-16-2009 10:51 AM
Unfortunately, the Xantrex is the only GPIB device I have available. (The PXI DAQ cards and relay card are all working fine/as before the upgrade).
It just seems funny that it was working fine one moment, then after the upgrade it now fails to detect the instrument, but I guess it could just be coincidence that the Xantrex GPIB interface has failed somehow - not sure how you can test for this? I did use the power supply out of the NI system for a short period, so the supply has been used stand-alone/non-GPIB mode, but not sure how the GPIB interface could have been damaged - the supply is still working in maula mode. But I can't now remember whether the GPIB interface was tested immediately before the upgrade. Is there anything else I can try before contacting Xantrex (Sorensen)?
07-16-2009 11:07 AM
07-30-2009 11:21 AM
I just heard from the supplier (TTI ltd) that they (finally) tested my Xantrex GPIB interface today - NO FAULT FOUND, by them, so this appears to put the failure back on the NI side of the fence (i.e. a LabVIEW problem, as originally suspected). Since I thought we tried everything last time, I'm not sure how much you can help me now. Before I went to the time and expense of sending the Xantrex back for test (it was under warranty) I even uninstalled the NI488 software and re-installed the original (much earlier ) driver version, but this did not solve the problem (still get hardware and software 'pass' under test). Looks like I am going to have to bin LabView 8.6.1 and possibly even 8.6. (it was working fine under 8.5) - and all points to the previous post/message of an 'old' GPIB card not working under the latest version of LabVIEW. Any help you could now provide would be much appreciated, as I am getting VERY frustrated, and I exceeded my 'things to try' ages ago. I hate software that does not work (I even managed to completely corrupt IE7 on an old PC last week after a failed (corrupted) upgrade to IE8 installation - system restore wizard does not work (it restores everything except IE7!!) and a re-install IE7 from new also fails - I had rejected the upgrade on all my other PCs!!!!)- anyway, enough about Microsoft products not working, but you can see that I have too much recent bad experience of 'simple' upgrades not 'doing as they say on the tin'.
Regards,
Roger