On 16/12/2014 16:36, amdx wrote:> On 12/16/2014 7:53 AM, amdx wrote: > > > Someone mentioned NI Spy, so I pulled that up and it list the > commands/addresses when I try to run my program. > > I made a screen shot of the info, the first 5 lines write when I open my > software, the rest write when I try to run a scan using the software. > > I have no convenient method to copy and paste from one computer to this > one, so a real screenshot. > >> http://s395.photobucket.com/user/Qmavam/media/P1010134_zps7478c31f.jpg.html >> > > Is there anything helpful in this data?Yes. Although I am forced to guess at NI's error codes I would venture that it is complaining about UD1 with a red ENOL(2) rather than 0. At a guess I'd venture Error No Listener. IOW there is no recognisable device sat at address 15 on the GPIB. -- Regards, Martin Brown
Error message on GPIB program, Help
Started by ●December 11, 2014
Reply by ●December 16, 20142014-12-16
Reply by ●December 16, 20142014-12-16
On 12/16/2014 10:55 AM, Martin Brown wrote:> On 16/12/2014 16:36, amdx wrote: >> On 12/16/2014 7:53 AM, amdx wrote: >> >> >> Someone mentioned NI Spy, so I pulled that up and it list the >> commands/addresses when I try to run my program. >> >> I made a screen shot of the info, the first 5 lines write when I open my >> software, the rest write when I try to run a scan using the software. >> >> I have no convenient method to copy and paste from one computer to this >> one, so a real screenshot. >> >>> http://s395.photobucket.com/user/Qmavam/media/P1010134_zps7478c31f.jpg.html >>> >>> >> >> Is there anything helpful in this data? > > Yes. Although I am forced to guess at NI's error codes I would venture > that it is complaining about UD1 with a red ENOL(2) rather than 0. > > At a guess I'd venture Error No Listener. > > IOW there is no recognizable device sat at address 15 on the GPIB. > >OK, what is a UD0 vs UD1. I'm thinking it is my software that is calling up the UD1, but it doesn't seem right that it would. Mikek
Reply by ●December 16, 20142014-12-16
In article <m6pdfn$spk$1@dont-email.me>, amdx <nojunk@knology.net> wrote:>The PCI slots are all in auto mode.One *possible* problem: on most machines, there are only a limited number of interrupts available to PCI slots. The BIOS may very well be mapping the PCI slot to an interrupt number which is being shared with other PCI slots or with on-board peripherals. Normally, with good PCI devices and a good o/s and well-written drivers, this shouldn't be a problem. PCI devices should have their own status registers which indicate whether they're generating an interrupt, and each device driver for a device sharing an interrupt will be given a chance to check its status. However, there are some bad PCI cards, and bad operating systems, and bad drivers, and any of these can result in lost or spurious interrupts or in delay in processing interrupts. If you boot up Linux (from e.g. a Knoppix live CD) you can log in and then see what interrupts are actually assigned to (or shared by) which devices... "cat /proc/interrupts". This only works for devices that have drivers installed, though. There's probably a similar capability available under Windows (e.g. the Hardware tab under the System control panel). You *might* find it beneficial to do manual assignment of your PCI interrupts, to try to give the GPIB card an interrupt of its own. There's no certainty that you can achieve this with your motherboard and BIOS, and no guarantee at all that it would help.
Reply by ●December 16, 20142014-12-16
On 16/12/2014 17:32, amdx wrote:> On 12/16/2014 10:55 AM, Martin Brown wrote: >> On 16/12/2014 16:36, amdx wrote: >>> On 12/16/2014 7:53 AM, amdx wrote: >>> >>> Someone mentioned NI Spy, so I pulled that up and it list the >>> commands/addresses when I try to run my program. >>> >>> I made a screen shot of the info, the first 5 lines write when I open my >>> software, the rest write when I try to run a scan using the software. >>> >>> I have no convenient method to copy and paste from one computer to this >>> one, so a real screenshot. >>> >>>> http://s395.photobucket.com/user/Qmavam/media/P1010134_zps7478c31f.jpg.html >>> >>> Is there anything helpful in this data? >> >> Yes. Although I am forced to guess at NI's error codes I would venture >> that it is complaining about UD1 with a red ENOL(2) rather than 0. >> >> At a guess I'd venture Error No Listener. >> >> IOW there is no recognizable device sat at address 15 on the GPIB. > > OK, what is a UD0 vs UD1. > I'm thinking it is my software that is calling up the UD1, > but it doesn't seem right that it would. > MikekI am guessing at NI's notation here but UD = User Device UD0 is the handle of the first device you declared and UD1 is the handle of the second You should be able to figure out which is which from the command syntax since one will be the signal gen and the other a DVM or something. Check the manuals and dip switches on the two HP devices and see if you can't find a noddy test program in the NI distribution that lets you send strings to a device number and watch what comes back. That is likely to be the fastest way to figure out what is going wrong. -- Regards, Martin Brown
