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

PSL.. Pico SCPI USBTMC labLib makes it easier to write your own PST.. Pico SCPI labTool

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. 
To make it easier to create several specialised lab instruments, the project is now split up in the Pico SCPI USBTMC labLib (PSL) and the original labTool (PST).
The labTool (as of release 6) is adapted to use the PSL. It serves as a proof of concept for the lib. And as a template project for new instruments.

image

This will enable the pattern: build little instruments, with cheap Picos, that can do great things. 
With USBTMC, SCPI and IEEE488.2 support out-of-box.

How does this work?

There's a new github project for the PSL. As much as possible of the common infrastructure is moved into the lib:

  • usbtmc handling
  • standard SCPI command definition and handling, including error handling, status byte management and service request support, 

The PST project has significantly slimmed down. It doesn't have to deal with the core functionality anymore, and can focus on the instrument functions:

  • DIGI IN
  • DIGI OUT
  • ANA IN
  • HIRES ANA IN
  • ANA OUT
  • instrument specific registers
  • naming for the USBTMC instrument
  • naming for the *IDN? string

For someone who wants to check out the instrument code: you will automatically also download the library.
Use this clone command, with submodules enabled, to fetch the code:.

git clone https://github.com/jancumps/pico_scpi_usbtmc_labtool.git --recurse-submodules

The build command works as before. The PST make file will automatically also call the PSL make file.
As usual, the release also provides the firmware precompiled and ready to load in .uf2 format. 

Want to start your own firmware project? 
Check out  Do you want to create your own Pico SCPI device, based on PST.. Pico SCPI USBTMC labLib (and labTool)? .

There are no functional changes in this release. That makes it easier to validate if this refactoring introduces regression.

link to all posts

Parents

  • Excellent work, I just tried it with my Labview Community Edition and it works like a charm.

    Just one idea (maybe crazy, I don't know). Is it possible to modify it for wifi and Pi Pico W. I mean, instead of USB, one should be able to connect to the Pico through WiFi with standard VISA string like "TCPIP0::address::something::INSTR" ?

Comment

  • Excellent work, I just tried it with my Labview Community Edition and it works like a charm.

    Just one idea (maybe crazy, I don't know). Is it possible to modify it for wifi and Pi Pico W. I mean, instead of USB, one should be able to connect to the Pico through WiFi with standard VISA string like "TCPIP0::address::something::INSTR" ?

Children
  • in reply to PavelKCZ

    Basic port to TCP is not hard: getting commands from LabVIEW to a socket, and replying back. There is essentially one entry point where you give data to the SCPI lib, and one exit point where you send back SCPI replies. I've done this a few times for Linux devices.

    The complex thing will be to create standard compliant devices that are detected by VISA . And to port the interrupt / service-request part of the lib's functionality (although that's optional).