Siglent SDS814X HD can’t select Auto Trigger  - Page 1
Forum section: electronics / testgear

author: Roman oh
author_rank: Regular Contributor
timestamp: March 24, 2025, 09:02:30 am
content: I Just picked up my brand new 814x HD; my 1104X-E will hopefully be relegated to the back shelf. I did the 824 upgrade straight away before I really started playing with it. As I was testing, I noted that I was unable to select Auto Trigger - no response to the button press, it stays on Normal. And no trace, “Waiting for Trigger”. Power up defaults to Normal, unlike the 1104X-E which defaults to Auto. I can select Single OK, but then if I press Auto the button press is detected but the mode switches to Normal.Is there some obscure configuration setting somewhere, or am I missing something really obvious, or is this a fault?If it’s a fault, how do I handle it? Return to vendor (a local Siglent reseller)? Or through Siglent somehow?Roman

author: tautech
author_rank: Super Contributor
timestamp: March 24, 2025, 09:27:59 am
content: Which firmware version is installed ?Screenshots using a mouse showing a pointer would be useful for us......

author: tautech
author_rank: Super Contributor
timestamp: March 24, 2025, 10:12:54 am
content: Auto or Normal triggering can only be selected from the front panel buttons or the Trigger dropdown menu.Using latest firmware here, V1.1.6.2, see webserver screenshots attached.

author: Roman oh
author_rank: Regular Contributor
timestamp: March 25, 2025, 04:22:19 am
content: thanks, @Tautech, for responding - and for all the help you give to Siglent fans everywhere!I am on software 1.1.3.8 at the moment - all my USB drives are in another place at the moment, but I will upgrade as soon as...(pity this can't be done via web-server - or can it?)I'm not sure what sort of screen shot would be useful (I don't yet have a USB mouse, but that's on my list).And clearly I haven't worked out how to clip selected quotes out of other postsSimple fact is, I cannot select Auto trigger, from buttons, trigger menu, or webserver control. Any attempt to do so gets me to Normal. Sounds like a software thing, but from searching posts on this forum, I can find no suggestion of a software bug related to this issue.The cal certificate that came with my instrument is dated 2025-02-08. How can it be so many software versions behind?Roman

author: tautech
author_rank: Super Contributor
timestamp: March 25, 2025, 07:27:12 am
content: Quote from: Roman oh on March 25, 2025, 04:22:19 amYou're on the last version....don't let the version #'s bluff you, sometimes there are several beta versions before public release.For giggles I've downgraded to 1.1.3.8 for the attached screenshot, this one from USB stick and no change of Auto/Normal trigger selection.I suspect something is up from your enhancements but have no grounds to prove it.Did you see the same trigger type selection behaviour before the enhancement ?I have an idea how to proceed but that's for later ......

author: Roman oh
author_rank: Regular Contributor
timestamp: March 25, 2025, 07:59:00 am
content: I can’t say I noticed anything wrong before the upgrade but I didn’t notice anything right, either - simply didn’t notice. Should I reverse the upgrade and reload the software?But surely this has been done by many before me without problems??Roman

author: tautech
author_rank: Super Contributor
timestamp: March 25, 2025, 08:15:12 am
content: Quote from: Roman oh on March 25, 2025, 07:59:00 amYup or you are the 1st to notice a trigger type selection issue.Generally you can roll back and forth firmware with Siglent devices unless it's specified in the install instructions; roll back to earlier versions is not supported or words to that effect.

author: Roman oh
author_rank: Regular Contributor
timestamp: March 26, 2025, 07:12:22 am
content: Last night I read the entire manual, and on the very last page, the very last thing, was a one-line reference to Firmware update via the webserver. So-o-o-o EASY!Anyway, I reset the instrument to 814 configuration, as it came, but this made no change to the Auto triggering problem.I reloaded V1.1.3.8 software - no change.I loaded V1.1.6.2 - no change.And I notice that "Force" trigger does not Force a sweep in the absence of input; according to my reading it should force a single sweep, should it not?I am now out of ideas. I would appreciate any further advice.Roman

author: tautech
author_rank: Super Contributor
timestamp: March 26, 2025, 07:56:30 am
content: Quote from: Roman oh on March 26, 2025, 07:12:22 amBit busy ATM but will be in contact soon.

author: rf-loop
author_rank: Super Contributor
timestamp: March 26, 2025, 12:36:52 pm
content: Quote from: Roman oh on March 24, 2025, 09:02:30 amHave you donekeyboard test (utility / maintenance / selftest Keyboard test) hard to believe there is problem because it still works many ways... but we all know well our friend Mr Murphy...Quote from: Roman oh on March 26, 2025, 07:12:22 amI have tested just now with SDS800X HD and latest FW (1.1.6.2) and trigger Force works just ok and also previously when I have used lot of SDS800XHD I have never seen symptoms / problems what you told.Btw, there is three places where you can Force...Drop down menu top of screen.Pushing bottom screen Trigger info (near Time and LAN info)It pops up window and there can selectThen screen top right corner where is Trigger counter and Siglent logo. Pushing it do Force.Naturally Force works only in Normal and Single mode. It Force one acquisition independent of signal and trigger.If it do not... there is something wrong.And Factory default for Trig mode is Auto. Weird is also that it goes back to Normal mode automatically if I understood right...I have never seen this behavior in this model.Please also do:1. Utility / Save/Recall select Mode Recall and select type Security Erase and push Recall2. Utility / Save/Recall select Mode Recall and select type FactoryDefault push Recall3. and remember carefully do full keyboard test as said previously and note every button and knob and push give just right info and nothing else.Quote from: tautech on March 24, 2025, 10:12:54 amAnd for OPThere is three places for select mode Auto, Normal and Single.1. Front panel buttons. (no push button for Force)2. Top of window Trigger dropdown menu (include also Force)3. Using bottom right side Trigger info. Pushing it, opens small window where can set also Auto, Single, Normal and Force trig (for one trigger independent acquisition)And extra... Force can also do without any menu... top right corner push with touch or klic mouse over Siglent logo.In Normal or Single mode Force start one acquisition independenly fron signal and trigger condition.(Single mode: If do Force then it do one Single independent of trig ans signal and after then Stop... so if need continue in Single, then need again

author: tautech
author_rank: Super Contributor
timestamp: March 27, 2025, 02:48:06 am
content: Quote from: tautech on March 26, 2025, 07:56:30 amCheck your forum messages.

author: tautech
author_rank: Super Contributor
timestamp: March 27, 2025, 07:25:49 am
content: Quote from: tautech on March 27, 2025, 02:48:06 amThis is the recommendation from Siglent as member rf-loop has already posted above:1. Utility / Save/Recall select Mode Recall and select type Security Erase and push Recall2. Utility / Save/Recall select Mode Recall and select type FactoryDefault push Recall3. and remember carefully do full keyboard test as said previously and note every button and knob and push give just right info and nothing else.

author: Roman oh
author_rank: Regular Contributor
timestamp: March 27, 2025, 11:02:42 am
content: Check your forum messages.Have responded.

author: Roman oh
author_rank: Regular Contributor
timestamp: March 27, 2025, 11:43:55 am
content: Thanks rfloop,(Still can't work out how to quote!)SO I did those resets as you suggested. After restore Factory Defaults the beast works exactly as it should. It even survived the update to 824. I guess I should have thought of this - I plead unfamiliarity and ignorance!I will only spend a brief time wondering what could have caused thisIssue resolved, problem solved. Many thanks to you and tautech for your help!Roman