Activity for lubos
-
lubos posted a comment on discussion Engineering 🇬🇧
Hi Edwin, You are right :), It works with new Gateway-2, where is set IP of remote Device. So I don't have to use the old way with "localhost" anymore? In picture You see TOP tasks and comparison between "localhost" and "192.168.2.50" Gateway. Thanks for help!
-
Hello Edwin, thanks for tips, but still it didn't help - same result. 'uname -a' shows: ---without arm64bit=0 (before) Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux ---with arm64bit=0 (after) Linux raspberrypi 6.1.21-v7l+ #1642 SMP Mon Apr 3 17:22:30 BST 2023 armv7l GNU/Linux Security screen still shows "Gateway not configured properly". Firewall is OFF. Thanks for info!
-
Yes, I have this tasks running from SSH login, see picture. Is it OK?
-
Hi, please after update to new version of CODESYS IDE V3.5 SP19, I can't scan and connect Raspberry Pi 4 Device with local Gateway. I've been trying to find a solution for a few days, but I haven't found. See attached pictures. CODESYS runtime and Gateway is installed on Device (i can read the status), but the connection is not estabilished. It seems, that Device don't answer right on TCP request (RST Flag is set in Wireshark packet data capture). There is "Gateway not configured properly" in Security...
-
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
-
Hello, I have problem to control GPIO pins on Raspberry Pi 4. I use latest CODESYS runtime Version 3.5.16.10. I can control GPIO from RPi 4 system (e.g. Python code), but not from CODESYS. I tried older runtime Versions too, another RPi 4 device, but nothing helps. On Raspberry 3B+ function everething without problem. Did You tried this or do You how to solve this issue? Thanks.