|
|
|
Why use JPA-SCPI Parser?
...simply
to save time, money, and money 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.” |
|
To read more of this customer's
comments, click here |
Let us explain
how JPA-SCPI Parser could help you too...
When creating the command language
parser for your instrument, you have four choices:
-
Don't support SCPI -
Implement your own proprietary command language instead, and write
your own command parser
-
Support SCPI - Write your
own SCPI parser in-house
-
Support SCPI - Employ a SCPI
consultant to write a SCPI parser for you
-
Support SCPI - Use a
ready-made SCPI parser: JPA-SCPI Parser
Options Compared
| Option |
Advantages |
Drawbacks |
| Don't
support SCPI; Implement proprietary command parser instead |
- Utilizes available in-house programming skills
|
-
Proprietary
command sets are unpopular with customers
-
Time
(& cost) spent to specify command set, design, implement
& test parser
|
Write
SCPI parser
in-house |
- Utilizes available in-house programming skills
|
-
Time
(& cost) to learn the details of SCPI that are necessary
to design and implement a SCPI-compliant parser
-
Time
to design & test SCPI parser - Estimate: minimum of 3 weeks
work for a competent programmer
|
| Employ
a SCPI consultant to write a SCPI parser for you |
|
|
| Use
JPA-SCPI Parser |
|
|
What One of Our Customers had to say:
|
“I had the parser
implemented in a test form in our embedded code the day after we
received [JPA-SCPI Parser] and it would have been sooner but I
didn't have time to look at it on the first day.
The following day our
programmer that is dealing with the PC side of the software also had it
running. We both found it very straight forward to use and the
documentation is superb (unusual for software products).
Our product is a multichannel, modular instrument (we don't even know
what some of the modules will be yet) and so we need a command language
that can expand with it, which is why we chose SCPI.
[JPA-SCPI Parser] will be of enormous use to us. We want to
spend our time on writing the code that makes our product unique and
not spend time writing the parser.” |
|
Malcolm Hartnell, Principal
Engineer
PerkinElmer Optoelectronics,
www.Opto.PerkinElmer.com |
|
