Isolated Counter Input onSC2345 with FT01

Hi folks,
newbie question: I need to count frequency, direction and volume from a flowmeter. The device supplies two
channels with square wave signals of 50% duty cycle, an Amplitude of 12-18 V. the two channels are behaving
much like the quadrature encoders of electric drives, i.e. the phases of the signals indicate the direction
of flow. I have a SC 2345 with FT01 modules available for the task which according to my understanding
could do the job, but requires TTL level for the signal. Could somebody provide me with hints on creating a
small circuitry (if possible inside the FT01) which provides optical isolation. I'm thinking of a NPN transistor
driving the input LED of a optocoupler device. However, if somebody has a working circuitry it wouldn't
mean less hassle to me creating and testing my own. TIA for any input.

Hello chefgps, & Buechsenschuetz,
National Instruments has a beta version of a product called the SCC-CTR01 that you may be very interested in reviewing. If you are interested, please contact [email protected] for more details.
The SCC-CTR01 is an isolation signal conditioning module for the TTL general purpose counter timer signals from the MIO device which can be used in a SC-2345 carrier in the counter slots. The maximum I/O signal voltage levels it can handle are 0-48V. The maximum I/O frequencies are 400kHz. The conditioning provided by this module is very similar to the PCI/PXI-6624 isolated counter timer boards. I think that the SCC-CTR01 module will be a good solution for your application without the hassle of designing, constructing, testing, and debugging your own custom isolation and attenuation signal conditioning.
Alternatively if you need a released solution right away then please consider the PCI or PXI-6624.
Please let me know if you are interested.
Have a great day.
Dan Hoar
Digital & Timing Hardware Project Manager
National Instruments

Similar Messages

Synchronize hardware timed buffered counter acquisition with buffered analog input acquisition

LV7.1
DAQmx
PCI-6036E
SC-2345
Windows 2000
Greetings.
I am simply trying to synchronize AI readings with readings from one Counter.
I am trying to perform buffered analog input synchronized with buffered counter acquisition.
I'd like the AI acquistion to trigger the Counter acquistion.
I'm currently setting the Sample Clock Source for the CI Cnt Edges Task to "Dev1/ai/SampleClock" but when I try and set the source for the "DAQmx Trigger" I can't seem to select one that works. I assumed that the source should be the "Dev1/ai/StartTrigger" but that produces and error as does selecting any of the PFI's.
I'm new to DAQmx and didn't have any luck with the examples or what's been previously posted.
Thanks for your help.
Attachments:
Initialization.jpg ‏84 KB

Gentlemen-
All of your initial help was great. I had some noise on my counter lines so switched from an E-Series card to a PCI-6259 M-series card in order to use the counter digital filters.
Now I can't get a corellated buffered counter and buffered analog input acquistion to work. This same code worked fine on an E-series card but it doesn't on the M-series.
I verified that the source and gate of the counter are working properly using the test panel and a external function generator.
But when I run the attached code I get no data out of the "Counter 1D U32 NSamples", only an error saying that the timeout of the function was reached and no count data became available. Am I missing the specification of a another clock or something?
The counters also work fine using the M-series example code "Count Digital Events (M-Series DAQmx) but this is not a buffered acquisition.
Any help would be greatly appreciated.
Steve
Attachments:
Sample_Code.jpg ‏136 KB

Benchmarks for Buffered Counter Input with X-Series Devices

Hi,
Does anyone know the maximum transfer rate (using dma) for the x-series cards?
I'm looking for data simillar to the one in this link:
http://digital.ni.com/public.nsf/allkb/72A7E41EE5A8756A862571DA0076F1D7?OpenDocument
More specifically I want to know the transfer rate for the PCIe 6343.
Thank you,
Eyal
Solved!
Go to Solution.

I benchmarked 8MS/s on a single channel on a USB-6353 (should have similar performance to the USB-6356/66) with a buffered counter input task. This was only a 10 minute test on my Dell E6400 laptop ( Windows 7 32 bit, Dual core P8600, 4GB memory) so a sustained 24/7 rate is likely less. Also, I wasn't doing much with the data, just displaying it in an array. This is pretty much topping out USB streaming on this system (32MB/s) so I wouldn't expect to get higher. I wasn't running much else in the back ground (Explorer, Powerpoint, Lotus Notes) and CPU was at ~20%.
Hope this helps,
Andrew S
Getting Started with NI-DAQmx
Measurement Fundamentals

PCI-6602 - What to do with unused counter inputs?

I've got an application where I need to track the position on two quadrature encoders. I've developed my application with VB6 however, I've been using a sample LabView program called "Meas-Ang-Pos-Buff.vi" for testing purposes. (I got the example off the NI discussion board). I'm seeing some very odd results that I can't explain.
For testing purposes, I've got one encoder tied to multiple channels on my 6602. I have the same 'A' signal and the same 'B' signal (from the one encoder) jumpered to multiple encoder channels. I'm using a onboard pulse generator to generate the latch pulse (connected to the Index/Z of each counter) to ensure there is no skew in my count values. I'm using an external servo to turn the encoder at a rate equal to my application speed.
The unexplanable results I'm seeing are below:
If I'm monitoring counters 0, 1 and 2, I see the following.
1) If I have counters 0,1,2 and 3 inputs connected to the same 'A' & 'B' from my encoder, the counts on all 4 channels (0,1,2,3) track perfectly.
2) If I disconnect counter 3 and only have counters 0,1, and 2 connected to the encoder, then counter 0 and 2 track perfectly, but counter 1 looses pulses (only when traveling in one direction, the other direction seems to be fine)
3) If I connect counter 3 to ground and have counters 0,1, and 2 connected to the encoder, I get the same result - bad.
4) If I connect EVERY counter input (2,3,4,5,6) to ground and only monitor counters 0 and 1, I still get bad results.
In summary, I ONLY am able to see the same number of counts while monitoring 3 channels IF 7 of the 8 counters are connected together (the 8th being my latch).
This happened to me in the past on a previous setup that did the same thing, but I was able to fix it by moving from counter 1 to counter 4. At that time, I chalked it up to a bad counter 1, but I think there is a bigger issue since it is happening again.
Please any advice would be appreciated.

Thanks for the response. This one has really got me confused and any help is greatly appreciated.
To answer your questions, no I have not modified the sample program and I'm using NI DAQ v8.5.
I've decided to break the problem down to see if I could find a pattern, but no such luck. Here is the testing that I've done.
I'm making the following connections while using the sample program I mentioned earlier:
Counter 0...............PFI_39 (term 02) - Channel_A(0).................PFI_37 (term 40) - Channel_B(0)
Counter 1...............PFI_35 (term 07) - Channel_A(1).................PFI_33 (term 06) - Channel_B(1)
Counter 2...............PFI_31 (term 34) - Channel_A(2).................PFI_29 (term 66) - Channel_B(2)
Counter 3...............PFI_27 (term 31) - Channel_A(3).................PFI_25 (term 63) - Channel_B(3)
Note: I connect the "Z" channel for gating purposes in my VB application, but this isn't required in the LabView sample program since the gating appears to be done internally.
My testing results:
1. If I jumper my one encoder to channels 0,1,2, & 3 at the same time, everything works great. Each channel reports the same number of counts regardless of whether I'm turning the encoder in the positive or negative direction.
2. If I disconnect channel 3 and only have 0,1 & 2 connected, then 0 & 2 track perfectly, but channel 1 looses counts in the negative direction.
3. If I only connect channels 0 & 1, then channel 0 counts perfectly in both the pos and neg direction, but channel 1 looses counts in the negative direction.
4. If I connect any channel by itself (0,1,2 or 3), each one counts perfectly.
5. If I connect channels 0 & 4, everything seems to be fine.
Like I said in my previous e-mail, if this hadn't already happened to me in a previous application, then I would chalk it up to a bad board. If I didn't get good results on each individual channel then I would chalk it up to a bad encoder pulse train. However, it definitely seems to have something to do with connecting multiple counters at the same time in a Motion Encoder Application. I have read the 6602 User Manual backwards and forwards looking for a nugget of explanation, but have found none. There was a section entitled "Counter Input Selections" on page 4-12 (table 4-2) that might offer some explanation, but neither me or my colleagues could understand what was being described. Any help deciphering that would be appreciated.
As of now, I'm going to proceed with my application, using channels 0 &4 (just as I've done in the past), however I don't feel comfortable not having an explanation for the 6602's behavior. Any insight would be greatly appreciated.

Route multiple 6602 counter inputs to one counter output...

Hi!
I´d like to route 4 different ttl signals, that are read by 4 different counter inputs to one single output channel (e.g. the output of one of the counters used) using pulse train generation with a divider of 4. Note that only one of the four inputs is active at the same time, to prevent overlay.
How can I do that with Traditional-DAQ?
Setup would look like this on the SCB-68
TTL1 ----o in0 (ct0)----o out0 TTL(1..4)/4 [Hz]
|
TTL2 ----o in1 -- (output of ct2 is redirected ro ct1)
|
TTL3 ----o in2 --
|
TTL4 ----o in3 (ct3)--
May it be better to just output each counter input signal at it´s own output and connect these outputs to one free I/O-pin hardwired?
Best regards
Zorniki

In the end I configured a counter for Pulse Train generation and opted to change the duty cycle and frequency via 'DAQmxWriteCtrFreqScalar" (i.e. Pulse Width Modulation)
I registered a callback for the 'DAQmx_Val_CounterOutputEvent' and then changed the dutycycle and frequency in that callback.
Unfortunately, I kept getting "The pulse generation with previous property settings must complete a
full cycle before the property can be updated." error messages and, opon further reading, managed to find a doc where National Instruments suggest adding a 'Wait(period)' before executing the 'DAQmxWriteCtrFreqScalar' call.
The problem with this solution is that it one has to wait a minimum of 2 Periods before the Pulse Train can be modified which is not acceptable for our work.
So is there an alternative solution which allows us to change the Pulse Train after only 1 Period ? Is there an event we can trap which allows us alter the Pulse Train after every period ? I'm sure PWM must be possible on Daq cards (PCI-6602 or PCI-6281 or PCI-6259)?
Cheers, Shaun.

Counter input problem

hi, i'm using a counter input to count the falling edges of a digital pulse. I need to convert this into a time based measurement (period/frequency), but am having a litle trouble doing this. If any one can help? i'd prefer it if it were as simple as possible, i.e. no fancy programming as I'm new to LabVIEW and would like to fully understand what i'm looking at!
Many thanks in advance!
tom

Hi
What version of LabVIEW are you using? If you're programming with version 7.0 or higher you can configure your counter for period or frequency measurements quite easily using the DAQ Assistant.
Just drop down the DAQ Assistant Express VI. The Wizard that opens will ask you to choose your input type. Choose Counter Input and it list options for Edge Counting, Frequency and Period Measurement. Choose the one you want then choose the counter with which to do the measurement. When you click Finish a configuration dialog box will open up for you to configure the Input Range, the Task Timing, etc. There will also be some further information in the help section along the right of the window. When you click OK the DAQ Assistant will build your code.
I've attached a Zip file with 2 labview programs to demonstrate this. (They're written in version 8). Connect DIO 0 to PFI 9 of your DAQ card (I'm using an M Series card. If you're using a different card let me know). Extract and run both files. The Digital Output VI generates an alternating high and low signal for each iteration of the loop. The Counter Frequency Measurement VI measures the frequency of this output. The frequency is determined my the Wait Until Next ms Multiple function so change the input to that to vary the frequency.
Let me know how you get on with that and if you require more info.
Good luck!
SarahB
NI | UK
Sarah
Applications Engineer | National Instruments | UK & Ireland
Attachments:
Frequency Measurements.zip ‏65 KB

Counter Output/Counter Input PXI Signals Behaving Erratically

Question for all your LabVIEW guru's out there,
I am running a frequency loopback test using the NI PXI 6229 MIO DAQ card. I am generating a "Counter Output" pulse train signal which feeds through my device under test and then back out of my device under test and back into the PXI 6229 for a "Counter Input" frequency measurement. Both the "Counter Output" and the "Counter Input" are assigned different PFI lines using DAQmx in LabVIEW.
I have 4 lines to test on my DUT. All four lines run this same frequency measurement but with different PFI lines on the PXI 6229. Each line is test independently.
This is my setup for the 4 lines:
Path 1: P2.0 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.1 (Counter Input - Frequency Measurement)
Path 2: P2.2 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.3 (Counter Input - Frequency Measurement)
Path 3: P2.4 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.5 (Counter Input - Frequency Measurement)
Path 4: P2.6 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.7 (Counter Input - Frequency Measurement)
where:
P2.0 = PFI8
P2.1 = PFI9
P2.2 = PFI10
P2.3 = PFI11
P2.4 = PFI12
P2.5 = PFI13
P2.6 = PFI14
P2.7 = PFI15
I have a LabVIEW VI which generates the "Counter Output" and reads the "Counter Input" frequency. I am seeing weird behavior from the PXI 6229 card. I can test "Path 1" and "Path 2" and the frequency I read is what I generated. No issue there. However, when I test "Path 3" and "Path 4" the frequency measurement is erratic. The readings are two different frequencies repeated over and over again and none of those frequencies are the expected frequency which was generated out of the "Counter Output." If I reset the card, and start by testing "Path 3" and "Path 4" the frequency readings are correct and the erratic behavior is gone. However, when I try to then test "Path 2" and "Path 1" now those lines have the erratic frequency issue. I can continue resetting the card and see same issue. The PFI lines that I test first will always pass.
To summarize:
Steps Taken:
1. Test Path 1 = SUCCESS
2. Test Path 2 = SUCCESS
3. Test Path 3 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
4. Test Path 4 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
5. Reset the PXI 6229 Card
6. Test Path 3 = SUCCESS
7. Test Path 4 = SUCCESS
8. Test Path 3 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
9. Test Path 4 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
I am wondering if Port 2 (P2.0-P2.7) on the 6229 card has certain dependecies and this is why I am seeing issues. I am trying to get around this issue so that I don't have to always reset the card.
Are P2.0-P2.3 (PFI8-PFI11) and P2.4-P2.7 (PFI12-PFI15) treated differently or require different setup? How do I resolve this issue?
Thanks so much!

I have a theory...
The DAQ card follows a policy called "lazy uncommit" wherein the terminal used for the output will continue to be connected to the counter even after the task has completed (until the terminal is needed for something else). So as you run more tests, the counter output will end up driving more lines. This behavior should be easy enough to confirm.
As the DAQ card drives more lines, I'd imagine this affects the actual signal. You could scope it to check, but it sounds like either the rise/fall times are becoming longer or some extra noise is being introduced on the line.
The readings are two different frequencies repeated over and over again and none of those frequencies are the expected frequency which was generated out of the "Counter Output."
This implies you are picking up an extra edge during transitions--this isn't too uncommon if the signal is noisy since there is no built-in hysteresis on the DAQ card. I would expect the measured frequencies to have periods that sum to either the full period or the semi-period of your actual signal (depending on how many duplicate edges are detected).
Suggestions are as follows:
To stop the DAQ card from driving multiple PFI lines, it would probably be easiest to just programmatically reset the device in between your tests (using DAQmx Reset Device). If you can't reset the device (e.g. because you are running some other task that can't be interrupted) then you can instead configure a dummy task that uses the PFI line in question as an input.
To stop the DAQ card from picking up multiple edges during transitions, you should configure a digital filter on the input terminals. If you reset the device it sounds like this might not be necessary... it's up to you if you want to configure this or not.
Best Regards,
John Passiak

Custom scale for counter input?

Hello everyone,
Is it possible to create a custom scale for a counter input? I saw there is a feature to allow input Custom Scale Name to the Channel Property Node. However, when I tried to create a custom scale to input to the channel, I got this error
Error -200212 occurred at DAQmx Read (Counter DBL 1Chan 1Samp).vi:1
Property: CI.MeasType
Corresponding Value: Count Edges
Property: CI.AngEncoder.Units
Corresponding Value: From Custom Scale
Channel Name: CountEdges
Task Name: MyCountEdgesTask
Do you know what is the problem with it? Thank you

How do you have the channel set up? Can you attache the VI's that you are using? Is this a global virtual channel?
Tim
Johnson Controls
Holland Michigan

How to count ONLY fields with a specific value

I modified the code below from the API reference to count combobox fields with a value of "MT" so I could total the number of a specific choice the form user input.
var count = 0;
for (var i=0; i<this.numFields; i++)
var fname = this.getNthFieldName(i);
if ( this.getField(fname).type == "combobox" && this.getField(fname).value == "MT" ) count++;
this.getField("mTurb").value = count.value;
Here's the problem: I tried to use a similar script, modified only slightly from this form, in another total field to tally a different choice made with comboboxes and the script continues to tally the first choice. An example of one of the modified versions of the script is below.
var gcount = 0;
for (var i=0; i<this.numFields; i++)
var gname = this.getNthFieldName(i);
if ( this.getField(gname).type == "combobox" && this.getField(gname).value == "MT" ) gcount++;
this.getField("gPack").value = gcount.value;
I suspect I'm just missing something painfully obvious to seasoned scripters, but I can't seem to figure it out and I need this script to be able to count the number of 9 different options in the comboboxes.

OK, you can use a script like the following as the custom calculate script for the text fields that perform the counts:
// Custom calculate script for text field
(function () {
    // Declare and initialize variables
    var fn, s = "MT", count = 0;
    // Loop through the combo boxes
    for (var i = 1; i < 25; i++) {
        // Determine the current field name
        fn = "M" + util.printf("%02d", i));
        // See if the field value matches
        if (getField(fn).valueAsString === s) count++
    // Set this field value to the count
    event.value = count;
Change the value of the "s" variable to match the item that you want to count. The first and last lines prevent the unnecessary creatio of global variables, which is good. It also makes it easy to transfer to a more general document-level routine, which would be event better, something like:
// Custom calculate script for text field
function getCBCount(s) {
    var fn, count = 0;
    // Loop through the combo boxes
    for (var i = 1; i < 25; i++) {
        // Determine the current field name
        fn = "M" + util.printf("%02d", i));
        // See if the field value matches
        if (getField(fn).valueAsString === s) count++
    // Set this field value to the count
    event.value = count;
You would then call this function from the individual text boxes with the following custom calculate script:
getCBCount("MT");
and replace "MT" with the vlaue you want to count.

6251 Counter input signal

Hello,
I am acquiring pulses which are 0-5V with the counter of the PXI 6251. However, I would like to know if it is possible to acquire pulses that are, for example 0-12V or 0-24V without damage the device. In other words, which is the voltage range for the counter input in a PXI 6251?
thanking in advance,
CJMV

Hi,
You will not be able to use the counter directly but you can setup an analog level trigger for your signals. This will create a pulse that isTTL compatible for you everytime the signal crosses a particular level. Then you can route this into your counter and perform any counter measurements on it. An example is this is shown here where it sets up a level trigger to make frequency measurements.
Alternatively you can purchase an industrial strength digital I/O board such as the USB-6525 but this does not include a counter.
Please let me know if this works out for you.
Message Edited by Abhinav T on 07-06-2007 05:20 AM
Abhinav T.
Applications Engineering
National Instruments India
LabVIEW Introduction Course - Six Hours
Getting Started with NI-DAQmx
Measurement Fundamentals

Encoder position WITHOUT counter input

Question:
I have three incremental encoders connected to my M-Series DAQ board (PCI-6229) that has TWO Counter input channels. I am measuring the position of each encoder. How do I measure the position of the third encoder if I have used-up both counter inputs? Is there a manual way to accomplish this using my older version of Labview (version 7 express)? Any help is appreciated.
-Clarkam1

clarkam1 wrote:
Ben,
I'm on an extremely small budget and can only use the items available to me at present time. That being said, is there no way to use one counter for multiple encoders? Or could an external device be used to count which the DAQ board would read? I appreciate your timely responses. I'm trying to explore all other options.
So do you work for free?
If you are determined to get all three counters going with that device, you have a big challenge ahead of you. I'll try to explain. At teh input of your counters you have signal conditioning that feeds the counter itself. To do the same thing using analog input channels (since all of the counters are already used) you will have to develop code that simulates the signal conditioning, converts the analog to digital (this may sound easy but if you need to implement over-sampling its not) and then do the work of the counter, again in software.
If my customer was forcing this on me I would first review the behavour of the hardware and use it to establish the requirements of my code. So if you do not have an EE background, you will first have to learn the hardware so you can write software that does the same thing.
So if you work for free then you may want to chase down the examples that NI ships for their FPGA targets that implement serial protocols and the like. You may be able to harvest some code and examples from there. If you don't work for free, then you really have to decide if you want to re-invent in software what you can purchase.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Low Pass Filter Counter Input Compact DAQ

Hello,
I need to put a 10kHz Low pass filter on a counter input.
I have a CDAQ 9178
and a 9421 Digital Input module
Acording to the documentation and my own experience I can't enable the filter on the Digital input card.
Is there another way to do this? I need to filter the signal in hardware.
Thanks
Dan

Your filter might work, however it is build to filter power lines, with current rating 6A and powerline voltage. You pay a lot for a box with screw terminals and a lot of copper and high rated capacitors.
Have you tried a simple RC lowpass (costs less than 50 cent, even when purchased in a pharmacy ) ? R=1500Ohm, C=10nF gives a coarse 10kHz first order lowpass. The C fits between the ground and input terminals of your DAQ, the R in the signal line to the input.
Output impedance of your source?
If you explain more of your application, type of signal, we might find other solutions.
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Problem resetting count on read with fp ctr-500 counter

Using the ctr-500 module with a FP-1000. I want to reset the count of a channel on each read. The CTR-500 manual says to selecting "Reset on Read" from the Value menu. I've done that but the counter never resets when I read it. I then tried clicking on "Creat item" under channel attributes in MAX. It creates an item called "Read Reset Mode @Count Input 0" under Data Neighborhood. Added that item to the program and wrote to it with both a 1 and 0, but when I read channel 0 it still will not reset. Obviously, I'm missing something. I would appreciate any help or a simple example so I can get this resolved. Thanks, Mike
Message Edited by mike72903 on 01-31-2008 10:51 AM
Attachments:
reset count1.vi ‏15 KB

Found an example. Thanks anyway

Graphing Encoder Counter Input in LabVIEW Signal Express

In LabVIEW SignalExpress, using a simulated daq system with a counter input, I set up a DAQmx Acquire of an Angular measurement based on a quadrature encoder. Acquiring N samples, I acquired a table of measured values. I would like to plot the results, however, I am not given the option to view the data in any other format. I can plot if I acquire one sample, but that does not allow me to sync the data with the analog input signal I would also like to acquire and view. I had to use an external clock to take the encoder data, so the data is acquired a double datatype. I would like to be able to view in realtime, encoder position with respect to time.

HI,
I want to obtain of this combination of hardware and software a system that allow me acquire a signal of the load cell and the counts of the incremental encoder’s pulses and represent in a graphic the force vs the distance.
The distance is pick up to a incremental encoder in a worm gear that with its movement, move a load cell in a base. the reading of the position is in millimeters.
In this moment, I can only represent the force, the position is only visible in a display, I want to take a samples of the force and the count in millimeters, ten or more times per second and perform a graphic in a real time.
Thank you for your answer
Best regards
Lizardo Laguna

Save counter input data against time

Hello, i would like to know about recording using a write to measurement file.
When i record a data like analog input, at the save file with display the analog data against time.
But when i tried to applied for the encoder, which is using counter input, in the .txt file dont display
the result as analog input. So can someone give me a guide on what to setting on write to measument
file to measure the revolution per minute rotation against time, thanks
Solved!
Go to Solution.
Attachments:
encoder recording.vi ‏180 KB

There is no setting for the Write Measurement File. Your problem is that you are passing a scalar to the function and that scalar has no timestamp information. When you use an analog acquisition, the data type is either a waveform or dynamic data type. Below is one way to add the timestamp information. You also should have a delay or msec wait in your loop. This can be used for the dt information.
Message Edited by Dennis Knutson on 09-24-2007 09:51 AM
Attachments:
Save Scalar with Timestamp.PNG ‏6 KB

Isolated Counter Input onSC2345 with FT01

Similar Messages

Maybe you are looking for