I would only expect afiximprovement that is achievable thru firmware with existing hardware. All of your issues are resolved if you just allow for two mode settings in the utility menu--SAFE and EXPERT or whatever. In the SAFE mode the 50R terminator disconnects whenever the input is overloaded (even at the lower ranges) and AC50R is disabled. EXPERT just gives you a warning and leaves you to fry your scope at will. Or maybe even have a LOCK setting where you need a password to access the 50R menu...
So it's certainly not very attractive to waste resources on something that in the end nobody will use anyway - because the way you have suggested (and the only feasible) is just too much hassle for the operator.
Today I check the "50Ohm behaviour" of an much more expensive scope, in this case a WR9054 from lecroy, appx 12 times more expensive than sds2k+.
First, it got only DC50, not AC50.
Second, when turning to 50 ohms, voltage per division will be limited to 1V/div.
Third, carefully increased the (DC-)voltage above the mentioned maximum of 5V, nothing will happen, increased to 7.5Vdc.
No warning, no switchback to 1M.
The instantaneous power in the resistor is V2/R. Would you guys be ok to lose a maths channel (ie use existing resources) to track this? Instead of having an artificial/compromise limit on the Y axis, have a limit on the time axis instead, eg 20ms total sample time? Then just put a small amount of logic in to automatically trip out if the mean V2 on the input BNC exceeds a preset value. You could also have a Vpeak threshold value if you wanted to, and trip on that too, just like a "real" circuit breaker.
While I appreciate that its not always possible to put comprehensive protection into high end instruments, because it can mess up the readings, it seems to me that having protection 'coverage' in a general purpose bench oscilloscope is something that's worth spending effort on. With Siglent philosophy of putting as much function as possible while being thrifty with the hardware costs, the software approach would seem to be a good, achievable match.
In a lab setting, especially in a training/university lab I imagine it is reassuring for the demonstrator to be able to say -- "don't worry about experimenting with the controls, you can't break anything".
And respectfully, "" In a lab setting, especially in a training/university lab I imagine it is reassuring for the demonstrator to be able to say -- "don't worry about experimenting with the controls, you can't break anything"." is exactly the wrong thing to say to university students. That is kindergarten "positive reinforcement" attitude. That is preschool stuff. In university, they better be taught to know exactly what will happen if they turn that knob... They are not playing with legos, they are supposed to be engineers and scientists... They came to university to learn to think and understand...Not randomly try stuff until it either works or explodes...
They are not playing with legos, they are supposed to be engineers and scientists... They came to university to learn to think and understand...Not randomly try stuff until it either works or explodes...
They are not playing with legos, they are supposed to be engineers and scientists... They came to university to learn to think and understand...Not randomly try stuff until it either works or explodes...
Unless they are training for Quality Assurance!
I expect every life critical system to be tested in all work/explode scenario as practical possible.
They are not playing with legos, they are supposed to be engineers and scientists... They came to university to learn to think and understand...Not randomly try stuff until it either works or explodes...
If you run the scope with 7.5V DC-input for a long time, the thermal protection should eventually kick in, but you might need an even higher voltage to achieve this.
Caution: The maximum input voltage depends on the input used. Limits are displayed on the body
of the instrument. Whenever the voltage exceeds this limit, the coupling mode automatically
switches to GROUND. You then have to manually reset the coupling to its previous state. While the
unit does provide this protection, damage can still occur if extreme voltages are applied.
Probe
.....
This state I haven´t reached.....Mhh...Should I try it..
So the SDS1204X-E has "Sample Logging" and "Measure Logging" built in, and NTP... I wonder if the 2000X Plus will ever get these ?
I found a small bug, there is a timezone setting option but it doesn't work ? I cannot get it to bring up any timezones.
So the SDS1204X-E has "Sample Logging" and "Measure Logging" built in, and NTP... I wonder if the 2000X Plus will ever get these ?
I found a small bug, there is a timezone setting option but it doesn't work ? I cannot get it to bring up any timezones.Email sent.
Nov 19 12:32:00 frodo dhcpd[23534]: DHCPOFFER on xx.yy.70.130 to <Scope-MAC> via xx.yy.70.1
Nov 19 12:32:00 frodo dhcpd[23534]: DHCPREQUEST for xx.yy.70.130 (aa.bb.117.101) from <Scope-MAC> via xx.yy.70.1
Nov 19 12:32:00 frodo dhcpd[23534]: DHCPACK on xx.yy.70.130 to <Scope-MAC> via xx.yy.70.1
Nov 19 12:32:00 frodo dhcpd[23534]: Added new forward map from sds2104x.mydomain.org. to xx.yy.70.130
Nov 19 12:32:10 frodo dhcpd[23534]: reuse_lease: lease age 10 (secs) under 25% threshold, reply with unaltered, existing lease for xx.yy.70.130
Nov 19 12:32:10 frodo dhcpd[23534]: DHCPOFFER on xx.yy.70.130 to <Scope-MAC> via xx.yy.70.1
Nov 19 12:32:11 frodo dhcpd[23534]: reuse_lease: lease age 11 (secs) under 25% threshold, reply with unaltered, existing lease for xx.yy.70.130
Nov 19 12:32:11 frodo dhcpd[23534]: DHCPREQUEST for xx.yy.70.130 (aa.bb.117.101) from <Scope-MAC> via xx.yy.70.1
Nov 19 12:32:11 frodo dhcpd[23534]: DHCPACK on xx.yy.70.130 to <Scope-MAC> via xx.yy.70.1
Nov 19 13:02:00 frodo dhcpd[23534]: Removed forward map from sds2104x.mydomain.org. to xx.yy.70.130
I just finished the "Options" on my newSDS2104X PlusSDS2504X Plus.
I haven't upgraded fw to latest yet, so i'm still on 1.3.9R12