Can someone confirm my suspicion (based on manuals) that the SDS1000X-E series does _not_ allow users to dim the overall LCD brightness?
Looks to me like SDS2000X+ or HD would deliver the ability to dial back the brightness
If by overall brightness you mean the backlight, then AFAIK no. There are other adjustments that seem sufficient and I've never, ever felt the need to try and reduce the brightness on this scope. The background is mostly black and there is an intensity control for the traces.
Can someone confirm my suspicion (based on manuals) that the SDS1000X-E series does _not_ allow users to dim the overall LCD brightness?
Looks to me like SDS2000X+ or HD would deliver the ability to dial back the brightness, but not the SDS1000X-E... idk whether I'll ever hear back from yday morning's emails to info@ & sales-usa@ but prime day prices are near the end...
(IMO LCDs sans dimming should be outlawed.)
If by overall brightness you mean the backlight, then AFAIK no. There are other adjustments that seem sufficient and I've never, ever felt the need to try and reduce the brightness on this scope. The background is mostly black and there is an intensity control for the traces.
Useful info for most, but in this case there's backlight bleed + contrast edge bleed that are filtered out by most brains, but astigmatism thwarts that filter, sometimes on its own, but especially when amplified by other visual sensitivities. "Ever endure a video shot by someone oblivious to how greasy their camera lens is? Like that."
(or so I'm told...)
OK so you have a LCD edge bleed problem do you ?
Was just trying to sort out whether the SDS1000X-E series allowed for overall (backlight) dimming like the bigger siblings have.
Please share more about 'troublesome for those with certain eyeball and/or neurological differences' for the designers to consider for existing and future products.
Discussing sensory phenomenology (ineffable by definition) seems a bit futile and truly I've gotta wonder if you're having a laugh.
Quote from: tautechPlease share more about 'troublesome for those with certain eyeball and/or neurological differences' for the designers to consider for existing and future products.
Discussing sensory phenomenology (ineffable by definition) seems a bit futile and truly I've gotta wonder if you're having a laugh.
Aside from that backlight request, basic consideration of the common (two?) variants of color blindness would probably be good practice. It doesn't help me in particular but I'm not just on a quest to self-serve.
Certainly not, do you expect the EE's that design this stuff to be optical experts, I don't and hence I asked for some guidance as I well know they can read English.
Hi Folks,
I've got an SDS1104X-E, stock OS 8.1 and FW 6.1.25R2 (if I remember correctly) that won't go past boot screen.
I've made several attempts at the powerup while tapping the MATH button "2 - 3 times a second" - no success. Probably no surprise I'm REALLY hoping there's a few other tricks I can try before sending off for warranty repair.
Is it reasonable/safe for me to try
1) prepping a USB drive with an OS update
2) Can I feed the web server an ADS file
Nothing particularly crazy done to it. About a year ago, I added ntpd using a method similar to what wpwrak described here
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1812089/#msg1812089
Yesterday I was contemplating a change that I ultimately decided to leave well enough alone. I can't rule out having started into it and set /usr/bin/siglent as rw before I decided to not bother. So, there's a chance it never got switched back to ro. Would have said it went through one reboot since then, but I left it running overnight and used it most of today before I rebooted and got here.
Here's more excruciating details in case any of it's useful:
- I get Siglent logo on screen and keys lit up (Run/Stop is orange, so R+G LEDs) for about 8 seconds, then they all turn off for half a second and all come back on. (With a proper bootup, after blanking, I'm used to seeing the channel buttons light up in sequence). I've let it sit for a few hours, no change.
+ Scope gets IP from DHCP server
+ Scope responds to ICMP pings
- SCPI and SOCKET ports 5024 and 5025 refuse connections
+ Web server is working, but
- SCPI commands fail ("*IDN?" gets a "Device can not be connected" response)
- On Information section, "Instrument Model", "Software Version" and "Serial Number" are all empty
- Instrument Control section just shows that spiffy Siglent logo
+ I can expand the controls section and the "Version Update" button appears to work
+ "Screen Save" and "Bin_to_CSV_Tool" buttons are functional, but not sure how much behind the web server are actually active.
- "Waveform Save" obviously does NOT work.
+ if I put a USB drive in the front or back USB ports, once the logo is displaying, the drive does show activity as though it's being enumerated, and maybe files system is being checked.
- I have a thumb drive with a "siglent_device_startup.sh" to launch telnetd, but this appears to do nothing.
Thanks
...I've made several attempts at the powerup while tapping the MATH button "2 - 3 times a second" - no success. Probably no surprise I'm REALLY hoping there's a few other tricks I can try before sending off for warranty repair...
...I've made several attempts at the powerup while tapping the MATH button "2 - 3 times a second" - no success. Probably no surprise I'm REALLY hoping there's a few other tricks I can try before sending off for warranty repair...
Never heard about that MATH button tapping. What's it for?...
Any other secret key combinations to be aware of?
Welcome to the forum and check your messages with our contact details so to fix this scope for you.
Don't try/use any other method than using the tools Siglent provide to us.
Thanks tautech, that did the trick and I'm back in business. Thanks for the assistance!
Thanks tautech, that did the trick and I'm back in business. Thanks for the assistance!
I've got one abstract follow-up: the web interface now shows
LXI Extended Functions null
LXI Version 1.5 LXI Core 2017
I'm going from memory, but pretty sure before the scope was out-to-lunch, the "LXI Extended Functions" had non-null info and "LXI Version" was something "1.5.x Core 2019". Curious why those are now different. Is this not contained in the OS/FW? A setting somewhere I'm overlooking.
Background: With the unbricked scope, I'm finishing some data collection where I want no doubts of consistency. I've got some scripted SCPI for automation, and I rely on some saved setups. Might be silly, but not interested in chasing differences in support functionality etc. between FW versions, so following recovery I "restored" OS to 8.1 and FW to 6.1.35R2 (I mispoke citing 6.1.25R2 as the FW ver in my earlier post).
When I step up my SCPI / LXI game, which will include a upgrade to V2 OS and current FW, how do I ensure there's nothing missing here?
Cheers!
[...]
Even EDUMODE shouldn't be shared on a public forum.
[...]
Even EDUMODE shouldn't be shared on a public forum.
That's interesting. Is there an NDA that applies to "EDUMODE" or, barring that, any way those w/ access to the feature(s) to be aware of this prohibition?
Hi there
Can anyone explain the meaning of the beep when starting the SDS 1104X-E?
My device sometimes beeps twice at startup? (Firmware version: V6.1.35R2)It's like a POST test but if you don't like it in Utilities you can turn the sound OFF. Use Default and it will be back unless you make your personal Default settings and save then using the Set to Default feature in the Save/Recall menu.
Some notes from using the scope (SDS 1104X-E 6.1.37R9).
B) Probe attenuation settings is more involved than needed. The procedure to change from 10x to 1x is:
............