Jump to content

xeden3

MrPLC Member
  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • Country
    Netherlands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

xeden3's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter

Recent Badges

0

Reputation

  1. Mr. Pturmel Thank you very much for your evaluation of LECPServer. If you have any suggestions for LECPServer, I hope to hear that. THX
  2. Pturmel thank you very much for your reply .. :P What you stated is very correct. I would like to make up three points for the problems I encountered in the project. 1. OPCUA needs to verify each connection 2. OPCUA is based on long connection, and it is likely to be abnormal when the network is unstable. (When using Kepserver 6.6/6.5/6.4, the short connection can easily crash Kepserver. This has been confirmed by the official. Of course, this problem has been fixed in version 6.9.) 3. OPCUA protocol packet is much larger than HTTP We have a project that uses LECPServer as a gateway, and then the LECPServer server is directly connected to the external network, other remote browser can directly read and write PLC data under the LECPServer through the Internet environment.
  3. If it is not in the environment of the Internet, Kepserver can be used as the middleware, and the PC can read and write data to PLC in OPCUA protocol, but OPCUA is not suitable for Internet. If the HTTP protocol is used, the communication middleware LECPServer is recommended, and the usage method is as follows. http://www.lecpserver.com:3001/#/node_read_write The key code is as follows $.post("http://lecpserver_url:port",{"action":"plc_read_node", "node":"NODES.PanMC.X0000"}, function(success, rtval){ // return the data of node address X0000 console.log(success, rtval); });
  4. Sorry, indeed I misunderstood the question But as far as I know, there is no PLC that can implement the Restful protocol. After all, this protocol requires a more complicated link mechanism and CPU resources. The more common practice is that the link end mainly writes to the PLC.
  5. Version 1.1.15

    6 downloads

    LECPServer A high-performance industrial connectivity platform LECPServer(Leanboard Equipment Communication Proxy Server), It is a high-performance industrial connectivity platform developed based on the JLean framework. It solves communications challenges with industrial devices and applications, with streamlined data through a single communications platform, Over 90% of PLCs can interact with applications through LECPServer by HTTP POST (Webapi), Users can connect, manage, monitor, and control diverse automation devices and so
  6. View File LECPServer-Manual-doc-en LECPServer A high-performance industrial connectivity platform LECPServer(Leanboard Equipment Communication Proxy Server), It is a high-performance industrial connectivity platform developed based on the JLean framework. It solves communications challenges with industrial devices and applications, with streamlined data through a single communications platform, Over 90% of PLCs can interact with applications through LECPServer by HTTP POST (Webapi), Users can connect, manage, monitor, and control diverse automation devices and so Submitter xeden3 Submitted 12/03/2022 Category Manuals, Tutorials  
  7. As far as I know, accessing PLC through ajax is not a routine operation. If you can, you can try LECPServer, an open source middleware. It can expose the PLC node address for reading and writing through HTTP POST. https://github.com/xeden3/LECPServer
×
×
  • Create New...