Driver/ZI UHF-LI Scope trigger not armable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 459
- Forks
- 359
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 73
Description
In the current version (commit b28c13d28879a8af059e0249cfcf99df32997807) of the ZI UHF-LI driver, the Scope parameter's get method both arms the scope trigger, awaits triggering, and transfers all the data. SInce this is blocking, it is not possible to arm the trigger, start a signal that sends a trigger using a different instrument, and only then poll the data.
I suggest splitting the current get method into an arm and poll method (where the latter will be called get). For using the scope in a loop, one would then have to arm at each loop point.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ZI UHF-LI driver's Scope parameter get method and trace its current arming, triggering, and data-transfer flow. Done means the blocking operation is separated so the scope can be armed before an external trigger and its data polled afterward, including use in a loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100