Should external clock be pulse or sinusodial wave?
Hi there,
I am going to connect an external clock source to 6711 card. But I wonder if the source should be pulse trains (squre wave) or could be sinusodial wave. When we say the frequency of the clock, does it mean the occurence of the rising edge or fall edge but not the pulse, right? And what's the voltage range for the clock signal?
Solved!
Go to Solution.
Hi dragondriver
The external clock should be a pulse train, not a sine wave.
When we talk about frequency, as you stated it means the occurrence of rising or falling edges within a specified time.
The voltage range should be from 0 to 5V.
Regards
Chris S.
Similar Messages
-
Single Pulse Width with External Clock
I am trying to setup a 6602 counter for a single (non-buffered) pulse width measurement with an external clock. Under normal testing, the unit under test will provide the pulses, I need to measure the number of pulses during different time periods (1, 60, and 300 seconds). I want to do a pulse width measurement and I'll supply the gate signal pulse to the counter for the specific time needed.
Under normal operation, the unit under test is wired into the counter's source and the pulse is wired into the gate. For testing purposes I am using a BNC-2121. I have the counter's source wired to the Adjustable Square Wave Output and the gate wired to the Trigger output.
Here is my C++ code. I am getting a timeout error on the read and I don't know why. Any help would be appreciated.
//Create Task
DAQmxCreateTask( "task1", taskHandle );
//Create Pulse Width Channel
DAQmxCreateCIPulseWidthChan( taskHandle, // TaskHandle
szCtrName.c_str(), // Counter Name
"", // Channel Name
dMin, // Min Value
dMax, // Max Value
DAQmx_Val_Ticks, // Units
DAQmx_Val_Rising, // Gate Edge
"" ); // Scale Name
//Set the Pulse Width Terminal to the gate signal
DAQmxSetCIPulseWidthTerm( taskHandle, // TaskHandle
"", // Channel
"/CTR2/PFI38" ); // Terminal
//Set the Timebase Src to the counter's source
DAQmxSetCICtrTimebaseSrc( taskHandle, // TaskHandle
"", // Channel
"/CTR2/PFI39" ); // Terminal
//Start Task
DAQmxStartTask( taskHandle );
//***Send pulse to gate counter***
//Read Counter
DAQmxReadCounterU32( taskHandle, // Task Handle
DAQmx_Val_Auto, // Num Samps to Read
10, // Timeout
ulBuffer, // Read Buffer
1000, // Buffer Size
&lSampsRead, // Num Samps Read
NULL ); // ReservedI've setup a pulse width task in NI-MAX using the onboard clock and everything worked fine, so I know the hardware is working.
My unit under test is providing the pulses (from gyros) I need to measure. The pulses indicate the position of the unit so there are X, Y and Z axis gyros. I need to measure these pulses for specific periods of time (1, 60, and 300 seconds). For example during the 1 second measurement, the X and Y gyros should measure zero pulses and the Z axis should measure 515 gyros. During a 300 second measurement the X and Y gyros should measure < 60 and the Z axis should measure 30800.
So the gyro pulses are wired to the counter input and I am using a DIO channel from NI-6508 to provide the gate pulse. The gate signal will be high for either 1, 60, or 300 seconds depending on the test. The gyro pulses are essentially the external clock to the counter. I want to count the gyro pulses during the pulse of the gate (DIO).
To simplify the setup, I connected to BNC-2121 directly to the card. I have the adjustable clock output going to the counter input of ctr0 and the trigger signal going to the gate of ctr0. Once the task has been started and before the read ( I had a breakpoint set in the code), I would press the trigger button on the BNC-2121 and hold for approx. 1 second. I then execute the Read statement, and I always get a timeout. From my experience working with NI, I'm guessing I don't have a channel property set correctly, but its not obvious to me and I can't find an example to do exactly what I'm trying to do.
The CTR2 designation in the code was the object name of the card. I have two 6602 cards in my chassis. I was using ctr0 of the second counter card, so PFI38/39 was correct.
Again, any help would be appreciated. -
Generate pulses in NI-ELVIS II to be used as an external clock
I am using the NI ELVIS II counter for edge counting and to set the clock for Sample clock function I have to use an external clock but I am not sure how to do it. I suggest I have to use Counter Output/ Pulse generation to generate a pulse with a desire frequency and output it on pin PFI12 or PFI13 or even Freq-Out pin and then use this pulse as the external sample clock.
I can do pulse counting withough using a sample clock function but I would like to sample as high as possible to have more points and less oscillation. Would you please help me with this vi. I have attached the vi to this post.
Attachments:
Edge Counting.vi 25 KBHi tintin99,
I'd recommend checking out the NI Example Finder, found in <LabVIEW> » Help » Find Examples...
Then navigate through Hardware Input and Output » DAQmx » Counter Measurements.
In particular, I'd suggest that you load up Count Digital Events.vi which shows how to implement simple Counter based Edge Counting measurements. These are useful for interacting with peripheral hardware such as Quadrature Encoders. With this VI running, you could also concurrently execute the Gen Dig Pulse.vi found in the 'Generating Digital Pulses' section also within the Counter Measurements category. These are both good demonstrations on how to efficiently create Counter I/O DAQmx tasks within LabVIEW and will serve as a great foundation for your own code.
As a general overview, there are three main terminals you will need to be aware of when dealing with Counters:
Source - The counter input signal, effectively the signal we wish to count.
Gate - An input signal which determines whether we should continue counting, based on digital highs, lows, active edges and falling edges. These can all be preconfigured in software.
Out - The counter terminal output. This will be used in pulse generation.
As you want to perform two Counter based tasks, you will need to make use of two different onboard counters. You can find out which pins can be used to access these different counter terminals by loading up the Measurement and Automation Explorer (MAX) and selecting your device under the Devices and Interfaces tree from the left hand pane. With the device selected, click on Device Pinouts, found on the toolbar. This tab could be hidden, so I suggest either maximising the MAX window or clicking on the double arrows on the right hand side of the toolbar to display any missing options.
Best of luck with your application.
Kind Regards,
Alex Thomas, University of Manchester School of EEE LabVIEW Ambassador (CLAD) -
DAQ Card is inducing noise on an external clock signal resulting in false triggering
I am using an optical encoder as an external clock source for analog measurements with a PCI 6036 card. The optical encoder signal is "filtered" using a Schmitt Trigger circuit and proper shielding practices are used on the encoder cable. I am using a recent version of Labview.
When the TTL square wave signal from the encoder is viewed on an oscilliscope (without the DAQ attached) it is a picture perfect square wave, nothing that would cause any problems.
When I then connect the encoder output to my PFI line (with or without the oscilliscope) I get false triggering due to intermittent (seemingly random...) high frequency noise "blips". Out of 360 expected samples, I will typically get between 2 and 6 "bonus" samples... When captured on a scope, the noise looks like a decaying sine wave and lasts for only a few us. the peak magnitude is tyically around 2 V or so as shown on the scope, which is apparently just enough to make my card grab a sample.
Since the noise is only present when the encoder signal is attached to the DAQ, it seems that the DAQ is somehow inducing noise into the signal.
I have been fighting this problem for a while now and tried the following:
1) I first tried the raw encoder signal, but then added the Schmitt trigger, increased the signal strength of the encoder lines by adding resistors to ground, double checked my shielding, etc...
2) I verified that my ground potential between my card and my conditioning circuit were not causing problems. The conditioning circuit and encoder is now powered of the card itself, which should resolve any possible problem with grounds.
3) Cursed at various inanimate objects (made me feel better but didn't help the situation)
4) Checked if I could set a minimum pulse width required to trigger off of an exernal scan clock (I can't with my hardware.)
5) Swapped my card with a card of a different type (problem is still there)
If anybody out there has some recomendations, I am open to anything.Hello OSU_Mech_Eng,
I'm not quite sure how the DAQ card could be inducing glitches into
your digital signal. Digital signals from mechanical devices like
quadrature encoders can often be glitchy or bouncy, but your schmitt
trigger should act as a debouncing filter to clean up that digital
signal. It sounds like you have thoroughly troubleshooted this
problem, and I would recommend moving on and trying to use a counter on
your DAQ board to generate the digital signal, rathar than using the
raw signal from your encoder/schmitt trigger.
You were correct when you stated that the best way to do this is by
configuring your counter to perform retriggerable pulse
generation. You can use the signal of from your encoder to gate
the internal clock on your DAQ card, creating a clean digital
signal. By setting the minimum pulse width of the signal, you
will be able to ignore the small glitches in your signal. Here is
a link to some Knowledgebases describing how to do this:
How Do I Remove Glitches or Add a Debounce Filter to My Digital Signal?
How Do I Define the Parameters for Pulse Generation in NI-DAQmx?
For further reference, on all of NI's new M-Series DAQ cards (PCI
625x), the PFI circuitry contains built in debouncing filters to
protect against small glitches in digital signals. If you have an
M-Series card lying around, it might be helpful to give that a try.
I hope this helps,
Travis Gorkin
Applications Engineering
National Instruments
www.ni.com/support -
How can I use external clock to implement a delay?
Hi all,
I am testing to use external clock to drive dev/PFI0 (on device 6711) which is used as the clock for the analog ouput. I have thinking two applications by using the external clock but I don't have much idea on the implementation yet.
First of all, I have a sequence of data (array) with each sample being sent at the interval of 1us. I use an external clock (10MHz) driving the PFI0 so it is pretty easy to achieve that goal. I am thinking what happen if I want each sampel being sent at different time. For example, if I have 5 samples, I want the first one sent 1us after the task start and wait 2us to send the 2nd sample, wait 5us to send the 3rd sample and wait 11 us to send the 4th sample, and wait 1us to send the last sample. Is it possible to achieve that based on the external clock?
Second question is about the delay. My code require ciritcal timing and the builtin delay doesn't behave very well because I am running in windows. I can increase the priority of the vi to highest, it helps a bit but still not perfect. I am thinking if it is possible to implement hardward delay based on the external clock. Any idea?Hello dragondriver,
To answer your first question, yes you could send data in that fashion. You would have to programmatically build a pulse train and use that to trigger the sending of data. The answer to the second question is essentially the same. You should be able to programmatically build a pulse train with a delay and use it as trigger to begin whatever operation you have.
Jonathan L.
Applications Engineer
National Instruments -
Is the PXIe-PCIe8361 adequate for this system? And external clock questions...
Hi all,
I have spent some time piecing together a system and I'd like a sanity check before pulling the trigger on this purchase. The system will contain the following hardware:
1. Chassis: PXIe-1078
2. Controller: PXIe-PCIe8361
3. 3 x PXIe-6363 (16 analog inputs each card, 32 digital inputs each card, all internally clocked @ 10kHz)
4. 2 x PXI-6224 (32 digital inputs on one, 8 digital inputs on the other, externally clocked in "bursts" of 62.5khz)
5. Labview software
The three PXI-6363 cards will be responsible for a mix of analog and digital measurements made @ 10 kHz, timed continuously by the onboard clock.
One PXI-6224 will be clocked externally @ 62.5 kHz and will be used to collect digital data on a 32-bit port. These clock pulses will not be continuous, but will occur in bursts lasting for 2ms every 20ms.
The other PXI-6224 will be clocked externally @ 62.5kHz as well and will be used to collect digital data on an 8-bit port. These clock pulses will not be continuous, but will occur in bursts lasting for 2 ms at random intervals.
My questions are:
1. Am I planning anything that looks unreasonable for this hardware?
2. Should I expect issues with data transfer rates with the PXIe-PCIe8361? I will be operating well within the advertised 110MB/s throughput of the device. I plan to stream this method... NI Fast TDMS data streaming
3. I have only ever used NI cards for continuous measurements made by an onboard clock. When I set up a task to collect data that is externally-timed, will the DAQ be expecting a "continuous" clock pulse, or will the system wait patiently for clock pulses to arrive at any rate (any rate within the spec of the card, of course)?
Thanks, any input is appreciated.Hello LucasH0011
1-As long as you put the PXI-6224 and the PXIe-6363 cards in the corresponding slots, meaning the express(PXIe-6363) in the express and the hybrid(PXI-6224) in the hybrid.
2-I think you would not have issues with the transfer rate.
3-Your timing specifications sound reasonable to me, I think you will be fine.
Here is a document that has useful concepts for the use of cards:
http://www.ni.com/white-paper/3615/en/
It is for the M-Series, but the concepts apply to the X-Series as well.
Regards
Ernesto -
Driving DO lines with external clock wired to PFI lines
Hi all,
I have few issues understanding how to use hardware timing resources in M series USB6229, with particular focus on DO. I have read last couple of day all google offered on the subject but I am still straggling with some basic tasks. To cut the story short, the 1e6 dollar question: can I set up 7 independent DO lines where (different tasks or virtual channels) where lines use same hardware timing source (eg, freqout or CO0 set to ~10kHz sampling time routed to PFI0).
Note: the reason I need 7 independent lines and not a port output (which would be obvious solution) is because I need to have (vastly) different number of samples and for each line.
Follow up question regarding timing: As I understood, any of PFI ports could be used and a input to the external clock which could be used to drive DO line(s) samples. I have tried to generate one DO, eg. P0\line4 by using CO0 to generate 10kHz sample rate. The signal on the line4 is pulse with frequency of few Hz which I routed to PF6 (with actual wire) in hope to use this signal as a clock for line5. I tried this but I am receiving errors about "resources in use"
Possible reason(s):
Specified route cannot be satisfied, because it requires resources that are currently in use by another route.
Property: SampClk.Src
Property: SampClk.ActiveEdge
Source Device: USB-6229
Source Terminal: PFI6
Required Resources in Use by
Task Name: _unnamedTask<7B>
Source Device: USB-6229
Source Terminal: PFI4
Destination Device: USB-6229
Destination Terminal: do/SampleClock
Task Name: _unnamedTask<79>
Apparently, many of internal clocks are routed internally to different PFI lines which mean the lines are occupied resource, and I do not know how to solve this.
I wanted to ask you does this principle sound as something that should work and if you know about some examples that would be excellent.
Any help would be greatly appreciated.
Cheers, Nenad> To cut the story short, the 1e6 dollar question: can I set up 7 independent DO lines where (different tasks or virtual channels) where lines use same hardware timing source (eg, freqout or CO0 set to ~10kHz sampling time routed to PFI0).
No, you can't. The USB-6229 has a single digital output FIFO which can only be used by one task at a time.
> Note: the reason I need 7 independent lines and not a port output (which would be obvious solution) is because I need to have (vastly) different number of samples and for each line.
It should be possible to generate all seven signals with a single task by generating a waveform that includes all seven signals. If the signals repeat at different rates or you need to start/stop them independently, you will have to disable regeneration and continuously generate new waveform segments on the fly. Continuous Write Digital Port - External Clock - Non Regeneration should be a good starting point for the DAQmx programming, but actually generating the data is likely to be the challenging part.
Brad
Brad Keryan
NI R&D -
Hello / Bonjour
I am using Labview 6.1 / Window 2000 and a NI PCI-6110 card.
The system that I develop uses an external clock (connected to the PFI7) to sample a signal in channel 0, a trigger connected to TRIG 1 starts an acquisition. The program controlling the DAQ is a modified version of “Acquire N Scans ExtScanClk D-Trig.vi” example, I have removed from this example the two sub-vi “AI Clock Config”. The program uses then the STARTSCAN signal as an external clock.
I have three questions:
1 How do you configure STARTSCAN to either the rising or falling edge polarity as it is stipulated in the pci-6110 user manual?
2 What is the purpose of the two sub-vi “AI Clock Config” in the “Acquire
N Scans ExtScanClk D-Trig.vi” as it seems the PCI-6110 card doesn’t need them to run properly with an external clock?
3 Should I configure the CONVERT* signal if I would like to sample the channel 0 signal immediately when a STARTSCAN pulse appears?
Thank youThank you rgharrison for your answer
I tried to make some modifications and tests following your comments.
I have incorporated the �AI Clock Config� in my application (which is now very similar to �Acquire N Scans ExtScanClk D-trig.vi� except that there is only one �AI Clock Config� VI) and I have these questions and comments:
As the PCI-6110 samples each channel simultaneously (and I want to sample only one channel), should I set the channel clock as you mentioned?
Given that my external clock is connected to PFI7 and I have specified �PFI pin, high to low� in �clock source code�, it doesn�t matter for the board if I set any PFI as �clock source string�: my board still find an external clock. But if I leave �clock source string� blank I�ve got
an error. I noticed also that the parameters of the �actual clock rate specification� cluster are still equal to zero. Is it normal or I misunderstand something?
I don�t understand why I should set up the �clock source� as fastest as possible, as I want to use an external clock and sampling my signal one time per external clock period. Also, in the �Acquire N Scans ExtScanClk D-trig.vi� exemple, after set the clock as fast as possible, the following VI �Ai Start� disable the internal clock, so again why set up the clock and disable it just after?
If I set the �clock source� at the maximum rate and if the scan clock (my actual external clock) is slower than the �clock source�, can the board acquire more than one sample by external clock period?
Regards -
Ni5640R sync with external clock
Hi,
I have a highly stable 10MHz sine source, and I need to phase-lock NI5640R's internal 200MHz generator to it.
I don't really understand half of the parameters in "Config Timebase". Any advice on how to do this?As I understand it, in:
CDC Clock Source tab:
* Clock Source = VCXO, since I need not external clock, but internal oscillator locked on external signal
VCXO tab:
* VCXO Control = PLL, since VCXO frequency will be controlled by external clock via PLL
* VCXO Enable = ON, obviously
Reference tab:
* RTSI Ext Ref Enable = OFF
* SMB Ext Ref Enable = ON, since this is the external signal source
* Clk100 Ref Enable = OFF
* RTSI(7) Direction = OFF, don't know what it is, but doesn't seem relevant
PLL tab:
* Ref Delay = 0ps, I only care about phase stability at the moment, so delay is not relevant
* VCXO Delay = 0ps, same here
* Ref Divider = 10, this divides 10MHz external reference to get 1MHz
* VCXO Divider = 200, this divides 200MHz internal generator to get 1MHz, then both 1MHz freq's are synchronized
* CP Current = 2.5mA, but I have no idea what this does
* CP Enable = NO, no idea
* CP Invert = NO, no idea
* PFD Pulse Width = 1500ps, (CDC7005 datasheet states, that PFD pulse is something that improves spurious suppression) I have no idea how wide the PFD pulse should be, I guess it depends on external source quality
* Lock Detect Window = 1.2ns, as I understand it, PLL is considered locked when rising edge of controlled signal of is in this window, so smaller window means less jitter
Routing tab:
* PLL Feedback Channel = Y2, this is by default, I don't know if this should be touched. This is also a bit confusing, since the choice is between [Y0, Y1, Y2, Y3, Y4, Y3, Y3, Y3]. I wonder how these Y3's are different?
* Y0 (ADC0) Division = divide by 2, Y0 Enable = YES, I see no need to modify this
* Y1 (ADC1) Division = divide by 2, Y1 Enable = YES, same here
* Y2 (DAC0) Division = divide by 2, Y2 Enable = YES, same here
* Y3 (DAC1) Division = divide by 2, Y3 Enable = YES, same here
* Y4 (RTSI Ref) Division = divide by 2, Y4 Enable = YES, same here
Misc tab:
* OPA Enable = FALSE, OPA is a enable/disable control for amplifier. I'm not really sure about what it does and if this is even connected in NI5640R, default is off
* Enable Ext Ref R = FALSE, may be something related to what I need, by default it is off
* Hold = FALSE, as I understand, when this is enabled, PLL tries to maintain lock when missing reference cycle, probably may be used for clock extraction from serial data stream. for this application it's not necessary
* NPD = TRUE, according to CDC7005 datasheet, NPD is asynchronous power down, and should be held high
* NRESET = TRUE, asynchronous reset signal, should be held high
* Bandgap Enable = TRUE, not sure what bandgap is, and I don't think it's relevant
External tab:
* HW NPD = TRUE, should be hardware power down
* HW NRESET = TRUE, hardware reset -
How do I use a quadrature encoder as an external clock (PCI 6229)
Hello, ( a similar post has been placed on DAQ forum apologies as I did not know best place)
I have a PCI 6229 M Series data acquisition card. I want to use a quadrature encoder to be the external clock driving the acquisition of a number of signals. I have set up reading 24 signals each time a clock pulse is received using the DAQ assistant and set my external clock to pin pfi8 (I think) this is then connected to an encoder output. This works well enough until the encoder is run too fast when it appears I am either missing pulses or getting bounce.
How can I set up to clock using a quadrature encoder? I have seen a number of questions on this forum regarding quadrature encoders and reverse counting but not on using them as an external clock.
Basically I want to have the stability and "bounceless" nature of using two outputs from a quadrature encoder whilst still using an external clock. Is this just a case of configuring controls to certain pfi's? If so how is it done?
Any help or pointers would be helpful. So far I have managed very nicely by simply using the DAQ assistant and the interface it has would suggest that if configured for a certain pfi pin I could actually still use it.
Thanks in advance.
KevinHi,
Well I've had alook into this for you and I'm not quite sure I understand what you are looking for.
Is it possible for you to phone back in to support?
The reason you are seeing bounce at high speeds, or indeed loss of points, is due to the sampling rate that you have set up.
What you will find is that the trigger will start an aquisition of a number of points at a certain rate. If your sampling rate is too low then you will not finish that sample batch before the next set of samples is recorded.
It is possible to use an external clock into a trigger or digital line, however this will limit the number of samples you can take to the speed of your encoder.
If you increase your sampling rates, and then configure a start trigger from a single input from the encoder you will be able to record a number of samples after a rising/falling edge. (Set the clock as an internal clock)
Hope this helps
AdamB
Applications Engineering Team Leader | National Instruments | UK & Ireland -
Hi,
when Using the Cont Acq&Graph Voltage-Ext Clk.vi i have Rate and Samples to read controls.
Is that means that evry time my external clock rise (for example) the Acq is done by a sorce clock inside the daq card
at the sample rate value is what Rate controller have?Barak,
When using an external clock, LabVIEW asks for those two parameters as data points for setting up a properly sized data buffer. You should set your rate to the maximum value that you would expect from your external clock. For example, if you're external clock varies from 34Hz to 40kHz you would set it for 40kHz but the acquisition will be done at your external clock frequency. The DAQ board will be using your external clock exclusively and will NOT be using an internal clock. The 'samples to read' will tell LabVIEW how many samples to pull from the buffer each time the DAQmx Read function is called (every while loop iteration). If that many samples are not present, the DAQmx Read will wait until that many samples are present. If you want the function to read all available samples, wire in a '-1.'
Patrick Barrett
PBear
NI RF -
External clocking on 6711 card
Hi all,
I just read the manual of the card PCI6711, it supports the external clock. So does it mean we can change the update rate by using different external clock rate?chris88 wrote:
HI dragondriver
They are both correct, the PCI 6711 supports external clocking for the analog output tasks, but for Digital I/O tasks the timing can only be set to software timed, meaning that you cannot use external clock for digital tasks.
The main difference between RTSI and PFI is the physical connection, PFI lines conects through the connector block you are using and the RTSI is connected through a RTSI bus cable used to synchronize several DAQ cards.
You can choose any PFI <0 to 9> and this article show how to select which PFI line is the source of sampling.
Regards
Thanks for the clarification . I only one doubt. Someone told me that 6711 only supports software-based digital pulse input/output but it supports external-clock-driving counter output. So when you said softwarebased digital I/O task, do you mean all digitals output including counter output? Thanks. -
External clocking proble with NI-DAQ 6534 after driver upgrade
Hello newsgroup,
I've got a Problem with a pattern generation using the NI-DAQ 6534.
I'm using it in 32 Bit Output mode with external clocking.
After changing the PC and the OS from a P II 333 Mhz running Win98
to a P 4 1,8 GHz running WinXP Pro the use of new drivers was nessasary,
because the old driver doesen't work at all. The following problem occurs
by using actual driver: Using my old programm external clocking doesen't
work anymore, but internal clocking works fine. I'm using C++ not Labview.
I'm not shure if this is the right newsgroup for my problem. If not please
give me a hint were it belongs to.
Regards
MichaelMichael:
What version of NI DAQ did you have? What version did you upgrade to? Is your 6534 a PCI board or is it an AT/ISA based device? Have you changed your code at all? You code should be fully compatible with a new version of NI-DAQ... Please provide more exact details of the problem so I can help futher. Are you getting errors or is it just not working?
Sincerely,
Brooks B
Applications Engineer
National Instruments -
Processor 2.6 Bus 800 shows at XP with 200 External Clock
Hi ,
I have a Pentium4 2.6MHZBus 800, 256MB DDR Bus 400, MotherBoard MSI 865PE Neo2,HD MAXTOR 80G ,VGA GeoForce 4 8X G.Ward 128MB DDR
I upgrade the bios version to the latest 1.9 the i run "LOAD HIGHST PREFORMANCE
But : at the windows XP with SP1 i found the software with read the system configuration ..reading my processor with External clock "200"
Does it show the right ?
OR should it be shown As "800"
By the way the OverClocking on the setup is disabled
Can i use overclocking here? to what range?
Advice please
Thanks in AdvaceHi Wonkanoby,
Im little bit confuse , how can I get the optimum performace of FSB 800 of my processor ? Below is my CPU-Z report and my Computer Specs
Intel P4 2.6Ghz HT @ 2.9Ghz
MSI 865PE Neo2
Geforce FX5200 128MB DDR
80Gig Seagate 7200RPM and 40 Gig Seagate 5400RPM see-through (modified)
GENERIC 256MB DDR400 memory
Pixel View TV tuner
D-Link Internal Modem
Cooler Master AERO CPU Cooler running at 3900RPM
5 X Cooler Master Fan Casing
HEC Power Supply 350Watts
3.3V = 28Amps / 5.0V = 33Amps / 12.0V = 15Amps
MSI CD-RW 52x32x52
ASUS 16X DVD
Win2000 SP3
CPU-Z Report
CPU-Z version 1.20a.
CPU(s)
Number of CPUs 2 (1 Physical)
CPU#1 APIC ID = 0
CPU Name Intel Pentium 4
Code Name Northwood
Specification Intel(R) Pentium(R) 4 CPU 2.60GHz
Family / Model / Stepping F 2 9
Extended Family / Model 0 0
Brand ID 9
Technology 0.13 µ
Supported Instructions Sets MMX, SSE, SSE2
CPU Clock Speed 2925.0 MHz
Clock multiplier x 13.0
Front Side Bus Frequency 225.0 MHz
Bus Speed 900.0 MHz
L1 Data Cache 8 KBytes, 4-way set associative, 64 Bytes line size
L1 Trace Cache 12 Kµops, 8-way set associative
L2 Cache 512 KBytes, 8-way set associative, 64 Bytes line size
L2 Speed 2925.0 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 256 bits
CPU#2 APIC ID = 1
CPU Name Intel Pentium 4 (logical unit)
Mainboard and chipset
Motherboard manufacturer MICRO-STAR INC.
Motherboard model MS-6728, 100
BIOS vendor American Megatrends Inc.
BIOS revision V1.7
BIOS release date 10/06/2003
Chipset Intel i865P/PE/G/i848P rev. A2
Southbridge Intel 82801EB (ICH5) rev. 2
Sensor chip Winbond W83627HF
FSB Select 533 MHz
Performance Mode enabled
AGP Status enabled, rev. 3.0
AGP Data Transfert Rate 8x
AGP Side Band Addressing supported, enabled
AGP Aperture Size 128 MBytes
Memory
DRAM Type DDR-SDRAM
DRAM Size 256 MBytes
DRAM Frequency 225.0 MHz
FSB:DRAM 1:1
CAS# Latency 2.5 clocks
RAS# to CAS# 3 clocks
RAS# Precharge 3 clocks
Cycle Time (TRAS) 6 clocks
# of memory modules 1
Module 0 DDR-SDRAM PC3200 - 256 MBytes
Software
Windows version Microsoft Windows 2000 Workstation Service Pack 3 (Build 2195) -
USB 6210 Using counter as an external clock
I was referencing an old post for how to read and write data from a quadrature encoder. I am using a USB 6210 card along with Labview 8.2.1. In the previous post it describes needing to:
"You will have to create an external clock using the other counter on
the board then route the signal either externally or internally"
I do not know what this means and I do not understand what is required to do such (Changes to wires, change the Vi...etc). If someone could please shed some light on this I would really appreciate it.
I am basing my approach on the following NI example:
Meas Angular Position-Buffered-Cont-Ext Clk.viHi rose8,
The example you are referencing requires an external clock to basically take samples of the angular position based on time. For instance, you can rotate your angular encoder all you want, but it will not save which position you are at until a sample clock rising edge is seen. When the sample clock rising edge is seen, then it places that position into a buffer, and continues to wait for the next sample clock rising edge to happen. Every time the rising edge happens, the position of your angular measurement is recorded one point at a time, stored in a 1D or 2D array.
The sample clock cannot be an on board clock that is already created. So now, we look at what sources we can use for our external clock to sample the position of our encoder and save it in our memory buffer. We can use an external source and bring it into the board, or we can create a clock using another counter on the board. Since you are looking to do this, I'll assume you want to create a clock from there.
In software, you specify two counter tasks; one to measure your angular position and one to generate a pulse train. The pulse train you generate will be the sample clock for the buffered angular position measurements you are taking. Now, you can route this externally or internally, based on your application. The easiest way is internally, because it doesn't require any additional wires to accomplish.
To route internally, all you have to do is for your DAQmx Timing VI, specify CtrXInternalOutput from your USB 6210 as the source, where X is the counter you generate your pulse train on. To see this source as an available selection, right click your Resource Name and select I/O Name Filtering from the shortcut menu, and then be sure that Include Advanced Terminals is checked.
In programming, you would want to start your angular position task first, and then start your clock generation from your second counter. They will run in parallel and just be sure to clear both threads at the end of your program. Hopefully this clears up some confusion for you.
Kyle A.
National Instruments
High Speed Digital I/O Product Support Engineer - R&D
Maybe you are looking for
-
Xbox 360: How To Open Your BT Home Hub Ports!
If you use a BT Home Hub and Xbox Live, you may need to open ports for a better connection, even if your NAT tests as Open. Some issues that this will fix: Friends list Voice chat Joining friends list games Joining some games such as Call of Duty 3 (
-
Media Encoder CC Problems - No sound and often crashes while rendering to Youtube 1080p 29.97 fps
I'm baffled by all of this. I'm trying to render a clip similar to this: http://www.youtube.com/watch?v=fprMxgfdpRo except there are 8 equalizers and I have to do it for a 2 hour podcast. I have to do it in 10 minute clips because it will either cras
-
Survey - What would your ideal T Series ThinkPad look like?
Link to thread with survey description and updated results. Results of Your Ideal Business-Class Laptop survey, concluded 2009-07-29. Did someone help you? Say thanks! with a kudo. Even better: Pay it forward, help someone else.
-
How to pay my final bill after switching carriers???
I switched to a different carrier at the end of June. I was on auto pay and as usual I received an email from Verizon Wireless regarding my final bill. The email said that the automatic payment would be made on August 7th. However, it is now the 15th
-
Have a key for photoshop cs5 need the download for new computer
My computer crashed and I have my key for CS5 but i can't find a place to download and I don't want cloud as I PAID for cs5 alreay.