Why use JPA-SCPI Parser?
To save time and money now, and in the future...
Since its launch in 2002, JPA-SCPI Parser has received widespread acclaim from its customers, including some of the World's largest manufacturers of programmable instrumentation. Even those with parsers already have told us that it was easier, faster and cheaper to use JPA-SCPI Parser than to modify an existing SCPI parser from another of their products.
"We want to spend our time on writing the code that makes our product unique and not spend time writing the parser."
Read the comments of this customer and others here.
JPA-SCPI Parser has been refined over the years so that it is the easiest and the fastest way to implement SCPI on your instrument today.
Options Compared
| Option | Advantages | Disadvantages |
|---|---|---|
| 1) Don't support SCPI; Write proprietary command parser instead | Utilizes available in-house programming skills | Proprietary command sets are unpopular with customers |
| 2) Write SCPI parser in-house | Utilizes available in-house programming skills | Time (& cost) to learn the details of SCPI needed to design & implement a SCPI-compliant parser |
| 3) Employ a SCPI-skilled consultant to write a SCPI parser for you | Time saved | COST |
| 4) Use JPA-SCPI Parser | Time saved; One-off, low cost; Maintainable by in-house programmers |
None! |