From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Reverse data output from Agilent 3458A

I'm taking 500 sub-samples of a 500mS ramp waveform from a function generator with the attached vi, and the data output is reversed in time. That is, the data as displayed on the waveform chart shows the TRAILING edge first - a time-mirror image of the actual waveform captured. I thought this had to do with LIFO/FIFO, so I forced FIFO, but it doesn't help. What must I do to get the proper time-sequence data from the DMM?

 

Can't seem to attach my vi , but it's identical to the Labview sample Agilent 3458 Acquire Multiple Measurement.vi, with the addition of a VISA Write MEM FIFO.

 

 

0 Kudos
Message 1 of 12
(3,612 Views)

AGAIN attachment didn't work. I'll try again.

0 Kudos
Message 2 of 12
(3,611 Views)

How are you getting the data?  Is it just an array or a waveform (with data, dt, and T0)?  If you just have the array, use Reverse 1D Array and be done with it.  If you have a waveform, then use the In Place Element Structure to get the Y, reverse the array, and write back to the Y.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 12
(3,579 Views)

@hammer3 wrote:

AGAIN attachment didn't work. I'll try again.


 

 

See if this link applies to you.

 

0 Kudos
Message 4 of 12
(3,564 Views)

I just turned off compatibility & let's see if I can attach the vi now... AND hope someone can address my original question.

0 Kudos
Message 5 of 12
(3,554 Views)

Wrong vi. This is the original.

0 Kudos
Message 6 of 12
(3,553 Views)

Ok, the data just comes out as an array.  Well if you know that the data is backwards, just use Reverse 1D Array (as I already stated) to flip it back.

 

I remember working with that DMM before.  I never found a way to get the data to come out like a FIFO.  That's just the way the instrument works.  Reverse the array and be done with it.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 7 of 12
(3,548 Views)

Clearly that will work as a  work-around or band-aid, but I was hoping to find someone knowledgeable to explain WHY it's happening. 

0 Kudos
Message 8 of 12
(3,530 Views)

Hi Hammer3,

I reviewed the code and was not able to find anything explicit that is reversing the data. Perhaps this happens because of how the instruments sends the data out. You can verify this by using the VISA test pannels in MAX to see how it receives information sent from the instruments. At the base of all of the subVIs used to read measurements is only a VISA read. Again, I don't see anything that would be flipping the data. Hopefully this helps, but at least you always have the option of just reversing the data if you see that it comes out in reverse order. I hope this helps.

Regards,

Michelle G
Applications Engineering
National Instruments
0 Kudos
Message 9 of 12
(3,507 Views)

It works that way becasue some FW engineer at HP wrote the dump routine that way.  LIFO/FIFO just sets which samples get overwritten when the buffer fills. 

 

The best explaination I ever came up with- and it has to do more with using the device than reality- is the operator usually stars with a input near 0 and triggers a digitization start.  when reading back its often likely that a value of 10 ADC counts can occur very near the trigger.  If you are using Term Chars to end your reads.  Yup you just read that "0x0A" and left all the interesting data in the unit.


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 12
(3,498 Views)