Siglent SDS1202X-E impressions and a couple of bugs to be aware of... - Page 1
Forum section: electronics / testgear

author: TonyWilk
author_rank: Newbie
timestamp: May 20, 2017, 02:25:44 am
content: Just got a new Siglent SDS1202X-E, £361.08 delivered from 'lacamax-shop' on eBay.I have a 60MHz Trio which I bought 30years ago and an aging Tektronics TDS210 (60MHz 2ch storage) and was looking for a nice new bit of kit for a project I'm involved with. I was looking for 2 or 4 channels, 300+MHz but saw this and thought... what the heck, I wonder what you get these days for 360 quid?Immediately puts the old Trio and Tek to shame, good display, pretty responsive controls, lots of menus to get lost in : )1G sampling is pretty limiting at the top end though.A couple of things caught me out and I spent the last 4 house sorting out what was going wrong...1st Bug:Trigger setup can get confused and stop triggering. The fix is to wiggle the trigger level knob.Details: Had the 'scope set to trigger in the middle of a 0-3v UART transit signal on CH1, trigger set to EDGE, RISINGPress trigger SETUP then press SLOPE, triggering stops sometimes. select RISING, triggering stops, now you can press a lot of things like Menu On/Off, Holdoff, SINGLE, NORMAL and it refuses to trigger. Press AUTO and it springs into life, press NORMAL and it doesn't do anything.Wiggle the trig knob a bit and it starts again.2nd Bug(s):Threshold levels are wrong if you have X10 probe selected. Serial decode stops working. Easy fix it to set X1 probe.Details: With a c. 0-3v UART signal on CH1, with X10 probe set, 1V/div you can press the trigger level knob to auto-set 1/2 level, the 'scope displays 1.4V and NORMAL trigger works fine. Then press DECODE, set Serial, UART, then set Signal. The Threshold adjustment went from -474mV upto 426mV and shows a dotted line on the trace which is consistent with that value (i.e. up and down by 1/2 a division at the bottom of the trace). If you adjust the line so it looks like it is on the signal, then decode doesn't work - because the line is wrong and the values displayed are wrong by a factor of 10.I spent **AGES** wondering why decode wouldn't work (this is the same for I2C decode as well).Bit if a side note... before setting up DECODE, you can set triggering to trigger on 'Serial', I set this up to trigger on 0x24 (the starting '$' character of a GPS message) and it worked fine - which was even more confusing when pressing DECODE, because you clearly see a serial string being triggered on a given character, but the decoder works independently with its own threshold values (that I had set wrong earlier).A final tipA lovely bit of kit for the price. If you already have a 'scope and/or thinking about 2 or 4 channels, remember that you can use the trigger output.Cabling trigger out from the Siglent to the Ext Trig on the old Tek I have 4 channels on two independent timebases.Still might get something else for RF work where I really need 300MHz or more, but now I think I'll look for a 2ch one and link it to the Siglent when I need to look at more channels of slower stuff.Yours,TonyWilk

author: tautech
author_rank: Super Contributor
timestamp: May 20, 2017, 01:46:49 pm
content: Welcome to the forum.Thanks for the feedback, yes these issues have been spotted already and reported to Siglent Tech support.Currently we are waiting for new firmware to address these issues.You can continue to report any other issues you find here or in the Siglent's support thread:https://www.eevblog.com/forum/testgear/siglent-technical-support-join-in-eevblog/

author: boggis the cat
author_rank: Regular Contributor
timestamp: May 21, 2017, 05:26:13 am
content: I received my unit from "tautech" on Friday, and have had a chance to do some messing about with this 'scope, as well as taking some measurements of the bandwidth to determine if there is a difference with the low V/div ranges (there isn't much: they stay well within 3 dB).So my two cents worth so far follows.Some approximate timingsBoot time is about 12 s, so not bad.'Self Cal' takes about 4 minutes 40 s. The percentage complete gauge that is displayed is (as is usual for these things) not accurate.Using 'Print' to take a PNG format screenshot is effectively instant and doesn't interfere with operation (that I can see). This is a huge improvement over 'scopes that insist on dumping a BMP format and take forever to do so.The [Do Self Cal] RoutineThe 'Self Cal' is worth doing if you want an accurate vertical scale indication. My particular one had a significant DC offset in the low V/div ranges, but was close to zero after the 'Self Cal'.Very few 'scopes sent in to us for calibration have this routine ever run by the customer. (Some 'scopes keep track of when the routine was last run: and if it was last year during the cal then I know the customer has used it the whole year without bothering to run it.)Menus etc. (and user confusion)The menus seem a bit confused. Depending on how you navigate them you can get odd behaviours. (Difficult to be certain of these are bugs, or user error.)Some behaviours seem to be based on different assumptions than I was expecting. For example, with both channels on:Press Press [Acquisition Normal], yields "Mem Depth 7M" (fifth 'softkey' from left)Press [Acquisition Normal] to set [Acquisition Peak Detect], yields "Mem Depth 7M"Press [Acquisition Peak Detect] to set [Acquisition Average], yields "Mem Depth 700K"Press [Acquisition Peak Average] to set [Acquisition Eres], yields "Mem Depth 700K"Press [Mem Depth 700K] twice to set [Mem Depth 7K], then keep pressing to set [Mem Depth 700K] againNow all acquisition modes are set to 700K.So the 'scope changes the depth immediately, then retains any changed setting through other acquisition modes. I was expecting it to keep track of the depth by mode, as that seemed logical to me.It is necessary to learn new equipment, of course, and I haven't come across anything particularly annoying so far -- bar the 'ghost' [Impedance 50] selection, and the  >  softkey that doesn't do anything (but doesn't seem to do anything weird).Possible Variable Initialisation BugsPretty sure this one wasn't 'user error': selected Video triggering, Sync Select, then [Field x]was initially set to [Field 0]. After setting it (to "1" or "2"), it retains the value. It appeared to actually start on Field 2(yes, it does), although I can't now check this. (Also selected "PAL", in case it makes any difference.)Edit: After doing a 'Factory Reset'.

author: arturfra
author_rank: Contributor
timestamp: May 24, 2017, 01:21:33 pm
content: Hi,I purchased the sds1202x-e it has a Good price for good oscilloscope, if in the future firmware upgrade i hope the user can change the dimension of the fonts specially for read values, because they are too small, it's very difficult to read

author: boggis the cat
author_rank: Regular Contributor
timestamp: May 25, 2017, 05:45:01 am
content: Quote from: arturfra on May 24, 2017, 01:21:33 pmYes, even if you could select a bold font the values would be more legible. (The display is nice and clear, but tiny fonts are a bit of an eye strain and make it more likely to misread something.)I also don't see why they couldn't give a few different options for whether to overlay measurements, list them below the trace window, or even reduce the width of the trace window in order to list measurements to the right (or left).Customisation options for the layout would be useful.

author: N8AUM
author_rank: Regular Contributor
timestamp: June 21, 2017, 07:12:38 pm
content: Not sure if mine has a bug or is just defective but within a 2 week period it would lock up and would not come out of screensaver mode, couldn't even turn scope off unless i unplug the mains. The few times that it did come out of screensaver mode the controls were unresponsive! sending it back today for an exchange.73 N8AUM Vidas

author: mikepa
author_rank: Contributor
timestamp: July 07, 2017, 08:27:38 pm
content: I chose the 1202X-E scope for a few reasons, but one was the switchable 50/1M impedance. It eliminates the need for cumbersome BNC Tees 50 ohm terminators. However, in the current firmware, changing between 50 and 1M Ohm does nothing.I just checked with Siglent and they told me the 50/IM switchable was not supposed to be available on the -E model, so the switch will be removed in the next firmware release. (It is available on the 1202X model for $200 more!). In fairness to Siglent I think it was during a review I was told the 1202X-E had switchable impedance, not in Siglent materials.

author: tautech
author_rank: Super Contributor
timestamp: July 07, 2017, 08:40:51 pm
content: Quote from: mikepa on July 07, 2017, 08:27:38 pmIn even the Chinese datasheet from last year there is no mention of 50inputs. Also in every online image I know of where you can see the writing by the inputs, again no mention of 50.It might confuse some that the X and X+ models have 50inputs but please remember the X-E is an Economy version and there will be features omitted in the X-E. (50 ohm inputs, 8" display......)

author: rf-loop
author_rank: Super Contributor
timestamp: July 08, 2017, 06:03:39 am
content: Quote from: mikepa on July 07, 2017, 08:27:38 pmPersonally I hope they do not this mistake that they remove this selection. Instead of remove they needrenameit! Why?My recommendation to Siglent is that they use this selection for make dBm @50ohm possible, specially for FFT scale.Just for tell to scope that there is external 50ohm termination in use by user. This 1Mpoints FFT is so nice that it is useful also bit develop also other ways for some more features and more sophisticated and better usability. dBm scale and measurements are only one desirable improvement. Just for: Scrap the playthings, get a real oscilloscope.1M FFTup to 80000 last acquisition time stamped and always bacround working history fifo buffer, up to 54M (no competitors exept example in expensive R&S)- stop and look back in history and analyze what just happendup to 80000 segment very fast sequence acquisition up to well over 400ksegment/s (kwfm/s) speed. (no competitors)(measured max quaranteed (no missed trigger events and acquisitions) speed 480ksegment/s @ segment length 700 samples)- blind time between segments down to <1.5usfull speed mask test with also full speed pass/fail output (no competitors)Always selectable linear/sin(x)/x vectors or dots for raw data points without "riglols". (fully post processing and available also afterwards in stopped scope and in history and segment memory what both always contain full raw adc data instead if screen frame)True full resolution and full bandwidth 500uV/div (no competitors)a.s.o.

author: nctnico
author_rank: Super Contributor
timestamp: July 08, 2017, 08:48:01 am
content: So many bugs (no competitors)For all the features you list with 'no competitors' I can come up with at least one oscilloscope brand which has the same feature.

author: boggis the cat
author_rank: Regular Contributor
timestamp: July 09, 2017, 09:02:46 am
content: Quote from: rf-loop on July 08, 2017, 06:03:39 amA better way to do this would be to have options within the FFT function. The present erroneous menu should be removed, as it could mislead people into believing that this is a 50 Ohm termination option (because this is how it is represented).It should be possible to have many options available to give the 'scope information required to make calculations.Revising the way measurements are presented would be useful, too. There is plenty of space below the trace window when the menus are off, and usually space to the right. Any empty areas could be used to better present measurements or other information.

author: rf-loop
author_rank: Super Contributor
timestamp: July 09, 2017, 01:50:57 pm
content: Quote from: boggis the cat on July 09, 2017, 09:02:46 amThese are my wordsin previous msg:Quote from: rf-loopOf course selection can also move to FFT menu. Or how ever but this selection need be available for external 50 ohmNow selection of course is wrong and it need fix.