SCPI Command(s) to read back waveform Search on MSO456 Series

Hello,<br> <br> If I setup a waveform edge search, how can I readback the the result or pin point a particular result?<br> <br> Maybe for example, if I want to read the time location of the last rising edge found from a waveform search?<br> <br> I can't seem to find any SCPI commands that lets me index through a result array or transfer a result array over to the host computer.<br> <br> Regards,<br> Mike

Hi Mike,<br> <br> First you should create a results table with the search results with the command <code>searchtable:addnew</code>.<br> Then, you can save this table to a file with <code>save:eventtable:searchtable</code>&#160; which you can then transfer to your computer with <code>filesystem:readfile</code> .<br> <br> This will give you an index of all the search hits found and their locations in time.

Hi Afonso,<br> <br> Awesome, let me try this out.<br> <br> Also, I have to apologize, I should have lead with my use case first before diving straight into asking about waveform search results.<br> <br> I hope you have some other suggestions before I try the search table functions...basically, I need to measure time delays for my HDMI signals, but I am noticing the delay function is giving me erroneous readings depending on the waveforms.<br> <br> I have 2 main from sources I am measuring from, HPD and DDC SCL.<br> When I am measuring from HPD Falling , I noticed if I set the 'to' waveforms (SCL, SDA, TMDS) to search backwards, the problem goes away<br> <br> However, if I measure from DDC SCL (should be last output, so look starting from the right) to compare it against the 'to' waveforms, I cannot get a good measurement. I think this is due to multiple edges occurring in both pre and post trigger.<br> <br> I can't seem to get this to work with the existing measurement system and have to use edge search to find the last edges of both 'from' and 'to' waveforms to calculate the timing difference.<br> <br> I am not sure if you have any suggests I can try before dealing with the search table solution? Preferably, if I can get away without setting the HPD measurements to backwards that would be a bonus as I am trying to main interoperability between different scope models and makers and some scopes don't have a backwards 'to' search function.<br> <br> Regards,<br> Mike<br> <br> &#160;

Hi Michael,<br> <br> This is becoming a rather complex question, it would be best to have your field applications engineer help you directly.<br> You should have gotten an email from him on this matter.