trigger oscilloscope lt354m

[giacomourbini]

I want to work with the remote control of the scope but I really don't know how to do that. I don't know why you are so rude to me. I'm still learning to work with labview.

[Dennis_Knutson]

Sorry of I came off as rude but you have ignored or dismissed my suggestions. You haven't downloaded the correct manual. You keep complaining about a lack of LabVIEW knowledge but from my point of view, it's s lack of instrument knowledge. You registered back on March. That is plenty of time to take several of the free tutorials.

[giacomourbini]

Actually I downloaded the manual you suggested me and as I already told you I have also tried with the OPC? query but it didn't solve my problem. Probably I didn't do that in the correct way but I don't know how to do that. And i didn't also find a command that tell me when the scope get an aquisition in the manual you gave me.

[giacomourbini]

---

billko ha scritto:

I downloaded the drivers for this device. I've attached a proof-of-concept version of your try.vi. Your attempt follows closely the example provided, but has no indicator on the waveform output! I replaced your loop exit control logic with a simple stop button for now, and placed a simple indocator on the output to verify that you are getting something. (I have no idea if this even works.)

These drivers are very old and cumbersome. I'm uploading more recent drivers that I found. They are at least in lvlib format. They also include extensive example, of which you might even be able to use the "loop" one without modification.

---

The drivers don't work for this instrument, sorry.

[billko]

I'm sorry for uploading the wrong drivers.  Did you get to try the VI I also uploaded?

[giacomourbini]

Yes, I did. But unfortunately it works like mine. Because also if the values of the waveform change only when the trigger comes, inside the while loop they "change" every iteration and so at the end I have a very long file.

[billko]

---

@giacomourbini wrote:

Yes, I did. But unfortunately it works like mine. Because also if the values of the waveform change only when the trigger comes, inside the while loop they "change" every iteration and so at the end I have a very long file.

---

Well... that's exactly what I would expect.  A LOT of data.  Then I guess I'm not understanding what it is that you wanted.  To me, it seems to be doing exactly what you wanted to do.  Keep getting data until you tell it to stop.  Is there something else that you need?

[giacomourbini]

I wanted to save data only when the trigger comes and not every iteration of the while loop. Anyway I think I have solved myself but thank you so much for your help. I really appreciated that you spent time for me.

[billko]

---

@giacomourbini wrote:

I wanted to save data only when the trigger comes and not every iteration of the while loop. Anyway I think I have solved myself but thank you so much for your help. I really appreciated that you spent time for me.

---

That's what I was hoping would happen, but I guess it didn't work out the way I had envisioned it to.  It's hard when you don't have the equipment in front of you.  Sorry I couldn't help you further.  If you still need help , though, please post what you have and I'll be happy to confuse you!  😄

[giacomourbini]

i know it's hard working without instrument and that is the reason why I appreciated your help more.

Thank you again