Siglent SDS1000X-HD - Bugs and "features" thread. - Page 1
Forum section: electronics / testgear

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 04, 2024, 08:04:14 pm
content: Hi, I'm starting a thread to track and list all bugs and strange observations for the Siglent 1000X-HD series.Current firmware is1.1.0.2Feel free to confirm it, I am not ruling out a PEBKAC on my side.Bug list:#1 Activatingcursorsmenuduring FFT makes FFT very slow.EDIT: Seems to be related to the presence of the floating menu, not the cursors. When the floating menu is active, and for ~2 seconds after it disappears, the FFT function slows down from ~15 updates per second to 2 updates per second.To reproduce: Feed 1MHz sine into CH1, PressDefault->Math->Function-> Freq-Analysis->FFT. Open and close the floating menu.#2 SMB share function suggests wrong format.The format suggested by the settings window is //server/share. I only got this to work with backslashes \\server\share on a Synology NAS SMB share.#3Probe Checkfunction is faulty.In the probe setup, there is a function to automatically detect and adjust the probe attenuation, using the internal cal signal as reference. Every 10:1 probe I've tried wound up setting a 30ish:1 attenuation.Note: confirmed as fixed in firmware 1.1.3.1#4 Decode function menu does not show the custom channel labels.You can set a custom label for each channel. The decode function still only shows CH1..2..3..4 when selecting the signals instead of showing the custom label.EDIT:This refers to the menu where you select which channel is which protocol signal.Analysis/Decode/Protocol signalsThis seems to be the expected behavior, the labels only show up next t the traces in the main window.#5 Firmware update of SLA1016 requires a reboot instead of reconnect.If you update the firmware of the SLA1016 with the scope, it prompts you to reconnect the SLA1016 after completion. However, the unit did not recognize the SLA1016 any more until I rebooted the scope.#6 Possible I²C decode issuesee:https://www.eevblog.com/forum/testgear/siglent-sds1000x-hd-bugs-and-features-thread/msg5433341/#msg5433341Note:Expected behavior as explained by 2N3055 below. Actually Siglent does it better than some "premium" brands.#7 Acquisition spontaneously fails completely. Reinstalling firmware required.https://www.eevblog.com/forum/testgear/siglent-sds1000x-hd-bugs-and-features-thread/msg5434688/#msg5434688Present in 1.1.3.1CHRISTMAS WISHLIST(take notes Siglent!)- Add a NTP server setting. It's running Linux, shouldn't be too hard.

author: Martin72
author_rank: Super Contributor
timestamp: April 04, 2024, 08:45:28 pm
content: QuoteThis surprises me a little, as the software should be pretty much the same for 800X HD and 1000X HD.Very stupid question:It is not enough to call up the function and store a label name there, you have to activate it again afterwards - you will have done that ?

author: Veteran68
author_rank: Frequent Contributor
timestamp: April 04, 2024, 08:52:56 pm
content: Quote from: BreakingOhmsLaw on April 04, 2024, 08:04:14 pmForward slashes are normal SMB share format for Samba/Linux syntax. Backslashes are for Windows syntax.With the scope OS being Linux-based, I would assume //server/share is expected. Are you saying the scope requires the Windows backslash format to work, but is still prompting you to use forward slashes?

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 04, 2024, 08:57:12 pm
content: Quote from: Martin72 on April 04, 2024, 08:45:28 pmI do believe so:EDIT:Martin, I may have not made myself clear enough. I am referring to this:

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 04, 2024, 08:59:15 pm
content: Quote from: Veteran68 on April 04, 2024, 08:52:56 pmThat is the case.

author: Martin72
author_rank: Super Contributor
timestamp: April 04, 2024, 09:36:18 pm
content: QuoteAh, but I don't think that's a mistake.It is (as an example) channel 2, why should there be a label text?The label only applies to the display on the screen.

author: tautech
author_rank: Super Contributor
timestamp: April 04, 2024, 09:40:23 pm
content: Quote from: BreakingOhmsLaw on April 04, 2024, 08:04:14 pmOh FFS they sent these out with that old FW !We know about some of your observations and 1.1.3.1 is being tested however not available to the public just yet.

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 04, 2024, 09:43:43 pm
content: Quote from: tautech on April 04, 2024, 09:40:23 pmJep, in fact, there isnoFW available for download yet whatsoever. Not even the one it came with.

author: tautech
author_rank: Super Contributor
timestamp: April 04, 2024, 09:47:10 pm
content: Quote from: BreakingOhmsLaw on April 04, 2024, 09:43:43 pmI know, preaching to the converted.Will send PM.

author: tautech
author_rank: Super Contributor
timestamp: April 04, 2024, 10:24:34 pm
content: Quote from: BreakingOhmsLaw on April 04, 2024, 08:04:14 pmAll models using this UI work in this way.In the Decode menu you assign the channels to the required signals, SDA, CLK etc.In the Probe menu custom trace labels are applied.Any changes would require a complete platform variation and many models would be impacted.Therefore a detailed report need be prepared for any consideration.

author: skander36
author_rank: Frequent Contributor
timestamp: April 05, 2024, 10:27:28 am
content: Quote from: BreakingOhmsLaw on April 04, 2024, 09:43:43 pmActually it is 1.1.3.1 (12 March) - on the China site- Use Edge browser with automatic translation. -https://www.siglent.com/download/firmware/?ProId=96I'm using it for about two month without problems and solved two major bugs ( arched waveform at maximum zoom and scope lock when using PSSR function in Power Analisys)Later edit:Reported bugs checked in 1.1.3.11. yes the FFT screen update slows down for 2 seconds when menu is activated (even is embeded or floating). Tolerable, not an issue.2. explained by Veteran683. probe check detect correctly attenuation setting.4. yes in decode menu the label setting does not appear.5. N/A

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 05, 2024, 08:19:53 pm
content: I found something else that someone might try to reproduce:It reliably does not decode the (7 bit) I²C addresses 0x78 (= 1111000 ) through 0x7B ( 1111011). So, these are all addresses starting with a "11110" pattern.Test setup:- I have an STM32 MCU trying to write a byte to the addresses 0x00 through 0x7F.- Voltage threshold for SDA / SCL at 1,5V, 4K7 pullup resistors to 3.3Volt.0x00 to 0x77 works fine, 0x78 to 0x7C fails, 0x7D, 0x7E 0x7F work fine again.

author: ZigmundRat
author_rank: Regular Contributor
timestamp: April 06, 2024, 12:31:30 am
content: I just received my SDS1104X HD (from reputable US reseller) and have now spent a little bit of time getting familiar. Liking it so far. I have not tried to replicate any reported bugs as of yet. Mine came with 1.0.7.2 firmware, which seems quite old. I’m waiting to see when the next official update is released before worrying about other updates or chasing bugs. Unfortunately I can’t help right now with your I2C address issue, but will be watching.I was a bit disappointed to see there is no NTP option in the network settings. I sort of assumed it would be there given the 800X support. I know it’s been mentioned before, but adding my vote to include this option in the future.

author: tautech
author_rank: Super Contributor
timestamp: April 06, 2024, 01:31:22 am
content: Quote from: ZigmundRat on April 06, 2024, 12:31:30 amNTP was never considered for 1kX HD as it already has a RTC, unlike the 800X HD series.

author: ZigmundRat
author_rank: Regular Contributor
timestamp: April 06, 2024, 02:49:25 am
content: Presence of an RTC does not necessarily obviate the use of NTP (SNTP)In this case I would grant that there are not many use cases where ongoing resynchronization would be required, and that this is more of a convenience item - at least as long as the RTC drift is reasonable. If you are trying to match up scope captured events and other external data/event data then such synchronization may be useful, but I have no definitive use case.

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 06, 2024, 09:45:58 am
content: Quote from: ZigmundRat on April 06, 2024, 02:49:25 amI'd even argue that having an RTC is all the more reason to support NTP.

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 06, 2024, 11:20:42 am
content: Quote from: skander36 on April 05, 2024, 10:27:28 amIt's gotten better with 1.1.3.1, but still worth looking into IMHO, since it might be the same reason why theBode Plotfunction is so dreadfully slow. The menu is always on during Bode Plot, so the function might suffer from the same issue.

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 06, 2024, 04:16:06 pm
content: Aaaaaand it's dead...Acquisition now has a permanent failure where everything between ground and the signal is filled with a pseudo 250MHz sine wave.Probe Ch.1 is connected to cal signal, Probe Ch.2 is attached to ground.I am not able to recover from this so far.Update:I was able to recover the normal operation by reinstalling the firmware.

author: skander36
author_rank: Frequent Contributor
timestamp: April 06, 2024, 04:58:39 pm
content: How was crashed?You were in the middle of something?

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 06, 2024, 06:20:44 pm
content: Quote from: skander36 on April 06, 2024, 04:58:39 pmI was playing arround with the Bode Plot function and FFT. Then I shut down the unit and went for lunch.When I returned, it immediately started up in that state.When this fault is active, it looks like it ia trying to interpolate anything into a 250MHz sine wave. It also combines all the samples from all channels into one trace. Really looks like the entire acquisition goes bonkers.

author: skander36
author_rank: Frequent Contributor
timestamp: April 06, 2024, 06:53:52 pm
content: Quote from: BreakingOhmsLaw on April 06, 2024, 06:20:44 pmBode plot was also responsible for PSRR bug. It was not closing completely and lock the scope when Power Analysis menu were open. The scope must be forced shutdown, reset to factory, and sometimes secure erased in order to be recovered.

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 06, 2024, 09:13:30 pm
content: So, I have a theory of what's happening with the I²C bug:A CAN bus expects something called "bit stuffing" if you try and transmit five or more bits that are all ones or zeroes. So instead of the 5th identical bit, an inverted "stuff bit" gets inserted. This is because CAN has no clock signal, so CAN relies on the data bits themselves to recover a clock signal. Hence, bit stuffing ensures that you have an edge every now and then to synchronize on.Let's look at that bug again. Only addresses starting with "11110" are not decoded. I'm willing to wager a nice bottle of single malt, that I²C decoding shares code with the CAN decoder and tosses out the "0" as a supposed "stuff bit". Consequently, the I²2 frame is "missing "a bit and is not decoded because it seems incomplete.I²C has a clock signal, so bit stuffing is not required. But somehow "11110" gets treated the way a CAN frame would. By the way, "00001" works fine.What do you think?

author: skander36
author_rank: Frequent Contributor
timestamp: April 06, 2024, 09:59:06 pm
content: It is possible but as long as you don't have a confirmation from inside, you can't be sure about the cause.For me as long as it can decode reliably what I need is enough for time being ...

author: 2N3055
author_rank: Super Contributor
timestamp: April 06, 2024, 10:53:56 pm
content: Quote from: BreakingOhmsLaw on April 06, 2024, 09:13:30 pmI'll send you my address for the bottle. I trust you to pick something nice.It doesn't work because those are not valid packets. From standard:111 10XX X 10-bit slave addressing111 11XX X Reserved for future purposesNice page:https://www.totalphase.com/support/articles/200349176-7-bit-8-bit-and-10-bit-i2c-slave-addressing/And if your reference for this is Keysight scope make note that their implementation is not correct, i.e. not according to standard. It will decode 7bit addresses with invalid ranges.Picoscope correctly decodes both 7 and 10 bit addressed I2C

author: BreakingOhmsLaw
author_rank: Frequent Contributor
timestamp: April 07, 2024, 09:55:59 am
content: Quote from: 2N3055 on April 06, 2024, 10:53:56 pmPlease do, I am a man of my word.QuoteIndeed. Come to think of it, I don't think I've ever used a non 7-bit I²C part in anger in the past 32 years as an EE. I completely forgot about the extended addressing.Anyway, a fine bottle of scotch will find it's way to Croatia as soon as it knows where to go.

author: 2N3055
author_rank: Super Contributor
timestamp: April 07, 2024, 05:06:54 pm
content: Quote from: BreakingOhmsLaw on April 07, 2024, 09:55:59 amMy friend,I was just joking. There is no need for it, really.My biggest reward is that I could help. Really, pleasure is all mine.That does not mean, that if you ever pass through Rijeka, Croatia, let me know, and we can have a sit down a have a proper drink!As for 10 bit I2C, I never used one either... But I encountered one on some device once. And I was confused that Keysight didn't do it properly. Luckily, my trusty Pico did....My best,Siniša

author: skander36
author_rank: Frequent Contributor
timestamp: April 08, 2024, 10:36:15 am
content: @BreakingOhmsLawI suggest you to revise points #2 and #7.On #2 clearly is not a bug. Veteran 66has explained why. If we using a Linux share we need to use this format.On #7 you need to see if this incident can be reproduced. Usually an incident that can't be reproduced can't be called a bug. There were a few others incidents that crash the scope but I can't reproduced anymore. But also on all my scopes I encounter this at a moment in time.(Keysight, RTB2K, Micsig, Rigol).Did you tried to reset to factory default, Secure erase, before reinstall the firmware?

author: skander36
author_rank: Frequent Contributor
timestamp: June 28, 2024, 09:40:40 pm
content: New Firmware for 1000X HD - 1.1.3.8I did not find 1.1.3.6 even on Chinese site, maybe in new units from factory.2024/06/141.1.3.81. Optimize UI, change "on/off" to "On/Off".2. Solve the problem that some numbers from 200-223 cannot be entered in the first byte of the IP address.3. Standard software functions of FG and LA.2024/05/221.1.3.61. Solve the problem of trigger holdoff fails.2. Solve the problem of CAN decoding causing crashes with a small probability. 3. Modify the kernel s olve the problem that scpi cannot beused on a computer with keysight driver installed4. Solve the problem of advanced trigger (Qualified, NthEdge, Delay, Setup/Hold) parameters are not recalled.5. Solve the problem of delay trigger level setting error.6. Solve the problem of when the edge is set to Alternating, trigger jitter will occur when entering the other trigger type.7. Solve some known problems.8. Optimize waveform capture rate.9. Optimize self calibration speed.10. Optimize UI.

author: Martin72
author_rank: Super Contributor
timestamp: June 28, 2024, 09:48:23 pm
content: QuoteThat would also be something for the SDS3000X HD.If you start the Self-Cal there, you can confidently go shopping, vacuum the apartment, make dinner...

author: skander36
author_rank: Frequent Contributor
timestamp: June 28, 2024, 10:22:28 pm
content: Quote from: Martin72 on June 28, 2024, 09:48:23 pmIt's take about 5 minutes now.Also waveform update does not seem to be faster, but I will keep measure in future.L.E. In dots mode I have obtained 128 K.

author: Martin72
author_rank: Super Contributor
timestamp: June 28, 2024, 11:00:03 pm
content: 5 minutes....Pah.Just under 50 minutes and you'll be in my class.QuoteThe information in the data sheet only refers to a "sweet spot", a time base and certain settings anyway.In the meantime, I've made my peace with it as long as it doesn't drop too much above and below the sweet spot.

author: skander36
author_rank: Frequent Contributor
timestamp: June 28, 2024, 11:04:34 pm
content: Before the update was about 10- 12 min. I don't remember precisely ...

author: uliano
author_rank: Regular Contributor
timestamp: November 12, 2024, 06:11:54 am
content: I didn't see this listed so I guess my unit is brokenOnly channel 2 and only close to 0V vertical offsethttps://youtu.be/DJZdw0w934E

author: tautech
author_rank: Super Contributor
timestamp: November 12, 2024, 06:17:37 am
content: Quote from: uliano on November 12, 2024, 06:11:54 amFW version ?Latest is:https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS1000X-HD_V1.1.3.8_EN.zipHave you done a Default ?Run Self Cal too.

author: uliano
author_rank: Regular Contributor
timestamp: November 12, 2024, 06:57:18 am
content: I have latest and did self cal.What's a default?

author: tautech
author_rank: Super Contributor
timestamp: November 12, 2024, 07:12:04 am
content: Quote from: uliano on November 12, 2024, 06:57:18 am2nd row down middle button.Screenshots and a description of settings and how to replicate are more helpful than a video where we can't clearly see the settings.

author: uliano
author_rank: Regular Contributor
timestamp: November 12, 2024, 07:37:18 am
content: Default 'll have to wait a few hours (I'm on my dayjob, now).Settings are:- all channels DC,- 1 MOhm,- 0.5 mv/div,- 0V vertical offset (except for the moves I made in the video to offset C2 over and under 0 by a few hundreds microvolts),- trigger is rising slope on C2 level + 400/500 microvolts. If I trigger on any other channel I get no events.if I move the offset under or over 0V the spike disappears.This happens more frequently after switching it on and becomes somewhat less frequent after a few hours of power on.If I set C2 to AC it still happens but way less frequently, I even captured a single event while on GND.The size of the spike is dependent on how many other channels are turned on. If I have only C2 or only 2 channels on the height of the spike is way lesser (but still captured by that trigger setting).All other channels appear flawless.

author: tautech
author_rank: Super Contributor
timestamp: November 12, 2024, 07:40:56 am
content: Quote from: uliano on November 12, 2024, 07:37:18 amCh2 was set to Trigger so at max sensitivity you're triggering on noise.....nothing to worry about and the reason you are only seeing it on Ch2.In the channel menu engage the 20 MHz BW filter and it will be gone...

author: uliano
author_rank: Regular Contributor
timestamp: November 12, 2024, 08:01:53 am
content: By setting the trigger on other channels (all other settings being equal) I've never seen *any* single spike. So no it is definitely something that's happening on the input circuitry of C2AFAIR setting 20MHz BW doesn't eliminate the problem (confirmation this evening)

author: tautech
author_rank: Super Contributor
timestamp: November 12, 2024, 08:11:59 am
content: Quote from: uliano on November 12, 2024, 08:01:53 amOkay, good info.Run Self Cal again after appropriate warm up.

author: uliano
author_rank: Regular Contributor
timestamp: November 12, 2024, 04:37:25 pm
content: Ok so I defaulted and self-calibrated it.Some new "features":- only when C2 is off then spikes appearing also on C1, when C2 is on then it "takes it over" all the spikes.- more notably now I'm on 10 mV/div scales and trigger i set to 6 mV- as usual spikes only when channel postion is close to 0https://youtu.be/QOvJI54BD0shttps://youtu.be/Hm2VK7kibIE(contacted assistance... )

author: uliano
author_rank: Regular Contributor
timestamp: November 12, 2024, 04:58:28 pm
content: Bandwith also doesn't seem to be the answer

author: tautech
author_rank: Super Contributor
timestamp: November 12, 2024, 08:45:21 pm
content: Quote from: uliano on November 12, 2024, 04:58:28 pmCan I ask if this is observed with open inputs or with probes connected ?About to do some checks with a unit I have here in case what you see is some local RFI/EMI at your bench.

author: tautech
author_rank: Super Contributor
timestamp: November 12, 2024, 09:18:33 pm
content: Quote from: uliano on November 12, 2024, 04:58:28 pmCan't replicate your results.Open inputs testsWith a Single trigger I can trigger on noise at low level trigger settings, under ~250uV.Some screenshots attached.#5png is a Single trigger setup waiting for a peak that never arrives at those trigger levels.All I can suggest is to investigate local RFI noise.....these can even be from some device in an adjacent room.

author: uliano
author_rank: Regular Contributor
timestamp: November 13, 2024, 01:49:43 am
content: If they were interferences:- they would show up at any vertical offset of the channel an not only close to zero- they would show up not only on ch2 an to a lesser extent on ch1 (that if I’m not wrong share the same ADC and therefore some input circuitry) but also on ch3 and ch4.- their amplitude would be independent from the vertical scale (of that i’m not so sure if the enter after gain stage, but it is a strange point of attack for RFI, much less likely the front end in my opinion). I observe the same amplitude on screen on both 0.5 and 10 mV/div.- they would be detected by old trusty 1104X-EI also moved to the opposite side of the flat to no avail, so it would have been a very pervasive RFI but yes this one is not conclusive.All of that points to a defect in the input pipeline of only 2 channels ,after front end just before ADC. As it is a subtle effect it may have escaped quality control.Let’s see when assistance reaches back to me what they’re gonna say.

author: zike
author_rank: Contributor
timestamp: December 15, 2024, 12:54:57 am
content: Today I got an SDS1204X HD (fw version 1.1.3.8 ) and also a SAG1021I arb. Appreciate any guidance on a few puzzles (yes, I did RTFM):1. Product page says you need a separate license to enable the wavegen, in addition to buying the hardware. It works out of the box; is this a ‘temporary’ license that evaporates? Like to know up front if they are going to brick it and soak me for more $ after the return window lapses.2. Any graceful way to abort a Bode plot during the sweep? Unresponsive while sweeping, and if you selected “Continuous” it loops indefinitely. Only thing I figured out is to fully exit Bode mode altogether, at which point it forgets the setup and reverts to (useless) default sweep parameters. Hope I’m missing something simple here.3. Which brings up, is it possible to save the Bode configuration, or at least have it come up in the last configuration used? Can any instrument states/setups be saved/recalled?4. FFT is pretty good, but again, a way to save/recall setups (and even apply them to a new channel) would be helpful. I can do FFT’s on two channels at once, but the display does very stupid things if I show them together, unless I manually enter all possible settings exactly the same for each channel.Incidentally, the scope should have plenty of grunt to do 2-channel cross spectrum, coherence and Fourier frequency response, and evidently bit depth and front end noise to make them count; is that too much to ask?5. Somehow I imagined they’d send me compatible 10x probes with a 200MHz scope advertised to have auto probe detect. The PP215 probes they sent are switchable 1x/10x toys with no signaling pin. Very disappointing. I had to dig out some ancient Tek P6106’s from the 1970s. (Yes, probe detect does work, with _real_ probes.)Happy for any wisdom you all can share. Don't get me wrong, I'm very pleased so far; a far cry from my last experience with Siglent. One day in, this appears to be an excellent tool. Thus, worth making better.Cheers,zike

author: tautech
author_rank: Super Contributor
timestamp: December 15, 2024, 01:05:57 am
content: Quote from: zike on December 15, 2024, 12:54:57 amThe need for FG and LA option licensing was deleted in the latest FW.QuoteIntuitively Run/Stop should cease the sweep...not sure so check.IIRC in one of the Bode plot menus you can also stop the sweep.QuoteUtility>Save/Recall menu allows for Setups to be saved, IIRC 5-10 internally for Recall and infinite when saved externally.QuoteYup disappoints me 2 but is the same for low BW SDS2000X Plus models also, only PP215 is supplied.

author: KungFuJosh
author_rank: Super Contributor
timestamp: December 15, 2024, 05:05:29 pm
content: Quote from: zike on December 15, 2024, 12:54:57 amIf you want them to include better probes, they'll raise the price. You're better off getting some nice probemaster.com probes.

author: zike
author_rank: Contributor
timestamp: December 16, 2024, 04:27:05 pm
content: Quote from: tautech on December 15, 2024, 01:05:57 amThanks for this guidance. I played with it a bit more and don't find a good way, perhaps I'm looking in the wrong place. It seems bode setup gets forgotten and reset to defaults once you navigate away to access the Save/Recall function. Also, it appears the saved Setups only include channel, timebase and trigger settings; recalling a Setup file did not appear to restore (or over-write) any of the math functions I had configured, for example.

author: sanderb
author_rank: Contributor
timestamp: April 11, 2025, 04:37:23 pm
content: As I mentioned in another post, the SDS1104X-U has pretty much been abandoned by Siglent since its release (never got any firmware update). I am now eyeing the SDS1000X HD, because although the SDS800X HD covers my current needs, my eyesight isn't great. I think it is overpriced compared to the SDS800X HD, and I woud prefer if Siglent at least differentiates it more through firmware features, but, did anyone notice that 1.1.6.2 is out for the SDS800X HD for a month now, while the SDS1000X HD is still on 1.1.3.8? Makes me wonder if the SDS800X HD is going to be much better supported, because it obviously is way more popular.

author: tautech
author_rank: Super Contributor
timestamp: April 11, 2025, 08:16:54 pm
content: Quote from: sanderb on April 11, 2025, 04:37:23 pm800X HD and 1kX HD have an option to increase font size for improved readability.@66 I'm wearing glasses for most bench work now however don't need the larger font ...... yet.

author: KAKUL
author_rank: Contributor
timestamp: April 13, 2025, 05:40:59 pm
content: Hi guys.I'm waiting for a great update with new features.

author: tautech
author_rank: Super Contributor
timestamp: May 08, 2025, 04:46:31 am
content: Quote from: KAKUL on April 13, 2025, 05:40:59 pmWe're looking at new beta FW now that will get these to where SDS800X HD is currently at.

author: Performa01
author_rank: Super Contributor
timestamp: May 08, 2025, 10:27:14 am
content: Quote from: tautech on May 08, 2025, 04:46:31 amI'm curious if many Tektronix users would ever be "waiting for a great update with new features". Or Keysight users. Or Rohde & Schwarz users. Or - you get the point.No, they certainly would not, because they know that every new feature would be an expensive paid option.Siglent, on the other hand, provides a lot of features for free, that used to be or still are expensive paid options elsewhere, such as usable memory depth, segmented memory, mask test or serial triggers/decoders for the most popular protocols.Why on earth expect certain people "great updates with new features" - for free, of course - from Siglent of all things? Just because Siglent was doing this sometimes in the past?

author: Martin72
author_rank: Super Contributor
timestamp: May 08, 2025, 02:29:42 pm
content: That's true, Siglent has spoiled its customers in this regard..And they forget that the devices are already pretty well equipped out of the box.As an example, to surpass the functionality of the Siglent FFT, I would have to purchase an additional option from LeCroy for €2,700, as the “normal” FFT function on MAUI scopes is clearly inferior to that of Siglent.On the other hand, Siglent also charges for additional options, such as extra decoders or power analysis.There have also been firmware updates that added new decoder types, which you have to pay for in order to use them without restriction.They're not entirely selfless...Perhaps they (Siglent) think along the same lines as me.What are new features, what are options...For me, a new feature is an extension of an existing function, something that makes the scope more attractive compared to the competition.Whether you should pay for it again...Siglent probably doesn't think so, otherwise they wouldn't have been made available free of charge as a firmware update in the past.Adding a new function, on the other hand, would be an option (for which you have to pay).As I said, “we” Siglent Scope owners have been very spoiled in this regard.I think it's a characteristic, a kind of corporate identity that they are known for, that sets them apart from others, and that's why people choose them.Nevertheless, you shouldn't expect a “big hit” every time there's a firmware update.Especially since it would make no economic sense to upgrade the small models to such an extent that there would be hardly any reason left to buy a larger one.Oh well, it's not a clear-cut case.

author: KAKUL
author_rank: Contributor
timestamp: May 08, 2025, 03:27:52 pm
content: I meant this features:custom channel colors,DVM...

author: Martin72
author_rank: Super Contributor
timestamp: May 08, 2025, 04:04:43 pm
content: These are more features from the next higher series (2000 series), which would of course be nice if they were also available for the 1000 series.But I find that hard to imagine.But never say never.

author: Performa01
author_rank: Super Contributor
timestamp: May 08, 2025, 04:21:42 pm
content: Quote from: KAKUL on May 08, 2025, 03:27:52 pmThese are not "new features" - they have been available on the higher end DSOs and even on some range of the upper class 2000 series scopes.It is just so that we cannot expect to have all these features even in the entry level range of instruments. For instance, the SDS800X HD series is even more limited purely by software, e.g. lack of the M2 measurement format. And it's not even always pure marketing strategy - often it's also a matter of limited memory or FPGA ressources on the cheaper machines.Cusom colors ara availabele in the SDS2000X Plus and higher.DVM is available in SDS2000X HD and higher.

author: hfleming
author_rank: Regular Contributor
timestamp: July 24, 2025, 09:39:29 pm
content: Just a heads-up. There is new firmware (1.1.6.7) available for the SDS1000X HD scopes. I couldn’t update it via the web server, but from memory stick it works fine.The release notes say that in XY-mode split screen is available, but I couldn’t get it working yet, and the manual hasn’t been updated yet. maybe I must do a set to defaults before the split-screen XY-mode becomes available?

author: KungFuJosh
author_rank: Super Contributor
timestamp: July 24, 2025, 09:54:03 pm
content: It's usually a good idea to restore factory defaults after a firmware upgrade.