Pci 6035E

Saludos, estoy manejando la tarjeta pci-6035E con un potenciostato marca pine, dicho instrumento ya cuenta con un software que me permite interactuar con la tarjeta, sin embargo quiero automatizar la tarjeta con labView, pero tambien utilizar es software del instrumento,
mi pregunta es si no causa conflictos el utilizar los dos programas (desde luego no al mismo tiempo) y donde puedo descargar el driver y ejemplos de aplicacion de la tarjeta.

Que tal Anibal
                         Gracias por utilizar el foro de National Instruments.
Para contestar tu pregunta se necesita mas informacion.
-Qué modelo de potenciostato estas utilizando?
AFCBP1?
-Qué version de labVIEW y de drivers utilizas?
Utilizas el PINECHEM?
Sin embargo podemos contestar algunas cosas sin esta informacion.
Para que tu puedas comunicarte con tu potenciostato necesitas saber de que forma se comunica o manda las senales por el PC interface connector que tienes en la parte de atras de tu potenciostato. ( Ver en que canal esta conectado las señales de los electrodos que tengas conectados y ver las caracteristicas en voltaje de esta senal)
No he tenido la oportunidad de utilizar el pinechem pero basicamente el proceso de adquisicion es controlable siempre y cuando  sepas en qué canal analogico de entrada viene la senal ( que no es tan dificil de descubrir en tu tarjeta desde MAX)
Puedes hacer mediciones con el aparato conectado a tu tarjeta y desde MAX hacerle test a cada canal de entrada.
Me imagino que el pinechem solo se utiliza para desplegar la adquisicion y no para controlar algun tipo de salida del potenciostato.
Si esto ultimo ocurre y se hace desde la tarjeta
tienes que investigar qué tipo de señal es para mandarla cuando sea requerido.
Basicamente tienes que saber cómo funciona el programa que quieres sustituir para poder utilizarlo desde LABVIEW.
SEGUNDO: Cuando tu utilizas un recurso de una tarjeta de adquisicion de datos , la utilizacion de este recurso tiene 5 pasos.
unverified
verified
reserved
running
commited
Como no sabes de que manera esten utilizando el recurso, TAL VEZ el PINECHEM deja en alguno de estos estados el recurso de tu tarjeta y la respuesta seria que NO puedes utilizarlos al mismo tiempo.
SI cada adquisicion de datos el otro software libera el recurso entonces SI se puede alternar la utilizacion  del control.
En fin anibal
como vez el asunto no es tan trivial y depende de cuanto conozcas el comportamiento del potenciostato.
Espero haberte podido ayudar
y estoy al pendiente de tus resultados.
Saludos 
Erwin Franz R.

Similar Messages

  • Connecting PCI-6035E and SCB-68 and control a laser to turn on/off

    I have connected SCB-68 to a 15pin cable and connected to a laser. From computer I have connected PCI-6035E board to SCB-68 to control a Laser to turn on and off from a LabVIEW program. I have connected PIN#, 6,7, 14 from SCB-68 to 15pin connecter cable, and I connected PCI-6035E board to SCB-68. My program is not turning on the laser.
    Solved!
    Go to Solution.

    dnchari:
    Thanks for the manual. Youll need to set up the jumpers for external modulation and laser enable as shown in section II of the manual.
    On you 15 pin connector you will need to wire pin 4 to pin 5. This will enable the laser. Later, once you can verify modulation, maybe we can use the DAQ card to control the on/off.
    You made mention of DACOUT0 and AOGND, these look like the signals you need to connect- DACOUT0 wired to pin 8 (EXT MOD) and AOGND to pin 7 (GND).
    NOTE: Looks like 0V into the laser is no power, 1.350V into it is full power, so do not exceed 1.350V when commanding the analog output voltage.
    Hopefully this should get you started. Wear the proper wavelength laser safety goggles.
    -AK2DM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    "It’s the questions that drive us.”
    ~~~~~~~~~~~~~~~~~~~~~~~~~~

  • PCI-6035E ... no DMA?!?

    Hi everyone!
    I have finally gotten to the point of testing the PCI-6035E I have in
    the PC it's supposed to run in, and it seems to work fine ... except
    that the driver (both NiDAQ 6.0 and 6.7) had no DMA. This is confirmed by
    running the test-panel, which issues an error about "first DMA channel
    not responding" but upon continuing displays the kind of data I would
    expect.
    The documantation says this card should have one DMA channel, but
    trying the card in two different computers (PC/Win98) leads to the same
    results: no DMA. Do I need to somehow activate this?
    Rudolf

    Rudolf Potucek wrote:
    >
    > Hi everyone!
    >
    > I have finally gotten to the point of testing the PCI-6035E I have in
    > the PC it's supposed to run in, and it seems to work fine ... except
    > that the driver (both NiDAQ 6.0 and 6.7) had no DMA. This is confirmed by
    > running the test-panel, which issues an error about "first DMA channel
    > not responding" but upon continuing displays the kind of data I would
    > expect.
    >
    > The documantation says this card should have one DMA channel, but
    > trying the card in two different computers (PC/Win98) leads to the same
    > results: no DMA. Do I need to somehow activate this?
    >
    > Rudolf
    Hi!
    Probably Your computer hasn't enough system resources.
    Grzegorz "GREG" Lentka
    "There is no second chance to make the first glanc
    e"
    "Nigdy nie ma drugiej okazji, zeby zrobic pierwsze wrazenie"

  • Lock in amplifier for PCI-6035E?

    Is there a LabVIEW lock in amplifier available that is suitable for use with the PCI-6035E card? I downloaded the LockInDEMOSimple and LockInDEMO VIs from the website - are these suitable?

    You would need a DSA-Board or a S-Series board to program a lock in amplifier.
    Because the M_series boards are multiplexing all there channels to one A/D converter, it is not possible to program a lock in amplifier with a M-Series device. You need a board that can sample multiple channels simultaneous, like a S_Series board or a DSA device.
    Check this link out for more details:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/3b2936e1afe39ac286256c2f00746422

  • PCI 6035E/6036E unable to read voltage on Analog input

    I am using LabVIEW 6.0.2 and have the 6035E in one machine and 6036E in another. I am trying to read a DC voltage from a device into the DAQ to use in my Program. Everything else on the cards seem to work, but I cannot get it to read a voltage.. it always says -10v when the measurement is near 4v. I have a handheld DMM to verify the device readings but the DAq will not work.. I have tried DIFF, NRSE, RSE and none seem to work.. Maybe I am setting it out wrong?
    Also what LV VIs should I use to get everything set-up properly?
    Thanks
    Jeff D.
    OS: Win 7 Ultimate
    LabVIEW Version: 2011,2010,2009 installed
    Certified LabVIEW Architect

    Hello jdebuhr,
    It is odd that you would not get anything from the test panels. You said that you have two boards, are you having the same result on both boards? How exactely do you have your system configured (signal connection, software configuration)? If everything is connected right and you are reading from the correct channel, then it appears that your board might be defective.
    Thanks for contacting national Instruments
    Serges Lemo
    Applications Engineer
    National Instruments

  • Dma channel problems

    Hello,
    I really need help on this one. Using PCI-6035E I am trying to output an analog signal (actually 2 waverforms interleaved together) on 2 channels while simultaneously using the two GPCTRs to measure two separate signals' pulse widths. The VI runs perfectly on some occasions, while on others I get "no DMA channel available for use". Whenever this message appears and I try to exit labview, the nipalk.sys driver messes up and I get a blue screen crash that says "process_has_locked_pages" (I traced the locked pages to this driver). I've tested this many times and it appears to me to be totally random. I've used the Set DAQ device information VI to set the two counters to use interrupts, but I need to use the one DMA channel for
    the analog output. My best guess is that there is some kind of resource conflict with something else in the PC, but I can't figure out how to change DMA assignments(I'm using Windows XP). The NI-DAQ Measurement and Automation Explorer tells me that the card is using DMA 0, IRQ 17. I've tried uninstalling all the NI-DAQ drivers, reinstalling and updating. Any help anybody could give me would be greatly appreciated.
    Thanks,
    Nick
    Attachments:
    aug7.vi ‏374 KB

    Hello;
    The PCI bus has 3 DMA channels that are share in between all devices that do DMA data transfers.There is nothing you can do to change that, since that is a PCI bus feature.
    The best way to go about that is to remove other devices that use DMA, such as network cards, for instance. That might free up more DMA access time for your DAQ device to execute its data trasnfers.
    Hope this helps.
    Filipe A.
    Applications Engineer
    National Instruments

  • DAQ doesn't show the input waveform in Labview as it is in oscilloscope.

    Just bought a PCI-6035E DAQ board + CB-68LP connector and testing it by inputing a square/triangluar/sine wave from a wave generator. In MAX, I can see the waveform as in the oscilloscope. However, when I try to see this input in Labview by using the Waveform Chart VI, the displayed waveform becomes an arbitrary one. Why is it happening and how can I correct it? I'm a novice in this field, so your advice would be highly appreciated.

    Seems that there's something missing in connecting to the daq card: in most cases this situation occurs when the signal reference is missing. When you input a signal in an oscilloscope, you wire both a signal and its reference (ground or similar), otherwise you see nothing than noise and disturbs.
    With a daq card things are a little more complicated 'cause you have a more flexible and more universal instrument than an oscilloscope; you must decide which type of connection to use: referenced- or not-referenced- single ended or differential connection, which channel(s) to use... and the configurations in MAX and in labview must match if you want to simplify your job.
    I suggest you to study carefully the card user manual when it describes the analog input w
    iring and all the consideration about different types of connection. My experience is that in most cases the differential input is better to reduce signal noise and reject disturbs, but you must use 2 channels per signal...
    You can also look at this tutorial about wiring an input signal:
    http://zone.ni.com/devzone/devzoneweb.nsf/opendoc?openagent&2E07CE2019CCB1D3862568650057930A&cat=99368070225FE073862567E6006C8DD7
    You're entering a (slightly) complicated but (very) interesting world. Good job!
    Roberto
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • Digital stimulus-f​requency response: Need to drive with digital output trigger. Using counters for response.

    I need to drive stimulus-response with a software driven digital trigger and NI-TIO counter based response. No analog I/O is really relevant, although I have a PCI-6035E multi-function DAQ as part of my gear. I intend to use the analog, but its timing is non-critical and can be software timed.
    The real trick is that I want to set the basic timing of the system (in the range of 1 - 50Hz) from the timer0 on the 6035E. This signal needs to be replicated to drive a trigger pulse and to route through RTSI (or a PFI) to trigger frequency counts using the four possible groups of counter/timers on the 6602.
    What I need is:
    while( enabled )
    Repeat at (
    software controllable rate = 1-50Hz)
    Trigger Sets a PFI line for 10-20us
    same trigger sets an RTSI line
    - Software Set Delay (usually zero)- stable is more important than the delay time!
    Count for software set time on 4 counters
    analog samples
    Post-process
    I want to do this in LabView. I have checked out the Advanced sychronization demos online, but the examples all use analog triggering and buffered digital I/O. This doesn't really address what I need to do.
    I have made some failed attempts which relied on software to sync up the trigger and the response frequency acquisition. This is definately flawed. I need to start the counting right after setting the digital output trigger, and stop the count after a fixed interval for frequency calculation.
    I am having trouble working through the signal routing to get the timing to trigger off the digital stimulus output pulse.
    Any help would be appreciated
    Thanks,
    Joe

    Joe
    What are you using the trigger from the 6035E for? I do not know what you mean by, "to trigger frequency countes."
    If you are having problems just routing the signal to the 6602, here is a vi that shows you how to route a signal through the RTSI cable to use as the source of a counter.
    Brian
    Attachments:
    Route_RTSI_to_Source.vi ‏67 KB

  • Pinball test fixture

    I am real new to Labview and I thought this would be a simple project to help me with the learning process. 
    I want to build a test fixture for the Pinball machine pcbs.  I have a number of them in storage from different manufactures.  I think most of this is just going to be inputing a closed switch message to either the lamp matrix or the solinoid drivers and then monitoring the outputs to see if the lamp light or solinoid fired.  This is where I want to start.
    Could I get an idea and overview of the hardware and basic Labview software approach you would use to do this?
    I have a PCI-6035E and a PCI-6534.
    Is there some hardware that would make this easier to create or will I need to create a test jig to to buffer the signals before going into the PCI cards?
    I am just looking for some general ideas on how to approach this.
    Thanks
    Kevin

    Hello uriahsky,
    I would like to point you toward some helpful links in finding common LabVIEW architectures as well as how to utilize the DAQ resources you've mentioned below. I would recommend that you also browse through the available LabVIEW examples as a getting started point for a new application in which you may then use DAQmx functions (highlighted in the getting started link below) to then control your hardware. 
    http://www.ni.com/gettingstarted/labviewbasics/  (Introduction to NI LabVIEW)
    http://www.ni.com/gettingstarted/labviewbasics/exa​mples.htm  (Finding Examples for NI LabVIEW) 
    http://www.ni.com/white-paper/2926/en  (Using a State Machine (Event Driven) Architecture)
    http://www.ni.com/white-paper/3022/en  (Application Design Patterns: Master/Slave)
    http://www.ni.com/white-paper/3023/en (Application Design Patterns: Producer/Consumer)
    http://www.ni.com/white-paper/5434/en  (Getting Started with NI-DAQmx: Main Page)
    Wes W
    Application Engineering
    National Instruments
    www.ni.com/support

  • Call Library node error [1]

    Hi,
    I've written a program to control the angular position by using PID control algorithm.
    The program works fine but after certain amount of time. The system hanged and need to shut down the LabVIEW and restart.
    The warning message pop up is showing in the attached file.
    One more question, is it the PCI-6221 M-series card can used for real-time application.
    Just for your information, I'm using:
    - LabVIEW 7.1
    - PCI-6035E
    The program is attached to the message "Call Library node error [2]"
    Thanks.
    Best regards,
    IANES
    Attachments:
    Error11.bmp ‏405 KB

    Hi,
    It would be very helpful if you could post the code you are using to generate this error. These call library errors can be caused by many things.
    Check out the following KnowledgeBases:
    http://digital.ni.com/public.nsf/websearch/0120D13​E4B4C94BB86256A3F007695EE?OpenDocument
    http://digital.ni.com/public.nsf/websearch/58596F5​D41CE8EFB862562AF0074E04C?OpenDocument
    -Sal

  • Segmentation fault when calling gpctr function from matlab mex file

    I am trying to write a simple mex file for square wave generation using counter1 of PCI-6035E. I am using matlab's native compiler to compile and link with the nidaq32 library, ver.6.9.3, with no errors. When the mex function is called from a matlab script, however, the program crashes at the first call, to reset the counter. (I can generate a square wave with the test panel.)

    Sorry for the delay in responding. I got caught up in other stuff. I am attaching my little program as requested. As you can see, I have just wrapped a mexFunction call round the example code for square wave generation. After I posted this, I tracked down a copy of BorlandC++, installed it on my computer and recompiled using that compiler and *b.* libraries. And would you know it, the program works. The question remains, though, why it doesn't work with Matlab's native lcc compiler. Plus, I have limited disk space, so if I can do without BorlandC, I can use the extra room. The runtime error was a Segmentation fault that I traced to the first call to GPCTR_Control.
    Attachments:
    pulsegen.c ‏4 KB

  • Motion control et Labview 6.1

    Bonjour,
    Je viens d'installer une carte PMC MFX PCI Series 1000 Multiflex Motion Control en remplacement d'une carte isa (incompatible avec les nouveaux systèmes).Un prog correspondant Motion Control gère le déplacement de sondes sur une table 1 axe de chez Schneeberger.
    L'ancien système, à savoir Labview 4, Motion Control pour la carte isa, et PCI 6035E (acquisition de données)exécute le déplacement dans un sens , s'arrête, et repart vers sa position initiale dite origine ou home (fait exactement le cycle proposé par le CW demo.
    Avec le nouveau système, à savoir Labview 6.1, carte PCI remplaçant la isa, PCI 6035E gère le déplacement aller, mais après arrêt ne reprend pas la position initiale.
    Il faut savoir que les résultats de l'acquisition (face avant et création dans fichiers tableurs)n'apparaissent qu'une fois que la procédure de retour du chariot est activée (donc invisible sur le nouveau système et le chariot doit être ramené manuellement avec CW demo).
    Aussi, remarque importante, le cycle proposé par CW demo fonctionne avec le nouveau système (activation sous WinControl de la bipolarité PWM avec 1om2).
    J'aimerais savoir ce qui peut provoquer ceci dans le diagramme joint (piste sur MCGo Home.vi)
    Merci.
    Attachments:
    BOSCDII16marsfintableau21.vi ‏815 KB

    alamarque,
    Tout d'abord, je n'ai pas les VI de controle de votre carte d'axes. De plus, la carte de contrôle d'axes en question n'est pas une carte NI, donc je ne connais ni les fonctions, ni l'outil CW Demo.
    Le plus simple serait de procéder par ordre.
    1. Avez vous des exemples simples de VI Lv mettant en oeuvre votre carte de contrôle d'axes? Si oui, avez vous essayé de les faire fonctionner seul?
    Peut être que le problèmes rencontré provient de la configuration de votre carte.
    2. Etes vous sur que l'application original fonctionnait bien en Lv 4.1 . La compatibilité est ascendante, et je ne vois pas de raison concernant le non fonctionnement de ce VI.
    3. J'ai vérifié les fonctions d'acquisition de la carte NI que vous utilisez. Elles sont rudimentaires, et dans le cas ou elles produiraient une erreurs, vous en seriez directement informé par une Popup d'erreur. Si vous n'avez pas d'exemples pour le point 1, je vous invite à faire un nouveau VI n'implémentant que la communication Motion (Votre mouvement d'aller retour) afin de déterminé si vous êtes capable de faire votre aller retour.
    4. Etes vous sur que le jeu de fonction Lv qui vous a servi a piloter la carte Motion ISA, est bien compatible avec votre nouvelle cartes PMC. Je penses que le constructeur de la carte pourra vous éclairer sur ce sujet. Peux être avez vous besoin d'un nouvelle DLL.
    Raphael TILLET
    NI FRANCE
    Cordialement,
    Raphael T

  • MC go home

    Bonjour,
    Je viens d'installer une carte PMC MFX PCI Series 1000 Multiflex Motion Control en remplacement d'une carte isa (incompatible avec les nouveaux systèmes).Un prog correspondant Motion Control gère le déplacement de sondes sur une table 1 axe de chez Schneeberger.
    L'ancien système, à savoir Labview 4, Motion Control pour la carte isa, et PCI 6035E (acquisition de données)exécute le déplacement dans un sens , s'arrête, et repart vers sa position initiale dite origine ou home (fait exactement le cycle proposé par le CW demo.
    Avec le nouveau système, à savoir Labview 6.1, carte PCI remplaçant la isa, PCI 6035E gère le déplacement aller, mais après arrêt ne reprend pas la position initiale.
    Il faut savoir que les résultats de l'acquisition (face avant et création dans fichiers tableurs)n'apparaissent qu'une fois que la procédure de retour du chariot est activée (donc invisible sur le nouveau système et le chariot doit être ramené manuellement avec CW demo).
    Aussi, remarque importante, le cycle proposé par CW demo fonctionne avec le nouveau système (activation sous WinControl de la bipolarité PWM avec 1om2).

    Voir le lien :
    http://forums.ni.com/ni/board/message?board.id=240&message.id=2150
    Sanaa T.
    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;}
    >> http://www.nidays.fr/images/081110_ban_nidays09_468X60.gif

  • CW demo PID pour suppression de Following error

    Bonjour,
    J'ai déjà écrit dans ce forum, concernant un problème de retour chariot sur une table 1 axe de chez Schneeberger avec une application Labview 6.1 nécessitant une carte PCI 6035E (acquisition données), et une Multiflex PCI (remplaçant une isa sur un ancien système).
    L'erreur a été trouvée dans une séquence commandant le retour, non exécutée à cause de la non détection de la position maximale dans un sens (450000 pas ou 90 mm).
    Pourquoi elle ne la détecte pas? La position réelle se distingue de la position optimale par une erreur de position (following error).
    Sortant de Labview, et passant sous CW demo, je fais une succession de Move + et Move - sur une certaine distance, et le problème d'erreur de position se remarque également (la position de retour à la position initiale change constamment: c'est donc un problème intrinsèque à la configuration du système et non de Labview.
    Consultant le CD motion control fourni avec la carte, j'ai appris que la configuration du PID avec ses paramètres de gain proportionnel, dérivé, intégral,...conditionnait l'erreur de position.
    Seulement, il ne donne pas de piste concernant les valeurs à apporter.
    J'aimerais connaitre le programme ou l'endroit où je pourrais obtenir le moyen de trouver ces valeurs (puisque je ne peux les tester directement), voire même ces valeurs.
    Fournie en pièce jointe, une capture écran de la présence du Following error dans l'application du CW demo (les valeurs de paramètres du PID sont celles données par défaut)
    Attachments:
    CWdemoreglage.JPG ‏133 KB

    Bonjour,
    Afin d'essayer de vous venir en aide, quelle est la carte de contrôle d'axes que vous utilisez?
    Cordialement
    David D.
    Ingénieur d'Applications
    National Instruments France

  • GPTR doesn't output pulses

    I'm controlling GPCTR0 on a PCI-6035E card with software (Labwindows) that has it send out a single logic pulse. In the past month, the counter has gone from working fine, to outputting pulses of about .1V, to not pulsing at all. I've tried switching to counter 1, to no avail. I've also run the online diagnostic on the PCI card, and it passes alll of the tests. What's going on?

    perhaps your VI may be corrupt. If it passes all the diagnostics and the other counter does the same, it is most likely a software problem. Perhaps your VI may be corrupted or something in the code is wrong. I think it would be helpful to see the code you are using to generate this pulse.
    Derek

Maybe you are looking for