Hardware clock in PCI-6052E

Is there any indication either it uses windows clock or DAQ STC built in timer.
my question is how we know that a normal
programme in labview is using which clock???

Dear Haider,
Since you are using AI Start, your analog input is hardware timed. This means that your data is read from the buffer at regular times. Everything else in your program is software timed. I know this because the software is doing the checking for the condition and the digital lines of the PCI-6052E can be output with hardware timing, but it involves using the an analog clock. For more information on this look at the examples in the Example Finder (LabVIEW help menu>>Find Examples) under Browse Hardware Input and Output>>Traditional DAQ>>Digital Input and Output>>E Series.
Have a great day!
Marni S.

Similar Messages

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

Hardware clocking error # 200550, PCI-5122

The PCI-5122 does not pass the self test. It
says "error 200550 occured. Possible reason: Hardware clocking error
occured". I'm not using any external clock and my PC is 3Ghz pentium
with Windows XP and Labview 7.0. Uninstall/install of NI_Scope and NI DAQmx didn't
help.
By the way, if I put PCI-5911 card instead of PCI-5122 into the same PCI slot, it works fine.

Hello Danraz,
It sounds like you have followed all of the recommended steps for troubleshooting for this type of error. As one additional step you could test it in another PC if you have one available. Unfortunately, you will most likely need to send your board in for repair. Please contact support to make arrangements. You will be asked to provide them the serial number of your board in order to have the board repaired, and they may also verify your troubleshooting steps at this time.
Regards,
Jennifer O.
Product Support Engineer - High Speed Digitizers

Minimum timeout for read operation in PCI-6052E.

Hi,
I am running an application at 600Hz where I must read data from a deice using the PCI-6052E. Running at 600Hz, i.e Ts=1/600 second, my read timeout in the DAQmxReadAnalogF64 function must be < Ts. Although, the application starts fine after few reading cycles, the application crashes with a DAQmx error:
"DAQmx Error: Measurements: Specified operation did not complete, because the specified timeout expired.".
knowing that the PCI-6052E can operate at 1Khz rate, taht is T=0.001, I find it wired that it is crashing for timeout I am using Tout=0.7*Ts whic is > than T.
What is the minimum timeout required?
Thanks.
Elias
"A man can succeed at almost anything for which he has unlimited enthusiasm."

Hi,
Timeout specifies the amount of time in seconds to wait for
samples to become available. If the time elapses, the VI returns an error and
any samples read before the timeout elapsed. The default timeout is 10 seconds.
If you set timeout to -1, the VI waits indefinitely. If you set timeout to 0,
the VI tries once to read the requested samples and returns an error if it is
unable to.
By available we refer to the data that has been acquire by
the card and placed into the buffer. You are doing a on sample at a time and
that you are not using the onboard clock. Since you are not using the onboard
clock you don’t have determinism on the rate at which you acquire the samples. “I
think by default the 6052E clock is 1KHz”, incorrect if you select your timing
as on “sample on demand” the rate is controlled by your “timed loop” but since
you are not in a Real Time OS you don’t control the rate of the loop, at least
at very high rates, you may run the first couple of iteration at one speed, then something happens on your PC and you CPU load increases, changing the rate of the while loop.
You have two options to set the rate you can do a software
timed operation (i.e. like you are doing right now), but it will be depended on
your OS and your CPU load or you can do a hardware acquisition where an onboard
clock controls the rate of the acquisition.
“I do not expect this to happen especially that the
PCI-6052E device used in doing the reading operation can run up to 1 KHz. I am
not sure what the problem is.” The problem here is that is not the 6025e not
been able to keep up is your computer. Look at the examples in: C:\Documents
and Settings\All Users\Documents\National Instruments\NI-DAQ\Examples\DAQmx
ANSI C\Analog In\Measure Voltage\ and let me know if they help.
You can post your code and I will lok at it if you want
I hope it helps
Jaime Hoffiz
National Instruments
Product Expert
Digital Multimeters and LCR Meters

PCI-6052E, C-file Programming, DAQ_Rate

I am trying to write a simple c-file to collect some data with my PCI-6052E
Card. The card should be able to handle a sample rate of 333kHz, but I am
finding even if I ask for all sixteen channels at 10KHz using the DAQ_Rate
function, I get an error with the time on SCAN_Start.
The folloing code snip-it generates the error:
<< Snip it>>
f64 dSampRate = 10000.0;
f64 dScanRate = 10000.0;
i16 iUnits = 0;
iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
iScanTB, uScanInt);
printf(" \tiSampTB =%d\n",iSampTB);
printf(" \tuSampInt =%d\n",uSampInt);
printf(" \tiScanTB =%d\n",iScanTB);
printf(" \tuScanInt =%d\n",uSscanInt);
<< Output >>
iSampTB = 1
uSampInt = 100
iScanTB = 1
uSscanInt = 100
Error: -10092
Some devices require a time gap between the last sample in a scan and the
start of the next scan. The scan interval you have specified does not
provide a large enough gap fo rthe board. See your documentation for an
explanation.
But if I use the following code I do not get an error:
<< Snip it>>
f64 dSampRate = 10000.0;
f64 dScanRate = 10000.0;
i16 iUnits = 0;
iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
iScanTB, 0);
printf(" \tiSampTB =%d\n",iSampTB);
printf(" \tuSampInt =%d\n",uSampInt);
printf(" \tiScanTB =%d\n",iScanTB);
printf(" \tuScanInt =%d\n",uSscanInt);
Could anyone point me in the correct direction?
Please reply directly to
tgaudett@n
mr.mgh.harvard.edu
Thanks in advance,
Tom

Thomas:
The second case works because you are disabling the scan clock, thus making
the acquisition "round robin" based on the sample clock.
If you want to make the first case work with 16 channels, I suggest you
change the dScanRate to this:
> f64 dSampRate = 10000.0;
> f64 dScanRate = 10000.0 /(16+1);
The +1 is just to offer a buffer time.
However, this means that your effective sample rate per channel (aka
dScanRate) is now 10000/17. Is that ok?
If you want the effective sample rate per channel (dScanRate) to be 10kHz,
then you need to bump up dSampRate to 10000 * 16 (=160000, which is
achievable on this device) or greater so that the A/D converter has enough
time to go thru all the 16 channels and still make the dScanRate.
I hope this helps.
| Ken Sadahiro ([email protected])
| Sr. Software Engineer, User Advocate
| Systems & Architectures: Applications Group
+----+-------------------------------------------
| National Instruments Corporation
| 11500-A North MoPac Expressway
| Austin, Texas 78759-3504 USA
| Tel: +1.512.683.8806
| Fax: +1.512.683.8641
| URL: http://www.ni.com/
Thomas Gaudette wrote in message
news:[email protected]...
> I am trying to write a simple c-file to collect some data with my
PCI-6052E
> Card. The card should be able to handle a sample rate of 333kHz, but I am
> finding even if I ask for all sixteen channels at 10KHz using the DAQ_Rate
> function, I get an error with the time on SCAN_Start.
>
> The folloing code snip-it generates the error:
> << Snip it>>
> f64 dSampRate = 10000.0;
> f64 dScanRate = 10000.0;
> i16 iUnits = 0;
>
> iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
> iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
>
> iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
> iScanTB, uScanInt);
>
> printf(" \tiSampTB =%d\n",iSampTB);
> printf(" \tuSampInt =%d\n",uSampInt);
> printf(" \tiScanTB =%d\n",iScanTB);
> printf(" \tuScanInt =%d\n",uSscanInt);
>
> << Output >>
>
> iSampTB = 1
> uSampInt = 100
> iScanTB = 1
> uSscanInt = 100
>
> Error: -10092
> Some devices require a time gap between the last sample in a scan and the
> start of the next scan. The scan interval you have specified does not
> provide a large enough gap fo rthe board. See your documentation for an
> explanation.
>
> But if I use the following code I do not get an error:
> << Snip it>>
> f64 dSampRate = 10000.0;
> f64 dScanRate = 10000.0;
> i16 iUnits = 0;
>
> iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
> iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
>
> iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
> iScanTB, 0);
>
> printf(" \tiSampTB =%d\n",iSampTB);
> printf(" \tuSampInt =%d\n",uSampInt);
> printf(" \tiScanTB =%d\n",iScanTB);
> printf(" \tuScanInt =%d\n",uSscanInt);
>
>
> Could anyone point me in the correct direction?
> Please reply directly to
> [email protected]
>
>
> Thanks in advance,
>
> Tom
>
>

PCI-6052E resource test fails at startup

Hello,
I am using a PCI-6052E board on an XP machine. The driver is 1.8.2.f0 and MAX version is 3.1.0.3021.
Every time I boot the system, the resource test in MAX fails: the DMA resources do not appear. The board must be reinitialized manually in MAX or through the DAQmxResetDevice function in any program. This works always well and the board can then be used properly.
I would appreciate very much any hint on how to have my board fully ready at startup.
Thanks a lot.
Pascal.

Hello PascalP,
I have first some questions :
What do you mean when you say : "The driver is 1.8.2.f0 "?
Do you receive code error? If yes, can you please send it?
Please do the following:
1) When you boot your PC, launch Measurement and Automation Explorer (MAX). Under devices and interfaces -> Traditional NI-DAQ Devices, right-click on your PCI-6052 and select Properties. Note how many DMA channels are assigned to your board (may have up to 3 channels). Click Test Resources. If the device fails, please continue with (2); otherwise, open up a Test Panel and verify that it works. Then close out of MAX and try running the examples that uses the device to see if you still have the error. If you still see the error, please let me know.
2) The device is not installed properly. Shutdown the computer, remove the card and reboot. Power down again, add the card, and power up the computer. If it still fails in MAX, continue to 3.
3) Try switching PCI slots. You may also need to uninstall and reinstall the driver. Be sure to remove the hardware anytime you remove the driver.
4) Try installing the driver and then adding the card on a different computer.
If after all of this you still have trouble, please let me know what has failed and what operating system you are using and give me more information about you PC.
Hope this helps.
Sanaa TAZI
National Instruments France
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

Hardware clock and system clock don't match

hello. i recently upgraded to kde 4.7, and i don't know if it's the culprit or not, but my system clock is now ahead of the hardware clock by the timezone offset.
my timezone is Asia/Manila, which is UTC+8. so if the correct time is 00:00, the system time is 08:00.
i dual boot with windows so the HARDWARECLOCK setting in /etc/rc.conf is set to localtime.
interestingly, the commands "hwclock --show" and "date" both show PHT as the timezone, but with the aforementioned time skew. to illustrate:
# hwclock --show
Fri 05 Aug 2011 10:45:02 AM PHT -0.500309 seconds
# date
Fri Aug 5 18:45:02 PHT 2011
running "hwclock --hctosys" fixes the problem while logged in, but restarting the computer reverts the problem. i could put a daemon that runs the command at startup, but i never needed to do that before and i'm not inclined to at the moment. i think this is just a misconfiguration somewhere.
thanks for any help you could give.

hello. it is
hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1312511647 seconds after 1969
Last calibration done at 1304274137 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/08/05 12:08:46
Hw clock time : 2011/08/05 12:08:46 = 1312517326 seconds since 1969
Fri 05 Aug 2011 12:08:46 PM PHT -0.690104 seconds

Installing PCI-6052E having trouble loading driver module - Switch Soft Panel

I'm having trouble installing my PCI-6052E card in a Windows 2000 environment. After installing the card in the computer I boot up the computer, from there I click on the Start button, programs, NI Switch and cannot get the NI-Switch Soft Front Panel to work. When I click on the icon I get an error message returned that says "Failure Loading Driver Module". Any ideas?

Hi PCI Card Problems,
Thank you for posting on the National Instruments forums.
If you are trying to use the NI-Switch Soft Front Panel, please make sure that you have a switch module installed.
If you are trying to bring a test panel for the PCI 6052E, then you will need to open the Measurement and Automation Explorer which is found in Start >> National Instruments >> Measurement & Automation. Right click NI PCI-6052E under Devices and Interfaces >> NI-DAQmx Devices and select Test Panels...
If you only have a PCI-6052E installed, then what you are seeing is expected behavior since the NI-Switch driver is only for National Instruments Switch modules.
Thank You,
Nick F.
Applications Engineer

[SOLVED] System time is +4hrs from hardware clock

Hello again.
Now I can't set up my system`s time properly. (Set system time from hardware clock)
Timezone is GMT+4 (Europe/Samara) and hardware clock (RTC) is set to proper time so does UTC.
But system`s time itself is 4 hours in the future from HW clock!
# hwclock --hctosys --utc
does nothing.
# timedatectl set-local-rtc 1
or
# timedatectl set-time "$mytime"
both do nothing and output following error:
Failed to issue method call: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Also, removing /etc/adjtime does nothing!
How can I fix it?
Last edited by eruditorum (2012-11-25 10:52:14)

ewaller,
hwclock from util-linux 2.22.1
Using /dev interface to clock.
Last drift adjustment done at 1353744432 seconds after 1969
Last calibration done at 1353744432 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2012/11/25 05:40:17
Hw clock time : 2012/11/25 05:40:17 = 1353822017 seconds since 1969
Sun 25 Nov 2012 09:40:17 AM SAMT -0.907738 seconds
Last edited by eruditorum (2012-11-25 04:35:10)

[SOLVED] Gnome clock is 2 hours off hardware clock

hi, i'm not sure if this is the right place to post but here we go..
I've just installed arch on my laptop and now everything seems to work pretty well, although the clock in gnome/cinnamon is 2 hours off hwclock/localtime. Does anyone have a suggestion how to fix this? I don't seem to be able to edit it manually through the gui
Last edited by frmi (2012-08-21 15:29:45)

2ManyDogs wrote:
When you did the install, did you do this step: https://wiki.archlinux.org/index.php/Be … clock_time
frmi wrote: the clock in gnome/cinnamon is 2 hours off hwclock/localtime
Does this mean your hardware clock is set to loacal time?
What does
sudo hwclock
return (and is that local time)?
and what is in /etc/adjtime?
This just made me realise that it's the hwclock which is off localtime.
Would
# hwclock --systohc --utc
Set the clock properly or should i use localtime instead of utc?
anyway here's the output:
[fm@fm-lap ~]$ sudo hwclock
Password:
2012-08-19T15:39:23 CEST -0.145579 seconds
[fm@fm-lap ~]$ cat /etc/adjtime
0.000000 0 0.000000
0
UTC
Last edited by frmi (2012-08-19 11:50:01)

Clock of PCI 5640R

Hi!
 I got a little bit confused by the clock of PCI 5640R.
 What does "nominal frequency" which appears when I add a clock in in the Project Explorer mean?
 How does it come into play with the following equation?
 DAC__IQ_Clk = 2 × REFCLKDAC_ × Clock multiplierDAC_ / InterpolationDAC_
 Thanks!
Dayu

Hi Dayu
The "nominal frequency" field in the Project Explorer is basically a value that the Xilinx tools use to determine if the FPGA code will run on the FPGA. In the process of compiling the code, it will determine the maximum speeds that portions of the circuit will run at. Say you specific 75.0 MHz. If Xilinx thinks the circuit can run at 100 MHz, there are no problems, but if Xilinx thinks that the circuit’s maximum speed is ~70 MHz, it will fail.
You should only have to change this if your FPGA code can’t run at the default number and you want to clock the circuit at a much slower rate. Then put in a value higher than the rate you are going to clock it, and lower than what the Xilinx tools say is the maximum rate for your code.
This value does not really factor into the DAC__IQ_Clk equation, which is configured with the Clock and DAC configuration VIs.
Jerry

OVM Guest wrong hardware clock

Hi,
I'm running an Enterprise Linux 6.3 (PVM) on an OVM host.
The problem is that the date in the EL guest doesn't correspond to the date in the OVM host. The time in /var/log/messages is skewed: it's 6hours too early.
The hwclock on the host:
[root@lnx-iaovm01 /]# hwclock
Fri 17 May 2013 10:53:51 AM CEST -0.737400 seconds
Output of the command on the guest:
[root@lnx-ianag01 vm]# hwclock --debug
hwclock from util-linux-ng 2.17.2
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
I tried the following solution: ln -s /dev/rtc0 /dev/rtc
but I don't have a /dev/rtc0 directory so this isn't very successful
I also tried setting my TZ in my /etc/profile (so the "date" command atleast is correct but since this is just an environment variable so it doesn't really help either).

Isn't it easier to just enable ntp to sync your VM with a clocksource locally in your network or on the internet?

KDM crash - hardware clock

I had some problems with a computer running KDE4 at work. KDM would crash back to console. Login in from console as root and switch between run levels back and forth - init 3 and back to init 5 - would get KDM up and running with no problem though.
Fix:
- in BIOS hardware clock was two hours back in time, adjusting it correctly mad KDM start correctly
From kdm.log:
kdmgreet(2657)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
This message is persistent even though KDM now starts. Intriguingly, at least for me, is the fact that the log after adjustment of time is two hours ahead of time. During crashes is was correct. System time was and is correct (ntpd).
Two questions:
- how come KDM log doesn't adhere to neither system or BIOS hardware clock?
- is it reasonable that such a "small" error causes KDM to crash?
The first question seems to be answered by the fact that kdm.log complaints about not being able to connect to D-Bus server. However why doesn't it? Dbus is started as it should, and no other services seem to

To restate the problem:
Microsoft Windows expects the hardware clock on the machine upon which it is running to be local time. Linux machines and others set and use the hardware clock as UTC (aka GMT) time. Thus, when a machine can be dual-booted,
there is a discrepancy in the reported time. You can modify the other operating system parameters to deal with a hardware clock in local time, or you can change Windows to cope with a UTC hardware clock.
While it is possible to kluge the time zone as is mentioned below, a simpler solution is to
synchronize Windows time with a NIST server ("time.windows.gov", e.g.) vs. the default Windows time server "time.windows.com". You can do this in the "Internet Time" tab when you click on the date/time on the system bar. Once it refreshes,
the time in Windows will be the correct local time, vs. the previously incorrect time.
One drawback of this method is that after booting into Windows, the incorrect time will be displayed until a refresh is performed against the NIST server. You can adjust how often this occurs on the "Internet Time" tab as
well. Another drawback is, of course, that you need an Internet connection.
I triple-checked that using this method does NOT change the hardware clock, which is good. I have used this method for a while. Your results may vary. Hope this helps.

Triggering possibilities by the NI PCI-6052E board

Will you tell me, how to use the NI PCI-6052E board for analog and digital triggering. I want the trigger to begin the measurement, to acquire data before the trigger occurs. In other words, the board must response to a pulse input. Also I want to know other trigger capabilities of the board.
Thanks,
Gen

I am happy to let you know the PCI 6052E has both analog and digital triggering options. You can set your analog inputs to start acquisition on a rising or falling edge of your trigger pulse. If you are interested in acquiring data before your event trigger you can set up a buffer to capture pre-triggered data. Assuming you are programming with LV and Traditional DAQ you can reference the following app note:
http://zone.ni.com/devzone/conceptd.nsf/webmain/2A03115556FB233386256870005BB522?opendocument
If the link above does not work, go to
www.ni.com/support
under option 3. select 'Tutorial/Application Note'
Then do a search for 'Tips and Techniques for DAQ Triggering'
If you are using the LV 7 and the express VIs to set up your DAQ, look under the
triggering tab of the express vi to set up analog vs digital trigger and buffers for pre-acquisition. If you don't have LV 7, I highly recommend it because the express vi's will help reduce your development time.
-JVH

QNX or Linux driver that will DMA from a PCI-6052E

Hi,
I am planning a QNX or Linux driver that will DMA from a PCI-6052E.
In the readme at
ftp://ftp.ni.com/support/daq/linux/Readme
snip ..
* DMA is not supported at this time. Doing DMA would require
programming the mMITE chip on NI's CPCI/PCI/PXI cards, and as of now
that information is only available under NDA, thus precluding an
open-source release. Feedback on this issue is appreciated.
snip ..
Is this readme up to date? I do need the DMA, and was hoping to get the
necessary info from the Linux code.
cheers -- Rick
Rick Leir
Pelyco Systems
rleir at pelyco dot ca replace at and dot
Sent via Deja.com http://www.deja.com/
Before you buy.

Yes sadly I have tried that config. I did a clean XP install with onboard sound and agp card, after install completes and windows loads for first time it would play most of the login tune then crash with a loud continuous shriek. Went into BIOS, disabled sound, unjumpered it, reboot, and boom it ran great.
Would an IDE contoller card be an option here? or would the stuttering Southbridge still be involved?

Hardware clock in PCI-6052E

Similar Messages

Maybe you are looking for