(no subject) ^{l-lll wiki (Thread)}
Last updated: 2025-05-13

wiki Discussion ^{glutenaron wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-05-13

blog Discussion ^{glutenaron blog (Discussion)}
Forum for blog comments
Last updated: 2025-05-13

(no subject) ^{glutenaron wiki (Thread)}
Last updated: 2025-05-13

Home ^{glutenaron wiki (WikiPage)}
Project Members: glutenaron (admin)
Last updated: 2025-05-13

wiki Discussion ^{jonesnatelye wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-05-13

blog Discussion ^{jonesnatelye blog (Discussion)}
Forum for blog comments
Last updated: 2025-05-13

(no subject) ^{jonesnatelye wiki (Thread)}
Last updated: 2025-05-13

Home ^{jonesnatelye wiki (WikiPage)}
Project Members: jonesnatelye (admin)
Last updated: 2025-05-13

Post by glutenaron on Safety drive EL6900 and mitsubishi ^{CODESYS Forge talk (Post)}
Hi, Im wokring to get my servo mitsubishi mr-j5-g40-rnj1 working with my safety drive. I have as you can se in the picture Ek1100 koppler and EL6900 as safety plc. My questien is how do i connect the safety_drive to the SM3_Drive_ETC_Mitsubishi_MelServo_J5_Axis1 down below? I get the error ((Logical I/Os]: The logical device 'Safety_Drive' is not mapped to any physical device.)) but how do i map this? regard
Last updated: 2025-05-13

wiki Discussion ^{shaurum wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-05-13

blog Discussion ^{shaurum blog (Discussion)}
Forum for blog comments
Last updated: 2025-05-13

(no subject) ^{shaurum wiki (Thread)}
Last updated: 2025-05-13

Home ^{shaurum wiki (WikiPage)}
Project Members: shaurum (admin)
Last updated: 2025-05-13

Post by mondinmr on Unexpected behavior in cyclic encoder read method during INT overflow (wrap-around) ^{CODESYS Forge talk (Post)}
Hi everyone, I’m investigating a potential issue with a cyclic method we use for reading incremental encoders in our libraries. I’ve come across two implementations that, at first glance, appear to perform the same operation: motionUnit.vlPositionActualValue is UINT due strange encoder type. Version A METHOD PROTECTED cyclicReadField VAR_INST actPosFieldOld: INT; rI: INT; delta: INT; END_VAR rI := TO_INT(motionUnit.vlPositionActualValue); delta := rI - actPosFieldOld; m_actPosRaw := m_actPosRaw + TO_LREAL(delta); actPosFieldOld := rI; IF settings.velocityFeebackMapped THEN m_actVelRaw := TO_LREAL(motionUnit.velocityActualValue); END_IF Version B METHOD PROTECTED cyclicReadField VAR_INST actPosFieldOld: INT; END_VAR m_actPosRaw := m_actPosRaw + TO_LREAL(TO_INT(motionUnit.vlPositionActualValue) - actPosFieldOld); actPosFieldOld := TO_INT(motionUnit.vlPositionActualValue); IF settings.velocityFeebackMapped THEN m_actVelRaw := TO_LREAL(motionUnit.velocityActualValue); END_IF Both use INT and the same delta logic, so they seem equivalent. However, when an overflow (wrap-around) occurs, version A continues correctly as expected, while version B unexpectedly resets to -32768 without a clear reason. Has anyone experienced similar behavior or can shed light on what might be happening here? It almost seems as if the cast to LREAL is being applied before the calculation — but that would be illogical and potentially very dangerous in many situations! Thanks!
Last updated: 2025-05-13

Post by glutenaron on Safety drive EL6900 and mitsubishi ^{CODESYS Forge talk (Post)}
Can also mention target version 4.15 codesys 3.5 SP21 (64bit) EL6900 version 4.0.3.0
Last updated: 2025-05-13

Unexpected behavior in cyclic encoder read method during INT overflow (wrap-around) ^{CODESYS Forge talk (Thread)}
Unexpected behavior in cyclic encoder read method during INT overflow (wrap-around)
Last updated: 2025-05-13

Keeping lost connection to BeagleBone Black (BBB) wireless ^{CODESYS Forge talk (Thread)}
Keeping lost connection to BeagleBone Black (BBB) wireless
Last updated: 2025-05-13

Codesys installation problem ^{CODESYS Forge talk (Thread)}
Codesys installation problem
Last updated: 2025-05-13

wiki Discussion ^{jromero213 wiki (Discussion)}
Forum for wiki comments
Last updated: 2025-05-13

blog Discussion ^{jromero213 blog (Discussion)}
Forum for blog comments
Last updated: 2025-05-13

Post by l-lll on CODESYS and Win10 - "the version profile is not valid" error ^{CODESYS Forge talk (Post)}
Hello, I also meet this problem, and the same problem occurred even after reinstalling CODESYS. I didn't fully understand your last description. Could you attach pictures for better illustration?
Last updated: 2025-05-13

Codesys V2.1 ^{CODESYS Forge talk (Thread)}
Codesys V2.1
Last updated: 2025-05-13

(no subject) ^{jromero213 wiki (Thread)}
Last updated: 2025-05-13

Home ^{jromero213 wiki (WikiPage)}
Project Members: jromero213 (admin)
Last updated: 2025-05-13

Sort by relevance or date