Afonso Teles

Hi Anirudhh,

eScope uses port 81, which is often blocked by routers and other IT devices, I'm pretty sure that's what's causing that issue.
I would suggest making sure the scope and PC are on the same router (routers will often have port blocking). If that doesn't work, you can try using a peer to peer ethernet connection.

Hi Anirudhh,

You can choose the format of the data the curve? returns. If you set it to return 1 byte per point in an integer format then it should be fast (depends on your connection of course), other modes like ASCII and floating point can take significantly longer.

If you configure it properly it should not take anywhere close to 1 minute for 1Mpts.

Hi Anirudhh,

To stop the acquisition you'll want to use acquire:state stop.

To transfer waveform points, you'll want to use curve? .  The format isn't .csv or anything like that, it's essentially just raw points (either ASCII or binary).
It is also possible to save a waveform as a file and then "download" it using filesystem:readfile.

From what you're describing it sounds like you might want to use the Act on Event function that's available on the instrument to automatically save waveforms.

Hi Daniel,

I was able to load your wfm file into ArbExpress and then save it a scope AFG .csv file and that successfully loaded onto the scope AFG.
The waveform looked a bit different from what I expected and I'm still working on figuring out why that is, but perhaps it's a good start.

Hi Julius,

That's an unusually short lifespan for the instrument, I will be contacting you through email to see if we can still honor the warranty or resolve this in some other way.

Hi Julius,

That's correct, it would have to be sent in for repair.
It might be covered under warranty, it's worth checking: https://www.tek.com/en/services/test-equipment-repair/warranty-status-search

Hi Julius,

I am not aware for a mechanism that would cause this on the TBS2000. It's possible it's a hardware failure from aging.

Hi Julius,

Is it possible you installed the TBS2000B firmware instead of the TBS2000 firmware?
This is a known problem and the only solution I know of is to send it in for repair.

Hi,

Unfortunately we will not be able to help you get that code as it's against our company policy.

I wish you luck in your repair!

Hi Sarmad,

I don't believe this is a problem with SignalVu but more with your Python installation.

Do you get the same error if you call pyvisa on a bare Python installation from the terminal?