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?

Similar Messages

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 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?

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

Controlling PXI-8110 watchdog

We are running a resource intensive application on the PXI-8110 and during the operation, the 8110 reboots. I believe this may be a built-in watchdog function? Is there any way to control this? Thanks.

Hi Wirehead,
You're right that the 8110 includes an onboard watchdog timer device, but this device won't reboot the system unless you explicitly arm it to do so. In other words, the timer must be enabled by software (using LabVIEW VIs), otherwise it cannot restart the system.
What OS are you using, and what is your application doing when it restarts? Does it always restart at the same point of execution?
Thanks,
Eric G.
National Instruments R&D

Video Output for PXI Embedded Real-Time Controller ?

I plan to purchase a PXI Embedded Real-Time Controller for security monitoring.
Is it possible to use the video output of a PXI Controller running RTOS to display messages from a LabVIEW RT application ? According to the documentation, it seems that the use of the video output is only possible for PXI Controllers running Windows XP.
Does it exist a specific application to do this with LabVIEW RT ?
Thanx.
H.L.
Solved!
Go to Solution.

Hi Yann,
The situation seems a bit confusing as in the link you've given above using the local monitor from a pxi labview rt system as the HMI without a pc attached, two messages (here and here) say that it is possible to display an image on the video output of a PXI RT controller using a function of the NI-IMAQ librarey (namely, the IMAQ RT Video Out VI) !
I have the NI-IMAQ library but no PXI controller to test if this solution should work or not
Does anyone have the answer ?
Thanx,
H.L.

Calling procedures multiple times passing rum time parameters

hii,
i ve this small prob with my procedure..my proc is
CREATE or replace PROCEDURE sad(star_val number,dept_id number) IS
BEGIN
update dept set star=star_val where department_id=dept_id;
END;
and i call this proc using a loop and give the values at runtime..
declare
v_count number(3);
begin
v_count := 4;
loop
sad(&value,&dept);
v_count := v_count-1;
exit when v_count=0;
end loop;
end;
this procedure runs only once with out looping 3 times..can anybody help me out..

.... passing rum time parameters ......
programming in the caribbeans must be wonderful
anyway : how do you know it ran only once ?
most probably it ran 5 times doing the same update defined by &value,&dept
ahh, now I get it, you believe you'll be asked again and again to enter values for &value,&dept .
Sorry, no can do, PLSQL is not interactive
further reading at http://tahiti.oracle.com

X2200 iLom and Watchdog timer...

I have setup our x2200 and have the iLom working great for most things.
I have two specific problems going on with it though....
First, sometimes the iLom just stops responding, I can't SSH, use the WebGUI or anything. I'm using the same mgmt. port for the global zones IP, which I can still log into. Once I log into the domain, I can reboot the server, or power it down and then the iLom starts responding again. Any ideas?
Second issue is that if I turn on the watchdog timer in the BIOS it will reset or power cycle (depending on which setting I setup) once the timer expires, even if booted into the OS. This is very disturbing, because I can't use the watchdog unless I want to reboot every five minutes. :/
Now I am installing the minimal Solaris 10 SUNWreq cluster, but I'm adding a number of packages back into the jumpstart session, including TCPWrappers. Is there a specific package that needs to be installed as part of the Solaris base install in order for the Watchdog to determine if the OS is up and running or should I open a hardware trouble ticket on the new server?
Thanks!
Information
Error in the ILOM Error Log:
OS Load Watchdog timeout cause STR_POWER_CYCLE1
Server x2200 M2
ILOM Version
BMC Version : 1.20
BIOS Version : S39_3A10
Description BMC Board Information
Device ID 5
Device Revision 0
Firmware Revision 1.20
IPMI Revision 2.0

Did you ever figure this out? I have been having the same problem since receiving my x2200 M2 a couple of months ago. I'm running the latest OpenSolaris and the watchdog timer will reboot continuously until it seems to give up and then just stops rebooting. I have a feeling it also disables the watchdog timer at that point.
Another frightening thing this server does is leave the power off, even when bios is configured to power on after a power failure!

How to start Flash Media Encoder 3.2 from Flex application with run time parameters?

Hello ,
I'm developing the application to stream High Quality video.While streming by default camera/microphone settings the qulaity of streaming is not upto my expected level.I want to stream through Flash Media Encoder.My aim is the user login to the application.Video/audio qulaity details are retrived from shared object stored in the client machine.The login user name only gathered at run time & it will be the streaming profile name to Encoder.Once the the Encoder started the outgoing video will be come into screen to client.Please guide me How to start Flash Media Encoder 3.2 from Flex application with run time parameters(User name as streaming name) without manually start the FME?
Thanks in advance.
Regards
Sasharyuva

Hi MarcSaphiron,
Could you please send the samples?It will be much helpful to complete my
job within the deadline.
Thanks in advance.
Regards,
Sasharyuva

Why do I get Error-22011 when I try to run a HW Watchdog Timer vi?

I am trying to use the HW watchdog timer vi's on the RT functions palette (Watchdog Configure.vi and Watchdog Clear.vi). Error-22011 is generated when Watchdog Open.vi is called (a subvi to Watchdog Configure.vi).
"Explain Error" gives this result:
"NI-Watchdog: The watchdog hardware you requested is already in use, or has been permanently locked."
I get this error every time I execute Watchdog Configure.vi even if the host computer and network controller have just been rebooted. There is no place to specify or lock/unlock the hardware (that I can find). I'm using Windows XP, LV8.5, and the FP2010 controller.
Thanks in advance for any help.
pmac

Yes, I have NI-Watchdog 2.1.5 installed on my FP.
In fact, I figured out what the Error-22011 problem was all about and I'm almost too embarrassed to say. I had Watchdog Configure.vi inside a while loop... so only the first iteration would be error free and for every iteration after that, the hardware would be "already in use". Hence, Error-22011.
I've made it over that hurdle, but I'm still having problems.
Now,I have both Watchdog Configure.vi and Watchdog Clear.vi outside the while loop and I put Watchdog Whack.vi inside the while loop (mainly to monitor the watchdog status output). I also wired the occurrence output of Watchdog Configure.vi to a second while loop in which there is a wait for occurrence.vi wired to a boolean indicator.
If I disconnect the ethernet cable while this vi is running, the program pauses and I get a Labview generated message informing me of a lost connection however, there is no occurrence generated and the watchdog stays in "running" status.
Apparently, I've misunderstood how to implement the watchdog vi's and I'll need someone to set me straight.
Is there anyone who can help?
Thanks,
pmac

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

Reason: watchdog timer reset.

Just recently, like the last 2 weeks I have had my AIR-LAP1042N-A-K9 and AIR-LAP1142N-A-K9 AP's suddenly reboot. Primary Software Version 7.4.100.0. I am using a 2504 controller,AIR-CT2504-K9. Looking in the traps I see:
106
Tue Mar 17 10:53:00 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
107
Tue Mar 17 10:53:00 2015
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
108
Tue Mar 17 10:53:00 2015
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
109
Tue Mar 17 10:52:58 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
110
Tue Mar 17 10:52:58 2015
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
111
Tue Mar 17 10:52:58 2015
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
112
Tue Mar 17 10:52:58 2015
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Radio interface reset. Status:NA
113
Tue Mar 17 10:52:56 2015
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
114
Tue Mar 17 10:52:56 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:18:33:9d:b6:f5:10 Cause=Radio interface reset. Status:NA
115
Tue Mar 17 10:52:55 2015
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Unknown Reset Status:NA
116
Tue Mar 17 10:52:55 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:b4:e9:b0:d4:59:90 Cause=Unknown Reset Status:NA
117
Tue Mar 17 10:52:55 2015
AP 'ESU13_DL_Room', MAC: b4:e9:b0:d4:59:90 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 01 m 40 s . Reason: watchdog timer reset.
118
Tue Mar 17 10:52:53 2015
AP 'ESU13_Conf_rooms_BC', MAC: 18:33:9d:b6:f5:10 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 01 m 42 s . Reason: watchdog timer reset.
And
167
Tue Mar 17 10:49:29 2015
AP 'ESU13_Administration', MAC: 18:33:9d:b7:09:c0 disassociated previously due to Link Failure. Uptime: 0 days, 20 h 18 m 52 s . Reason: Capwap Echo request.
168
Tue Mar 17 10:49:29 2015
AP 'ESU13_Basement', MAC: 18:33:9d:b7:28:a0 disassociated previously due to Link Failure. Uptime: 7 days, 23 h 19 m 29 s . Reason: Capwap WTP Event request.
169
Tue Mar 17 10:49:29 2015
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:18:33:9d:d2:4a:00 Cause=Unknown Reset Status:NA
170
Tue Mar 17 10:49:28 2015
AP 'ESU13_Meridian', MAC: 18:33:9d:d2:4a:00 disassociated previously due to Link Failure. Uptime: 14 days, 13 h 38 m 32 s . Reason: Capwap Echo request.
171
Tue Mar 17 10:49:28 2015
AP 'ESU13_Soar', MAC: 18:33:9d:d2:37:20 disassociated previously due to Link Failure. Uptime: 137 days, 20 h 30 m 58 s . Reason: Capwap WTP Event request.
I have read that the watchdog issue is related to version 7.4. Do I need to go back to 7.3 or is there a newer version that addresses this?
TIA,
Eric

Hi Eric,
Upgrade to 7.6.130.0 as 7.4.100.0 is initial release of 7.4.x & had lots of bugs.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn76mr03.html
HTH
Rasika
*** Pls rate all useful responses ****

WANTED: NI PXI-6602 counter/timer

I'm looking to buy a used NI PXI-6602 counter/timer board. Got one?

"Zvezdana S." wrote in message
news:[email protected]..
> Hugh,
> To possibly obtain an used board from National Instruments, you should
> contact your regional Internal Sales Representative (ISR) for possible
> used boards. If you are not sure who your ISR is, generate a service
> request at:
I never knew NI had an SRQ line we could pull.
Craig Graham
Physicist/Labview Programmer
Lancaster University, UK

Nexcom SBC watchdog timer

Hi All,
Has anybody had any success in communicating with the watchdog timer (WDT) built into industrial single board computers?
I am using a Nexcom Peak 777 which seems to have a fairly standard WDT. Apparently it just needs a configuration written to a control register on 0xF2, so I have done this using the Port Out VI (WinXP), but it does not seem to be doing anything. I would expect if I had the config set up correctly after the specified timeout period the PC would reset and it does not.
There is no control at all of the WDT in the BIOS.
Any ideas?
Thanks
nrp
CLA

Hi,
Looking at page 33 of the manual for the 777 it appears you have to first set this register before applying:
MOV al, 0h //set to 0
AND al, 10000000b //Set timeout value (1-255)
OR al, 10000000b //activate this setting
MOV dx, F2h //set the above to the register
Are you doing these to setup the board?
Kind Regards,
Applications Engineer

PXI-6528 Watchdog Timer parameters

Similar Messages

Maybe you are looking for