"Use "REBOOT" instead of RST to actually reset the scope (power cycle it)"
*RST is what is needed in this case. Doing a reboot, keeps the scope in its current state (sans the Fine VDIV bug acknowledge by Siglent). Rebooting also causes the scope to loose connection with the VISA driver/program. I am using Agilient connection expert. I have to refresh the interface after a reboot command in order to connect to the scope again. It's funny, a reset doesn't cause that.
"All of the statistics can be accessed for all channels even when not on screen with the PAVA? command. E.g. C1:PAVA? PKPK will grab thr peak to peak value"
Yup, I missed that on page 107, I believe, of the manual.
"To clear all statistics use the PACL command"
This does not reset the Statistics Count, at least for me. That's in the Pass/Fail section of the manual. I do not use any pass/fail features.
"To setup custom measurements you can use PACU"
Yes, they show up in the order that they were selected. I was just upset that *RST already created two measurements for you. There doesn't appear to be a away to remove measurements once created. On the scope itself, you can do that by press "Clear". There doesn't appear to be a SPCI command to do this. The also isn't an SPCI command to press the "Statistics" button to turn on statistics.
"As for determining when the scope is back from a reset. That would just be polling IDN when it responds the scope is able to measure."
Doesn't work, causes a VISA TimeOut error to pop-up from the visa driver. Unfortunately, On Error, can not intercept visa errors. Some commands don't cause that.
"There is also a switch command for statistics. But not sure its relevent to you PASTAT"
Yes, that works! "PASTAT ON".
"Also not sure if its helpful but you dont really need to rate limit yourself with this scope. The SCPI buffer size is about 700K characters. So you can throw it pages of commands and it will just work through them."
Unfortunately, while the scope is resetting, VB does know it is resetting and keeps sending command. Most commands are lost and not in that command buffer. Right now, I am using a Sleep(4000) command after issuing the "*RST" command. It only has to reset the scope one time, when the program/utility first loads so it not a real big deal, just not as efficient as it could be.
Thanks kindly for the response,
Dave