Olivier

MrPLC Member
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Olivier

  • Rank
    Hi, I am New!

Profile Information

  • Country France
  1. PLC program uploading automation

    So after a few days to investigate and fight with various issues. The IC Memory Card features wrote me some "qpg/qpa/dat password protected files" on my hard drive. -> Checked Link my PC to PLC through Ethernet (after many unsuccessful tries due to a defectuous wire) -> Checked Connect to the PLC via FTP (after many unsuccessful tries due to Windows Defender Firewall) -> Checked Write files on PLC via FTP -> Checked Develop a C# program to do the job (just to keep a trace of it : to make FtpWebRequest work it must be configured with KeepAlive = false and UsePassive = false) -> Checked Conclusion : Thanks to your help it seems I have succeeded in having a reliable tool to transfer programs to PLC I found just one limit (hoping I won t meet it) : program and parameters files can only be written on Device Memory when using FTP and not on the ROM (it is a MELSEC documented rule) -> I cross fingers for our programs to be small enough
  2. PLC program uploading automation

    Hello, First of all thank you for your suggestions ! Why don't I password protect the program ? Well ... because I thought to protect the PLC content but I did not think of protecting the source program at all. Thx ! After some tries it already helps me a lot. But that won't solve all my problems because I meet a vicious circle because actually I want my operator to be allowed to write on the PLC but not to read from it : The operator gets the source program file from a file server The operator open the source program with GX (and thanks to your suggestion he can't read it : OK) The operator then write the program to PLC. The operator set the read/write PLC password(s) into the PLC (I didn't try yet but I don't think we can define a read password on the PLC before having downloading any program on it) The main point : how to prevent this operator from reading from the PLC and downloading it into a new GX file ? I thought of SD cards but I have been told the transfer from SD card was really slower than USB and we will have several programs with several operators. So I am quite sure that on the second production day we will discover some PLC with the wrong program on it About FTP : When the Ethernet connection is used between PC and PLC we really can use FTP to upload/download the program ? I thought it was only a feature to transfer data but not the program. I will have a look on this ... By the way for FTP and SD Card what do you transfer/copy on it exactly ? Is it a .gxw file or is there any result file being generated from GX Works to get ? When I use USB I don't see any output file so I suppose the program content is directly streamed through the USB port.   To sum up having a tool using some configuration files to download program into PLC while setting a reading password on it after writing would have helped me a lot
  3. Hi, In conception phase we currently use GXWorks to upload programs to PLC (L-Series). In production mode, for different security reasons we would like to automate this transfer so that the operator does not access directly to the program. Do you know any tool allowing this by using command lines and not GXWorks UI ? (GXWorks does not seem to be "command line" friendly As a POC I  have automated the GXWorks UI in C#  (by simulating menu or buttons clicks) but I don't find it reliable (what if an unexpected popup "pops" ? ). PS : I am a totally noob in this PLC world so maybe I missed stg in the docs ...