Jump to content

[Request for feedback] Python visual scripting IDE


Recommended Posts

Hello LAVA community!

We've built a free, open-source visual programming IDE that comes with out-of-the-box support for SCPI and most popular instrument brands (NI, Keysight, Tektronix, Rhode & Shwarz, etc). 

We're looking for beta users and feedback to make this Desktop app as useful as possible. It's completely free and does not require any coding or command-line knowledge. In particular, we're looking for feedback on how this early version of Flojoy compares to LabVIEW and TestStand. Here are a few getting started links:

  1. Download Flojoy (for Mac, Windows, or Linux)
  2. Flojoy examples for Tektronix instruments
  3. Flojoy examples for other hardware devices and instruments
  4. [Advanced] How to build your own Flojoy drivers and blocks in Python
  5. YouTube channel

If you have questions or need help connecting to an instrument, please simply reply below or join our Discord chat. If you don't see your instrument supported in Flojoy's blocks, let us know and we may be able to add it for you.

Screenshot of Flojoy desktop app:

image.png.a3fc915005cd4453488a8f4aac924817.png

 

 

 

Edited by Jack Parmer
Link to comment

This is exactly the kind of feedback we're looking for - thank you!

In terms of a test sequencer / test orchestrator, the UI that we've been contemplating would allow you to import full Flojoy test apps (or Python scripts) as blocks on the canvas, then wire these "super blocks" together in parallel or series. The last block might generate a report and upload it to a data store. Do you think that this would be sufficient for batch test orchestration, or should we consider a different UI?

(Also agree on the videos - we'll start getting more into the nitty gritty of what each test & measurement app is doing).

Appreciate any thoughts, feedback, suggestions, ideas, etc. Thanks again!

Link to comment
On 12/15/2023 at 5:28 PM, Jack Parmer said:

This is exactly the kind of feedback we're looking for - thank you!

In terms of a test sequencer / test orchestrator, the UI that we've been contemplating would allow you to import full Flojoy test apps (or Python scripts) as blocks on the canvas, then wire these "super blocks" together in parallel or series. The last block might generate a report and upload it to a data store. Do you think that this would be sufficient for batch test orchestration, or should we consider a different UI?

You may want to reconsider trying to advertise this as a test sequencer competitor. Wiring together blocks is NOT a test sequencer by a long stretch. If that was the case there would be no Test Stand, since LabVIEW can do that already since 35 years. Users of applications like Test Stand expect a lot more than that. Maintenance of test limits, possibly with database backend, easy logging of results to databases, simple log and report file generation, ease of adaption of test conditions and test flow during production. Generally Test Stand and similar applications still require a lot of work to get a full test application together, but they do not require any programming for at least these sort of things anymore. I'm not a fan of the often hidden configuration for these things, but this is the added value proposal for Test Stand and friends that its users expect. Yet another flow chart application is not going to cut it for any of them.

In terms of LabVIEW, there is obviously still a long way to go for Flojoy to get near to being a real contender in data flow programming. But I do definitely applaud you guys for the effort so far, and for the short time you are working on this thing, it looks already quite useful. The comparison with NodeRed looks pretty apt. I always found that rather limited in many ways compared to LabVIEW. A little like a Visio Flow Chart with some added execution logic behind it. Potentially useful but not quite able to implement more complex program logic that has many parameters flowing from a lot of nodes to even more other nodes. Some would probably say that that is an advantage as the complexity of a typical LabVIEW program can get overwhelming for a beginner. But I would rather have a bit to much complexity at the tips of my fingers than to run into all kinds of limitations after moving from simple node flow charts to real programs.

Edited by Rolf Kalbermatter
Link to comment
  • 2 weeks later...

Thank you Rolf! This helps a lot. It's not the first time that we've received feedback about needing a test sequencer -  I'll get back to this thread when we have a first version of a more robust test sequencer early next year (2024). In the meantime, if you think of any more must-have features or requirements, please share!

For folks stumbling across this thread, here's a gallery of Flojoy test & measure apps: https://www.flojoy.ai/gallery

Edited by Jack Parmer
Shorten
Link to comment
  • 2 months later...

Hi again @Rolf Kalbermatter and @ShaunR

We've added a test sequencer to Flojoy's open-source desktop app. You can see a demo of it below on YouTube or read about it on Flojoy's blog

Anyone is of course welcome to try this free, Python-based test sequencer and give their feedback here. Download link: https://docs.flojoy.ai/studio/installation/

Thanks for your time and comments!

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.