I've updated Codesys from 3.5.9.40 to 3.5.10.0, and downloaded + installed the codesyscontrol for raspberry pi package again.
When i try to connect to my raspberry now, codesys refuses because the pi doesn't have the correct and new version of codesyscontrol installed.
If i go to "update Raspberry Pi", there is no .deb file selectable. i searched for *.deb in all directories on my computer, and have found none. how can i get the new .deb file?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
should be here after installing/updating the package:
"c:\Users\<yourwindowsusername>\CODESYS Control for Raspberry PI\codesyscontrol_arm_raspberry_V3.5.10.0.deb" </yourwindowsusername>
BR
Edwin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the email with the file. This seems to be a bug. There was no .deb file on C:. i also checked this directory. although, there isn't a "users" directory on my C:\ drive, it's named "Benutzer" here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, how did you find the .deb file? i have the same problem with codesys version 3.5 SP 16 Patch 3. First i did not have the menue entry under Tools -> Update raspberry Pi, i managed that in adding it with customize. Now i cant find the .deb package.
I even updated to 4.0.0.0 and there is no *.deb Package in C:\Users>username>\CODESYS Control for Raspberry PI\
Any advise?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I managed to solve the problem. When i start the codesys engineering as normal user (without admin rights), I do not see any runtime and the Update Raspberry Pi symbol does not appear under Tools Menu. When i start the engineering with right click -> run as admin. The Button under Tools is appearing and i can install the runtime on the raspberry Pi without any problems. It seems that codesys has some problems with uac under windows 10.
Maybe this helps some other users, when searching it on google.
Best Regards
M.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I've updated Codesys from 3.5.9.40 to 3.5.10.0, and downloaded + installed the codesyscontrol for raspberry pi package again.
When i try to connect to my raspberry now, codesys refuses because the pi doesn't have the correct and new version of codesyscontrol installed.
If i go to "update Raspberry Pi", there is no .deb file selectable. i searched for *.deb in all directories on my computer, and have found none. how can i get the new .deb file?
Hi,
should be here after installing/updating the package:
"c:\Users\<yourwindowsusername>\CODESYS Control for Raspberry PI\codesyscontrol_arm_raspberry_V3.5.10.0.deb" </yourwindowsusername>
BR
Edwin
Thanks for the email with the file. This seems to be a bug. There was no .deb file on C:. i also checked this directory. although, there isn't a "users" directory on my C:\ drive, it's named "Benutzer" here.
Hi, how did you find the .deb file? i have the same problem with codesys version 3.5 SP 16 Patch 3. First i did not have the menue entry under Tools -> Update raspberry Pi, i managed that in adding it with customize. Now i cant find the .deb package.
I even updated to 4.0.0.0 and there is no *.deb Package in C:\Users>username>\CODESYS Control for Raspberry PI\
Any advise?
I managed to solve the problem. When i start the codesys engineering as normal user (without admin rights), I do not see any runtime and the Update Raspberry Pi symbol does not appear under Tools Menu. When i start the engineering with right click -> run as admin. The Button under Tools is appearing and i can install the runtime on the raspberry Pi without any problems. It seems that codesys has some problems with uac under windows 10.
Maybe this helps some other users, when searching it on google.
Best Regards
M.
Thanks for sharing the information buddy, i too faced same issue. Now with help of yours i had cleared it.