Products > Test Equipment
SPD3303X-E SCPI Interface issues
<< < (7/8) > >>
KE5FX:

--- Quote from: HendriXML on June 16, 2020, 08:02:34 am ---I'm not sure wether it would help (it's been a while). Like I said the software state is changed by the commands, the hardware syncing seems to need a delay. I know this because I did send a query to the device right after to check its software state. The trick would haven been to do that until it would match the required one. But that surprisingly fails.

Speaking of "definitely wrong" to bypass faulty behavior sounds a bit condescending, especially when no information is given about what really goes faulty. I agree it is wrong to have to add delays, but if its the only way, it can't be wrong at the users side.

--- End quote ---

*OPC? means OPeration Complete.  If it returns before the operation is complete -- meaning before the hardware actually carries out the foregoing command(s) -- it's a firmware bug, and should be reported as such.

Not condescending, and not a matter of opinion, but part of the standard.

It's true that there's an equivalent ESR bit, but unless you need to poll some other status bits, I'm unaware of any benefit to issuing *OPC;*ESR? rather than just *OPC?
tv84:

--- Quote from: KE5FX on June 16, 2020, 12:56:05 pm ---It's true that there's an equivalent ESR bit, but I'm unaware of any benefit to issuing *OPC;*ESR? rather than just *OPC?

--- End quote ---

I could analyse in greater detail but I don't think it's worth it.

One thing is certain, Rigol uses only *ESR? verification when executing their calibration scripts.

Edit: Reading the standards page that you referenced, it's perfectly clear that we are talking about different bits in the Standard Event Register.

OPC - deals with bit 0   (previous instructions concluded)
ESR - deals with bit 3 and 4  (error in previous instruction)

So they are complementary instructions.
KE5FX:

--- Quote from: tv84 on June 16, 2020, 12:59:44 pm ---OPC - deals with bit 0   (previous instructions concluded)
ESR - deals with bit 3 and 4  (error in previous instruction)

So they are complementary instructions.

--- End quote ---

They don't do a good job of describing it, but bit 0 of the *ESR? query will go high when all operations are complete, including an *OPC command.  Rohde & Schwarz's app note is a lot clearer (see page 12).
HendriXML:
I think I missed the above discussion...

Does the above mean that checking the ESR status solves the timing issue? That would be great!

I would also like to read the channel 3 output status.

Using SYSTem:STATus? only gives the status of CH1 and CH2, not CH3

If someone has a solution for that, that would be great too!
rfclown:
Old thread, but thought I'd put something in here that I had to figure out to communicate SCPI over ethernet with a Siglent scope (don't remember model, 4 channel). I communicate with instruments using LabVIEW's VISA Read and Write vis. I discovered that I had to put the VISA vis in synchronous mode. It isn't even a wired option of the vi. You have to right click on the "VISA Write" or "VISA Read" vi and select either "Do I/O Synchronously" or ""Do I/O Asynchronously". Asynchronous is the default, and the Siglent scope didn't like it. In all my years of remote instrument control with LabVIEW (about 30 years) I've never run across this one. I didn't know it existed. I've got old HP gear that I have to use a different GPIB "mode" from the default, but never heard of the synchronous thing.

It was in the Siglent manual to use synchrounous. This was at work, so I don't have the scope or the manual in front of me to double check this. I am really disappointed in the remote operation of the scope. I've worked with many different instruments, and reading the waveform is the least straight forward of anything I've come across (getting all the parameters correct for scaling and such). If it comes time to buy a similar type scope for home, this would be my biggest negative on the Siglent. I've been ok with the basic manual operation of it.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod