Wrote Python drivers for the Pollux Drive#12
Open
Speedy939 wants to merge 4 commits into
Open
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
1. Background:
Currently, our test setup relies on a LabVIEW GUI to control the Pollux high-resolution positioning controller. To fully automate our testing and integrate this hardware into the Semi-ATE testflow, we need a dedicated Python driver.
The Pollux drive is critical for our magnetic testing capabilities. It is responsible for setting the magnetic field at various spatial coordinates and rotating the magnetic fields to provide either steady-state or constant-velocity magnetic field stimulation to the Device Under Test (DUT).
2. Objective:
Develop a robust, object-oriented Python driver that handles bidirectional communication with the Pollux Drive via USB (virtual COM port). This driver must expose a clean API for the Semi-ATE testflow to command physical movements, set speeds, and query hardware status.
3. Hardware Capabilities:
The driver must abstract the hardware's capabilities into Python methods, specifically supporting:
4. Technical Specifications:
5. Port Configuration (Reverse-engineered from LabVIEW NI I/O Trace):