Pxi 6528

Dear all
I am using PXI-6528 for my project.In max card passes the self test,pin 49,50 shows 5 v,but when i write digital port high that time crossponding pins shows 0v only.I want to know how to configure power on states in this card like (0- 60VDC).
Thanks
Venkateswaran V
Automation Engr
Pricol Ltd

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?

Similar Messages

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?

Issue with PXI 6528 test panels

We are using a real time 8106 controller in a PXI rack with some 6528 digital I/O boards. We have loaded all necessary drivers to the system and can see the cards in Max but are unable to run Test panels as the options to set the port bit states are greyed out. Has anyone had experience of this ?
Thanks
Peter Heseltine

Hi Peter,
The NI PCI/PXI-6528 device provides 24 isolated input channels and 24 isolated output channels that are not bidirectional. Are you getting the same behavior on ports 3-5.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

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

NI PXI-6528 programming

I want to do a loopback test for a NI PXI-6528. It has 24 isolated input channels and 24 isolated output channels. I have a fixture that allows me to wrap each input pin to each output pin. So, bit 0 of Port3 (output) is wired to bit 0 of Port 0 (input). Ports 3,4,5 are outputs and Ports 0,1,2 are inputs. I'd like to basically walk a one down the 24 output bits and read each one individually at it's respective input. I setup two DAQmx Assistants (two tasks?) such that each task contains the individual channels (24 bits) of the input/output. The code I've attached is nowhere near complete, but merely a snippet of what I'd like to do. Ultimately, I'd like to automate this test, but initially, I'd like a control, say a 24 value boolean array that corresponds to each output bit, and a similar one for the input bits. I'd like to set a bit (or several) and say 'write' and see the respective Input booleans light up.
Can someone shed some light on how I can have bit level control of the I/O?
Attachments:
PXI_Out_2.JPG ‏101 KB
48Ch_Opto_Iso_IO.vi ‏111 KB
PXI_Out_1.JPG ‏54 KB

I had the DAQmx assistant generate code for both the input & output tasks. I then added some of the code you suggested in the previous message. Any idea why it would think the channel number in data vs task is different? I don't actually compare the output and what's read at the input yet, primarily because I'm not sure how. In general, I'm not sure how to (outside of a looping construct) specify one particular output and one particular input.
Attachments:
DAQmx_1.PNG ‏60 KB
DAQmx_2.PNG ‏29 KB

Pxi 6528 board status

Hi,
i want to develop my own linux driver for PXI 6528. any one can say me how i can read board status, means register address of board status register?
Thanks

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?

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?

Compatibilité applications PCI transférées vers PXI

Bonjour,
Actuellement mon logiciel de pilotage d'entrée/sortie utilise des cartes PCI-6528 et PCI-GPIB. Mon but est d'effectuer un portage de ce logiciel sur rack PXI avec cartes PXI-6528 et PXI-GPIB. Ma question est donc la suivante :
Y aura-t-il des retouches à apporter au logiciel (adressage des cartes ?) ? En gros le soft est-il indépendant du hard ?
Merci d'avance
Résolu !
Accéder à la solution.

Bonjour,
Votre controleur PXI est sous Windows ou sous LabVIEW RT?
Si votre contrôleur tourne sous Windows, il n' y a pas de problème le portage est très rapide comme vous l'a indiqué Ludovic.
Mais si votre contrôleur tourne sous LabVIEW RT, alors il vous faudra adapter votre code et les modifications peuvent être importantes.
Cordialement,
Yann

Labview RT 14.0 Scheduler Assert%3A __1276 Scheduler Assertion Error%3A 80000004

We have a multithreaded CVI app (~20 threads) running on a PXIe-8135 (4 CPUs). The application never gets done starting all the threads before blue-screening with the following error:
Scheduler Asser: __1276
Scheduler Assertion Error: 80000004
Interrupt Disabled. Scheduler Enabled. ....
More details:
System
Chassis 1 PXIe-1085:
PXIe-8135 Controller
PXI-6704 (7 of them), initialize properly, thread runs successfully until blue screen
PXI-8431/8 (8 of these, total of 64 RS422 channels, about 40 being used currently for test), it is during the starting of these threads (one for each board) that it blue screens
PXIe-8374 (for using Chassis 2 as an extension of Chassis 1)
Chassis 2 PXIe-1075:
PXI-8370 (connected to PXIe-8374)
PXI-6528 (1) threads run fine
PXI-6529 (4) threads run fine
NI-8234 (4) not used currently
The scheduler error happens at different times, but always during the starting of the RS422 threads. Can anybody give a hint as to why the Scheduler Assertion Error occurs, and particularly this specific error?

Hi,
I have a couple of questions for you.
1) Has this application ever worked?
2) Can you attempt to replicate this issue with less RS422 channels? Basically, is there a maximum number of RS422 channels where the error is received, or if you had only 1 channel being used, would the error still happen?
3) Do you have another PXIe controller that you can try?
4) Did anything change in your system that would have caused the error?
Kevin S
Applications Engineer
National Instruments

A problem for the picture control .

Hello,
There is such a question :
When loading a picture into a picture indicator , I can pop up a dialog and have the user to assign some property values for the picture , the application then saves the values to a file . I believe I can recover graphics information through reading the file , but how to create such a mechanism which can assign or associate a data type (e.g. a Boolean value) as the user specified to a picture ? Of course , in edit status , a control can be customized and replaced by a picture sign , but I need to realize this when the application is running . Thanks .
David

Here is a VI-in-progress drawig some components of our system. I will post shape subVI's in subsequent replies.
This VI simply generates random numbers and colors shapes
accordingly. Therefore, separate shapes in the same picture
indicator are individual indicators. What I am aiming to do is
use event structures to make individual shapes in the single picture
indicator controls as well as indicators (i.e. On mouse over circle,
open "plotpressure.vi", on mouse click on diamond, send 5 volts to
channel AO 21, PXI 6528).
I have read some threads indicating the need for tedious locating of
different regions in the picture indicator for event programming, but I
have not gotten that far yet. I am still designing a picture
indicator with individual indicators.
Brad
The main VI is the "Multiple Shapes Example.vi"
It calls "Draw LE ESA.vi" and "(XY)r to 4s square.vi" among others. I will post the others subsequently.
Attachments:
(XY) r to 4s square.vi ‏10 KB
Multiple Shape Example.vi ‏23 KB
Draw LE ESA.vi ‏59 KB

Input and output on same device, producer/consumer structure

Hello interested people,
I have a question about using the same device for both digital inputs
and outputs. I have written a simple program of one while loop
that continuously polls the device, processes, and requests. I
have addressed the device using two DAQmx Asst. and I have attached
them with their error in/out cluster terminals to provide data flow and
eliminate the chance of addressing the devices at the same time (which
produces an error). Now I want to change this program structure
to a producer/consumer loop foundation with state machine.
In this design, I will have the DI in the producer loop and the DO in
the consumer loop, under one of the states. I can't simply
connect the error in/out ports in this configuration, so my question is
how to avoid the error caused by addressing the same device
simultaneously with two different tasks (input and output)? I
have attached two VI's, the "One Loop" vi is the original configuration
(simplified), and the Producer-Consumer vi is a NONSENSICAL program
that simply represents the desired configuration. (I don't need
any comments on the programming of this vi, it is only an example for
illustration of the problem).
I am thinking about bundling the input data and the error cluster, both
from the PXI 6528 DI, into one cluster, queueing that up, and
unbundling the de-queued elements for some kind of data flow between
the producer loop and the "Request" state of the consumer loop.
Is this the right approach, or am I barking up the wrong tree?
Thanks
Attachments:
One Loop DO DI.vi ‏102 KB
Producer-Consumer DI-DO.vi ‏106 KB

Hello,
It sounds to me like you really have two modes:
1. user interface actions determine execution
2. user interface is locked, and execution is automated.
I think it would make sense to use the producer consumer for an architecture. Basically you would do the following:
1. program the producer to handle the user interface as you normally would.
2. provide one additional event case in the producer which would be your "automated handling" case. In that case, you could put a state machine which could run until whatever conditions were met to put your program back in "user interface mode".
Keep in mind that you can use custom USER EVENTS to programmatically generate events ie. you can trigger the start of your "automated handling" form anywhere in your code at virtually any time.
I think this would allow you to take advantage of the producer consumer architecture in its intended spirit, while integrating an automated routine.
I hope this helps!
Best Regards,
JLS
Best,
JLS
Sixclear

7,1 was a dream: Media shortcuts/front panel issues

Hey
I have a Dell Inspiron 6400. On the front it have this Media Shortcuts / Frontpanel
In iTunes 7.1 they did work. Like, I could minimize iTunes, use other programs and still I could change songs and stuff. But after all the updates on iTunes, this ability is gone. It's only with Windows Media Player it'll work.
Anyone have an idea about how I can fix this?
(or that Apple could fix this and keep it in their iTunes in the future)
Message was edited by: VonWeibye

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

Failure niimacq

Bonjour,
j'ai un testeur qui fonctionne avec TestStand,
LabWindows pour les dll, LabViewpour les fichiers VI, Vision Builder,
NI-Switch, NI-Motion, DATASOCKET, NI-CAN, NI-DAQ, NI-DMM avec un chassis
PXI comportant :
- 1 carte PXI7350
- 1 carte PXI GPIB
3 carte PXI 6528
- 1 carte PXI 8461
- 1 carte
NITB 2706
- 1 carte NITB 2632
de temps en temps il
reste planté et perd la com avec l'automate (par TCP IP com XWAY)
quand
je le relance il plante avec la com GPIB, je dois éteindre le PC,
redémarrer le chassis et démarrer le PC pour relancer l'application.
Aucun
message a part dans l' Observateur d'évènements application le message
suivant :
[nipalu] Warning:
.\source\lib\windows\loadKern.cpp:358 - libKernelDriverLoad: Failure
loading driver using new packaging:niimaqk, status:-50251
J'ai
réinstaller tous les driver et application sur un autre PC et pareil...
connaissez-vous
ce message d'erreur ?

Bonjour lolo73,
Quelle est votre version des drivers IMAQ, IMAQdx ? (information disponoble dans Measuremant and Automation Explorer : Programmes » National Instruments » Measurement and Automation Explorer).
Quelle est votre caméra ?
Quelle est votre matériel pour effectuer une acquisition d'image ? Ethernet ? Carte PXI spécifique (NI ou non) ?
Quelles sont les versions de vos logiciels ? TestStand, CVI, LabVIEW, et Vision Builder.
Cordialement,

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

How to switch two Digital IO in a DAQmx as a output

Hello, i need to switch two Digital IO in a DAQmx (Output in a PXI-6528).
LabVIEW launch next error:
Error -200014 occurred at DAQmx Create Channel (DO-Digital Output).vi
Possible reason(s):
Terminal cannot appear multiple times within a single digital input or output task.
Physical Channel Name: port3/line0
Virtual Channel Name: PXI1Slot3/port3/line0
Task Name: MyDigitalOutTask

Hi Andreu,
the best way to analyze your question is to post a short example on the programming language that you´re using in order to investigate a little bit.
Moreover, under NI Find Examples of LabVIEW (if you programm with LabVIEW), you can find several examples how you can programm your digital port about (you can type "Write" or "digital" under Search tab).
One example would be: "Write Dig Chan-Int Clk-Dig Start.vi".
Regards
Diego M.

Pxi 6528

Similar Messages

Maybe you are looking for