Jump to content
  • 0

Logic Analyzer - Data Acquisition on Trigger - Files saved show no triggered data


Slawek

Question

Using Logic Analyzer on an AD2, I am reading six digital inputs, and one I2C bus and have enabled logging to CSV file upon a "triggered acquisition".  I have gotten five triggered acquisitions over the course of two days but the CSV files show no digital transitions or I2C packets at all.

1) Why is this happening?
2) Can I somehow preview the the prior captures in Waveforms?

This is very important for the project I'm working on.

Version 3.8.2 64-bit Qt5.6.3 Windows 7

WF_Setup.png

acq2019-04-04 10.07.21.4.csv

Link to comment
Share on other sites

7 answers to this question

Recommended Posts

Hi @Slawek

The trigger positions in your capture is at 10ms. You are capturing from 7 to 12 ms after the trigger event and I see no activity on the I2C lines.

You can look back the last 10 captures (by default) using the Buffer option. The highest number is the last capture.
image.png.c72c836d10423c21b2b95a2ad1c2f05e.png

Link to comment
Share on other sites

Hi @attila. I'm pretty confident I had "Position" field at 0s prior to arming during my previous log attempts. It just happened to be at 10.12ms in my screenshot due to me searching around for the transition edge. My I2C bus is quiet.

The csv I attached shows differently, but I've had csv log files that go from -0.0007 to +0.004415 seconds which suggests that the trigger point (0.0000 seconds) is where an edge would be present. If your output file saves times relative to the "Position" setting, then that is very misleading, it should be absolute from the time of trigger.

I stopped the run and went down through the buffer by using the down arrow. The capture on the screen only decrements by 10ms (at 500us/div, my window is 5ms). You seem to suggest it'll show previous captures that have occurred in the past which in my case can be  many hours. How do you define capture?

buffer_change_only_ms.png.87dd606c687928adb7c41b3dc7bf7915.png

Link to comment
Share on other sites

I know, that's what I said in my prior edited comment.

On 4/5/2019 at 8:29 AM, Slawek said:

The csv I attached shows differently, but I've had csv log files that go from -0.0007 to +0.004415 seconds which suggests that the trigger point (0.0000 seconds) is where an edge would be present.

If in the CSV, there is no 0->1 or 1->0 transition at time = 0, then this is a bug of some sort.

Is the low level hardware telling the software there is a trigger, but it cannot appropriately send the data upstream to the software?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...