Home (version 1) discussion
arwie
wiki
(Thread)
Home (version 1) discussion
Last updated: 2024-04-25
wiki Discussion
batuhanarslan
wiki
(Discussion)
Forum for wiki comments
Last updated: 2024-04-25
blog Discussion
batuhanarslan
blog
(Discussion)
Forum for blog comments
Last updated: 2024-04-25
Home
batuhanarslan
wiki
(WikiPage)
Project Members: batuhanarslan (admin)
Last updated: 2024-04-25
(no subject)
batuhanarslan
wiki
(Thread)
Last updated: 2024-04-25
Post by reinier-geers on License problem gateway
CODESYS Forge
talk
(Post)
16.4 Epis What has it to do with the manufacture? It just a licence more not. So basicly the idee of codesys sucks. 3s acts like its posible to add a license. And then it depence on the manufacturer. Why ?? Its a computer !! has nothing to do with the manufacturer. Most dont what a basic licence because they have to pay for that. 3s is the problem not the manufacture of the hardware. Its like the licence of the raspberry pi. HMI is not working. Sorry you get a refund. Why suggest that its possible wen its not !!. It cost me a lot of time. Who pays my time. Why do i have to pay for somting thats not working.
Last updated: 2024-04-26
wiki Discussion
zcakar
wiki
(Discussion)
Forum for wiki comments
Last updated: 2024-04-26
blog Discussion
zcakar
blog
(Discussion)
Forum for blog comments
Last updated: 2024-04-26
(no subject)
zcakar
wiki
(Thread)
Last updated: 2024-04-26
Home
zcakar
wiki
(WikiPage)
Project Members: zcakar (admin)
Last updated: 2024-04-26
Safety EL6900 com Error
CODESYS Forge
talk
(Thread)
Safety EL6900 com Error
Last updated: 2024-04-26
wiki Discussion
rjames
wiki
(Discussion)
Forum for wiki comments
Last updated: 2024-04-26
blog Discussion
rjames
blog
(Discussion)
Forum for blog comments
Last updated: 2024-04-26
(no subject)
rjames
wiki
(Thread)
Last updated: 2024-04-26
Home
rjames
wiki
(WikiPage)
Project Members: rjames (admin)
Last updated: 2024-04-26
Post by cpoi on Safety EL6900 com Error
CODESYS Forge
talk
(Post)
Hello, I using the EL6900 module with EL 1904 and EL2904 on Ethercat, and I have a ComErr on the EL6900. The FSoE Adresse : EL6900 = 1 EL1904 = 11 EL2904 = 15 Any suggestion? Thanks a lot in advance.
Last updated: 2024-04-26
Post by scoob on ModbusFB - Slow Response Time
CODESYS Forge
talk
(Post)
Hello, I have been trying to use the ModbusFB functions so I can put some code into libraries, but it seems to be very slow for me. I have a Modbus device with 100ms registers. I previously setup 10 channels in the 'traditional' Modbus Slave with channels and mappings - and set a cyclic trigger at 100ms - this worked fine. I then tried the ModbusFB example, and setup reading the same 10 blocks of modbus addresses, copying the example and putting all of the requests into an array and triggering the requests sequentially. I timed how long the requests are taking to get round to each one, and it is around 1s 450ms. How do I speed this up to match the cyclic time? IF NOT(init) THEN init := TRUE; // Set the required IP address: ipAddress[0] := 192; ipAddress[1] := 168; ipAddress[2] := 1; ipAddress[3] := 10; // Pass the required IP address to the clinet FB: client_NetworkSwitch.aIPaddr := ipAddress; client_NetworkSwitch.udiLogOptions := (ModbusFB.LoggingOptions.ClientConnectDisconnect OR ModbusFB.LoggingOptions.ClientReceivedValidReplies); // Try to connect the client client_NetworkSwitch(xConnect:=TRUE); // Configure all the channels to read connecting them to the client: portStatus_Request(rClient := client_NetworkSwitch, uiStartItem := 4096, uiQuantity := 32, pData := ADR(portStatus), udiReplyTimeout := udiReplyTimeout); portSpeed_Request(rClient := client_NetworkSwitch, uiStartItem := 4352, uiQuantity := 32, pData := ADR(portSpeed)); flowControl_Request(rClient := client_NetworkSwitch, uiStartItem := 4608, uiQuantity := 32, pData := ADR(flowControl)); linkUpCounter_Request(rClient := client_NetworkSwitch, uiStartItem := 5888, uiQuantity := 32, pData := ADR(linkUpCounter)); txPacketCounter1_Request(rClient := client_NetworkSwitch, uiStartItem := 8192, uiQuantity := 100, pData := ADR(txPacketCounter1)); txPacketCounter2_Request(rClient := client_NetworkSwitch, uiStartItem := 8292, uiQuantity := 28, pData := ADR(txPacketCounter2)); rxPacketCounter1_Request(rClient := client_NetworkSwitch, uiStartItem := 8448, uiQuantity := 100, pData := ADR(rxPacketCounter1)); rxPacketCounter2_Request(rClient := client_NetworkSwitch, uiStartItem := 8548, uiQuantity := 28, pData := ADR(rxPacketCounter2)); txErrors_Request(rClient := client_NetworkSwitch, uiStartItem := 8704, uiQuantity := 64, pData := ADR(txErrors)); rxErrors_Request(rClient := client_NetworkSwitch, uiStartItem := 8960, uiQuantity := 64, pData := ADR(rxErrors)); // Trigger all client requests initially FOR clientRequestsCnt := 0 TO (SIZEOF(clientRequests)/SIZEOF(clientRequests[0]))-1 DO pClientRequest := clientRequests[clientRequestsCnt]; pClientRequest^.xExecute := TRUE; END_FOR // Prepare sequential trigger / control of client requests. clientRequestsCnt := 0; pClientRequest := clientRequests[clientRequestsCnt]; END_IF // Call the client to do request processing: client_NetworkSwitch(); // Now we trigger client request sequentially ... IF NOT pClientRequest^.xExecute AND NOT pClientRequest^.xDone AND run AND client_NetworkSwitch.xConnected THEN pClientRequest^.xExecute := TRUE; END_IF // .. and check result/error IF pClientRequest^.xExecute AND run AND client_NetworkSwitch.xConnected THEN IF pClientRequest^.xDone THEN // Prepare next trigger of client request (a rising edge of xExecute) pClientRequest^.xExecute := FALSE; IF clientRequestsCnt < SIZEOF(clientRequests)/SIZEOF(clientRequests[0])-1 THEN // next client request clientRequestsCnt := clientRequestsCnt + 1; ELSE clientRequestsIterationCounter := clientRequestsIterationCounter + 1; clientRequestsCnt := 0; END_IF pClientRequest := clientRequests[clientRequestsCnt]; END_IF END_IF I did try a semi-coded way using the IoDrvModbusTCP library, and setting the slave com settings, then 10 commands and 10 requests, then using a TP on xDone as a pause, before triggering another request - this is time the delay is around 120ms - so the device is fine with the speed, just something I am doing wrong in the ModbusFB method I am sure.
Last updated: 2024-04-26
Post by valenting on Problem with Licenced Software Metrics
CODESYS Forge
talk
(Post)
Hi, I tried with another project, using codesys SP20 with the latest visualization installed, I can install the application on my device but it doesn't work I get an exception "invalid license metrics" and the app won't run See attached the metrics in project and allowed by license, and the logs What am I supposed to do ? Everything is in the newest version and the values are lower than allowed and nothing works...
Last updated: 2024-04-26
ModbusFB - Slow Response Time
CODESYS Forge
talk
(Thread)
ModbusFB - Slow Response Time
Last updated: 2024-04-26
Home (version 1) discussion
marek2811
wiki
(Thread)
Home (version 1) discussion
Last updated: 2024-04-26
Post by eschwellinger on License problem gateway
CODESYS Forge
talk
(Post)
I just try to help. Anyway it is a big difference if a Store SL runtime or an oem plc and licence is used. These licenses need to be activated on plc side - so you have dependencies to the version (CODESYS and Runtime Version) Did you ever ask Epis out for this situation? They should know which license fit to their device. Even they should know if the device is capable for Softmotion and see the requiremnts in the CODESYS store: Runtime 4.9.0.0 - how should this work with Epis 3.5.16.x? Anyway refund is not a problem.
Last updated: 2024-04-26
Post by eschwellinger on Can't connect to Device Raspberry Pi 4 from CODESYS IDE V3.5 SP19
CODESYS Forge
talk
(Post)
with latest version?
Last updated: 2024-04-26
Can't connect to Device Raspberry Pi 4 from CODESYS IDE V3.5 SP19
CODESYS Forge
talk
(Thread)
Can't connect to Device Raspberry Pi 4 from CODESYS IDE V3.5 SP19
Last updated: 2024-04-26
Post by peterned on CNC - system goes to X=0 Y=0 before CNC file execution starts, how to avoid that?
CODESYS Forge
talk
(Post)
Hi, I have a XY system and use a CNC file to move it. Everything works OK, except for the following: when CNC execution starts, the system rushes at high speed to (X=0, Y=0) point, and only then goes to the first line of the CNC file. If one of the axes is near 0, the system jumps and immediately stops with an error. In the CNC file settings (screenshot attached) I specified low default values for speed/acceleration and a start position different from 0,0 - but all that is ignored. Any idea how to avoid that move to 0,0 ? Thanks.
Last updated: 2024-04-26
wiki Discussion
zerika
wiki
(Discussion)
Forum for wiki comments
Last updated: 2024-04-26