FORUM | LATEST POST | # TOPICS |
---|---|---|
General Discussion Forum about anything you want to talk about. |
How to turn on a GPIO from a device function block by lwalbert 2022-09-29 |
1 |
Hi, You can give a try it by adding "Codesys.exe" in the "Exclusions > Process" section of the Windows Security Center or your antivirus program. I hope it works for your situation. Antivirus programs check many things during both the installation or startup of an application, and may be slow down or block some functions. Regards Imdat
Hello, As far as I know, no matter which home mode is selected, the axis must be in Standstill mode to run MC_Home according to PLCopen state machine. However, if the function you want can already be done from a parameter in the driver of the vendor you are using, you can try to perform the same function by sending the required value to that parameter via communication with the SDO write command. Regards, Imdat
Is it possible to use MC_Home without enabling the drive (MC_Power)? On the drive the homing method 35 (Homing on current position) has to be executed. The drive has to stay disabled due to safety. This is explicitly allowed by the drive. Unfortunately MC_Home reports the error SMC_REGULATOR_OR_START_NOT_SET when executed. Are there other options to start homing, if not with MC_Home?
with latest version? 4.16.0.0? Use the CODESYS Installer to download all required packages if you need an offline installation
with latest version? 4.16.0.0? Use the CODESYS Installer to downliad all required packages if you need an offline installation
..just use 'putty' ssh client on the virtual machine to login for a test to the pi. if this work it should work in CODESYS too.
with latest version? 4.16.0.0?
Hi, Is there a solution found for the problem described in first post? Any version above Codesys 3.5 P19 hangs during start up. It makes no difference whether I simply start Codesys or open a project directly. I'm using Windows 10 Home edition. Thanks!
Hi, I have the same problem, is there a solution?
Yep sure, though now that i think of it, its a pi 4. My bad. The whole ordeal was necessary to use the VGA666 adapter. That needs the old graphical system and GPIO directly on the CPU. Edit: Putty on the virtual development machine connects fine. But i did change the login/pw. The account is still a sudo'er so that should be all right. Edit2: Sorry i get a "Comment rate limit exceeded" from the forum. Then i'll add it as edit here. So i have tried the stock raspberry pi image on a different pi5 (truly...