SMU-Agilent_415x -> add VSU channels

[franz-sweepMe]

VSU allow only to source voltage, so no measured values are returned

[gemini-code-assist]

Summary of Changes

Hello @franz-sweepMe, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces support for Voltage Source Unit (VSU) channels on the Agilent 415x parameter analyzer. The changes enable users to select and utilize VSU channels for voltage sourcing, while correctly disabling measurement functionalities and current sourcing, aligning with the hardware's capabilities. This enhancement provides more comprehensive control over the instrument's various channel types by integrating VSU channels into the existing driver architecture.

Highlights

• VSU Channel Support: Added comprehensive support for Agilent 415x VSU (Voltage Source Unit) channels, allowing them to be selected and used for voltage sourcing.
• Measurement and Sourcing Restrictions: Implemented logic to explicitly prevent current sourcing and measurement operations when a VSU channel is active, aligning with the hardware's voltage-sourcing-only capability.
• GUI and Internal Handling: The GUI now includes 'VSU1' and 'VSU2' as channel options, and internal methods have been updated to correctly identify and manage VSU channels (assigned internal IDs 21 and 22).
• Documentation and Clarity: Updated docstrings and the device description to clearly state the purpose and limitations of VSU channels, including their lack of measurement and compliance settings.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds support for VSU channels to the Agilent 415x driver, enabling voltage sourcing and preventing measurement operations on these channels. However, a high-severity command injection vulnerability was identified where the source parameter, derived from user input, is not properly sanitized, potentially allowing arbitrary commands to be executed on the instrument. Additionally, there are suggestions to improve channel parsing robustness, fix a variable usage bug, and enhance code consistency and documentation.