Batch Actions Feature

[mauroalexandre]

Proposal: Batch Actions Feature

Hello! I would like to propose a new feature for Fuxa that could be extremely helpful in various scenarios I've encountered in my projects.

Sometimes, multiple actions need to be executed together in a sequential flow. While it’s generally ideal to handle all logic within the PLC, that’s not always possible. Here are a few scenarios where this feature would be beneficial:

1. Mixing multiple products (recipes)
2. Triggering different production lines

I propose creating a batch actions feature that can be executed either through script execution or via element event actions.

In addition, I’ve attached some images illustrating a proposed interface design for this feature.

I’m not entirely sure if I have the technical expertise to implement this on my own, but I’m willing to try. What do you think of this idea? Would it be accepted if implemented?

[MatthewReed303]

@mauroalexandre I have used websocket connection to Node-Red and used this simple Ladder for node-red to handle some basic logic stuff where scripting was not ideal and CodeSys License was over kill. https://github.com/redplc/redplc

It would be cool to have a Node-Red driver in connections and Fuxa nodes in Node-Red where all tags in the connections can be used directly.

[mauroalexandre]

@MatthewReed303 Having support for Node-Red would certainly be a significant advancement for the project.

However, in this specific case, I believe that a user-friendly interface for programming the execution of multiple actions would be the ideal solution. Often, the individuals operating the supervisory system and modifying these logic flows do not have deep technical knowledge. Additionally, I am aware that what I am proposing could very well be achieved through scripts.

[unocelli]

@mauroalexandre Interesting and in fact it is missing, it's about making a UI for what you can actually already do with scripts. Creating a stream like node-red to be integrated into fuxa seems very challenging, I think we should add checks on more tags (if) and delays, maybe we could use some graphics library like blockly , rete, Drawflow

[henjoe]

Drawflow might be a good choice, kinda similar to nodered.

I am thingking what if we simply integrate nodered natively in the Fuxa Editor? Without using websockets, like there will be a custom node (in nodered) to read/write/add tags directly to Fuxa.

[MatthewReed303]

Having a node-red integration that can interact with tags/connections/scripts would work well. I display node-red in Fuxa using an iframe and web sockets to communicate with tags. And displaying node-red server in Iframe works fine. Having the Fuxa integration in Node-Red is the way to go so we can browse and select tags etc just enter the Fuxa server address and API port and have an connection. What are your thoughts @unocelli @mauroalexandre

[henjoe]

Having a node-red integration that can interact with tags/connections/scripts would work well. I display node-red in Fuxa using an iframe and web sockets to communicate with tags. And displaying node-red server in Iframe works fine. Having the Fuxa integration in Node-Red is the way to go so we can browse and select tags etc just enter the Fuxa server address and API port and have an connection. What are your thoughts @unocelli @mauroalexandre

You mean by "websocket" is using the WebAPI in device right?

[MatthewReed303]

@henjoe nope, I use websocket directly in the script, I added how to use it in the Wiki https://github.com/frangoteam/FUXA/wiki/HowTo-WebSockets

[henjoe]

@henjoe nope, I use websocket directly in the script, I added how to use it in the Wiki https://github.com/frangoteam/FUXA/wiki/HowTo-WebSockets

Oh I see thanks for clarification.
On my case I use webAPI and just simply update the API's return data (JSON - array of object) on nodered.

[mauroalexandre]

@unocelli

Do you think implementing it in a simpler way, as proposed, would be a good first step? I'm asking because I’d like to get approval before proceeding with this feature.

[unocelli]

I think it is an important feature and in any case we can extend it later with a flow editor. it would be great if the configurator eventually created some kind of function or script to be executed. or what would you have planned?