lubos

Hello, I try to add variable to trace monitor on CODESYS Raspberry Pi SL, but it is not possible. I see error message by variable field: "Not a traceable variable". Is there some support of trace on RPi? Version of engineering: CODESYS V3.5 SP16 Version of runtime: codesyscontrol 4.0.1.0 (armhf) Thanks for info!

Hello, I try to add variable to trace monitor on CODESYS Raspberry Pi SL, but it is not possible. I see error message by variable field: "Not a traceable variable". Is there some support of trace on RPi? Version of engineering: CODESYS V3.5 SP16 (armhf) Version of runtime: codesyscontrol 4.0.1.0 (armhf) Thanks for info!

Hello, I try to add variable to trace monitor on CODESYS Raspberry Pi SL, but it is not possible. I see error message by variable field: "Not a traceable variable". Is there some support of trace on RPi? Version: codesyscontrol 4.0.1.0 (armhf) Thanks for info!

OK, can be, that You have another Problem.. but this need more description of Your issue.. In Raspbian is neccessary to allow control of GPIO in "Interfaces - Raspberry Pi Configuration". I hope, this You have set if You uses Python. Which CODESYS and runtime version do You use? Do You set outputs or read inputs? Can You send some printscreens or whole project is best...

Here is detailed picture how to change GPIO control... Update Device for GPIO:

Here is detailed picture how to change GPIO control... Update Device for GPIO:

Hello, I solved this issue with use of new CODESYS runtime V3.5.16.20. There I used new GPIO driver: "GPIOs B+/Pi2". (The older was named "GPIOs A/B" and worked me only on RPi3B+). Lubos

Hello, I solved this issue with use of new CODESYS runtime V3.5.16.20. There I used new GPIO driver: "GPIOs B+/Pi2". (The older was named "GPIOs A/B" and worked me only on RPi3B+). I dont know how is GPIO driven from Python, how system manage this. Please send us some code as example... Lubos