Feature suggestion:
Measurment mode:
- When long click on the measurement table, activate its measurement cursors.
- When cursors for measurement are activated, show what table it belongs to. Have a red rectangle around the table or soemthing.
Feature suggestion:
Measurment mode:
- When long click on the measurement table, activate its measurement cursors.
I like the first suggestions a lot! When I add measurement cursors, I typically do it as an afterthought: I already have the measurement set up, but may start to wonder "Is it really measuring what I want it to"? Having a quick way to bring up the cursors, without going through the menu again, would be great.
Wanted:
Displaying the waveform update rate (as seen on the new Magnova scope).
Has already been heard and judged to be a good feature, but has not yet been added to the list.
Wanted:
Displaying the waveform update rate (as seen on the new Magnova scope).
Has already been heard and judged to be a good feature, but has not yet been added to the list.Added to Wanted Feature No.35. This way, there is no need to connect to Trigout to test the waveform capture rate.
There is absolutely no unused space left, especially on the SDS800X HD.
Maybe we should request an (optional) Info box in the bottom area, similar to the Timebase info box, where we can have the Acquisition mode together with waveform update rate. In general, info displays in the trace area should be optional and movable at the very least - smilar to the FFT info block.
Well, I then asked him why you don't use the oscilloscope itself. It knows it, and in fact it knows it perfectly.
I do a lot of RS485 serial decoding on an SDS2000X HD, and one of the things I miss that the older R&S RTB2004 it replaced had was the ability to show the entire "message" as a single frame/packet, and not as single bytes in a list, like the Siglents does it.
https://www.eevblog.com/forum/testgear/siglent-sds2000x-hd-12bit-(published-for-chinese-domestic-market-only)/msg5270949/#msg5270949I've been an R&S RTB2004 user for several years but decided to buy an SDS2000X HD to use as a secondary scope.
I liked it better than the RTB2004, so the Siglent is now the main scope. And after 3D printing that VESA mount for it, it's such a convenient instrument!
However, one thing I haven't figured out is the UART bus table.
I do a lot of half-duplex RS485 decoding, and with the RTB2004 it would display each "frame" (burst of characters) on a single line in the table. The Siglent on the other hand, just places each character on a new line in the table, and I end up having to fiddle a lot to compare two received "frames".
Is there a way to have the bus table look like the RTB2004 that grouts the received data in "frames" rather than filling a list I must scroll through?
electronics hobbyist, can you add the following feature to the list as well? I have an SDS2000X HD at work, and I've ordered a 1000X HD to have at my bench at home, but this (missing) feature I'm pointing out applies for the entire Siglent lineup AFAIK, at least the 800X HD, 1000X HD, and 2000X HD. I know many other manufacturers do it exactly the way Siglent does it, but that doesn't mean it could have been done better!
Serial decodingI do a lot of RS485 serial decoding on an SDS2000X HD, and one of the things I miss that the older R&S RTB2004 it replaced had was the ability to show the entire "message" as a single frame/packet, and not as single bytes in a list, like the Siglents does it.
https://www.eevblog.com/forum/testgear/siglent-sds2000x-hd-12bit-(published-for-chinese-domestic-market-only)/msg5270949/#msg5270949I've been an R&S RTB2004 user for several years but decided to buy an SDS2000X HD to use as a secondary scope.
I liked it better than the RTB2004, so the Siglent is now the main scope. And after 3D printing that VESA mount for it, it's such a convenient instrument!
However, one thing I haven't figured out is the UART bus table.
I do a lot of half-duplex RS485 decoding, and with the RTB2004 it would display each "frame" (burst of characters) on a single line in the table. The Siglent on the other hand, just places each character on a new line in the table, and I end up having to fiddle a lot to compare two received "frames".
Is there a way to have the bus table look like the RTB2004 that grouts the received data in "frames" rather than filling a list I must scroll through?
electronics hobbyist, can you add the following feature to the list as well? I have an SDS2000X HD at work, and I've ordered a 1000X HD to have at my bench at home, but this (missing) feature I'm pointing out applies for the entire Siglent lineup AFAIK, at least the 800X HD, 1000X HD, and 2000X HD. I know many other manufacturers do it exactly the way Siglent does it, but that doesn't mean it could have been done better!
Just unboxed my new scope and getting to grips with it - apologies if this is just a setting which can be changed somewhere, but it seems unintuitive and a limitation...
I'm probing a CAN signal - actually one of the training outputs from my MSOX3104A - and before I can decode it, I need to know the bit rate.
I couldn't find an automated measurement that gives this quickly and easily. IIRC it was added in firmware after release on the Agilent, and it's handy. I think it just measures the minimum observed pulse width (either positive or negative) within the captured data.
Feature request 1: bit rate measurement, please!
In the absence of an automatic measurement, I figured I'd just do it the old-fashioned way. Capture a packet, find the narrowest pulse and assume it's 1 bit wide. Then, put the cursors on the edges as accurately as possible, and measure their separation.
The odd behaviour is that the delta-X measurement on screen doesn't show the distance between the cursors if one of them is off screen; instead, it 'clips' to the edge of the screen, and if both are off screen then it just reports the width of the screen, or zero if both cursors are off to the same side.
That's really misleading. It clearly remembers the correct cursor positions if they're pushed off screen, because they come back to the right place if I adjust the time base to bring them back.
If I were feeling unkind, I'd call this a bug, though it's clearly intentional behaviour. I just can't think of any circumstances when I'd want to measure between a cursor and the edge of the display, as opposed to between the two cursors.
Feature request 2: delta-X time measurement actually measures the time between X1 and X2 even if one or both of them is off screen - not between a visible cursor and the edge of the screen.
(Example photos: both cursors on screen, showing delta-X = 8.01us, and the effect of just speeding up the time base 1 click; this pushes X1 off the left side of the screen, and the delta-X readout becomes 6.77us which is effectively meaningless).
Good suggestion for the entire platform range and one I believe could be accomplished quite simply by adding a menu View (type) option in the Decode List comprising of a Bytes or Frames choice, Bytes being the current list default view.
Feature request 1: bit rate measurement, please!
As for cursor behaviour it is not a bug.
Scope's capture ENDS with the end of screen.
Serial decodingI do a lot of RS485 serial decoding on an SDS2000X HD, and one of the things I miss that the older R&S RTB2004 it replaced had was the ability to show the entire "message" as a single frame/packet, and not as single bytes in a list, like the Siglents does it.
https://www.eevblog.com/forum/testgear/siglent-sds2000x-hd-12bit-(published-for-chinese-domestic-market-only)/msg5270949/#msg5270949I've been an R&S RTB2004 user for several years but decided to buy an SDS2000X HD to use as a secondary scope.
I liked it better than the RTB2004, so the Siglent is now the main scope. And after 3D printing that VESA mount for it, it's such a convenient instrument!
However, one thing I haven't figured out is the UART bus table.
I do a lot of half-duplex RS485 decoding, and with the RTB2004 it would display each "frame" (burst of characters) on a single line in the table. The Siglent on the other hand, just places each character on a new line in the table, and I end up having to fiddle a lot to compare two received "frames".
Is there a way to have the bus table look like the RTB2004 that grouts the received data in "frames" rather than filling a list I must scroll through?
electronics hobbyist, can you add the following feature to the list as well? I have an SDS2000X HD at work, and I've ordered a 1000X HD to have at my bench at home, but this (missing) feature I'm pointing out applies for the entire Siglent lineup AFAIK, at least the 800X HD, 1000X HD, and 2000X HD. I know many other manufacturers do it exactly the way Siglent does it, but that doesn't mean it could have been done better!Good suggestion for the entire platform range and one I believe could be accomplished quite simply by adding a menu View (type) option in the Decode List comprising of a Bytes or Frames choice, Bytes being the current list default view.
There certainly is sufficient room in the Decode Lits menu to add a View header with Bytes and Frames as the pop out choices.
In addition just the List headers would require modifying for a Frame view labels.
See screenshot and suggest where a new View (type) header should be added.....IMO directly below Display.
As for cursor behaviour it is not a bug.
Scope's capture ENDS with the end of screen.
Try: capture a whole pulse, stop acquisition, then use the magnifier to zoom in on each edge individually to position a cursor accurately. The delta-X interval is reported correctly, regardless of what portion of the trace is on screen.
Then, exit magnifier mode and zoom in on one of the edges by changing the time base and position instead. The delta-X measurement is now clipped to the edge of the display.
The two methods result in different behaviour, and that can't be right. I humbly suggest that the distance from a cursor to the edge of the screen isn't ever useful, could be misleading, and should instead always be the distance between cursors - just as it is if the magnifier is used.
On the Siglent, pressing 'single' fills the screen, but the acquisition begins and ends with what can be displayed, even if that leaves memory unused. Why not fill the memory, so I can trigger on an interesting event and then scroll back and forward to see what happened before and after?
Navigation defaults to "by time". Frankly, I have not understood what that mode is needed for at all: I have a dedicated horizontal position knobfor continuous adjustment, or can call up a keypad quickly via the Timebase info box if I want to go to an absolute value.
I would much rather use Navigation -- and the dedicated arrow buttons on the front panel -- to navigate by history frame: Stop an acquisition, and have the buttons ready to step through the history frames right away.