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

  • Works like a charm! Is raising SRQ expected, or yet to be coming? 

    Also, am I correctly doing the setup for SRQ be fired up? 

    image

  • in reply to ggabe

    > Is raising SRQ expected, or yet to be coming? 

    To do. I could not get it to work. The code knows when to fire the SRQ, but I don't know (yet?) what to do in usbtmc to send correct data back

    > Also, am I correctly doing the setup for SRQ be fired up? 

    Looks correct.

    To make (example) pin 2 (also bit 2 of the custom register) fan out from CONDITION to EVENT:

    1 set the edge filter. Positive, negative, or both

    STATus:OPERation:DIGItal:INPut:NTRansition 4
    STATus:OPERation:DIGItal:INPut:PTRansition 4

    If you use the first statement, negative edge will set the EVENT bit 2. If you use query 2, a positive transition will do that. If you call both, any state transition on pin 2 will fan out to the event register.

    2 enable fan out of EVENT register sum to OPERation status register, bit 0:

    STATus:OPERation:DIGItal:INPut:ENABle 4

    3 From then on, to fan out to the OPER bit of the Status Byte register (bit 7):

    STATus:OPERation:ENABle 1

    4 And to call the SRQ when the OPER bit is set (that does not answer correctly at the moment):

    *SRE 128

     This will actually call my function setControlReply(). I have developed attempts to reply the correct answer, but the reply wasn't spotted by the SCPI client (LabVIEW, or the Interactive test tool from NI). 
    Currently its implementation is empty. I'm studying the TinyUSB code to see how I can put the state machine in the right state that it sends the data.
    At this moment, I only managed to send data after I received a command. The service request is different - I have to reply on an internal firmware status change. And I haven't managed to get that working yet.

    TL;DR: Custom registers work. Fanout works. OPER and STATUS BYTE work. SRE does not work.

Comment
  • in reply to ggabe

    > Is raising SRQ expected, or yet to be coming? 

    To do. I could not get it to work. The code knows when to fire the SRQ, but I don't know (yet?) what to do in usbtmc to send correct data back

    > Also, am I correctly doing the setup for SRQ be fired up? 

    Looks correct.

    To make (example) pin 2 (also bit 2 of the custom register) fan out from CONDITION to EVENT:

    1 set the edge filter. Positive, negative, or both

    STATus:OPERation:DIGItal:INPut:NTRansition 4
    STATus:OPERation:DIGItal:INPut:PTRansition 4

    If you use the first statement, negative edge will set the EVENT bit 2. If you use query 2, a positive transition will do that. If you call both, any state transition on pin 2 will fan out to the event register.

    2 enable fan out of EVENT register sum to OPERation status register, bit 0:

    STATus:OPERation:DIGItal:INPut:ENABle 4

    3 From then on, to fan out to the OPER bit of the Status Byte register (bit 7):

    STATus:OPERation:ENABle 1

    4 And to call the SRQ when the OPER bit is set (that does not answer correctly at the moment):

    *SRE 128

     This will actually call my function setControlReply(). I have developed attempts to reply the correct answer, but the reply wasn't spotted by the SCPI client (LabVIEW, or the Interactive test tool from NI). 
    Currently its implementation is empty. I'm studying the TinyUSB code to see how I can put the state machine in the right state that it sends the data.
    At this moment, I only managed to send data after I received a command. The service request is different - I have to reply on an internal firmware status change. And I haven't managed to get that working yet.

    TL;DR: Custom registers work. Fanout works. OPER and STATUS BYTE work. SRE does not work.

Children
No Data