PCI-6733

PCI-6733について質問させて頂きます。
開発環境[Borland C++ Builder 5 Pro(embarcadero)]でPCI-6733を制御するアプリケーションの開発を検討しています。
ドライバ｢NI-DAQmx｣に一通り目を通しましたが、対応可説明を確認できませんでした。
｢NI-DAQ｣も調査したところ、7.4で対応可能らしき説明を見つけましたが、Borland C++ Builder 5にNI-DAQ 7.4は対応していますか？
あるいは対応しているverを教えて頂けないでしょうか。
ftp://ftp.ni.com/support/daq/pc/ni-daq/7.4/readme_jpn.html#OS

daiji様
ディスカッションフォーラムにご投稿頂き有難うございます。
回答が遅くなり誠に申し訳ございません。
DAQmxをBorlandでご使用頂くにあたってC用のインポートライブラリがありますが、
これはLabWindows/CVIサポートとしてインストールされます。
英語の内容ではありますが、詳しくは以下のウェブ資料をご参照下さい。
How Can I Use The NI-DAQmx ANSI C Function Library With Borland C and Delphi?
また、LabWindows/CVIをお持ちでない場合も上記リンク先から
インポートライブラリをダウンロードして頂けますのでご利用下さい。
宜しくお願い致します。
日本ナショナルインスツルメンツ
技術部　山下　顕多朗

Similar Messages

Platform services PCI 6733

Bonjour,
Après avoir installé un carte PCI 6733,sous Measurement and Automation, je peux faire l'auto test de la carte (résultat OK), je peux accéder au panneau de test et l'utiliser avec succès, je peux créer une tache type génération de tension sur l'une des voies disponibles, mais dès que je veux l'utiliser en cliquant sur le bouton exécuter cela me renvoi l'erreur -50400, NI platform services : le transfert n'a pas pu être achevé dans la période de timeout ou le nombre spécifié de tentatives. je précise que je n'ai modifié à ce stade aucun des paramètres fixés par défaut lors de la création de la tache. Le problème reste le même lorsque je cherche à utiliser l'un des exemples fournis avec labview. Je pense à un problème d'installation. Je suis sous seven pro 64 bits, et j'ai testé avec le NIDAQ9.0.2 fournit sur le cd de la carte, avec la version 9.1.7 et 9.2.2.
Comment trouver l'origine de mon problème qui doit être du à une mauvaise utilisation de ma part (pour info, je n'ai jamais eu de soucis avec XP SP2 et la version 4.4.1f0 de measure and automation).
Merci pour vos éclairement ou suggestion de test.
Cordialement,

Bonjour,
Il s'agit surement d'un service qui n'a pas du s'installer correctement, je vous invite à réaliser les mêmes opérations que dans ce post:
http://forums.ni.com/t5/Discussions-de-produit-de-NI/Probl%C3%A8me-de-carte-NI-PXIe-6672-timing-modu...
Cordialement,
Da Helmut

Any examples that work with a PCI-6733?

I've been looking for a LabView example VI that has a very simple front panel for working with motors. I just got a PCI-6733 and haven't been able to find a real world example. Such as a motor starting, and doing something. If you know of one plz point me the the right direction.

Thanks, I can use the AO vi's.

Register level programming for PCI 6733

The information provided online for RLP with PCI-6733 is very limited. Only the register map for PCI-6713 is provided @ http://www.ni.com/pdf/daq/us/release_ni67xx.pdf.
However, how the board maps its resources on the PCI bus is not clear. So could you please provide the following information
1. What the manual means by "Base Address" and "Window Address".
2. What is mapped by each of the boards BARs (Base Address Registers).
3. The difference of registers between PCI-6713 and PCI-6733.
If possible, could you please provide a detailed reference for this Analog Output board as for other boards, such as PCI-DIO-96.

Maybe you don't need the MITE manual after all. My documentation (from 2003) lists only the "DAQ-STC Technical Reference Manual - Part Number 340934B-01" and "PCI/PXI 671x/673x Register Map". I don't know where I got the information about the MITE -- one comment in my code suggests comedi.org, while another one mentions I started rewriting the code to get rid of the comedi stuff (so there must be information available from somewhere else, probably extracted from the DDK).
IIRC the MITE is only used once, for initialization.
I'm sorry I can't provice any code, but the driver I wrote is not openly available.
Warning: Some of the DAQ-STC information was wrong in the version I used, I had to use trial & error for some of the funtionality.
Check out:
http://digital.ni.com/manuals.nsf/websearch/E929838D7D0EE50986256728007FEADF?OpenDocument&node=132100_US
http://digital.ni.com/public.nsf/websearch/15f094f65a17e3af8625660d0018a20a?opendocument
Message Edited by Thorsten Jens on 08-22-2008 08:17 AM
Message Edited by Thorsten Jens on 08-22-2008 08:22 AM

Problème synchronisation PCI 6733

Bonjour,
Ce post est un peu la continuation d'un autre initié sur la base d'une PCI 6733. Les voies analogiques sont le résultat de calculs, 1 seconde de signal est préalablement calculé et envoyé aux buffeurs de la carte. Parallèlement les signaux digitaux sont eux aussi calculé sur cette durée de 1s et envoyés au même moment que les voies analogiques dans la tache correspondante (les fréquences d'échantillonnage des signaux sont les mêmes, ie même nombre de points analogiques et numériques. Pour chaque type de voie 10 buffeurs sont définis (donc un décalage de 10 entre ce qui calculé et ce qui est joué).
Ma question: de temps en temps, on peut constater en sortie de carte un décalage (non fixe, entre 100ms et plus d'une seconde) de synchronisation entre les voies analogiques et numériques. A l'envoi sur les taches Dacqmx, les voies sont synchrones, en sortie de carte PCI 6733, elles ne le sont plus.
1/ Sachant que le problème est aléatoire, et qu'un arrêt de l'application et un redémarrage suffise pour que tout rentre dans l'ordre, puis-je trouver un moyen de détecter ce problème et le signaler à l'utilisateur via l'interface?
2/ D'ou pourrait venir ce décalage , et surtout comment s'assurer de la synchronisation des 2 types de voies?
Merci pour votre aide,
Cordialement.

Bonjour,
Avez-vous fait un benchmark de vos calculs ?
Combien de temps prend un calcul d'une seconde de signal? Il serait intéressant de connaitre cela.
Par ailleurs, il y a des fonctions DAQmx qui permettent de connaitre l'état du buffer de la carte. Cela pourrait donner une indication supplémentaire sur l'origine du problème.
Afin de mieux vuos aider, pouvez-vous nous dire en quoi vous développez : LabVIEW, CVI, autre ?
Cordialement
Jean-Philippe C.
National Instruments France

Eeprom address and caldacs model/address for pci-6014 and pci-6733

I have one pci-6014 and one pci-6733.
I need to transfer the calibration constants from eeprom to caldacs.
I search the adrress of the constants in the eeprom and the model and address of che caldacs.
Tanks

Hello,
It seems to be a common mode voltage or ground loop problem.
When you are sourcing an output signal from your DAQ board, the signal is already grounded, it means that it has already a reference. If you measure this output with a measurement device, which has also a ground, the both ground potential are not necessary equal. This difference is the common mode voltage and influences your measurement (offset).
Please check the following links to have more detail about grounded signal.
http://zone.ni.com/devzone/conceptd.nsf/webmain/8D907374C5E867F186256C640059F30C?opendocument
http://digital.ni.com/worldwide/france.nsf/webtechsupp/0E6A8D5999CEE1AF8025683C0056A4B1?OpenDocument&node=163080_f
Best regards,
Alexandre D
National Instruments

Reusing digital trigger on PCI-6733

I am working with a PCI-6733 analog output card. I would like to use the digital trigger to start a waveform, then use it to start another waveform without stopping the first (then start a third while the first two are running, and so on). I don't need to reroute the trigger signal - all the pulses can (but don�t have to) come through the same PFI terminal.
I haven't been able to do this with NI-DAQmx (I get errors, e.g. -50103, -89137, saying the "resources are in use"). Is it possible? Can it be done using register level programming? - looking through the register level programming guides, I didn�t see anything that indicated setting a new trigger would stop the currently running waveforms.
Thanks in advance,
Matt

Hello Matt,
I believe you can do it only if you use different PFI lines to trigger your waveforms. You won't be able to do it with one digital trigger, that's why you were getting those errors.
Try using three PFI lines to trigger each waveform and let me know if it works please.
LA

PCI 6733 self-test

I installed DAQ cards PCI 4472 and PCI 6733 in the same machine.
4472 works fine. But 6733 shows this message:
" Error 200020 - occured at self test".
I have installed NI DAQmx 7.3.
My computer in which both the cards are installed is a
Dell Precision 360, P4, 2.6 GHz, 1 GB RAM, with Windows XP.
I tried to install 6733 in two other computers. It passed the self test in both of them.
One of the machines had Windows 2000 and other had Windows XP(configuration similar to mine).
So there seems to be no problem with the card. I formatted my machine
and tried to install the card again. Even then, I get the same error
message. There is no resource conflict with Windows.
I removed 4472 from the slot and checked with just 6733 on the machine.
I also tried it in all the PCI slots. That doesn't seem to be useful
either. What could be the problem?
Can I use the card even if it doesnot pass the self test?
RVR

RVR,
Thank you for contacting National Instruments.
Have you tried reproducing this problem with the latest NI-DAQmx drivers (7.5)? Are you able to use the card even though it fails the self test?
It is possible that your system is not supplying the necessary 3.3 V and 5 V supply from the PCI bus. This can be especially true when using industrial PCI or expansion PCI chassis. Verify that your computer's motherboard has a 3.3 V supply for the PCI bus before proceeding with other troubleshooting. Visit Appendix A of the NI 671X/673X User Manual for more information.
Michael P
National Instruments

Hardware Clocking Error PCI-5122

I tried to run the vi attached (which i've run many times before) and my computer bluescreen. When it rebooted, I could no longer use my PCI-5122 digitizer card. When I try to do a device test or device reset in MAX, it tells me that theres a hardware clocking error.. I was using an external trigger for the aquisition, but don't think I was using an external reference clock. Could someone help me fix this?
Thanks
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5
Solved!
Go to Solution.
Attachments:
OPO Monitor.vi ‏53 KB

Hi,
This error may be the result of a hardware failure where the only
solution is a repair or replacement. There are however, some basic
troubleshooting steps that have been known to correct this issue
without a return.
Reboot the PC or PXI controller.
Try a different PCI or PXI slot.
Update the driver to the latest version.
If possible try the card on a different machine.
If these steps to not correct the issue then it is likely the
board requires repair which can be arranged by contacting National
Instruments Technical support (in france: 01 57 66 24 24).
Best regards,
Thomas B. | CLAD
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Inscrivez-vous gratuitement aux Journées Techniques : de l'acquisition de données au contrôle/com...

Connecting RTSI line to non-NI PCI card

I would like to trigger analog output on a PCI-6733 and trigger an non-NI PCI card using the GPCTR0 output. It appears I can direct the GPCTR0 output to the UPDATE for AO on the PCI-6733 and do this internally (say using RTSI-1). If I do this I presume that RTSI-1 will also be mirrored on the "external" RTSI bus and avaliable for triggering?
The non-NI card in question as 5V-tolerant LVTTL inputs. Of what points should I be aware as I proceed? As you can tell from my question I am a bit fuzzy on using the RTSI bus.
Thank You Very Much.

Hello GLewen,
Thank you for contacting National Instruments.
If I understand your question correctly, I believe you have the right idea. One of the main purposes of the RTSI bus is to facilitate the synchronization of multiple devices. It is also used to internally route signals. Before using the RTSI bus with DAQmx, you will need to register a RTSI cable in MAX (regardless of whether you are actually using a cable).
If you programmatically route the output of GPCTR0 (i.e. pulse train generation) to your AO Update via RTSI 1, you will literally be placing the pulse train generated by the counter on RTSI 1. You can then use RTSI 1 as the trigger source on other devices.
If you are using a non-NI PCI card, it is unlikely that the card is going to hav
e a RTSI connector on it. In this case, you will need to come up with your own method of harnessing the signal.
There are a few points to be aware of are. Although unlikely, any damage caused to your NI card by doing this could void your warranty. Be careful that you do not drive a RTSI line with multiple sources. This could damage your card.
I hope this helps! If you have further questions about the RTSI bus or internal routing, let me know.
Matthew C
Applications Engineer
National Instruments

6733 multiple frequency waveforms

I am working with the PCI-6733 DAQ card in the DIAQMX C environment (Not Labview).
I need the card to perform two separate (but not simultaneously on the same card) functions
I need to be able to generate 8 sine waves of independently varying frequencies (from 50 to 70 Hz).
I need to be able to generate 8 square wave of independently varying frquencies (from 1 to 10KHz).
Any examples out there?
Thanks,
A Hancock

A. Hancock,
There is a handy example that illustrates waveform output using the onboard clock located in the DAQmx example folder. Assuming you installing DAQmx to it's default location, it would be located:
C:\Program Files\National Instruments\NI-DAQ\Examples\DAQmx ANSI C\Analog Out\Generate Voltage\Cont Gen Volt Wfm-Int Clk
Simply load a regular waveform into this example. It defaults to a sin wave, you could easily adapt it for a square wave.
Changing the frequency is relatively straightforward, simply make a call to the DAQmxSetSampClkRate function before or while the task is running. This and all of the other functions are detailed in the DAQmx API located here:
"C:\Program Files\National Instruments\NI-DAQ\Docs\cdaqmx.chm"
or under Start > Programs > National Instruments > NI-DAQ > NI-DAQ C Reference Help.
Good luck,
--Paul
Applications Engineering
National Instruments, Inc
http://www.ni.com/support
--Paul Mandeltort
Automotive and Industrial Communications Product Marketing

Recognizing hardware from a Windows virtual machine hosted on Linux

Hi,
I would like to isntall windows in a virtual machine run from linux, and run my labview vi's and do aquisition from there. I tried once using a virtualized Windows XP 32-bit on ubuntu 64-bit, with Virtualbox, but the windows installation didn't recognize my PCI-MIO-16E-4 card. Maybe its because I didn't have the linux drivers installed.. I don't know. Soon I will begin using a the 7853R FPGA with the PXI-1036 Chassis, and would prefer if my virutalized Windows installation could see this hardware.
Has anyone gone through the steps of using NI hardware from a virtual Windows installation? Either Virtualbox, Xen, Vmware, or whatever..
Thanks,
-Sidney
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5
Solved!
Go to Solution.

Hi Sidney,
I see that this thread is a bit old, but I still have something to add. I know for a fact that VirtualBox, VMWare and VirtualPC won't let a guest OS see any real PCI card installed on the host computer. However, you might have better luck with Xen. There are options in Xen which allows you to pass PCI devices forward to guest OS's. People have gotten pretty far with using PCI forwarding that they have even managed to run Windows Vista with full hardware acceleration with Aero as a guest operating system. The only requirement is for your CPU to have virtualization support, i.e. the vmx or svm flag. The only catch is, Xen is significantly harder to set up.
I haven't tried this myself, and I am not from the LabVIEW group, and I am by no means authorative on this topic (don't let my signature fool you).
If you manage to get this to work, we would be interested to hear from you!
Yi
Software Developer
National Instruments - Electronics Workbench Group

Create 4 digital output pulses base on input ttl signal

Hi
I am a beginner in Labview and would appreciate any advice on how to solve the following problem.
I am creating a TTL pulse train, and would like to send that into Labview as input. For every falling edge detected on the input signal, I'd like Labview to generate 4 digital output pulses. For each output pulse, I'd like to be able to specify the delay, and duration. The picture should illustrate it more clearly, with the numbers showing the intended order of magnitude.
System: NI PCI-6733 DAQ card, Labview 8.5
My daq card has 2 24-bit timers, and 8 digital I/O but I don't know what the best approach is for creating between 4-8 output pulses of this precision..should it be handled in hardware, or in software? And how would I go about it
Thanks,
-Sidney
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5
Solved!
Go to Solution.

Hi Yann,
Wow, thank you so much for this example! I'm trying to take a look at it, but when I run it.. it responds with the following error message
Error -200452 occurred at Property Node DAQmx Trigger (arg 1) in DAQmx Start Trigger (Digital Edge).vi:1->reprise-1.vi
Possible reason(s):
Measurements: Specified property is not supported by the device or is not applicable to the task.
Property: Start.TrigType
Task Name: _unnamedTask<49>
This is strange too, because ive already used the Digital Edge Start trigger for a different application with this card.
-Sidney
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5

Best practice for code structure to control multiple devices in a 2 stage-sequence

I have a question about code architecture and getting multiple devices controlled and sychronized for one experiment. This is an "architecture"-type inquiry, so I am hoping for some suggestions on how to proceed.
I run an experiment in which I control 2 NI PCI-6733. I am soon to add a Tektronix AFG 3022B, and have long been putting off an opportunity to rewrite my labview code from the ground up. I inherited it from an earlier research, and while functional, I would like to make it easier to modify and break up into subVi's and such. Link to the current program (labview 8.6.1) is here if you would like to see the code that is currently used, and the subvi's are in a zip file. The current version of the experiment consists of just one stage, all the writing of the data to the PCI cards is saved for the end. I need to change this in my new setup though.
The new experiment consists of 2 stages. The first will run (looping an output array to the PCI cards) until it hears a "true" from another computer (connected via TCP). At that point, it should switch to stage 2 and run a sequence (usually 10^5 timeunits in length, where the time unit is 0.1 ms) that outputs to the two PCI cards, the AFG 3022B, and with the flexibility to add more devices in the future.
Most appreciated would be structural advice. How to arrange the VIs, if it's good to use a "master" VI that would control the two subVi's of stage 1 and 2, etc... Feel free to ask for more details if it would help clarify my question. Thanks!
Solved!
Go to Solution.

Programs of this type usually use a state machine of some sort. You can find many tutorials on LabVIEW state machines in these forums or the LAVA forums. If you are doing a rewrite, I would also recommend you consider LabVIEW classes. They help modularize your code and make the subparts more reuseable. You may end up with less to maintain, as a result.
<shamelessPlug>You may also want to consider TestStand. It was designed to run sequences of tests, so may make your life easier. It could also be gross overkill.</shamelessPlug>
Let us know if you run into issues with state machines or classes.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Dell 2000FP monitor

Hi,
Our lab recently purchased a Dell Precision 650 workstation along with
a Dell 2000FP LCD monitor. We installed our DAQ boards, a PCI-6733
and a PCI-6120, and everything seemed happy. The PCI-6733 is
connected to our rack by the CA-1000, and the PCI-6120 is connected by
a BNC-2110.
We were testing the setup and noticed that there was a DC offset of
about 50 mV when monitoring channel 0 of the PCI-6733 on a scope. The
offset was present on all the output channels. No LabVIEW programs
were running and no signals were being sent. After trying a few
things, we turned off the monitor, and the offset disappeared.
We then tried to plug the monitor into a different outlet. We tried
using the RGB connection of the monitor. We tried using the DVI
c
onnection of the monitor. We tried changing the position of the
monitor. Nothing worked and the offset remained. We were also able
to reproduce this offset by using our old DAQ computers with different
DAQ boards and different graphics cards along with the LCD monitor.
We then connected our old CRT monitor and the offset disappeared.
Has anyone experienced any problems with LCD monitors? Has anyone
experienced similar problems with this particular model, the Dell
2000FP? It's hard to believe that the offset is caused by the monitor
but all of our tests so far have shown that that is indeed the case.
Thanks in advance,
Brian
Solved!
Go to Solution.

Brian,
I have never experienced this behavior, and I have definitely used LCD monitors with DAQ systems. Are the video cards that you are using PCI or AGP? If you have only tried PCI video cards, and your motherboard includes an AGP slot, I would suggest seeing if an AGP video card solves the problem. Also, if you move the LCD monitor further away from the PCI-6733, is the offset affected?
Spencer S.

PCI-6733

Similar Messages

Maybe you are looking for