CODESYS Talk
... the stars needed? [CmpCharDevice] PermittedPath.0=/dev/i2c* PermittedPath.1=/dev/spidev0.0 PermittedPath.2=/sys/class/gpio/* PermittedPath.3=/dev/gpiochip*
CODESYSControl_User.cfg [CmpCharDevice] PermittedPath.0=/dev/i2c PermittedPath.1=/dev/spidev PermittedPath.2=/sys/class/gpio/ PermittedPath.3=/dev/gpiochipPerm will be solved to 4.23.0.0 release
CODESYSControl_User.cfg [CmpCharDevice] PermittedPath.0=/dev/i2c PermittedPath.1=/dev/spidev PermittedPath.2=/sys/class/gpio/ PermittedPath.3=/dev/gpiochipPerm
Hi together, -> I updated my raspberry pi3 with runtime 4.22.0.0, and then no I2C device is running. -> when i switch back to runtime 4.20.0.0 all I2C devices running. what have i additionally to do, so that I2C Bus is although running in the newest Runtime Version 4.22.0.0 ? I did read something about security changes on the new runtime Version, but i do not clear understand, what i have do do, do bring the I2C Bus to live again ? ... there should be a Dialog in the Runtime Deploy tool, (see the...
Hi Georg, Thank you very much for your help and for taking the time to look into my issue! After reversing the directions of A2 and A3, the robot now moves correctly according to the coordinate system. That solved the main issue with the joint rotation directions. However, I still have two issues: When I command the robot to move along the X, Y, and Z axes, the movement seems slightly off, and the trajectory appears somewhat diagonal instead of following a straight line along the commanded axis....