05:21 <_whitenotifier-b> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±2] https://github.com/ngscopeclient/scopehal-apps/compare/2b6c841ed306...6c4e37671bbb

05:21 <_whitenotifier-b> [scopehal-apps] azonenberg 6c4e376 - Updated submodules including workaround for graph editor segfault

09:29 <_whitenotifier-b> [scopehal] hansemro opened pull request #825: SiglentSCPIOscilloscope: improve SetADCMode reliability for SDS2000X+ - https://github.com/ngscopeclient/scopehal/pull/825

09:29 <_whitenotifier-b> [scopehal] hansemro opened pull request #826: SiglentSCPIOscilloscope: update SDS2000X+ comments - https://github.com/ngscopeclient/scopehal/pull/826

09:32 <_whitenotifier-b> [scopehal] hansemro commented on pull request #826: SiglentSCPIOscilloscope: update SDS2000X+ comments - https://github.com/ngscopeclient/scopehal/pull/826#issuecomment-1831533009

09:35 <_whitenotifier-b> [scopehal] hansemro synchronize pull request #826: SiglentSCPIOscilloscope: update SDS2000X+ comments - https://github.com/ngscopeclient/scopehal/pull/826

09:36 <_whitenotifier-b> [scopehal] hansemro commented on pull request #826: SiglentSCPIOscilloscope: update SDS2000X+ comments - https://github.com/ngscopeclient/scopehal/pull/826#issuecomment-1831539875

09:49 <_whitenotifier-b> [scopehal] hansemro commented on issue #820: Siglent: Initial force trigger results in continous single trigger operation - https://github.com/ngscopeclient/scopehal/issues/820#issuecomment-1831559880

15:35 <_whitenotifier-b> [scopehal] azonenberg pushed 2 commits to master [+0/-0/±2] https://github.com/ngscopeclient/scopehal/compare/277b4c52dcf9...b56ac3902195

15:35 <_whitenotifier-b> [scopehal] hansemro 29de5f9 - SiglentSCPIOscilloscope: update SDS2000X+ comments

15:35 <_whitenotifier-b> [scopehal] azonenberg b56ac39 - Merge pull request #826 from hansemro/siglent-sds2000xp-comment-update SiglentSCPIOscilloscope: update SDS2000X+ comments

15:35 <_whitenotifier-b> [scopehal] azonenberg closed pull request #826: SiglentSCPIOscilloscope: update SDS2000X+ comments - https://github.com/ngscopeclient/scopehal/pull/826

15:35 <_whitenotifier-b> [scopehal] azonenberg closed pull request #825: SiglentSCPIOscilloscope: improve SetADCMode reliability for SDS2000X+ - https://github.com/ngscopeclient/scopehal/pull/825

15:35 <_whitenotifier-b> [scopehal] azonenberg pushed 3 commits to master [+0/-0/±3] https://github.com/ngscopeclient/scopehal/compare/b56ac3902195...a3434e28edcc

15:36 <_whitenotifier-b> [scopehal] hansemro 086b346 - SiglentSCPIOscilloscope: SetADCMode: move :WAV:WIDTH command to end and query trigger mode for delays This shifts the :WAV:WIDTH command after stopping/re-arming the trigger and replaces thread sleep with a query command. Inserting query commands seems to work more reliably under latent/unstable network connection scenarios.

15:36 <_whitenotifier-b> [scopehal] hansemro 2ac506f - SiglentSCPIOscilloscope: SetADCMode: always set trigger mode to auto This addresses a race condition between the scope in normal mode (continuous single trigger) and SetADCMode SCPI command sequence that results in an unexpected force trigger. For reference, SDS2000X+ will force trigger if set to single trigger while already awaiting to be single triggered rather than resume

15:36 <_whitenotifier-b> in single trigger. This force trigger behavior can be confirmed by sending the following commands together: :TRIG:MODE SINGLE;:TRIG:MODE SINGLE;:TRIG:MODE? This should reply with FTRIG. However, by inserting :TRIG:MODE AUTO between the two :TRIG:MODE SINGLE commands, we can prevent a force trigger from happening.

15:36 <_whitenotifier-b> [scopehal] azonenberg a3434e2 - Merge pull request #825 from hansemro/siglent-sds2000xp-adc-set-v2 SiglentSCPIOscilloscope: improve SetADCMode reliability for SDS2000X+

15:36 <_whitenotifier-b> [scopehal] azonenberg closed issue #821: Siglent: Improve SetADCMode reliability under slow/unstable network connection - https://github.com/ngscopeclient/scopehal/issues/821

17:37 <_whitenotifier-b> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±4] https://github.com/ngscopeclient/scopehal-apps/compare/6c4e37671bbb...abe3c6fd0ebd

17:37 <_whitenotifier-b> [scopehal-apps] azonenberg abe3c6f - Allow waveform groups to be renamed, use stable IDs for back end even if group is renamed. Fixes #640. Group renaming only works if group is UNDOCKED (see https://github.com/ocornut/imgui/issues/316) for now.

17:37 <_whitenotifier-b> [scopehal-apps] azonenberg closed issue #640: Allow waveform groups to be renamed - https://github.com/ngscopeclient/scopehal-apps/issues/640

18:10 <_whitenotifier-b> [scopehal-apps] azonenberg opened issue #649: Filter graph editor: when first instantiating a new node, make sure it won't displace anything already there - https://github.com/ngscopeclient/scopehal-apps/issues/649

18:40 <_whitenotifier-b> [scopehal] azonenberg opened issue #827: LeCroy: support "fast edge" as trigger source for edge trigger - https://github.com/ngscopeclient/scopehal/issues/827

18:40 <_whitenotifier-b> [scopehal] azonenberg opened issue #828: LeCroy: Support "AC line" as trigger source for edge trigger - https://github.com/ngscopeclient/scopehal/issues/828

19:00 <_whitenotifier-b> [scopehal] azonenberg pushed 1 commit to master [+0/-0/±1] https://github.com/ngscopeclient/scopehal/compare/a3434e28edcc...ad2dcbddac7a

19:00 <_whitenotifier-b> [scopehal] azonenberg ad2dcbd - MovingAverageFilter: change default depth to a nonzero value so we don't get garbage when creating a new filter instance

23:51 <d1b2> <hansemro> These look great. I think max icon should use a different waveform with a more obvious peak.