Post B6CJOmfNzbCW7NMSJM by azonenberg@ioc.exchange
(DIR) More posts by azonenberg@ioc.exchange
(DIR) Post #B6CAn5Qkyratfz236W by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg With slight delay I have tried today's master branch against my Siglent scope (with 16 bits data width).It not crash, but time data graph is "strange".In caption:- ngscopeclient display- photo of what my scope currently display
(DIR) Post #B6CAn5coG3EeHMfftI by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne Hmm, that does indeed look strange.What happens if you configure 8 bit mode, does it work normally or show the same weird behavior or something else?
(DIR) Post #B6CAn69QInK5uVvij2 by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg If I zoom out the waveform, only aliasing appearing
(DIR) Post #B6CAuHEnTr26K2rnNo by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg And generator pattern.
(DIR) Post #B6CAuHO0vaPCmdB9kW by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne Can you save a scopesession and upload it somewhere so I can look at the raw data?
(DIR) Post #B6CC92TClhGworD03U by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg You will have a beautiful core file with it.I tried to change bit depth, and clear screen.Has it doesn't do anything (visualy), I did file -> closeApp return to default stateI'm not able to reconnect to the scope and console shows:ERROR: failed to get window handleWarning: GetDigitalHysteresis is not implementedWarning: Socket read timed outWarning: Bad IDN response ERROR: Persistent bad IDN response, giving upWarning: Socket read timed outERROR: Bad IDN response Warning: No bandwidth detected for model "".1/2
(DIR) Post #B6CC92vv2wF0FudvoO by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg ERROR: Unknown protocol ERROR: Unknown scope typeERROR: Unknown prtocolERROR: Unknown protocolERROR: Protocol error, flushing read stream: Error while parsing channel offsetERROR: Protocol error, flushing read stream: Error when parsing channel attenuationAbandon (core dumped)./ngscopeclient2/2
(DIR) Post #B6CC936CQiSqlnS8ps by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne So that sequence of errors tells me the scope stopped talking outright, maybe the SCPI server process in the firmware crashed, and ngscopeclient got very confused trying to handle empty strings coming back.Not all of the parsing logic is super robust to this kind of failure so null dereffing or something doesn't surprise me; making it at least gracefully disconnect when TSHTF is planned eventually but will take some effort.
(DIR) Post #B6CCcybtgR1nXHY9HU by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg I created a directory for that with all infos in the previous share link.
(DIR) Post #B6CD5S6PcrAZ72OwO8 by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne I seem to have misplaced the link can you resend?
(DIR) Post #B6CDCiXEva0k6YPigC by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg Sure:https://kdrive.infomaniak.com/app/share/261117/3b2f3511-4418-4aea-8b30-4c7ac8f842b0
(DIR) Post #B6CIrmfexHiqZjkmgK by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg Ok I think I understood the aliasing problem.It's correct and due to on screen time scale compaction between scope and app.I change memory depth to 200Mpts, and get same result on both screens.(and still in 16 bits mode)
(DIR) Post #B6CIrmpaMNf74WOi9Y by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne aha, ok. That's weird though, ngscopeclient should be recording the same amount of memory as the scope (although you can zoom further into it). If you zoom ngscopeclient out all the way, it should be displaying the same thing the scope shows.If not, that's odd.
(DIR) Post #B6CJJU7LWv538oudiS by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg It looks to be uncorrelated.I change the memory depth and recapture without changing displayed signal.And when I zoom out I have much more datapoints displayed in app than on scope screen.(and previously it was reversed, less datapoints available in app than displayed on screen)
(DIR) Post #B6CJOmfNzbCW7NMSJM by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne Hmm, interesting. If you mouse over the channel name in ngscopeclient and check the tooltip, are you in fact getting the number of points you have selected? Or is the scope not properly executing the "set memory depth" command?
(DIR) Post #B6CJp6sxRRlMM4GL2m by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg Information provided by tooltip is the same as displayed on scope screen.Perhaps Siglent do some decoupling when reading memory for occurs.
(DIR) Post #B6CSCRkQqC1dLuugb2 by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg Is there a way other than preferences menu to check if collected data are in 8 or 16 bits range?Because rendering seems to do a lot of smoothing, so even zoomed a lot my plots looks the same in both mode.
(DIR) Post #B6CSCRuMFHxtqhYc4G by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne Not without setting breakpoints or something.Everything is converted to float32 as early as possible so we have a unified interchange format that all drivers and filters can speak without conversion
(DIR) Post #B6CSKGH7Ndku5Rvcjw by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg Are you interested by the same capture in 8 bit mode?(with it you can replay Siglent 8 and 12 bits acquisition on same source)
(DIR) Post #B6CTdg8TYUH9kSi06i by azonenberg@ioc.exchange
0 likes, 0 repeats
@jenesuispersonne Honestly at this point I am completely swamped with todos, data, and tickets. If my recent refactoring didn't introduce a regression, which appears to be the case, then we can put a bow on this for now. It's not any worse than it was before.Now, if you're offering to spend more time with the Siglent driver yourself and actually take a more active role developing it, I'll certainly support to the extent practical. We may eventually get to the point that it make sense to have a test platform that is able to record and replay interactions with real hardware as part of a test suite, but right now I have too much else on my plate to even think about it.
(DIR) Post #B6CUDhc7XLnYl2khpg by jenesuispersonne@piaille.fr
0 likes, 0 repeats
@azonenberg ok,For now I have also so many things waiting for me, I can't invest too much time in the app.But investing time in ngScopeClient is also in my todolist. not the first item, but not the last 😊 .