Group Actions
Engagement
  • Author Author: Jan Cumps
  • Date Created: Date Created
  • Views 611 views
  • Likes 9 likes
  • Comments 2 comments
Related
Recommended

PST.. Release 5 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 5.

What's new?

This release adds experimental functionality.

Release 5 adds these new SCPI functions:

IEEE 488.2 service request support instrument can notify host based on events in the status byte

image

Other functionality added:

unit tests tests for service request added

More info on the experimental functionality:

 PST.. Experimental event / trigger support for Pico SCPI labTool - 6: Service Request from Instrument to LabVIEW flow 
PST.. Experimental event / trigger support for Pico SCPI labTool - 7: Test Service Request from Instrument to LabVIEW flow 

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

LabVIEW

This version includes LabVIEW example for the Service Request functionality.

link to all posts

  • in reply to rsc

    I've been thinking about versioning, and what should change when cutting a new release.

    • should the *IDN? report a different version?
    • should the LabVIEW driver check for it?
      give a warning when driver and firmware don't match?
      fail if they don't match?
      give the flow designer the option to check for firmware version or ignore it?
    • things we haven't considered yet

    At this moment, the .uf2 is a little gesture for those that don't like to play with the sources. To lower the entry path.
    Playing with the sources and let the community develop features was the raison d'être.
    The rest is being worked on as an afterthought Slight smile.

  • Now that you have released multiple revisions, it would be helpful for version tracking to have the revision number in the filename.

    pico_scpi_usbtmc_labtool.uf2 could be pico_scpi_usbtmc_labtool_R5.uf2

    Scott