Load PLCnext Engineer project through SFTP?

Hello, Is there a way to send a PLCnext Engineer project to a PLCnext Controller without PLCnext Engineer? Is there a way to load the files through SFTP? I’ve seen a folder in the Binary folder of the project which look like the PCWE folder in the PLCnext Controller (/opt/plcnext/projects/) However, I’ve seen a notice to not make any changes in this folder. Picture of the folder in the PLCnext Engineer project Binary folder: pcwe1 Picture of the folder in the PLCnext Controller: pcwe2 Picture of the notice: pcwe3 Thank you and take care! Robin

image.png


Hi Robin, I don’t know the answer to this question, but … have you tried it? Copying the files to the PLC using WinSCP (for example) won’t change the files, so you won’t be breaking the rules. Worst case, you’ll crash the PLC and may need to delete the PCWE directory. If you want to try it, I would recommend not leaving any “old” project files in the PCWE directory when you copy the new files. You might even be able to just delete the old PCWE directory on the PLC, and replace it with the new one. If you’d rather not try this, I’ll give it a go tomorrow. ~ Martin.

Hi Martin, Thanks for the quick answer. Much appreciated. Yes, I tried it. I replaced the PCWE folder that was in the PLCnext with the one in the project directory and it didn’t work. I had to make a factory default to be able to use it again since it was always in error. Downloading a new project wasn’t working. There’s probably other files to take into consideration? Best regards! Robin

OK, I’ll ask around. There must be a way, but there might be a secret trick that we’re not allowed to know. Let’s see. ~ Martin.

Hi Robin, One of my colleagues here has tried the simple procedure we discussed - several times - and it works for him every time.

                                             * Delete the PCWE directory on the PLC.
                                             * scp -r PCWE admin@192.168.1.x.:~/projects/
                                             * Restart the PLCnext Runtime.

If this does not work for you, what appears in the Output.log file when you try to start the runtime?

Martin, We have used this last method with multiple projects (and multiple FWs) with no issues :slight_smile: Normally what we do after the binaries are copied is just a full reboot of the controller to ensure there aren’t any lingering issues.

Hi Martin, I tried another time the simple procedure that you suggested and it did work two times in a row! However, the third time it didn’t work and end up in the same state that I was when I tried the first time. Here’s a part of the log file. It seems to have an invalid config exception? log0 log1 log2 Thanks and take care! Robin

Hi Robin, I need to ask the obvious question - at the start of the procedure, did you delete (not over-write) the PCWE directory from the PLC, before doing anything else? That error looks like it would happen if there were vestiges of an old project in the PCWE directory tree. If the answer to the question is “yes, definitely”, then please email me the project that does not work. ~ Martin.

Hi Martin, Yes, I deleted (not overwritten) the PCWE directory from the PLC before trying to transfer the PCWE directory from the binary folder of the project (through WinSCP). I’ll send you an email. Thanks! Robin

Hi All For me the failure only exists when I pulled the plug instead of a software reboot of the controller.

Issue was similar as to your screenshots. I borrowed the technique to deploy PLCnE projects trough docker containers.
Seems to work fine :slight_smile: Dries