You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PulseView is GUI for sigrok which makes especially experimenting with live captures/traces and triggers comfortable, allowing to stack mathematical expressions and protocol decoders (both in python).
It would be really nice to have integration of Husky into sigrok/PulseView for live capture.
I quite understand that given the sophistication of Husky's triggers+parameters and other settings it'd be non-trivial work, but it could just be with simplest triggers at beginning (maybe trick around more complex parts could be additional entry of python code for PulseView scope setup?)
Three examples of how I used it to stack analog and digital functions/decoders, or multi-traces (Proxmark 3, Hantek DSO-2090; general math functions are only in Nightly builds at the moment) :
(T55xx via Proxmark3, convert analog signal via schmidt trigger and apply stacked decoder)
(example with 96 traces recorded)
(stacking arbitrary math expressions in nightly builds)
PulseView is in my experience much more pleasant for live experimenting than any Jupyter client (includes default web one, Qt one, even paid ones like PyCharm Pro).
The text was updated successfully, but these errors were encountered:
Haven't looked at live sigrok before - we talked about using it for decoding at least at one point.
I think the main complexity will be around our current interface - basically it's most likely you need the existing USB interface to do configuration etc. This means then a small daemon or something needs to funnel the 'raw' capture data out to sigrok most likely. We did experiment a bit with this, but it quickly got complex trying to interact from both the Python "configuration" script & pushing data out.
However something as a first test that might work is a simple mode where from within Python/Jupyter you simply enter 'sigrok mode', that basically spawns the daemon which is funneling data out to a e.g. UDP port or something similar that pulseview listens on.
The current 'streaming mode' functionality often requires a capture thread anyway, so it's not totally alien basically if we tried something like that first.
Not sure on timeline, but will leave this open so we can discuss updates (or if someone is gung-ho and sees the topic...). Thanks for starting the idea!
PulseView is GUI for sigrok which makes especially experimenting with live captures/traces and triggers comfortable, allowing to stack mathematical expressions and protocol decoders (both in python).
It would be really nice to have integration of Husky into sigrok/PulseView for live capture.
I quite understand that given the sophistication of Husky's triggers+parameters and other settings it'd be non-trivial work, but it could just be with simplest triggers at beginning (maybe trick around more complex parts could be additional entry of python code for PulseView scope setup?)
Three examples of how I used it to stack analog and digital functions/decoders, or multi-traces (Proxmark 3, Hantek DSO-2090; general math functions are only in Nightly builds at the moment) :
(T55xx via Proxmark3, convert analog signal via schmidt trigger and apply stacked decoder)
(example with 96 traces recorded)
(stacking arbitrary math expressions in nightly builds)
PulseView is in my experience much more pleasant for live experimenting than any Jupyter client (includes default web one, Qt one, even paid ones like PyCharm Pro).
The text was updated successfully, but these errors were encountered: