Since the problem on the Gen 2 R1 regarding Sdcard file write and reads cropped up preventing me from using the SDCard to store a data file on, I have been trying to come up with a method of writing a file to the PC hard drive that doesn’t involve security problems, and is secure from losing data.
After many possible scenarios considered, I finally figured that using the recipes might be simplest means and most solid means. Yes, I looked at History files in PD, but that would not work for several format reasons. Then looked at transmit string table, but that ends up involving firewall issues.
Turns out recipes could be the simplest means, except for one little quirk. The current version of recipes works really fast and is solid. The problem is it was never intended to be used to transfer data from one controller to another. The problem exists where the templet and file path begin with the controller name, which is “Pac Controller”. So I if you have more than one control engine attached to PD, how does it decide which controller it picks??? Not sure how that works, but it does…so since set up recipe manager to have the same string table uploaded from one controller, then downloaded to another (SoftPac in this case) it does not work. This because the
download manager doesn’t allow to use a separate template file. I tested this by editing the controller name from Pac Controller to SoftPac. Then triggered only the download and whala.
Looks like Ill have to have a script that will edit the rcp file controller name to SoftPac and then trigger the download.
It would be a nice feature to have to transfer large tables, or set of tables from one controller to another, or better yet, have an option for the existing upload recipe create a standard CSV file format on the PC hard drive???