Group Actions
Engagement
  • Author Author: Jan Cumps
  • Date Created: Date Created
  • Views 850 views
  • Likes 8 likes
  • Comments 10 comments
Related
Recommended

PST.. Release 7.1 for the Pico SCPI labTool firmware: 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.
In this post: new functionality available in the Release 7.1.

image

What's new?

Release 7 firmware makes it simpler for instrument developers to start a new project:

SCPI-LIB embedded in the project The Pico SCPI labLib (PSL) now has the SCPI-LIB as a submodule. It's no longer needed to download that lib's sources separately.
The SCPI_LIB_PATH environment is deprecated.
SCPI LIB build is handled by the PSL. It's no longer required to handle the sources build or manage the includes in the firmware app project.
SCPI terminator character configurable (7.1) The app used the SCPI-LIB default CRLF. The setting can now be changes in the application. PST set to LF only (like Keithley, Rigol, BT)
SCPI identifier with Pico unique id (7.1) The serial number in the PST identifier returns the Pico unique id (was: empty)
python unit test updates (7.1) Race condition in Service Request solved.
Moves on when Service request not invoked after 5 seconds
Adapted the SCPI identifier test (for terminator character and serial number)

The LabVIEW release adds 1 example:
image

How to get the software

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

New LabVIEW examples

You can run all examples with a Pico programmed with the PST firmware.

link to all posts

Parents

  • I’ll have a break then pick these new features up.

    on a not wholly unrelated point: did you know that you can wire an error indicator to the loop terminator (it picks up the error Boolean inside the cluster)?  I’ve seen the shift register used for the error indicator a number of times today and I don’t know why.  Either it is carrying no error, in which case you can use the same value that entered the loop for each iteration, or it is an error in which case you really want the loop to terminate - passing the error back just means, typically, any sub-vi will do nothin so you loop needlessly until the stop is pressed.  I’m now thinking I’m missing something!?!

    Also, I don’t know why the visa session has a shift register and I’ve seen that a few times today as well.  Does that change during the iteration when a visa call is made?

  • in reply to Andrew J

    shift registers will be gone in next release

    image

  • in reply to Andrew J

    There is definitely the possibility to make better examples. I'm following what Keithley does mostly. Not the best practices for a sturdy flow. But on the other hand simpler to follow the core flow.

    I should improve some of the driver blocks though. The "time-out-swallow" part in the Initialize VI, is a remnant from a previous instrument I designed.
    It's so long ago that I can't remember if it had to do with TCPIP or USB-Serial issues. But it should not be in this driver's process.

    I think I should revisit the driver blocks when I have quality time, and check them off with the latest template examples from LabVIEW. That's where they were initially based on (many moons ago).

Comment
  • in reply to Andrew J

    There is definitely the possibility to make better examples. I'm following what Keithley does mostly. Not the best practices for a sturdy flow. But on the other hand simpler to follow the core flow.

    I should improve some of the driver blocks though. The "time-out-swallow" part in the Initialize VI, is a remnant from a previous instrument I designed.
    It's so long ago that I can't remember if it had to do with TCPIP or USB-Serial issues. But it should not be in this driver's process.

    I think I should revisit the driver blocks when I have quality time, and check them off with the latest template examples from LabVIEW. That's where they were initially based on (many moons ago).

Children
No Data