Products > Test Equipment

Open source EEZ Studio for accessing your (SCPI) instruments

<< < (13/32) > >>

prasimix:
First, I'd like to announce a hot fix for M3 release (0.9.2) since few minor issues were found when working with project in ESP. It is relevant only for people who is willing to try to create or edit instrument extensions.


--- Quote from: RoGeorge on January 02, 2019, 07:28:37 pm ---
If writing a 'How to define an extension for a new type of instrument, step by step' is too time consuming for the current developing stage, maybe you can just record the screen while you re-create a very popular instrument, like Rigol DS1054Z, then post the video on YouTube.  Something casual, for developers, not marketing-level video production (eventually you can post the video as unlisted).

A simple walk through will be enough at first, in order to understand the steps and the main idea, without describing each and every button and field.


--- End quote ---

Sorry for not responding faster regarding delivering of instrument extension creation instructions, but I planned to start that process in a day or two. I'm trying to finish some other things before Chinese New Year celebration begins :). Thanks for suggestion about making a video with screenshot sequence. I'll take that into account.
 

--- Quote from: RoGeorge on January 02, 2019, 07:28:37 pm ---Just a small note for the SCPI commands that are sent by the 'Screensshot' button of the EEZ Studio (Rigol DS1054Z family extensions):

For the DS1054Z (and probably all the Rigol 1000Z oscilloscopes family), there is no need to send an SCPI 'STOP' before 'DISP:DATA?'.  The ':STOP' is sometimes mandatory (e.g. for ':WAVeform:DATA?'), but 'DISP:DATA?' can capture the screen while the oscilloscope is in the RUN mode.  Without the STOP before screenshot, the oscilloscope will preserve the RUN or STOP mode before and after the screenshot.


Another thing, it was not possible for me to edit the commands sent by the 'Screenshot' button, yet it was possible to add a new button for sending only a 'DISP:DATA?' (without the preceding STOP command).  The newly created button is working as expected.

I guess some files from the 'Rigol DS1104Z' extension were deployed as read only.

--- End quote ---

That's right. Currently we have STOP command in shortcut that comes with Rigol instrument extension, and you can in the meantime easily override it by creating your own shortcut and hide or delete one that comes from instrument extension. Here is instructions for other members how to do that and what you probably accomplished successfully:

First, open your instrument and make sure that you're in "Terminal" tab where you can check what shortcuts are currently visible:



If you move to "Shortcuts" tab you can see a list of currently available user defined shortcuts and one that comes with instrument extension. In this table you can see which one is selected to be visible in the toolbar and from here you can remove or edit selected shortcut.
Please note that shortcut that comes with instrument extension once deleted can be restored only by reinstallation of instrument extension.



If you don't want to delete it you can select it and deselect it's presence on the toolbar. Also it's possible to remove its assigned key (F2 in example below):



Now, you can define your own shortcut using "Add shortcut" green button, when an entry form will appear:



When the old shortcut that comes with instrument extension is deselected and a new one is added shortcut list will looks like this:



Finally when you move back to "Terminal" tab a new toolbar will appear:


prasimix:

--- Quote from: Rerouter on January 03, 2019, 04:46:00 am ---
--- Quote from: RoGeorge on January 02, 2019, 07:28:37 pm ---A simple walk through will be enough at first, in order to understand the steps and the main idea, without describing each and every button and field. 

Another thing, it was not possible for me to edit the commands sent by the 'Screenshot' button, yet it was possible to add a new button for sending only a 'DISP:DATA?' (without the preceding STOP command).  The newly created button is working as expected.

--- End quote ---

There are 3 main files for the definition, the .idf .sdl and the package.json

The idf atleast to me, seems to be the most basic stuff, like the error handling,

The sdl is where you define every single little detail about all the commands for the help tree, what parts are optional, what is required, and defining the return data type, though its unclear how one would fully flesh this out for commands with multiple parameters

and the package.json is where all the built in commands like the ones you want to edit are baked in to, but can be opened with a text editor, and the script you want to edit is baked into some oddly formatted java script (seems to be mainly things for a parser?? e.g. newlines and escaped text)

Using this I have so far made a definition with an image for the siglent 1000X-E's, but its not fully fleshed out, bloody thing has some 415 SCPI commands, 70% of which where undocumented.

--- End quote ---

There is no need to dig into any of above mentioned files :). That's why ESP part of the EEZ Studio exists.
Anyone who is eager to see how instrument extension "source" looks like, before step-by-step instructions is not ready, I can suggest to open one of the existing project for our EEZ H24005 power supply, currently supported Rigol scopes. In addition to that M3 version is now capable to import as a project a Keysight Command Expert offline command set zip file. A whole library (over 1GB) is freely available from here.
For example, let's say that you'd like to see how instrument extension looks like for Rigol DSO/MSO1000 family. Clone or download studio-extensions repository, and then in ESW choose File > Open... option and select org/rigol/rigol_ds_mso_1000/rigol_ds_mso_1000.eez-project file from your local disk where you clone or download repository.



And you are there... feel free to explore all menus for which I have to tell you how to use it properly :).

If you'd like to import any of Keysight command set as an ESP project, go back to ESW and this time select File > Import instrument definition... option:



Select .zip file of interest and if it's valid Keysight package a new selection form will appear:



Select Project and new ESP window will appear with parameters extracted from Keysight package. Choose Workbench extension option if simply want to add "compiled" instrument extension for selected Keysight instrument as already described in the post #12.

TiN:
prasimix


--- Quote ---Our current problem is that we don't have access to any instrument equipped with GPIB interface. I tried few times to find something as second-, third-, any-hand on the eBay but without success. Other possibility is to locate somewhere in our close proximity (actually Zagreb, Croatia, that unfortunately isn't a hi-tech zone) and try to do some development work. I'm also not aware about any T&M rental service that covers Croatia (that is for some time now part of EU). In one or another way it should be based on sort of GPIB to USB or GPIB to Ethernet bridge similar to one that you mentioned or something else (preferably open source if you ask me).

--- End quote ---

Not sure if there was any progress on GPIB side , but I have quite a fleet of instruments with GPIB that I can help to test with, if the support there. Currently I use my GPIB interfaces on linux machines (RPi) so I don't know much on what is needed (smallest/easiest libraries /etc) to make it work on Windows. Also I'm far from software world, but can do basic scripting coding to help testing.

I have industry NI GPIB-USB-HS dongles and Agilent 82357B dongle to test with, and also few Agilent E5810A GPIB-LAN gateway (visible on Windows just like LXI device over ethernet, that gateways "gpib0,N" parameter to the specific N GPIB instrument).
If you think it's helpful, I can send you 82357B dongle (free of charge) for development, as I don't use it anymore.

Once you get GPIB interfacing, i'll be happy to invest time and help adding Keithley, HP/Agilent/Keysight, Fluke and Wavetek/Datron instruments into your promising EEZ Studio.

prasimix:
Many thanks TiN for your generous offer. Yes, having access to GPIB adapter will be definitely a great step toward adding meaningful integration of GPIB channel into the EEZ Studio. I can send you in PM my address.

prasimix:
I'll present here some of new features added into M3 version.

Database housekeeping

Under Settings on the Home page is now possible to compact database, which can grow considerable over the time:



EEZ Studio will remind you (with small red indicator on the Settings icon) once a month to perform database compression. When Compact database is finished, a small summary will be displayed as shown below. Size reduction is not significant in my case since I've performed compression recently.



Exchanging session items using notebooks

Notebooks allows you to export or import selected items from the instrument session, and combine items from more instrument sessions on the single place. That could be beneficial for exchanging information with other EEZ Studio users. To initiate creation of new notebook, select one or more items from instrument session first. A new icon will appear in upper right corner called Export selected history items to notebook:



That option offers three possibility. If you'd like to exchange your data with other user select Export as notebook file. Two other options can be used to export items to new or existing notebook within EEZ Studio.



If notebook is exported into file (with .eez-notebook extension), the following new message will be displayed:



Working with notebooks is possible by selecting Notebooks tab on the Home page:



Here you can add a new notebook or import it from file, for example import notebook file:





For testing purposes, above mentioned test notebook file is zipped and attached in this post that you can for test import and display it in your EEZ Studio. Please first unzip it since forum does not allow attachment with any extension type.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod