Products > Test Equipment

Open source EEZ Studio for accessing your (SCPI) instruments

<< < (12/32) > >>

Rerouter:
Looking forward to your write up, I have gotten most of my scopes written up in your current XML formats, but the definition is an invalid link and it seems its not fully implemented?

Things like synopsis of a function, a command format, or making a clear way to deal with mandatory and optional terms

prasimix:
Hi everyone, just a quick notice that the latest milestone (M3, v0.9.1) is just published and available on the GitHub for download and evaluation. I didn't manage to include step-by-step instructions how to add a new instrument, but I'll try to keep up with the promise and start to write about it here in the coming days. I'll also post screenshots about newly added features. Thanks in advance for your attention and possible comments and questions.

RoGeorge:
Installed the Linux deb version on Ubuntu 18.10, then grabbed a screenshot from a Rigol DS1054Z.

All working, THANK YOU!  :clap:


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. 


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.


Good idea to make a separate repo for the instruments (extensions only).
So far, great job!  :-+

bicycleguy:

--- Quote from: prasimix on December 31, 2018, 02:07:50 pm ---Hi everyone, just a quick notice that the latest milestone (M3, v0.9.1) is just published and available on the GitHub for download and evaluation. I didn't manage to include step-by-step instructions how to add a new instrument, but I'll try to keep up with the promise and start to write about it here in the coming days. I'll also post screenshots about newly added features. Thanks in advance for your attention and possible comments and questions.

--- End quote ---

New years resolutions  :-+

Rerouter:

--- 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.

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