PXI 652x DIO Readback?

I have a PXI 6528 DIO board with TTL output channels that NI claims to have readback capability. I think I need readback capability to facilitate SE execution steps. How can readback be accomplished in SE or DAQmx? A very old LV 6.1 vi example is available here
http://www.ni.com/example/29102/en/
but SE cannot run an old LV 6.1 vi. Can someone either answer my question or at least convert the LV 6.1 vi example to LV 2010+??
Thanks for any advice

http://forums.ni.com/t5/Version-Conversion/Example-VI-for-PXI-652x-DIO-from-LV-6-1-to-LV-2010-11-12-...
You also need to explain where you got the idea that you need read back capability. An SE step will set the logic states. Do you doubt that the write will not work?

Similar Messages

How do I calculate the max latency of a PXI 8135 (controller) to PXI 6528 (DIO) output?

We are using a PXIe- 8135 Controller and a PXI-6528 DIO module in a PXIe-1082 chassis. We are sending DIO input and output commands using Powershell in Windows 7 on the controller. Due to tight requirements I need to know what is the max latency from when the Powershell command is issued to when the read input or write output command will take place in the DIO I/Os.
If this should be in a different Community Board Location please let me know.
Thanks for the help in advance,
Dan_F

Hello dan_f,
As the latency of Powershell and Windows are not tested, it is hard to determine the latency of your setup. The latency from the PXIe-8135 to the PXI-6528 should be in the realm of nanoseconds. The PXI-6528 does have a couple of latency numbers that can be found within the user manual on Page 24, and they are as follows:
Minimum pulse-width for change detection - 150 µs
Propagation delay - 65 µs, typical
You may be able to do some testing to ballpark the latency of the controller OS/software side of the input/output commands, but depending on how critical this latency is to your measurements, you may want to look into using a real-time OS instead.
Chris H
Applications Engineer
National Instruments

Acquire single point 12 bit data @ 200Khz using PXIe 6535 DIO RT

I want to acquire single point 12 bit data @ 200Khz using PXIe 6535 DIO, PXIe 1072 chasis and 8820 controller in RT. Problem is I am unable to acquire data as triggered input. Loop execution time takes ~10us (measured using rt tick count). Thus It misses the samples. Am I missing something? What are the proper ways to acquire digital data in RT?
Also I am wondering whether I can use the SMB connector of 8820 controller as my acquision trigger input pulse. I am completely new to RT. Any help will be appriciated.
Thank you.

Hi jtele1,
To make sure that the data gets written in the correctly order I would recommend monitoring the Time Out of the write. If a time out occurs you could stop writing all FIFOs and then start when all the Time Outs are no longer there. Another option is to look at your host side and determine if you can read larger chunks of data at a time and allow the host side to deal with processing the data. An additional option would be to look into high throughput streaming for FlexRIO. In this setup you will be writing the data directly to disk on your host side and then you could process the data at a later time. I have linked an example below, this example was giving me trouble so please let me know if you have trouble loading this example. Depending on your situation these may not all be acceptable options but you will need to ensure that you are not filling any of your FIFOs. Lastly, from what I can tell you are using a Windows OS as your host and in that situation you have no way of controlling when your LabVIEW application gets processor time. If you were to switch to a Real Time controller you would be able to ensure when certain tasks are run and add priority to tasks. Please let me know if you have further questions.
High Throughput Streaming
https://decibel.ni.com/content/docs/DOC-26619
Patrick H | National Instruments | Software Engineer

Ports being damaged on PxI-6508 DIO

wondering if anybody else has run into this or something similar. I'm using two PXI-6508 DIO cards, one in slot 2 of my chassis and one in slot 3(PXI-1010 chassis). the card in slot 3 is for digital outputs, slot 2 is for digital inputs.
A few months back I had to have the card being used in slot 3 repaired because some of the ports had been damaged (pins were stuck high). After the board was returned I installed it in slot 2, now the other board that is in slot 3 has damaged ports(not the board that was repaired before).
The confusing thing is that the board that I'm testing with them is just an interface board, it's basically all straight feedthroughs some with pullups or some lines are inputs to an inverter or something similar
. Nothing high current/ voltage. The pins that got damaged actually just drive lines with only a pullup and no other electronics, so I'm basically coming from slot 3, through a 1K resistor in my fixture, into the B.U.T. and then into slot 2.
I was told it could be a grounding problem and to make sure the grounds from slot 3 and 2 are at the same potential...they are. One interesting thing though. The cable coming from slot 3 was damaged and one of the grounds from the card was not getting to my fixture...but the other one was...and the grounds are connected internally on the PXI-6508 so as long as one is connected to my system ground then I should be ok right?
Anyway, has anybody else had problems with DIO cards? Like I said I'm not working with high currents or voltages...only ports being used as outputs have been damaged.
Any advice?
Thanks in advance

Thanks for the reply Spencer, yes it turns out the same lines were damaged in both instances. Actually the ports CPBA, CPBB, CBPC were damaged both times.
I found a problem in my fixture where I had two digital lines coming from the DIO cards (both outputs) going to the same pin on my board (via two different connectors) I was driving one of them high and low while the other one was initialized low but not used. This could have been my problem, essentially what I had done was connect two outputs together, both initialized low, and then driven one high. I've made the necessary changes in my fixture and HOPEFULLY, this problem will not occur again.
Thanks

Defekte PXI-6533 DIO-Karte

Sehr geehrte Damen und Herren,
ich habe zwei defekte PXI-6533 Karten mit folgenden Fehlern:
SN: 16D268A
Fehler:
- Karte wird von PXI-1042Q und MAX 5.4.0f0 erkannt.
- im MAX wir bei Selbststest der Fehlercode -200020 ausgegeben.
- beim Zurücksetzen der Karte im MAX wir der Fehlercode -50150 ausgegeben.
- Beim Aufruf des Testpanels im MAX stürzt der PC mit Bluescreen Meldung ab!
SN A68BB9
Fehler:
- Karte wird von PXI-1042Q und MAX 5.4.0f0 erkannt.
- im MAX wir bei Selbststest der Fehlercode -200020 ausgegeben.
- Zurücksetzen der Karte im MAX i.O.
- Alle Ports reagieren nicht mehr, weder wenn diese als Input oder als Output konfiguriert sind.
Ich benötige zum Einsenden hierfür eine RAM-Nummer, bzw. können sie schon im voraus beurteilen, ob diese Karten überhaupt noch repariert werden können bzw. was eine Reparatur kosten wird?
Vielen Dank.
Mit freundlichen Grüßen
Michael Müller
Greetings Michael

Guten Tag Herr Müller,
bitte stellen Sie diesbezüglich telefonisch eine Supportanfrage bei National Instruments unter der Nummer 089 7413130.

Hardware compare issue - PXI-6552

Hi!
I'm using a PXI-6552 DIO module for testing SDRAM chip.
I'm not sure about hardware compare operating. I'm using a sequence of 0 and 1 to drive the tester during write command and H/L as expected responde with read command.
Does the H/L response data puts the driver to high impedance?
The problem is that also when i skip the write command I retreive (fetch) the response data correctly.
Thank you!
MM

Thank you for the answer!
My configuration is a little bit different because I use the D0..D7 lines as bidirectionl lines.
I noted that the system works while the clock frequency is below 25 MHz, but i don't know why.
Has anyone tried to use this module above 25MHz?
Thanks a lot!
MM

PXI-6528 Watchdog Timer parameters

I am using the PXI-6528 DIO on PXI chassis. This board is an opto-isolated TTL DIO. The card has an on-board Watchdog timer. I have DAQmx Generate - Digital Line Output (PXI-6528) steps in Sequence steps with "reuse hardware" permitted which set lines high or low as needed for commanding solid state relays (SSR). When the project runs, the behavior non-deterministically sets all lines to low when transitioning to the next Sequence step. If I run each DO step independently it works perfectly every time.
To investigate this phenomenon, I did a simple bench check to rule-out SE software errors. I simply patched from the DO port to the DI port on the same card. Then I added a DI Acquire step just after every DO step to electrically read the states. The result is that the DO port really is going low when the SE software is programmed for high or low! It seems to me that the only thing that can override the SE logic is the Watchdog timer.
Reading this NI White paper:
http://www.ni.com/white-paper/14616/en/#toc4
It seems that it is critical to configure the Watchdog timer to achieve stable behavior from the 6528 card. BUT, neither MAX, DAQ Assistant, or SE have an obvious way to configure the Watchdog timer.
QUESTION: Within SE-DAQmx-Generate-Digital Line Output step what are the parameters that control or disable the Watchdog timer for the PXI-6528?

Update:
I have found more information at this URL:
http://zone.ni.com/reference/en-XX/help/370471AC-01/cdaqmxsupp/pci-6528/
This is the C programming reference specific to the PXI-6528. Reviewing the Watchdog timer properties we find that the "Timeout" property can disable the timer with a value of -1. On the DAQmx Assistant GUI for DO, the Advanced Timing tab does have a Timeout property which will accept a value of -1; however, one must set the Generation Mode to N-Samples to activate the Timeout input field. As the 6528 fundamentally cannot generate samples, then we must reset the Generation mode back to 1-Sample (On Demand) with the effect that the Timeout property is greyed out on the GUI - does this signify that the -1 value for Timeout is ignored?

MAX does not detect my PXI-5122 and PXI-6551 cards in a PXI-1045 chassis.

I have been using a PC with MXI-3 to PXI-1045 chassis to develop LabView TestStand code. Things are fine on my development PC. [Software configuration report attached nireport_rich.txt].
I have a 2nd PC set aside to test my deployment packages. I installed a GPIB card and MXI-3 card in my deployment test PC, and loaded a bunch of hardware drivers. [Report attached nireport_depPC_0006.txt]
All the PXI cards are found just fine when my development PC is connected, but when I power up my deployment PC (with MXI-3 connected to the 1045 chassis) -- I can't import the development configuration [exported from development PC] because the deployment PC does not see the PXI-6551 DIO card in slot 6 [PXI6::10::INSTR] and the PXI-5122 card in slot 13 [PXI8::15::INSTR].
I keep reviewing the hardware driver versions installed, and the only small difference that I see at this point is that the deployment PC has a slightly older version of NI-Switch.
Anybody have any ideas of what I can try next? I'm out of ideas.
. . . . hmmm, can't seem to attach more than one file, so here's the software info on the deployment PC
NI Software Information:
CVI Run-Time 7.0.0.395
NI-DAQ 7.3.0f1
NI-DAQmx 7.3.1f0
NI Script Editor 1.1
NI-DMM 2.3.1
     Soft Front Panel 2.3.0
NI-FGEN 2.2.1
     FGEN Soft Front Panel 2.2
NI-488.2 Software 2.30
IVI Compliance Package 2.2 2.2
LabVIEW Run-Time 7.0
Measurement & Automation Explorer 3.1.1.3003
Measurement Studio 6.0
     For Visual Basic
          ActiveX User Interface 7.0.0.344
          ActiveX 3D Graph 7.0.0.344
          ActiveX DataSocket 4.2.2.1
NI-USI 1.0.2
NI-HSDIO 1.2.1.3
NI-HWS 1.2.2.0
NI-PAL Software 1.8.2.0
NI-SCOPE 2.7.0f5
     SCOPE Soft Front Panel 2.1.0
NI Spy 2.2.0.12
NI-SWITCH 2.30.49153
NI-TClk 1.2
TestStand 3.1
NI-VISA 3.2
     visa32.dll 3.2.0.19
     NiVisaServer.exe 3.2.0.19
     NIvisaic.exe 3.2.0.19
LabVIEW Run-Time 7.1

Hello Maggie,
Appreciate your assistance and reply.
The pxisys.ini and pxiesys.ini files are modified by me with referring to
1)PXI System Alliance PXI-2 SW spec,
2)PXI-6 SW spec,
and 3)pxisys.ini pxiesys.ini generated by MAX v5.3.0f0 with NI PXIe-1075 + NI PXIe-8133.
The content in pxisys.ini/pxiesys.ini generated by MAX looks like simple. Consequently, I modified and checked it line by line according to actual hardware of PXES-2590+PXIe-3975. Then, MAX just list devices as described in the first post. I tried to find the root cause but in vain.
Is this minor issue can be related any incorrect tag lines in pxisys.ini or pxiesys.ini I posted?
Is any suggestion tests I can do to troubleshoot root cause?
Looking forward your reply.
Cheers,
KL Tseng

NI PXI 6251 SPI emulation

Hi,
I'd like to use NI PXI 6251 DIO to setup and run an SPI communication using Labview2013. Is it possible, do you have any suggestion?
Thanks!

use the right hardware http://sine.ni.com/nips/cds/view/p/lang/en/nid/202368
Of course it is possible to emulate a SPI interface but it will be "Clunky" low, speed and won't support features like "Clock-Streaching" very well.
Jeff

Pxi-6562 connector

I am using a PXI-6562 LVDS DIO board. I will manufacture a custom cable to connect to the PXI-6562 LVDS DIO card. Can you give me the part number of the mating connector that attaches to the PXI-6562 DIO?
I need a generaric part number or commercial part number for the mating connector so that I can manufacture a custom cable for the PXI-6562 LVDS DIO card.
Thank you,
Roger

Hi Roger,
I think the information you are looking for is here: Where Can I Find Dimensions for the LVDS Infiniband Right-Angle Connector, Part 779157-01.
Regards,
Travis Ann
Customer Education Product Marketing Manager
National Instruments

[HELP] NI MAX Error and Lockup...

I have a NI PXIe 1062Q and NI PXIe 8135. Windows 7 Professional 64-bit installed.
I removed all the NI software using the control panel and then installed NI Developer Suite 2012. As part of the install the following was installed:
NI Developer Suite Core
FPGA Deployment Option (Excluding Xilinx Compilation Tools 10.1)
Automated Test Option
I2C & SPI
NI Serial + VISA
When I start NI MAX it errors with an exception. If I continue it then locks up. All the menus are greyed out! It was working (with the error), but now it locks up completely.
I have attached the dump and log file.
Also in the rack are:
PXI-6509 DIO Card
PXI-7953R + 5734R DAQ + FPGA
CB2-1-PIPE USB controller
PXI-2503 Switch
PXI-4070 DMM
PXI-8430/4 RS-232 Card
Christopher Povey
Senior Test Systems Engineer for BAE Systems.
Solved!
Go to Solution.
Attachments:
20150203_090112-NIMax-0000134C.log ‏9 KB
20150203_090112-NIMax-0000134C.log ‏9 KB
20150203_090112-NIMax-0000134C.zip ‏26 KB

I worked it out in the end.
The PXI chassis came pre-installed with a few cards we had ordered. I think NI installed the drivers for these cards (probably later than 2012). I then removed all the NI software from the Control Panel and installed NI Developer Suite 2012. I think the drivers clashed. I did a full system restore from the image on the drive and re-installed NI Developer Suite 2012 and it was fine.
Christopher Povey
Senior Test Systems Engineer for BAE Systems.

RT Remote Front Panel issues.

I'll start with my setup:
2 PXI-1042 chassis connected via fiber-optic using NI PXI-8336 (MXI-4) cards.
Chassis 1: PXI-8108 embedded controller running LabVIEW Real-time OS (2010), PXI-6528 DIO, PXI-8336 MXI-4.
Chassis 2: MXI-4 in slot 1, 4 PXI-8334 DMM, PXI-6528 DIO, PXI-6281 M-series DAQ.
The real-time executable monitors analog and digital inputs and DMM measurements, displays the values using numeric and boolean indicators, generates alarms and allows users to acknowledge alarms via a Remote Front Panel. The code has a custom error handler that traps errors and stores them in a global array. This allows the code to display them on a console and allows the user to acknowledge and clear errors, and scroll through multiple error messages. We used property nodes sparingly.
The system is monitored by two laptops with the correct run-time engine installed (both laptops have the LabVIEW development suite). Under normal conditions, one laptop keeps control of the Remote Front Panel at all times.
The problem:
The system was running flawlessly for 3 months of continuous use. Then, for no apparent reason, the indicators that display measurements from "Chassis 2" (specifically the DAQ) stopped updating.
If the user refreshed the browser, the Remote Front Panel client would reconnect to the RT Web Server and get updated values, but they were always static. Essentially, refreshing the browser took a "snapshot" of the data, but the indicators did not update continuously as before. At the same time, DIO inputs to "Chassis 1" responded appropriately to changes in state.
Refreshing the browser on one laptop would update the values for that laptop only, and the other laptop could be refreshed independently and have different values displayed, but both laptop's indicators were static. During this time, the DMM measured inputs were not changing and the "Chassis 2" DIO inputs did not change state (i.e., we could not perturb the inputs), so we could not determine if those indications were affected.
Also, the error console did not respond to user input until the browser was refreshed and the client reconnected to the target.
We know the RT application is running on the target because there is code that monitors the status of the loops by changing state every loop iteration and displays the status to the user.
Our short-term solution was to reboot the RT controller by powering down both chassis, starting "Chassis 2", then starting "Chassis 1". It's been running for a few days now without incident.
Since the data displayed after refresh was accurate based on comparison to gages in the system, we do not suspect a measurement problem.
Possible culprits:
1. The RT Web Server has malfunctioned in some way (memory problems, synchronization, etc.)
2. The MXI-4 link.
3. Cosmic rays? Sunspots? Nearby radar stations? Neighboring HAM radio operators (with massive amplifiers)?
If anyone has any ideas, they are welcome. We are concerned that this will be an ongoing problem, if only every few months or so.

Could you clarify a bit on how the PXI-6528 was acting while you were seeing these problems? Does this card have values display on the Remote Front Panel, and if so were they still updating properly? I believe you were saying that, but I wanted to be sure because that makes a big difference.
If everything became static, including the DIO card, at the same time, then I'd say see if your browser updated, or something in your network settings was changed without you noticing. Perhaps an update ran and reset some of your firewall settings, or an Internet Explorer update changed something that required a reboot.
If just the outputs of chassis 2 were the problem, and the DIO card values on your remote front panel still worked well, then it is most likely a problem with your MXI-4 cards or your fiber optic cable that cause the change in behavior.
Miles G.
National Instruments
Applications Engineer

High Impedance Measurement

Hello,
I am interested in measuring the high impedance value of a PXI-6533 DIO.
I need to make sure that no problems occur when connected and not
used in certain parts of the test.
Ernest

Ernest
I have
the output of a digital board connected to the 6533. Other parts of the board
are connected
to a DMM
and 6120 and other cards. In past tests I tried to set the lines on the 6533 to
the high
impedance
mode but the measurements on the other cards would only work when the 6533
was
disconnected. I want to make sure that the impedance is indeed high and would
like to
measure
the value.
Ernest

How can I communicate PXI-6509 by Static DIO Register-Level Programming?

- How can I communicate PXI-6509 by Static DIO Register-Level Programming?
PXI-6509 physically Port0 is connected to Port1.
For checking all connections are correct for this case so I have used DAQmx Test Panel. Just in case everything is ok.
  In this case I interested in to communicate the PXI6509 by Register-Level Programming.
I have tried to use Open VISA Test Panel for sending and reading data (in MAX explorer) and
use NI-Spy for checking communication data.
The first step I configured Port0 to Outputs state and Port1 to Inputs state.
The second step I setup Port0 to 0xAA.
  The third step I read back Port1 and expected data will be 0xAA but just only 0x0. Why???
   1              ViOut8(0x03D83318, 10, 0x00000041, 1)

Hello!
We don't do support on register-level programming but the problem you are experiencing might be due to tri-state on the ports?
Please check this manual that covers register programming of the device you are using:
http://digital.ni.com/manuals.nsf/websearch/47300C3471742AD0862570AE005E0AD1
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal

Regarding NI PXI-6602 - How to route PFI_33 to a grounded DIO Line.

The PXI-6602 card with the TIO chip seems to be very robust on counter and DIO pin assignments and routing, but I have found that counter 1 has a pin (PFI_33 -AUX IN (UP/DOWN) ) that has been troublesome. I need to either route this pin to another pin such as a DIO pin set as an output and pulled LOW or be able to manipulate the pin to a low state when I setup counter 1. This is to ensure that noise is kept to a minimum due to the PXI-6602 being cabled to a board with a PLD on it. Any solutions on how to tie PFI_33 low?
-Tim

B Spears,
Looks like I'm heading down that path... We were looking to do it in software, but nothing has come to light. Interesting enough, DAQmx has a good sub-vi (DAQmx Connect Terminals.vi) but I am dealing with code back from LABView 5 days utilizing Traditional DAQ. Try writing a snipet utilizing both "Write to DIO.vi" and "DAQmx Connect Terminals.vi" and watch the error codes fly.
One option NI has offered was to re-write the DIO tasking in DAQmx instead of traditional... this maybe an option... but, wow! That's a lot of code.
Thanks for the reply B Spears,
-Tim

PXI 652x DIO Readback?

Similar Messages

Maybe you are looking for