Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

First point error

Hello!
I have a problem when I acquire with a DAQPad 6070E and the S&H SC-2040E.  The acquisition is correct except the first point. I am triggering with a encoder in channel 0. In the text file below you can see this effect.
Regards and thanks in advance.

Jorge Arroyo
0 Kudos
Message 1 of 11
(4,478 Views)

Hello,

can you give me more details about the error you are seeing? I have opened the .txt file but I don't know which is exactly the error. It appears a lot of numbers in columns

How many channels are you acquiring? Which type of trigger are you using? What type of signal does the encoder give? Are you acquiring the encoder signal as well?

In terms of soft, which version of LabVIEW are you using? Can you attach the VI to see how you are doing the programming?

Thanks and regards

crisR

0 Kudos
Message 2 of 11
(4,451 Views)
Hello CrisR. Thanks for reply!!
The txt file have two channels ordenate in colums. The first one is the encoder, (between aprox 0 y 5 V) and the second is the pressure of one cilynder from a engine. I am acquiring with LV 8.2 and Traditional NI-DAQ. I am doing an analog triggering acquisition with the encoder channel as trigger.  I think the problem can be in the "AI Read" VI, in the input called "read/search position (from mark)". In "position" I have "relative to trigger point", and I think I must change to another one, but I don't know which would be the correct (maybe "relative to end of data). I am trying to begin the acquisition when the trigger exceed 3,5 V.

Thanks and regards.

Jorge Arroyo
0 Kudos
Message 3 of 11
(4,445 Views)

Hello,

now, I am seeing correctly the two columns because I have opened it with Notepad instead of Internet Explorer.

Well, I think your answer resides on the LV Help, precisely in the AI Read help.

read/search position defines where you want to read from the acquisition buffer. For conditional retrievals, read/search position specifies where to begin the search in the acquisition buffer. The VI adds read offset scans to the mark specified by position to determine the starting point for the read. You express read offset in scans. The read offset parameter can be negative. The default setting and input is 0.

position indicates which input buffer reference mark is the read reference point. This reference can be the read mark, the beginning of the buffer, or the most recently acquired data (end of data). Initially, the read mark points to the beginning of the acquisition buffer. As you retrieve data from the buffer using this VI, LabVIEW increments the read mark to point to the next block of data to be read.

0 Do not change the position setting (default input).
1 Relative to the read mark (default setting).
2 Relative to the start of buffer.
3 Relative to the end of data.
4 Relative to the trigger point. This mode is valid only when the buffer completes.

read offset—The VI adds read offset scans to the mark specified by position to determine the starting point for the read. Refer to the description of the AI Buffer Read VI for more information.

What happens if you don't cable any input to read/search position input parameter ( relative to read mark and 0 )? I think you shouldn't have any problems and it is the normal usage.

regards,

crisR

 

Message 4 of 11
(4,442 Views)
Hello crisR. 
Thank you very much.
I'm going to disconnect this input and I think it will work properly.

Thanks & Regards

Jorge Arroyo
0 Kudos
Message 5 of 11
(4,437 Views)

Hello,

I hope so as well.

Let me know when you do the trials. Are you doing a finite acquisition or a continuos one?

Regards

crisR

0 Kudos
Message 6 of 11
(4,437 Views)
Hello crisR.
Finally, with this VI I have solved my problem.  I create a buffer of n (number of samples) + 1, and I acquire only n samples. In "read/search position" I configure "relative to end of data" with 1 of offset, to avoid first sample be acquired. If I disconnect this input I obtain the first point error.
Please, let me know if there is some error.
Thanks & Regards

Jorge Arroyo
0 Kudos
Message 7 of 11
(4,426 Views)


Mensaje editado por Jarr

0 Kudos
Message 8 of 11
(4,414 Views)
Hello again.
I have found another problem in the signal. As you can see in pictures I acquired the two channels (encoder+pressure). In some encoder pulses the value is over 5 V (picture 1). This is due to a special characteristic of this encoder. There is no problem in the encoder signal with this values. But if you see the pressure signal, you can see ghosting(?). I thought it is a impedance problem, but when I had couple between the encoder channel and the pressure channel, the pressure rose some mV when the encoder rose, and fell some mV when the encoder fell. This problem is different, the couple is in just one point. Now, we think it could be a problem in SC 2040, but we don't know of to solve it.
Have you any idea??

Thanks and Regards

Jorge Arroyo


Download All
0 Kudos
Message 9 of 11
(4,412 Views)

Hello,

taking a look into picture 2, it seems pressure signal goes down when encoder goes up. You are saying the opposite, aren't you?

Try with different lower sampling rate values? What does it happens?

Regards

crisR

0 Kudos
Message 10 of 11
(4,368 Views)