Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCPI Command Handler #11

Open
3 tasks
ztnel opened this issue Jan 23, 2023 · 0 comments · May be fixed by #62
Open
3 tasks

SCPI Command Handler #11

ztnel opened this issue Jan 23, 2023 · 0 comments · May be fixed by #62
Assignees
Labels
firmware embedded software development protocol Communication and IIC protocols

Comments

@ztnel
Copy link
Contributor

ztnel commented Jan 23, 2023

Description

SCPI (Standardized Command for Programmable Instruments) appears to be the primary choice for implementing a command wrapper for an embedded system integration test platform. The goal is to develop a scpi command handler which is capable of being memory configurable to support a variety of programmable and measurement endpoints. TCP/IP will be the interface medium for SCPI commands.

Input Stream -> String Parser -> Command Filtration -> Function Selection -> Parameter -> Function Execution -> Result / Return Code -> Output Stream

Verification

Ensure the system can respond to scpi commands sent out by general purpose open source libraries such as lxi-tools and PyVISA

Tasks

  • SCPI string parser (support common SCPI syntax)
  • Create memory map for command hierarchy
  • Create function execution handlers with standardized error codes
@ztnel ztnel added firmware embedded software development protocol Communication and IIC protocols labels Jan 23, 2023
@ztnel ztnel self-assigned this Jan 23, 2023
@ztnel ztnel linked a pull request Jul 14, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
firmware embedded software development protocol Communication and IIC protocols
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant