Search talk: codesys box with en/eno

 
<< < 1 .. 237 238 239 240 241 .. 922 > >> (Page 239 of 922)

new version of CODESYS have problem to load GSDML files CODESYS Forge talk (Thread)
new version of CODESYS have problem to load GSDML files
Last updated: 2024-05-20

Safety CODESYS Forge talk (Thread)
Safety
Last updated: 2024-05-24

RecipeManCommands.ReloadRecipes CODESYS Forge talk (Thread)
RecipeManCommands.ReloadRecipes
Last updated: 2024-05-24

JSON CODESYS Forge talk (Thread)
JSON
Last updated: 2024-06-21

SysProcessExecute CODESYS Forge talk (Thread)
SysProcessExecute
Last updated: 2025-10-24

SysProcessExecute CODESYS Forge talk (Thread)
SysProcessExecute
Last updated: 2025-10-24

SysProcessExecute CODESYS Forge talk (Thread)
SysProcessExecute
Last updated: 2025-10-24

Mailversand CODESYS Forge talk (Thread)
Mailversand
Last updated: 2025-12-04

SBOM CODESYS Forge talk (Thread)
SBOM
Last updated: 2026-08-21

SBOM CODESYS Forge talk (Thread)
SBOM
Last updated: 2026-08-21

Deutsch πŸ‡©πŸ‡ͺ CODESYS Forge talk (Discussion)
German forum
Last updated: 2026-10-19

Archive CODESYS Forge talk (Thread)
Archive
Last updated: 2026-03-10

CNC15_LargeGCode.project CODESYS Forge talk (Thread)
CNC15_LargeGCode.project
Last updated: 2026-05-05

ModbusTCP_FunctionCode06 CODESYS Forge talk (Thread)
ModbusTCP_FunctionCode06
Last updated: 2026-05-14

ModbusTCP_FunctionCode06 CODESYS Forge talk (Thread)
ModbusTCP_FunctionCode06
Last updated: 2026-05-18

Post by yueqiqi on Where Can I download the latest Version of CoDeSys V CODESYS Forge talk (Post)
Where Can I download the latest Version of CoDeSys V2.3?
Last updated: 2026-06-15

Where Can I download the latest Version of CoDeSys V CODESYS Forge talk (Thread)
Where Can I download the latest Version of CoDeSys V
Last updated: 2026-06-15

Visualisierungswerkzeuge CODESYS Forge talk (Thread)
Visualisierungswerkzeuge
Last updated: 2026-06-15

Test CODESYS Forge talk (Thread)
Test
Last updated: 2026-09-22

Scheduler CODESYS Forge talk (Thread)
Scheduler
Last updated: 2026-01-16

Beobachtungszeitpunkt CODESYS Forge talk (Thread)
Beobachtungszeitpunkt
Last updated: 2026-03-04

CloseTargetVisu CODESYS Forge talk (Thread)
CloseTargetVisu
Last updated: 2026-03-11

Post by gmau on Station 'xyz': AR aborted by device (alarm.ind): AR consumer DHT expired CODESYS Forge talk (Post)
Hello, I am writing to You with the problem of Profinet communication in my Codesys V2.5 SP21 project working on Codesys Control RTE V3 x64 device. I have implemented multiple Profinet devices in the network, the Profinet itself is configured properly, based on the hardware and software parameters of the industrial PC (Windows 10 IoT). My Profinet network contains such Profinet devices as a robot, IO-Link master with some devices on it, IO modules, safety, vision sensor (the configuration is attached to this topic). Once every few hours, sometimes more often, sometimes not even once a day, the error show up at one, two or a few random modules at the same time, every one is the same: "Station 'xyz': AR aborted by device (alarm.ind): AR consumer DHT expired". The communication is then lost with that module, but it is up instantly. It is not such a problem when it comes to regular IOs, but with safety or rotation table, it causes errors and machine stops. I have tried multiple solution based on any forum suggestions, manuals, etc., but it is still happening. Mabye when I turned on the Watchdog for this communication, it is happening less times, but still, I could not turning up the Watchdog parameters at the expense of cycle time of the process. The same is with Send Clock, Reduction and DHT. I have one of the ethernet port on the PC configured with CmpEt1000Drv driver. The card itself is Intel Ethernet Connection I219-LM. These devices are connected to one EKI-2728-NI-A Profinet switch (it was changed from the standard non Profinet one, but still nothing has changed). As I said ealier, I am attaching all the configurations for each device and the communication itself - if any of You had the same problems or have any ideas what could be the cause, I would be much gratefull for any help. For now I am out of ideas, if You have any additional question, please ask. Sincerely, PF
Last updated: 2025-09-04

Post by rossanoparis on CAN TX regression in Control for Raspberry Pi 4.21.0.0 with CAN API library (RX works, TX silently fails) CODESYS Forge talk (Post)
Environment: Target: Revolution Pi (Kunbus RevPi), armv7l 32-bit OS: Raspbian GNU/Linux 9 (Stretch), kernel 4.19.95-rt38-v7 (SMP PREEMPT RT, built 2022-03-22) CAN: via SocketCAN (can0) Runtime: CODESYS Control for Raspberry Pi SL IDE: CODESYS V3.5 SP22 + patch 3 (previously V3.5 SP22 + patch 2, where everything worked with runtime 4.18.0.0) Library: CANBusAPI from the "CAN API" package, version 1.0.0.3 Summary: The setup worked correctly with V3.5 SP22 + patch 2 and runtime 4.18.0.0. After updating the IDE to SP22 + patch 3 and the runtime to 4.21.0.0, CAN transmission via the CANBusAPI library stopped working. Reception is unaffected. There are no error indications anywhere: the application runs normally and the CAN diagnosis reports a healthy bus. Systematic testing (below) shows the problem follows the runtime version, not the IDE update. Regression isolation: The same application (compiled under SP22 + patch 3, unchanged between tests) was downloaded to the same target with different runtime versions, changing only the runtime each time: 4.18.0.0: TX and RX both work 4.19.0.0: TX and RX both work 4.20.0.0: TX and RX both work 4.21.0.0: RX works, TX does not The behavior is fully reproducible in both directions (downgrading to 4.20 restores TX, upgrading to 4.21 breaks it again). Hardware, wiring, OS, project, and application code are identical across all tests. Diagnostic data (CANBusDiagnosis FB, while the application is transmitting on 4.21): ctSendCounter: incrementing normally ctTxErrorCounter: 0 ctRxErrorCounter: 0 eState: ERROR_FREE xBusAlarm: FALSE So the library accepts and counts the outgoing messages, no TX errors are reported, and the CAN controller state stays error-free, but the messages never reach the other nodes on the bus. Expected behavior: Messages sent via CANBusAPI (CANDriver / SendMessage) are transmitted on the bus, as with runtime versions up to and including 4.20.0.0. Notes: I am aware that the CAN API package (1.0.0.3, from 2016) is old; however, the regression is tied to the runtime version, since the identical binary works on 4.18-4.20. Questions: Is there a known change in CmpSocketCanDrv / CmpCAACanL2 between 4.20.0.0 and 4.21.0.0 that could affect TX via the CAN API library? Is runtime 4.21.0.0 still supported on Debian 9 Stretch (kernel 4.19, RT-patched), or is a newer OS required? If a minimum OS/kernel requirement was introduced with 4.21, is it documented?
Last updated: 2026-08-17

Post by yannickasselin on MQTT QoS 1 & 2 CODESYS Forge talk (Post)
Hello, I am using Codesys sp20p3 and IIoT library 1.11. I am trying to test QoS 1 & 2 and I have some issues. I am using mosquitto as the broker. I am also using some other MQTT clients like Node-Red and TwinCAT. They all work as expected for every QoS levels. I only have issues with Codesys MQTT client. In the Codesys client, if I subscribe to a topic as QoS 1 or 2, and a client publishes to this topic, I receive the message. But if I disconnect the Codesys client from the network and a client publishes to the subscribed topic, when I reconnect Codesys client to the network, I don't receive the messages as expected. Also there does not seem to be an auto-reconnect feature. So I have to manually set the mqttClient.xEnable bit to FALSE then back to TRUE in order to reconnect to the broker, then I also have to set the subscribe.xEnable to FALSE and back to TRUE in order to re-subscribe to the topic, but even then, I don't receive the messages that were published while I was disconnected. What am I doing wrong? I set the cleanSession bit to FALSE and I give my client a clientID. With the TwinCAT MQTT Client, I do the same thing and everything works as expected. It even auto-reconnects to the broker. I would expect Codesys MQTT Client to be as reliable as TwinCAT. Maybe I am doing something wrong? I also noticed that when trying to publish a QoS 1 or 2 message while disconnected from the broker, it does not work. In TwinCAT, I am still able to publish. The messages are stored in the client and published once reconnected to the broker. I would expect to be able to do the same thing in Codesys. Is this all possible? Am I doing something wrong? Thank you
Last updated: 2024-10-26

<< < 1 .. 237 238 239 240 241 .. 922 > >> (Page 239 of 922)

Showing results of 23050

Sort by relevance or date