I've investigated the problem I'm having with NI VISA 3.0.0 on LV RT 7.0
with
properly identifying PX2000 105 and 107 cards, and here are some
discoveries
I've made:
1) The manufacturer and model register based IDs (numeric) are being
returned
scrambled; instead of 0x157F and 0x105 or 0x107, they're coming back
0x0001
and 0x1105 for the 105 and 0x0002 and 0x2107 for the 107 card.� This is
probably why VISA RT is not returning the proper Model and Manufacturer
names
I look for.
2) As Julie, the NI support engineer I spoke to today, reported, the slot
properties now appear to be working.
3) It seems that MAX is attempting to work on the RT box - I notice plenty
of
modules for it, and running MAX on the host actually rewrites pxisys.ini
on
the target RT box.� The format its writing is not compatible with the old
(hack) VI that handles programmatic slot configuration discovery by
reading
pxisys.ini from the ni-rt\system directory on the RT box.
4) I needed to run the VISA Driver Development Wizard to write .INF files
out
for the 105 and 107 before they would even show up in the VISA system, but
as
I mentioned earlier the manufacturer and model codes and names are
incorrect,
thereby preventing me from properly detecting PXIT cards in the slots.� I
don't know if they are operational via VISA yet, I will try it soon.
5) The VISA subsystem properly identifies Ni cards even with no .INF files
in
\ni-rt\system.� Generating an .INF file didn't cause a failure in model
codes
or names, the NI cards are still identified properly.� (Perhaps there is a
problem actually reading out the model and manufacturer codes in the EEPROM
of
the 105 and 107, maybe mishandling of the sub-manufacturer and sub-model
codes
that those cards have?� Smells to me like the wrong registers are involved
somehow . . . and those sub model and manufacturer codes may just be
involved.)
6) The "VISA Find Resource" VI apparently has a bug where it stops when it
finds an empty slot - at least that's what the cause seems to be in a
couple
of quick tests I ran.� It starts at the high slots and works its way down,
and
seems to miss cards lower than an empty slot.� I had problems with this VI
in
LV 6.1 as well, but I'm not sure if the failure cause was the same.
Symptom
was similar though, it only returned a subset of the cards.� In 6.1, it
seemed to only return the PXIT cards and not the NI cards, but now its
returning NI cards.
7) MAX seems totally incapable of ascertaining what the devices on the
system
are - it always reports only the 8176 controller and nothing else.� Things
seemed to improve a bit when I threw up my hands and wiped the hard disk
and
freshly reinstalled LV RT 7.0, but I'm not positive . . . at any rate, be
advised that I started out with a fresh hard disk at some point early on
in
the experiments.� But MAX seems to be trying to report the configuration.
😎 The VISA Interactive Control hangs even when just pulling down menus,
it
should be looked at.� I was going to try to see if there was a way to use
it
on the remote target to query the registers of the PXIT cards directly to
see
what the codes came out as.
I think that is all.� NI: please don't throw this email away because it
doesn't have a special request number, just create one for me will you?
My NI
ID is 198262, Vance Socci.
-Vance Socci
-Lockheed Martin Missiles & Space
