Hi Team, In our application we have added a support file we fill with data from the PLC. It’s a simple .csv file for information the end user can download and process further. It works and the customer is happy. When we update the application and re-send the project tot the controller the support file is overwritten with the innitial file and the data added later on is lost. When we remove the file as a support file from PLCnENG we can still write from the application but can’t download it from the Ehmi. Because of this issue we have 2 questions: 1: Is there a way of downloading a file by using the Ehmi that ISN’T a support file added by PLCnENG? We now use the native button->action on click->Execute command->Open support file 2: Is there a way of preventing the file being overwritten when updating the application? Thanks in advance.
Hello ckemper, I’m not familiar with your application, but I would like to help you. Please find the answers to your questions below: 1: Is there a way of downloading a file by using the Ehmi that ISN’T a support file added by PLCnENG? We now use the native button->action on click->Execute command->Open support file → The eHMI provides the User-Commands to the Application running on the PLC. → You can use the file handling FB’s located in Library “PLCnextBase” (https://www.plcnextstore.com/1035) → Or you can try to implement the linux shell based solution via FB “PBCL_SysLinuxShell_1” (see also Point 5.4 SysLinuxShell FB with examples) 2: Is there a way of preventing the file being overwritten when updating the application? → Yes, please check, If the file already persists before executing the “write access” e.g. via FB “PBCL_FileExists_1”. Best Regards Eduard