Dongle von Linux-Modul (ARM64) nicht erkannt ^{CODESYS Forge talk (Thread)}
Dongle von Linux-Modul (ARM64) nicht erkannt
Last updated: 2024-09-23

J1939 Problems ^{CODESYS Forge talk (Thread)}
J1939 Problems
Last updated: 2024-09-23

Post by elektron785 on Dongle von Linux-Modul (ARM64) nicht erkannt ^{CODESYS Forge talk (Post)}
Ich hatte noch einmal Zeit das mit der Lizenz zu probieren und habe dazu über den Codesys Installer das Virtual Control SL runtergeladen und ausprobiert, aber leider ohne Erfolg. Zunächst habe ich "Docker_codesyscontrol_virtuallinuxarm64_4.13.0.0_arm64.tar.gz" aufs Board geladen und das Image mit docker load geladen. Mit dem Befehl docker run --rm -dt --name codesys --network host -v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ --device-cgroup-rule='c 13: rmw' --privileged 470a708f17a2 hab ich dies dann ausgeführt, aber das Problem, dass ich das Board im Netzwerk dann nicht finden konnte. Damit ich die Verbindung herstellen konnte, habe ich die Datei "DockerRuntimeStart.sh" so verändert, dass ich den Teil: -p 11740:11740/tcp \ -p 443:443/tcp \ -p 8080:8080/tcp \ -p 4840:4840/tcp \ gegen --net host \ ersetzt habe. Das Skript habe ich dann aufs Board geladen und bash DockerRuntimeStart.sh -i codesyscontrolvirtuallinuxarm64:4.13.0.0 -c codesys -H verdin-imx8mp- ausgeführt. Nun konnte ich in Codesys wieder eine Verbindung zu dem Board aufbauen, aber der Dongle wird leider immer noch nicht im Lizenz-Manager erkannt. Wie kann ich denn prüfen, dass auf den USB-Stick vom Container aus zugegriffen werden kann?
Last updated: 2024-09-23

Post by rossanoparis on Clarifications regarding the appropriate runtime system to use ^{CODESYS Forge talk (Post)}
Hallo all I would appreciate some clarifications regarding the appropriate runtime system to use. I've been using 'KUNBUS CPUs' and 'CODESYS Control for Raspberry Pi MC SL' for the last 4 years. Recently, there have been some changes in the CODESYS licensing policy. [ https://store.codesys.com/en/howto_applicationbasedlicenses ] My questions are mainly two: 1) If I need to start a new project using 'KUNBUS CPUs', which is the correct runtime system to use. 2) Old projects built using 'CODESYS Control for Raspberry Pi MC SL' should be updated to another RT system? Current RT systems ... a)CODESYS Control for Raspberry Pi MC SL b)CODESYS Control for Linux ARM SL c)CODESYS Virtual Control SL May I count on receiving an explanation to understand the differences among the runtime systems listed above? A detailed and well-organized answer would be greatly appreciated. Kind regards Rossano
Last updated: 2024-09-23

Post by tobthi on Ethernet/IP ^{CODESYS Forge talk (Post)}
Hello, I have a Cognex camera that I would like to add to my Codesys program. Communication should work via Ethernet/IP. However, I always get the following error message, which is why I can't add the camera.
Last updated: 2024-09-23

Post by pierre on difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Post)}
same situation for DeviceID. In the stubfile this is Deviceid
Last updated: 2024-09-23

Stack overflow with really simple function ^{CODESYS Forge talk (Thread)}
Stack overflow with really simple function
Last updated: 2024-09-23

Post by opineiro on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
Hi there, I have a Keyence bar code reader connected to my plc through Ethernet/IP. The Bar code is 20 digits long (like 30100790020493036016), the scanner reads it correctly (I can verify that through the keyence software) but when it sends it through ETH/IP, it doesn't fit into a 64 bit variable and it trunks the data.(I've tried ULINT and LWord without success). When I loaded the EDS file, the read variable was defined as a byte with 128 bits length, which is quite strange for me. (see attached picture) How do I manage this variable? Thanks!
Last updated: 2024-09-23

Post by opineiro on Ethernet/IP ^{CODESYS Forge talk (Post)}
Hi Tobthi, Do you have the eds file of the camera? I usually load first the eds file and then add the device to the Ethernet/IP scanner.
Last updated: 2024-09-23

Post by opineiro on Stack overflow with really simple function ^{CODESYS Forge talk (Post)}
Thanks, I'm going to rework everything with this in mind.
Last updated: 2024-09-23

Post by ph0010421 on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
So it's currently mapped to an array of BYTES? Can you create a UNION? TYPE sBytesString : UNION AsBytes: ARRAY[0..127] OF BYTE; AsString: STRING(128); END_UNION END_TYPE Map it to the bytes, read it in the STRING!
Last updated: 2024-09-23

Post by ph0010421 on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
My guess is that's a STRING, not an INT type. And it's 128 bytes, not bits
Last updated: 2024-09-23

Post by pierre on difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Post)}
Last updated: 2024-09-23

difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Thread)}
difference between stub file and source file in scriptengine
Last updated: 2024-09-23

Post by opineiro on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
Thanks, that's what I thought initially. The point is that I can't select a String type variable. See the attached image
Last updated: 2024-09-23

How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Thread)}
How to manage variable types larger than 64 bits - Ethernet/IP
Last updated: 2024-09-23

Post by opineiro on How to manage variable types larger than 64 bits - Ethernet/IP ^{CODESYS Forge talk (Post)}
Thanks, I'm going to try it!
Last updated: 2024-09-23

Post by tobthi on Ethernet/IP ^{CODESYS Forge talk (Post)}
Thank you very much.
Last updated: 2024-09-23

Post by malie on Bibliothek konnte nicht aufgelöst werden ^{CODESYS Forge talk (Post)}
Ich hab noch etwas rausgefunden, falls jemand anderes noch ähnlich lustige Probleme hat. CoDeSys kann sich an der Windows UAC vorbeischleichen. Sprich man öffnet die CoDeSys IDE ohne Umweg über den CoDeSys Installer (in dem man gefragt wird ob man mit Administrator Rechten arbeiten will) und ist manchmal Admin. Deshalb kam ich nicht auf die Netzwerklaufwerke. Ich hab keine Ahnung warum das so ist. Abhilfe hab ich mir mit dem Registrykey geschaffen mit dem man auch als Admin auf Netzwerklaufwerke zugreifen darf. Einfach folgende Code in eine "DateinameMeinerWahl.reg" Datei kopieren und mit Rechstklick der Registry hinzufügen. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "EnableLinkedConnections"=dword:00000001
Last updated: 2024-09-23

Bibliothek konnte nicht aufgelöst werden ^{CODESYS Forge talk (Thread)}
Bibliothek konnte nicht aufgelöst werden
Last updated: 2024-09-23

Post by davidbo on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
I have noticed that a rm file1.txt command on a shell has an impact on the cycle time for a TASK writing to file2.txt. Seen in the Monitor fane of the Task configuration Furthermore if a TASK makes a system call like rm, its cycle time increases of course but it seems to have an invisible impact on other TASKs too. I have a TASK for handling communication over the CANbus (SPI) where it stops sending "Heartbeats" for many seconds when another TASK does a system rm. Why is that not seen on the Monitor fane? Is even codesyscontrol paused when system calls are made? The CPU load is about 30-40%
Last updated: 2024-09-23

Ethernet/IP ^{CODESYS Forge talk (Thread)}
Ethernet/IP
Last updated: 2024-09-23

J1939 TX/RX PDU1 ^{CODESYS Forge talk (Thread)}
J1939 TX/RX PDU1
Last updated: 2024-09-23

Post by lbartik on J1939 TX/RX PDU1 ^{CODESYS Forge talk (Post)}
Is it possible to transmit a PDU1 PGN using the J1939 manager and local device? What if I need to transmit a PGN RQST via 0xEA00 (PGN 59904)? How would I do this P2P (Destination < 0xFF) or broadcast (Destination 0xFF)? I don't think this is possible for any destination type. I don't think it's possible to receive broadcast PDU1 messages either. For example, an address claim PGN 60928 (0x18EEFF80) is addressed to all nodes (0xFF) and not any specific local device so it will be filtered out. These are major oversights in the IoDrvJ1939 library to not support every PDU1 RX/TX scenario. IoDrvJ1939 supported scenario: 1. Receive (RX) PDU1 (P2P) destination-specific (PDU-specific < 255) to local device with matching address IoDrvJ1939 unsupported scenarios: 1. Receive (RX) PDU1 (P2P) global (PDU-specific = 255) 2. Transmit (TX) PDU1 (P2P) global (PDU-specific = 255) 3. Transmit (TX) PDU1 (P2P) destination-specific (PDU-specific < 255)
Last updated: 2024-09-23

Post by davidbo on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
3.5 18 SP2 I think the control is 4.2.0.0. I am not in the office before on Wednesday.
Last updated: 2024-09-23

Sort by relevance or date