With the new firmware installed, the autocal behaves the same.
You can turn off the autocal but it is not sticky. Once the scope has been power cycled, it will be enabled. They will store all of the settings as defaults on power down but this function is not included. My guess is customers would bitch about the inaccuracy. They may be some INI or registry setting that would overwrite how the autocal works but I have never seen anything published for it.
What's to complain about, you low-life who dared to (AFAIK) never buy TME worth millions of $ from them, and who, to make things worse, dared to "infest" many with a "I like LeCroy" virus?!
I'm an example of your "victims". I always took you to be someone who again and again, intentionally or not, showed a LeCroy scope to be something nice and desirable.
When I bought the first one, there really was nothing brand new with a decent BW and in my price range. I was familiar with the brand and bought a used one. That scope is has many features that you would only find in a high end scope still today. Then again, there are things a cheap modern scope can do that this scope can't. Consider math functions were important for physics. Modern scopes have a lot of digital decoding for example.
We don't appear to do much in the states and guessing the high end market dried up. Companies needed to find some way to be profitable. As they shift their focus to higher volume, lower end test equipment and rebranding, hard to say how it will work out.
On a more serious note: situations like this one are appalling to me. How a largish corporation dares to clearly not give a flying f_ck about a grown up man/customer, no matter whether direct or indirect, who (AFAIK) never uttered anything in any way unfair about them.
One more reason for us to hope and wait for somewhat equivalent alternatives from Siglent and possibly others. And @Siglent, pay attention! There's an important lesson to learn here. Stay the way you are, continue to listen to customers and to treat them well and fair!
A few years ago, a member here had provided details on how to defeat the licensing with their older X-Stream software. There were some comments about LeCroy not letting that slide as they still used that software with some of their current products. And they make money on those licenses. I suspect at least some of their reluctance to remain more open was due to this little episode.
Not unexpected the 5 GHz probes are not listed as an accessory for 2 GHz scopes as the 2.5 GHz active probes cover this range.
Not unexpected the 5 GHz probes are not listed as an accessory for 2 GHz scopes as the 2.5 GHz active probes cover this range.
Turn it whichever way you want, incl. - probably correctly - assuming that I'm sometimes stupid.
But that won't change the fact that I won't consider Siglent active probes a day earlier then when they have a "probe" section in their "product" main menu.
Although I like Siglent a lot, I really do.
With the new firmware installed, the autocal behaves the same.
You can turn off the autocal but it is not sticky. Once the scope has been power cycled, it will be enabled. They will store all of the settings as defaults on power down but this function is not included. My guess is customers would bitch about the inaccuracy. They may be some INI or registry setting that would overwrite how the autocal works but I have never seen anything published for it.I'm torn on this one.
Like you I wish for total control and anything not required for a quick measurement need have the functionality to be set to OFF and remain this way after reboot.
The more serious user of course knows an instrument needs to get to temp equilibrium before taking precise measurements but to have LeCroy holding their hand seems a little OTT just so they won't get complaints of system performance when the scope is still cold.
Do you have a User definable Default to change this behaviour with a single button press immediately after boot ?
In the end Lecroy scopes like these aren't made to be used as daily drivers. These are to be considered data acquisition & signal analyses systems in 1 box for which accuracy and repeatability of measurements matters most. Sure you can use them as an oscilloscope up to some point but there are limits due to the relatively simple architecture (completely seperated acquisition & processing logic) Lecroy used.
os·cil·lo·scope ä-ˈsi-lə-ˌskōp
ə-
: an instrument in which the variations in a fluctuating electrical quantity appear temporarily as a visible wave form on a display screen
With the new firmware installed, the autocal behaves the same.
You can turn off the autocal but it is not sticky. Once the scope has been power cycled, it will be enabled. They will store all of the settings as defaults on power down but this function is not included. My guess is customers would bitch about the inaccuracy. They may be some INI or registry setting that would overwrite how the autocal works but I have never seen anything published for it.I'm torn on this one.
Like you I wish for total control and anything not required for a quick measurement need have the functionality to be set to OFF and remain this way after reboot.
The more serious user of course knows an instrument needs to get to temp equilibrium before taking precise measurements but to have LeCroy holding their hand seems a little OTT just so they won't get complaints of system performance when the scope is still cold.
Do you have a User definable Default to change this behaviour with a single button press immediately after boot ?
It's a scope and 8-bits at that. Precise measurements may be a bit of a stretch under the best case.
As for the single button, not that I am aware of. You maneuver to the menu, select a tab, disable the autocal. Typically, turn the scope on. Maybe after 10 minutes you set it manually, assuming you remember. I'm not sure how you could have your cake and eat it too. I can understand why they chose to make it work this way but I can't understand why they don't offer other options. It really only comes into play when looking at slow signals and forgetting to disable that feature after power up. If it had some intelligent mode where if the temperature has changed and there are no trigger events for some time, manually trigger. Of course then I would be pissed I lost my data I captured on the screen.
Not unexpected the 5 GHz probes are not listed as an accessory for 2 GHz scopes as the 2.5 GHz active probes cover this range.
Not unexpected the 5 GHz probes are not listed as an accessory for 2 GHz scopes as the 2.5 GHz active probes cover this range.Is the 2.5 GHz figure probe-only bandwidth or bandwidth at the probe tip with a supported scope? If the former, then connecting a probe with 2.5 GHz -3dB bandwidth to a scope with 2 GHz -3 dB bandwidth won't give the full 2 GHz bandwidth, and there is a valid argument for using a higher bandwidth probe to maximize the bandwidth with that scope.
Good question yet as always RTFM.
P17
https://siglentna.com/wp-content/uploads/dlm_uploads/2021/11/SAP1000_SAP2500_UserManual-EN01A.pdf
How much time does your autocal consume ?
I dug out my SDS6204A of which I was darn sure I could disable the QuickCal but now it seems not.
@~10m a 2s QuickCal is performed.
... Autocal on this scope takes maybe 1 - 3 seconds. Basically a life time.
The most common oscilloscopes have a tight coupling between the acquisition and generating the visible traces (rendering). This allows for dealing with deep memory in a faster way, doing hardware decoding and rendering acquisitions into traces much faster. The way Keysight has constructed their Megazoom Asic based scopes is the complete opposite of how Lecroy oscilloscopes are setup. You'd say they are both oscilloscopes but they are different like a Philips and Torx screwdriver are different.
Good question yet as always RTFM.
P17
https://siglentna.com/wp-content/uploads/dlm_uploads/2021/11/SAP1000_SAP2500_UserManual-EN01A.pdfUnless the F****** manual is misleading. Can you explain, particularly for the SAP1000, how a 1 GHz bandwidth probe on a 1 GHz scope can have a 1 GHz bandwidth at the probe tip, while it should be -6 dB down at 1 GHz by the definition of bandwidth being the -3 dB point? Either the probe-only bandwidth is overly conservative (the minimum guaranteed bandwidth must be well above 1 GHz), or the bandwidth at the probe tip is way optimistic. If the "1 GHz" probe is actually guaranteed to be > 1.5 GHz probe-only, that would be useful information when using the probe with a scope with a wider bandwidth.
Maybe you missed this bit from the Warranted characteristics table:
Bandwidth (with scope) 1 GHz(SDS5104X) 2 GHz(SDS6204A)
Maybe you missed this bit from the Warranted characteristics table:
Bandwidth (with scope) 1 GHz(SDS5104X) 2 GHz(SDS6204A)If you sell scopes, then I think it's important to know that if you have a 1 GHz BW signal generator feeding into a 1 GHz BW probe into a 1 GHz BW scope, then the guaranteed frequency response is -9 dB at 1 GHz, so the -3 dB bandwidth will be substantially less than 1 GHz (about 500 MHz for a classic 1st order Gaussian response). To guarantee -3 dB at 1 GHz all components need to have substantially more than 1 GHz of guaranteed bandwidth. Exactly how much more depends on the shape of the frequency response of each component. You are basically adding up the curves (in dB, multiplying in linear voltage units). If you prefer time domain, then you can also talk about the geometric sum of rise times, but I couldn't find a rise time specification for this probe.
I think it's important to know that if you have a 1 GHz BW signal generator feeding into a 1 GHz BW probe into a 1 GHz BW scope, then the guaranteed frequency response is -9 dB at 1 GHz, so the -3 dB bandwidth will be substantially less than 1 GHz (about 500 MHz for a classic 1st order Gaussian response).
Textbook doctrins are far too simplistic to reflect the real world. They don't help much when it comes to practical applications.
Back in early 2019, I've measured the system bandwidth of an SAP1000 prototype in combination with a pre-production unit of the SDS5104X (Siglents first GHz-DSO). That resulted in ~1.11 GHz:
https://www.eevblog.com/forum/testgear/at-last-siglent_s-sds5054x-touchscreen/msg2165488/#msg2165488
The bandwidth of the DSO frontend with direct coax connection was only very slightly better at 1.17 GHz and I need to stress that the frequency flatness of my pre-production SDS5000X was not optimal yet and the frontend for the final devices has undergone some redesign.
https://www.eevblog.com/forum/testgear/at-last-siglent_s-sds5054x-touchscreen/msg2430978/#msg2430978
So clearly that particular probe and scope are performing better than advertised. Certainly nice for you as a user, but not something one can consistently rely on, otherwise obviously the manufacturer would have put it in the datasheet.
Are you saying that in the real world, a probe with 1 Ghz -3 dB bandwidth with a scope with 1 GHz -3dB bandwidth will have 1 GHz system bandwidth? Because that's what the warranted specifications say. Any SAP1000 with a probe-only bandwidth of 1.01 Ghz is considered in spec according to the manual, as is any SDS5104X with 1.01 Ghz bandwidth. Is the roll-off is that sharp that these two together will have at least 1 GHz system bandwidth together? Or does Siglent do DSP correction for these probes?
So clearly that particular probe and scope are performing better than advertised. Certainly nice for you as a user, but not something one can consistently rely on, otherwise obviously the manufacturer would have put it in the datasheet.
If on the other hand, you take a random probe, just because it has a high bandwidth rating and looks sexy, and use it with a DSO were the HF-compensation of the probe doesn’t fit, you might actually end up with a performance that is worse than with matching probes that have a lower bandwidth rating.
Up to this point I’ve never seen any serious T&M-gear hat would not exceed its specifications. For lower end devices, this is usually even more pronounced. Have you tried to calculate what bandwidth the SAP1000 would have to have according to the textbook, in order to achieve a system bandwidth of 1.11 GHz when the bandwidth of the DSO itself is 1.17 GHz? You should definitely try this exercise 😉
So clearly that particular probe and scope are performing better than advertised. Certainly nice for you as a user, but not something one can consistently rely on, otherwise obviously the manufacturer would have put it in the datasheet.
It's actually typical of Siglent to modestly rate their toys.
Up to this point I’ve never seen any serious T&M-gear that would not exceed its specifications. For lower end devices, this is usually even more pronounced.
It's actually typical of Siglent to modestly rate their toys.It doesn't matter. Warranted specs are the specification you base the certainty of the measurement results on. If you buy 10 oscilloscopes to use in a production line, you aren't going to measure each of them AND/OR trust they won't get worse over time and temperature due to component temperate, drift and aging.
So there I am, waiting for my illusive event and the scope's temperature/time/whatever has changed and it wants to autocal but is stuck waiting for the trigger, just like I am. Then it happens, the elusive trigger that both the autocal and me have been waiting on. The scope starts the autocal. A second event happens immediately and it is still running the autocal.