Activity for phenixrb
-
phenixrb posted a comment on discussion Runtime 🇬🇧
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
-
ok , but how to fix the error installation of raspberry package 4100
-
hello ,for me , run codesys installer don't start the update to 3.5.17.1 ?? I use the 32bits version
-
hello ,for me , run codesys installer don't start the update to 3.5.17.1 ??
-
thanks edwin I tried to make it complicated ...... by trying to change the path of the file, really sorry. on the other hand, for the I2C network it is 502 for the type in the xml file, isn't it? thanks again
-
HI Edwin, I want to compile this one : https://forge.codesys.com/forge/talk/Runtime/thread/8981ce928a/#a6f8 MCP4728.devdesc.xml [2.38 KiB] I2C_MCP4728.library [335.03 KiB] there are some months I had been able to do for the MCP3208. but now I am unable to repeat the procedure ....... sorry I forgot all.
-
I reread this post, but it didn't help me https://forge.codesys.com/forge/talk/Runtime/thread/9c2e44d5e4/?limit=25#f07d
-
HI Edwin, I want to compile this one : https://forge.codesys.com/forge/talk/Runtime/thread/8981ce928a/#a6f8 there are some months I had been able to do for the MCP3208. but now I am unable to repeat the procedure ....... sorry I forgot all.
-
Hello everyone , I am calling on you because I can no longer compile and register a driver at all, and have it available in a program I don't remember the steps anymore .... when you have the ".library" and "devdesc.xml" files. as in the posts proposed by other contributors if you could describe this to me, I would appreciate it very much. (I spent the day doing trials) thank you
-
hi, I think there is an error for the type ,to be confirmed, because I'm not sure : "Set the Type to 502 for all I2C devices <devicedescription> ... <device> ... <deviceidentification> ... <type> 502 </type> ... </deviceidentification> ... </device> ... </devicedescription> " in the xml file the type is 501, as for the SPI devices. thanks
-
Good morning all , have you ever used the library offered here? : https://forge.codesys.com/forge/talk/Runtime/thread/8981ce928a/#a6f8 is there an example with a value slidebar? which parameter should be used to vary the voltage value at the output of the MCP? thanks, for any help.
-
I have a raspberry pi 3 B + with a codesys license, that works fine, I haven't updated, just in case. for the raspberry pi 4 , I use it just for tests actually , so I will wait for a patch from codesys. thank you
-
Hello , I have the same problem after the update of the raspberry pi 4 ....
-
hello everyone, hope you are well. I come back to you concerning the MCP3208, after making the changes to go from MCP3008 to MCP3208, seen earlier in the post. first, the modifications work well with the MCP3208, I receive many values of the chips. my problem: I would like to use two MCP3208 chips. I noticed that in the lib for MCP3008 or now MCP3208, it is not possible to choose the hardware address, as it is possible to do for MCP23S17 chips. and so I can only use one MCP3208 chip. thanks for any...