VXI 1394 viMove error

"1394 Slot 0 viMoveOut16 error"
"I just updated NI-VISA from 2.5.2 to 3.2. When I now run my application I get a bus error during a viMoveOut16 function call. Using VIC I was able to determine that viMoveOut16 will return a bus error code when the transfer count is > 2000. Is there a setting to increase the transfer count?"

Hello,
If you could provide the error number and message it will help troubleshoot. What seems to be happening is that the number in length + the offset is greater than the space in memory then it gives an error. To correct this, change the length size to be smaller or allocate more memory. There is a function called ViMapAddress that is used to set the amount of memory.
If this doesn't fix the problem, please provide with the error message.
As a reference here is the link to the VISA Programmer User Manual
NI-VISA Programmer Reference Manual
Hope this helps
Ricardo S.
National Instruments.

Similar Messages

How can i use NI's VXI-1394 controller to control the CONDOR's VXI-1553B module?

Now I want to use the NI's VXI-1394 to control a CONDOR's VXI-1553B module.But I did a test and found that the NI's VXI-1394 can not control that module.The VXI-PCI8015 can control the VXI-1553B module.
But I have a VXI-1394 module and I want to use that to control the CONDOR's VXI-1553B module.How can I do that?Give me a hand,please.

Hello Lincoln,
Judging by the fact that you mention the VXIpc-8015, I am deducing that you are using the VXI-MXI-2 card under Windows NT. Is that correct?
Under Windows NT, the VXI-MXI-2 board and the VXI-1394 need to use different versions of the NI-VXI driver.
The VXI-PC-8015 (MXI-2) should be using NI-VXI v3.2, while the VXI-1394 needs to use a special version of the driver (v2.1.1) because Windows NT does not natively support the IEEE 1394 protocol.
The issue may simply be the wrong driver, but if it is not, we will need to know more information about your system.
1a. What version of NI-VXI are you using with the VXI-1394
1b. What version of NI-VXI are you using with the VXI-MXI-2)
2. What OS are you running?
3. How are you attempting to communi
cate with the CONDOR device?
4a. What configuration utility are you attempting to use with the VXI-1394
4b. What configuration utility are you attempting to use with the VXI-MXI-2
5. Is the CONDOR device register based or message based VXI device?
6. Have you used NI-Spy? If so, can you generate NI-Spy logs that might help debug this issue? There is a quick tutorial on NI-Spy here.
Start with these steps, and let us know how it goes. Thank you!
Regards,
Josh Hernstrom
Applications Engineer
National Instruments

How to use VXI-1394 with notebook computer

hello!
Some notebook computers have 1394 port. Now I want to use notebook computer to control the VXI-1394 module.It's said that you are writting the drivers for the VXI-1394 which is used in notebook computer.I don't know whether this kind of driver is accomplished or not.Tell me,please.
Thanks a lot!

lincoln,
If you are using Windows 98/ME/2000 and have an OHCI compliant 1394 port (which many laptops have) then we have software that you can use. NI-VXI 3.x will allow you to use any OHCI compliant 1394 port with the above named operating systems and a NI VXI-1394 controller.
Trey Hamilton
Applications Engineer
National Instruments
http://www.ni.com/support

VXI-1394 adapter not recognizing or communicating with my hardware

I'm using a VXI-1394 adapter on conjunction with Labview to run some hardware that we build but the 1394 is unable to communicate with the hardware. Resource Manager runs fine and I am able to load our software in labview, but there is no communications occuring. I have swapped the suspect 1394 card with a known two seperate good ones and they work well. I am fairly confident the board is bad, but I'm not sure how to desribe what is wrong on any technical level.
-Tony

Tony,
Before you send in your controller for repair, could you clarify a few things for us? When you say that Resource Manager (resman) runs successfully what do you mean? Does it find all the devices in the chassis? Or does it just complete without locking up or failing? Also, which 1394 boards have you swapped out, VXI-1394 cards or PCI-1394 interfaces?
The reason for the first set of questions is if you are able to find and recognize all the devices in your VXI chassis when running resman, then that is an indication that the board is working, and that there is some other problem with your system.
Also, have you tried changing the address of the VXI-1394 card or resetting the EPROM or anything like that? Please let us know.
Thanks,
Logan S.

VXI-1394's problem!!

When running Resouce Manager, popup a dialog which include following information:Unable to initialize NI-VXI driver.Unable to access NI-VXI interrupt server process.When running Test & Measurement Explorer, popup a dialog which include following infromation:T&M Explorer is unable to determine the type and logical address of the local VXI/VME controller.Configuration EEPROM is invalid and cannot be fixed!
who can help me !!!

Hi gpibssx,
There are several troubleshooting steps you need to go through in order to diagnose this problem.
1. If you don't have one, get yourself a copy of the VXI-1394 manual for more information. First things first, go through Appendix C and make sure the switches and jumpers on your board are set to the default settings:
http://digital.ni.com/manuals.nsf/webAdvsearch/96D8B27866FEE70C86256816005CAE3F?OpenDocument
2. The VXI-1394 has two sections in the EEPROM, one that contains user-customizable settings, and the second the contains factory default unchangable settings. You can boot off of the factory EEPROM, which won't be corruptable, and then will be able to reset the EEPROM on the user side. Refer to Appendix C in the manual above for instructions on
Loading the Factory EEPROM.
3. Refer to the document below for restoring the user EEPROM once you've loaded the factory EEPROM. The document is valid for the VXI-1394:
http://www.ni.com/support/vxi/eeprom/eeprom.htm
Regards,
Josh Hernstrom
Applications Engineer
National Instruments

The VXI-1394/G front panel GPIB connector is supported under WindowsNT4.

Does it been supproted under Windows2000?

IEEE-1394 is not native to Windows NT. Because of this, there are a few 3rd party 1394 device drivers for Windows NT out there. However, there are frequently issues that arise because Windows NT does not support 1394. The NI-VXI driver included a 3rd party PCI-1394 driver to allow the VXI-1394 to be used under Windows NT.
Currently, the only NI-488.2 driver that supports the GPIB port on the VXI-1394/G is for Windows NT. R&D has considered making the investment of developing a new version of NI-488.2 that will support Windows 2000. However, I do not believe a decision has been made at this time. Since a PC is already a part of your system solution, we recommend using a PCI-GPIB card installed in the PC. There are also other GPIB so
lutions, such as the GPIB-ENET and GPIB-USB.
Julianna Forrest
Applications Engineer
National Instruments
www.ni.com/ask

NI-VXI 1394 Firmware with win7

Hello all,
I'm facing a problem currently when our VXI rack which is worked well under Win XP needs to be ran under win7 as well because our company internal policy won't let us further use XP. I made experiment already with drivers from NI website, but non of them were worked. BTW NI compatibility chart shows that VXI with FireWire is not supported under Win7 but USB. Anyway I never give up, and trying to find a solution
ideas:
- maybe some redirectional extra program which would redirect USB connection to FireWire ??
- an external converter which can convert USB to FireWire??
Do you have further ideas or even a solution?

Hi,
According to this site, the VXI-1394 is not supported under Win7: http://digital.ni.com/public.nsf/allkb/63E23F33EB70A086862571EA00659E04
Regarding the firewire/usb question, I'm afraid I don't understand what you are asking. Could you please explain somewhat longer what you mean?
Have a nice day,
N.

VXI-USB viMoveInXX errors

When I call viMoveIn using a VXI-USB controller the data returned is sometimes corrupted.
I don't have this error with any other VXI controller including the Prodac USB.
Both 16 and 32 bit transfers are getting errors.

Hi K. Coggins,
You mentioned that you are having a similar issue. Does this mean that you are also receiving corrupted data when using a VXI-USB device? Does this also occur when calling viMoveIn? Have you tried any of the suggestions Logan S. made above? The more information you can give me about the errors you are having, as well as the hardware and software you are using, would be extremely helpful.
For more information on VXI bus timing, take a look at the following links:
http://digital.ni.com/public.nsf/allkb/B7E440E8BD0D50DC862571B5004E6947?OpenDocument http://zone.ni.com/devzone/cda/tut/p/id/4365
I hope this helps a little. Give me as much information as possible, and I will look into the issue a little further.
Lauren L.
Message Edited by Lauren L on 10-22-2007 08:36 AM
Applications Engineering
National Instruments

Drive VXI-MIO-64E-1 in LabWindows/CVI

I'm integrating a VXI system based NI's VXI-1394 controller in which VXI-MIO-64E-1
was used. My develop envirenment is LabWindows/CVI 5.01. When I use the MIO
card to sample a waveform, the only length of the waveform I can sample is
2048Sa. Then, I insert 2 SIMM with size of 8MB to the MIO card, but it is
useless.
How can I configure and use the onboard Mem of VXI-MIO-64E-1? Could you give
a sample program in CVI?
Thank you very much!

Hello Vishnu,
Unfortunately, the VXI-DAQ cards are no longer supported, but you can find information about using them in the manual. The VXI-MIO Series User Manual has details about setting the input range in Chapter 3 on page 3-4.
Good luck with your application!
Meghan
Applications Engineer

Can multiple 1394 Controllers be switched in and out of operation and configured correctly?

The test system I'm working on has a 'core' VXI System using a Slot-0 1394 Controller that is always powered up but also requires other systems to be switched in and out as required under the control of LabVIEW 7.1 software. The interface to all of the VXI systems is made via PCI Firewire interface to the single controlling PC.
The test system needs to be able to perform various sequences of actions using multiple peripheral systems but always with the 'core' system powered up. An example sequence would be:
1) Power up the 'core' VXI system and communicate with the instruments
2) Power up peripheral VXI system '1' and communicate with the instruments
3) Power down peripheral VXI system '1'
4) Power up peripheral VXI system '2' and communicate with the instruments
5) Power down peripheral VXI system '2'
6) Power down the 'core' VXI system
In order to simulate the above sequence of actions in a test environment I have two VXI Chassis systems and three Slot-0 Controllers which I have attempted to use as follows:
1) Power up VXI Chassis 1 and communicate with the instruments
2) Power up peripheral VXI Chassis 2 and communicate with the instruments
3) Power down VXI Chassis 2 and replace the Slot-0 Controller
4) Power up VXI Chassis 2 with the new Slot-0 Controller and communicate with the instruments
5) Power down VXI Chassis 2
6) Power down VXI Chassis 1
I have registered all of the Slot-0 Controllers in MAX beforehand and they are persistent and appear as VXI systems '0'-'2' in the GUI.
I have run resman programmatically in LabVIEW 7.1 (using NI-VXI 3.3.1 and the suggested patch) using a command line of "resman -b'n' -o" (where 'n' is the system number) in order to run the executable silently (which will be required for the completed test system). Resman is run after the power up of each chassis (for that VXI system only) in steps 1 and 2 and works ok at these stages. When resman is run after the power up in step '4' however, resman crashes along with LabVIEW.
As an extra test I tried just attempting to 'find' each of the systems using the 'VISA find resource' VI after the power-up of each VXI system but without performing any other actions (i.e. running resman or communicating with the instruments). For steps 1 and 2 this also works ok but in step 4 this again results in a fatal crash in LabVIEW.
Could you tell me if these crashes are to be expected or if I am doing something wrong?
thanks
Lee Hutchinson
Test Software Engineer
BAE Systems
Waterlooville
Hants

Hi Lee,
In the VXI-1394 User Manual we say that you should always have VXI unit powered up before the PC. I think this would go for peripheral VXI units as well. For this system to work stabley I would have thought that you need to power up the peripheral VXI chassis, then the core then the PC. The way you are doing it at the moment you are effectively replacing one 1394 controller with another and I don't think the PC will be able to handle the references to them in this manner.
Regards
Jon B
Applications Engineer
NIUK

Make error when compiling gspca

Hi, ive downloaded gspca source and modify it in order to get my webcam working, but when i type 'make all' i get:
[jk@arch4linux gspca-7876678e39df]$ sudo make all
make -C /home/jk/gspca-7876678e39df/v4l all
make[1]: se ingresa al directorio `/home/jk/gspca-7876678e39df/v4l'
creating symbolic links...
make -C firmware prep
make[2]: Entering directory `/home/jk/gspca-7876678e39df/v4l/firmware'
make[2]: Leaving directory `/home/jk/gspca-7876678e39df/v4l/firmware'
make -C firmware
make[2]: Entering directory `/home/jk/gspca-7876678e39df/v4l/firmware'
make[2]: Nothing to be done for `default'.
make[2]: Leaving directory `/home/jk/gspca-7876678e39df/v4l/firmware'
Kernel build directory is /lib/modules/2.6.30-ARCH/build
make -C /lib/modules/2.6.30-ARCH/build SUBDIRS=/home/jk/gspca-7876678e39df/v4l modules
make[2]: Entering directory `/usr/src/linux-2.6.30-ARCH'
CC [M] /home/jk/gspca-7876678e39df/v4l/firedtv-1394.o
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:21:17: error: dma.h: No such file or directory
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:22:21: error: csr1212.h: No such file or directory
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:23:23: error: highlevel.h: No such file or directory
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:24:19: error: hosts.h: No such file or directory
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:25:22: error: ieee1394.h: No such file or directory
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:26:17: error: iso.h: No such file or directory
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:27:21: error: nodemgr.h: No such file or directory
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:37: warning: 'struct hpsb_iso' declared inside parameter list
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:37: warning: its scope is only this definition or declaration, which is probably not what you want
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'rawiso_activity_cb':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:53: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:54: error: implicit declaration of function 'hpsb_iso_n_ready'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:61: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:62: error: implicit declaration of function 'dma_region_i'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:62: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:62: error: expected expression before 'unsigned'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:63: warning: assignment makes pointer from integer without a cast
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:64: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:68: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:82: error: implicit declaration of function 'hpsb_iso_recv_release_packets'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'node_of':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:87: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:87: warning: type defaults to 'int' in declaration of '__mptr'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:87: warning: initialization from incompatible pointer type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:87: error: invalid use of undefined type 'struct unit_directory'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'node_lock':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:92: error: implicit declaration of function 'hpsb_node_lock'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:92: error: 'EXTCODE_COMPARE_SWAP' undeclared (first use in this function)
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:92: error: (Each undeclared identifier is reported only once
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:92: error: for each function it appears in.)
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:93: error: 'quadlet_t' undeclared (first use in this function)
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:93: error: expected ')' before 'arg'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'node_read':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:98: error: implicit declaration of function 'hpsb_node_read'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'node_write':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:103: error: implicit declaration of function 'hpsb_node_write'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'start_iso':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:114: error: implicit declaration of function 'hpsb_iso_recv_init'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:114: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:116: error: 'HPSB_ISO_DMA_DEFAULT' undeclared (first use in this function)
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:118: warning: assignment makes pointer from integer without a cast
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:125: error: implicit declaration of function 'hpsb_iso_recv_start'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:128: error: implicit declaration of function 'hpsb_iso_shutdown'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'stop_iso':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:139: error: implicit declaration of function 'hpsb_iso_stop'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: At top level:
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:154: warning: 'struct hpsb_host' declared inside parameter list
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'fcp_request':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:167: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:168: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'node_probe':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:182: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:182: warning: type defaults to 'int' in declaration of '__mptr'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:182: warning: initialization from incompatible pointer type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:182: error: invalid use of undefined type 'struct unit_directory'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:187: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:187: error: 'quadlet_t' undeclared (first use in this function)
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:188: error: implicit declaration of function 'CSR1212_TEXTUAL_DESCRIPTOR_LEAF_DATA'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:188: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:188: warning: assignment makes pointer from integer without a cast
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: At top level:
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:243: warning: 'struct unit_directory' declared inside parameter list
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'node_update':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:245: error: dereferencing pointer to incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: At top level:
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:253: error: variable 'fdtv_driver' has initializer but incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:254: error: unknown field 'name' specified in initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:254: warning: excess elements in struct initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:254: warning: (near initialization for 'fdtv_driver')
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:255: error: unknown field 'update' specified in initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:255: warning: excess elements in struct initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:255: warning: (near initialization for 'fdtv_driver')
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:256: error: unknown field 'driver' specified in initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:256: error: extra brace group at end of initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:256: error: (near initialization for 'fdtv_driver')
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:259: warning: excess elements in struct initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:259: warning: (near initialization for 'fdtv_driver')
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:262: error: variable 'fdtv_highlevel' has initializer but incomplete type
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:263: error: unknown field 'name' specified in initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:263: warning: excess elements in struct initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:263: warning: (near initialization for 'fdtv_highlevel')
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:264: error: unknown field 'fcp_request' specified in initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:264: warning: excess elements in struct initializer
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:264: warning: (near initialization for 'fdtv_highlevel')
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'fdtv_1394_init':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:271: error: implicit declaration of function 'hpsb_register_highlevel'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:272: error: invalid use of undefined type 'struct hpsb_protocol_driver'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:273: error: implicit declaration of function 'hpsb_register_protocol'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:276: error: implicit declaration of function 'hpsb_unregister_highlevel'
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c: In function 'fdtv_1394_exit':
/home/jk/gspca-7876678e39df/v4l/firedtv-1394.c:283: error: implicit declaration of function 'hpsb_unregister_protocol'
make[3]: *** [/home/jk/gspca-7876678e39df/v4l/firedtv-1394.o] Error 1
make[2]: *** [_module_/home/jk/gspca-7876678e39df/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.30-ARCH'
make[1]: *** [default] Error 2
make[1]: se sale del directorio `/home/jk/gspca-7876678e39df/v4l'
make: *** [all] Error 2
[jk@arch4linux gspca-7876678e39df]$

Mr.Elendig wrote:1. you don't need to be root to run make
I used root because the compiler gave me an error of permission denied.
Mr.Elendig wrote:2. LANG=C make 3. /usr/src/linux-2.6.30-ARCH does not contain the whole source, grab it from kernel.org
can you explain this a little more detailed?

Assigning VXI IRQ using GPIB/VXI-C controller.

I am updating an older system to more robust COTS configuration and need to assign a different IRQ to each Cubic VXI Rx'r in the chassis. This was done automatically with my old controller (NI pc870) but with the replacment GPIB/VXI-C all instruments come up on IRQ7.
I have experimented with the NVConfig and only managed to get all Rx'rs to come up on IRQ6.
My goal is use the GPIB as a dumb (completely unconnected) VXI controller to simply boot and arbitrate the the BUS. I have an embedded VME board to service the interrupts.

Hello Dalu,
In the past, National Instruments only officially supported a few Code Instruments, which are documented in Appendix B of the GPIB-VXI/C User Manual, but I did not see the VX4240 in the Appendix.
NI officially discontinued support for code instruments on the GPIB-VXI/C about 6 years ago, so you might want to consider moving to a newer VXI controller to access your device. You can find more information on our VXI-MXI-2, VXI-MXI-3, and VXI-1394 remote controller options here.
Regards,
Joshua Hernstrom
PXI/VXI Product Support Engineer
National Instruments

Code instrument for binary transfer from VX4240 using GPIB-VXI/C Slot0

The binary waveform transfer from Tektronix's VX4240 does not work together with NI's GPIB-VXI/C Slot0. According to Tektronix NI has developed a Code Instrument to circumvent this problem. Where can I get it and how does it work ?

Hello Dalu,
In the past, National Instruments only officially supported a few Code Instruments, which are documented in Appendix B of the GPIB-VXI/C User Manual, but I did not see the VX4240 in the Appendix.
NI officially discontinued support for code instruments on the GPIB-VXI/C about 6 years ago, so you might want to consider moving to a newer VXI controller to access your device. You can find more information on our VXI-MXI-2, VXI-MXI-3, and VXI-1394 remote controller options here.
Regards,
Joshua Hernstrom
PXI/VXI Product Support Engineer
National Instruments

ViFindRsrc is have a problem with three or more crates

I have customer who has 4 crates of VXI hardware and in each of the crates it has 1394 VXI Control. When he runs our client software with three crates or more, viFindRsrc command will give him a error code VI_ERROR_RSRC_NFOUND. The DLL that is being use is one that we wrote and it loads the VISA32.dll dynamic.
An also when try to do the same thing here with three crates I have not problems. So any suggestions that you have to help me figure this out would be great. Also if could take some time try with any devices that you have would also be great.

Hi,
What versions of NI-VXI and NI-VISA are you using?
How is your system configured? Do you have all four chassis attached to the computer directly using IEEE 1394, or are they daisy-chained off one of the VXI-1394 controllers?
Can you post a NI-Spy capture when they run viFindRsrc? Here is a link to creating a good NI-Spy capture for troubleshooting. Have a great day!
Regards,
Missy S.
Calibration Engineer
National Instruments

Experience in programming LabVIEW with HP E1432A

Can someone share his/her experience in controlling HP/Agilent E1432A VXI module?
The last posting on the forum about HP E1432A was dated in 2001. I know NI has a LabVIEW plug&lay instrument driver (wrapper) now for the E1432A module.
How easy is it to synchronize multiple E1432A modules in a VXI chassis? and what is maximum numbers of channel and sampling rate you used successfully via an NI VXI-1394 (FireWire).
You help is most appreciated.
Regards
Ian Ren

Hi, Chris
I used the Agilent E8491B, IEEE1394 Firewire interface. With MS Windows 2000 & LabView
I think i had 4 E1432A cards (64 chns)
The COM measurement engine software was a free down load from VXI Technologies who have taken on production of the 1432 type of cards from Hewlett Packard / Agilent it enables you to use active x to control the cards it originally was also provided free from Agilent. But looking at their (VXI Tech) site today I do not see it, suggest you ask them they may have changed the name.
I add here the text supplied with the software help file to give you some more idea of what it does.
"ME4X library is created on top of the E1432 Plug and Play driver. One question is whether you should use ME4X or the Plug and Play driver when you create an application. ME4X has both advantages and weaknesses against using the Plug and Play driver.   The biggest advantage is the ease of use. It is possible to build an application with less than 1/10 of development time.   There are some drawbacks. To make the library easy to use, many functions are hard coded in the library. This will cause some compromise in the feature set and performance overhead. Although ME4X covers most applications, there may be a case where a feature you want to use is only available in the Plug and Play library.   If the measurement speed is more critical than flexibility, you may want to write a simple but not flexible program using Plug and Play.   Here are some general guidelines to determine which library should be used.
· If you want to build an application quickly without learning the hardware detail.     Use ME4X
· If you want to spend more time for data analysis and testing than application development.   Use ME4X
· If you are not comfortable programming in C or other low-level languages.    Use ME4X
· If you already have a working program using Plug and Play, there is no reason to use ME4X.
· Your application must run on HP-UX operating system.     Use the Plug and Play library
· You are a professional programmer, time for program development is not critical, and you want to build an application to get the most out of the hardware in terms of speed and features.   Use Plug and Play library
If you have never written an application for E1432/33/34 VXI modules and are still not sure whether to use ME4X or the Plug and Play library, I highly recommend to start with ME4X."
Hope that helps.

VXI 1394 viMove error

Similar Messages

Maybe you are looking for