maybe this is because of the description:502 for I2C ? <type>502</type> https://forge.codesys.com/drv/io-drivers/doc/I2C/
Hi, You're welcome ingo, it seems to me that's the purpose of this forum, some helped me when I was stuck, so if I can save others from spending hours looking for solutions. it would be nice if codesys looked at the problem too.... otherwise, I use a raspberry pi4, and the device is updated on "GPIOs B + / Pi2" as in the picture.
okay, this is how I did it: download the raspberry 4.1 package in a folder, open codesys installer, selected "change" in version 3.5.17 "install files" and choose the downloaded 4.1 package, codesys installer installs the package. after I find version 4.1 in the codesys runtime package. just update the raspberry with version 4.1
hello galexis, can you show a screen image? you say 4.1 is installed, ok, but where?
Hello everyone, if it helps: not using GPIOs_A_B, I disabled it in the program and that solved my problem. although GPIOs appear as "not used", it seems that this is not taken into account well in codesys. this remains a problem for those who want to use GPIOs_A_B
Hello everyone, if it helps: not using GPIOs_A_B, I disabled it in the program and that solved my problem. although GPIOs appear as "not used", it seems that this is not taken into account well in codesys.
Hello everyone , I updated to version 4100 and since I see a fault in the GPIOs of the raspberry: I am using a raspberry GPIO to pulse to an external hardware watchdog. the pulse is managed directly by raspbian: import RPi.GPIO as GPIO import time PULWD = 16 # BCM / GPIO GPIO.setwarnings (False) GPIO.setmode (GPIO.BCM) GPIO.setup (PULWD, GPIO.OUT) while True: GPIO.output (PULWD, 0) time.sleep (0.5) GPIO.output (PULWD, 1) time.sleep (0.5) so far this has always worked with all other versions of codesys....
ok ,thank you , I could update now