Yes, that is my current setup. however, i am trying to reduce the time taken for creating a table for updating the downtime in each machine.
trying to explain.
I have 20 machines connected to a PLC
The data about production is updated every minute by the way of count of product in the last minute for each machine
the main database is hence a table of count of product for each machine updated every clock minute with a timestamp
now, at the end of a shift of 8 hours, i am asking the shift executive to update the downtime reasons.
upon selecting a machine, the NR flow calculates the downtime (where count is zero) period by going through the database and creating another temporary table to effectively give the Machine/From Time / TO Time /Duration and a space holder for him to enter / select a downtime reason from a dropdown (which also comes from a database)
this takes a while for each machine, and I want to automate this process of 'calculating' the downtime for ALL machines simultaneously without him need to select the machine each time he is done with one.
I found that making a single table with all machines with downtime data is somehow faster and easier for the operator.
but this is overwhelming for him to see all data at once on a screen, so i would like to filter the machines by clicking a button for each machine or by a dropdown, at this point all the calculations are already done, and i dont want to invoke a mysql query again to display the table, just want to show / hide relevant data.
I am not sure i am making a valid point here, since
if you cant explain something in simple sentences, then you must be doing it wrong
You can consider using @omrid01/node-red-dashboard-2-table-tabulator, which fully supports any type of filtering (e.g. configured, dynamic, conditional), including a persistence option.