Afonso Teles

Hi Carrie,<br> <br> I've seen such a bug previously but I believe it has been fixed.<br> What firmware version are you running? If it's not 2.0.3 then please update and see if the problem remains.

Hi Xiang,<br> <br> If you're using pyvisa, you can just use <code>read_raw()</code> with no arguments and it will automatically read the whole file and stop, there's no need to set the number of bytes to read.<br> And in fact the argument to <code>read_raw()</code> isn't the number of bytes to read, it's the chunk size to do that reading in, different things, as documented here: <a href="https://pyvisa.readthedocs.io/en/latest/api/resources.html#pyvisa.resources.SerialInstrument.read_raw">https://pyvisa.readthedocs.io/en/latest/api/resources.html#pyvisa.resources.SerialInstrument.read_raw</a>

Hi Clark,<br> <br> Let's say you have two ground referenced signals, one that goes all the way up to +4.25 V and another to -4.25 V and we're measuring between the two.<br> This result in 8.5 V differential voltage, while staying below the 7 V common voltage limit.<br> <br> The dynamic range of 8.5 Vpk-pk is just restating the differential dynamic range of +- 8.5 V.<br> <br> The scope should give a warning if you exceed the differential dynamic range, but I don't believe the same is true for common mode voltage.<br> <br> +-25 V is the maximum non-destruct common-mode voltage, below that it shouldn't be damaged but also might not operate properly.<br> <br> For specifications I would suggest going to the specifications and performance verification manual instead of the user manual: <a href="https://www.tek.com/en/manual/low-voltage-differential-probe/tdp1500-differential-probe-low-voltage">https://www.tek.com/en/manual/low-voltage-differential-probe/tdp1500-differential-probe-low-voltage</a>

<p>Hi Xiang,</p> <p></p> <p>My bad, the channel 1 badge is right there, of course it's a channel 1 measurement.</p> <p></p> <p>From my testing, the frequency (and period) measurements only use the mid level and hysteresis, the high and low level don't seem to affect it.</p>

Hi Xiang,<br> <br> It's unclear which channel your measurement is working on, but I will assume it's channel 2.<br> The problem is that there are different frequencies in your signal depending how you measure it. You have to be clear about what you want to measure by manually setting the reference levels in the measurement configuration tab, preferably to absolute levels.

Hi,<br> <br> This seems like an issue best handled by your local support team, so I've reached out to them and they should be in contact with you briefly.

Hi David,<br> <br> After querying the event status register, you can see the warning message that generated that error by doing <code>ALLEV?</code> .<br> That should give you more information on which command is giving you trouble. You could also query <code>*ESR?</code> after every write command, which is what I do in my own scripts with a <code>write_safer()</code> function I create for that purpose.<br> &#160;

<p>Hi Carrie,</p> <p></p> <p>This appears to be a problem with the Siglent function generator that Siglent itself can't offer a fix or workaround for, so I don't think I can do much more to assist you here.</p>

<p>Hi Erik,<br> <br> By default Excel does not show all the digits for very long numbers, you have to manually increase the displayed digits. I've attached a picture of the toolbar button where this is usually done.</p> <p></p> <p>If that doesn't solve it then I would ask if you could attach the .csv file here so I could examine it more closely.</p>

Hi Jingru,<br> <br> As Alan correctly said before, <code> CH&lt;x&gt;: CLIPPing&#160;</code> is used to check if a channel is currently clipping.<br> Your problem is slightly different, your channel is not clipping when you send the SCPI commands to get the measurements but it was previously clipping during the last acquisition.<br> <br> For this reason the <code>CH&lt;x&gt;: CLIPPing</code>&#160; command won't work for you, instead you should, after querying the mean of your measurement, query <code>*ESR?</code> which will return a value of 16 (bit 4) if there was an execution error (described on page 3-15 of the programmer's manual) and you can then see that error message by doing <code>ALLEV?</code>.