Node Red - Write file data into Pac write node

[Beno]

Keep in mind that as your users change the table data, this flow will break in different (and fun) ways.
Also you wont need that delay node if you switch the construction from parallel as you have, to serial like this:

Its never (ever) a good idea to do parallel reads like that with Node-RED as it places a really large sudden load on the controller as it tries to do all those RESTful calls to the controller to get the data.
As the data changes, the RESTful response will change.

This post will help you with a whole bunch of resources:

Optimizing Node Red Flow

I have a Node Red Flow that is doing a couple dozen writes to scratch pad per second. (or is supposed to…) It seems to have trouble getting all of them done. I suspect writes are getting queued, but over running the write buffer or something. Here is a screenshot of the Node Red. I’m working to optimize the Flow by combining all scratchpad reads, then combining all writes (Write to multiple RIO scratchpad using 1 groov i/o write node), then perhaps using fewer time injects. Is there anything e…

Note the one comment toward the bottom that exactly replicates your setup…I have found in the past that if you fetch ‘all at once’ (triggering several PAC Read nodes at once), especially when reading tables, you can get connection errors. Daisy chaining from a single Inject node, as Beno shows in his example flow, overcame this problem.

Saving each PAC table into its own file would be another way around this issue.
Don’t forget you can use the time function to create a time stamp directory so the user knows exactly his latest data.

Sending an email attachment with Node-RED

You can use the Node-RED email node package to send emails with attachments as soon as it’s installed, but there are a few small details that are critical in getting it to work smoothly. In this post I’ll go over a basic flow to read in a specific file on a regular schedule and email that file out as an email attachment to yourself or other recipients: [image] This flow was written using Node-RED v1.0.3 on groov hardware, but this technique will work for many Node-RED versions running on othe…

(Simply use your file write node vs the email one).

So, bottom line, you are very close to having things break, before you deploy into production, you really should rearrange it from parallel to serial so you don’t get any surprises down the road.