Group Actions
Engagement
  • Author Author: Jan Cumps
  • Date Created: Date Created
  • Views 1302 views
  • Likes 11 likes
  • Comments 7 comments
Related
Recommended

PST.. Release 4 for the Pico SCPI labTool firmware (experimental functionality release): what's new?

Jan Cumps

The Pico SCPI labTool (PST) allows you to connect your PC to equipment to control and monitor all sorts of things. It runs on a Raspberry Pico.

image

In this post: new functionality available in the Release 4.

What's new?

This release adds experimental functionality.

Release 4 adds these new SCPI functions:

digital input in: registers instrument specific registers for digital input pins

STATus:OPERation:DIGItal:INPut:CONDition?
STATus:OPERation:DIGItal:INPut:PTRansition
STATus:OPERation:DIGItal:INPut:PTRansition?
STATus:OPERation:DIGItal:INPut:NTRansition
STATus:OPERation:DIGItal:INPut:NTRansition?
STATus:OPERation:DIGItal:INPut:EVENt?
STATus:OPERation:DIGItal:INPut:ENABle
STATus:OPERation:DIGItal:INPut:ENABle?

Other functionality added:

refactoring closer integration of usbtmc and scpi parser library

More info on the experimental functionality:

 PST.. Experimental event / trigger support for Pico SCPI labTool - 1: investigate
PST.. Experimental event / trigger support for Pico SCPI labTool - 2: design the registers
PST.. Experimental event / trigger support for Pico SCPI labTool - 3: Instrument Specific Registers Test
PST.. Experimental event / trigger support for Pico SCPI labTool - 4: let TinyUSB USBTMC code use SCPI-LIB's Status Byte register
PST.. Experimental event / trigger support for Pico SCPI labTool - 5: Propagation to IEEE488.2 SCPI Registers Test

How to get the software (binary included)

check this post for a "how to install firmware and run the first LabVIEW process" video.

download link info
Pico firmware backwards compatible with previous versions. includes the .uf2 file to program your Pico right away
LabVIEW driver backwards compatible with previous versions. driver blocks for new functionality and extra examples

Command reference

This section describes the added commands. It lists

  • the SCPI syntax,
  • LabVIEW Virtual Instrument driver block
  • the pins that are used, 
  • parameters, return values.
digital input registers query the registers of a digital input, set filter and fan-out to IEEE488.2 Operation Status register

bits:

0: GP20
1: GP21
2: GP27

registers:

CONDition
PTRansition
NTRansition
EVENt
ENABle

fan-out to IEEE488.2:

Operation Status[0]
SCPI STATus:OPERation:DIGItal:INPut:CONDition?
STATus:OPERation:DIGItal:INPut:PTRansition
STATus:OPERation:DIGItal:INPut:PTRansition?
STATus:OPERation:DIGItal:INPut:NTRansition
STATus:OPERation:DIGItal:INPut:NTRansition?
STATus:OPERation:DIGItal:INPut:EVENt?
STATus:OPERation:DIGItal:INPut:ENABle
STATus:OPERation:DIGItal:INPut:ENABle?

VI Use LabVIEW VISA write and read

For the compete reference:  PST.. Program the Pico SCPI labTool? 

LabVIEW

This version doesn't include LabVIEW changes. I cut a driver release, to keep the versions in sync.

link to all posts

Parents

  • Jan, you are moving much faster than I can keep up.

    Don't stop, I will work with which ever version I can get into my Pico.

  • in reply to DAB

    Don't worry,  . All releases are incremental. This firmware is still compatible with the initial release. And with all previous versions of the SCPI driver.

    in essence, there is

    • a set of simple functionality. With a LabVIEW block to support each of them:
      • digital in and out
      • analogue in and out
    • a medium advanced function. Still supported by a LabVIEW block, but requires you to connect an ADC IC to the Pico:
      • high precision analogue in
    • advanced functionality, supported by lower level LabVIEW write and read blocks:
      • the instrument specific registers

    All of this works in isolation. You can get a useful design by just using the simple functions.

Comment
  • in reply to DAB

    Don't worry,  . All releases are incremental. This firmware is still compatible with the initial release. And with all previous versions of the SCPI driver.

    in essence, there is

    • a set of simple functionality. With a LabVIEW block to support each of them:
      • digital in and out
      • analogue in and out
    • a medium advanced function. Still supported by a LabVIEW block, but requires you to connect an ADC IC to the Pico:
      • high precision analogue in
    • advanced functionality, supported by lower level LabVIEW write and read blocks:
      • the instrument specific registers

    All of this works in isolation. You can get a useful design by just using the simple functions.

Children
  • in reply to Jan Cumps

    (add:)

    The advanced functionality isn't required for this device. It's my attempt to grow "building SCPI firmware" skills. That's the reason why I called them experimental. And took care to not let them interfere with standard functionality.

    I'm convinced that this design is a valuable lab instrument as it is.
    And I like to use it to get some niche SCP skills - both for LabVIEW and instrument firmware development.

    I'm trying to keep all of that in the open - publishing my (sometimes naive) code and LabVIEW drivers. The only way to get good feedback is by publishing what you do - and hope that it gets challenged/reviewed.

    But my goal is not just to build a SCPI instrument. I also want to improve my own capabilities. That's why you'll see  a mix of needed functionality and fancy stuff.
    If you have similar goals, feel free to contribute to the core. Or to use this project to grow your own professional skills.