<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for kenth1973</title><link href="https://forge.codesys.com/u/kenth1973/activity/" rel="alternate"/><id>https://forge.codesys.com/u/kenth1973/activity/</id><updated>2025-12-17T19:01:59.992000Z</updated><subtitle>Recent activity for kenth1973</subtitle><entry><title>kenth1973 posted a comment on discussion Motion 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#e0fe" rel="alternate"/><published>2025-12-17T19:01:59.992000Z</published><updated>2025-12-17T19:01:59.992000Z</updated><author><name>kenth1973</name><uri>https://forge.codesys.com/u/kenth1973/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#e0fe</id><summary type="html">Hi Georg OK got it, thank you. I respect your (CODESYS) policies on that issue. Will try to update according to your recommondation if the customer experience same error in the future. Though - from within my coding heart it does bother me deeply, that I cannot get further understanging/knowledge on the iPhasingState, but I guees I will have to swollow that bitter pill and get on with it! hehe ;-)</summary></entry><entry><title>kenth1973 posted a comment on discussion Motion 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#af91" rel="alternate"/><published>2025-12-17T13:44:12.423000Z</published><updated>2025-12-17T13:44:12.423000Z</updated><author><name>kenth1973</name><uri>https://forge.codesys.com/u/kenth1973/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#af91</id><summary type="html">Hi George - ok thanks - but who created this FB in the first place? Could you lead me to the creator company? Is CODESYS not the old S3 that created this FB? :-)</summary></entry><entry><title>kenth1973 posted a comment on discussion Motion 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#b0df" rel="alternate"/><published>2025-12-11T12:29:08.681000Z</published><updated>2025-12-11T12:29:08.681000Z</updated><author><name>kenth1973</name><uri>https://forge.codesys.com/u/kenth1973/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#b0df</id><summary type="html">Hi George. Thx for the info and recommendation - the robot is running production at customer. But - would you have any information about the states numbers and their different explenations?</summary></entry><entry><title>kenth1973 posted a comment on discussion Motion 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#c943" rel="alternate"/><published>2025-11-22T20:56:51.788000Z</published><updated>2025-11-22T20:56:51.788000Z</updated><author><name>kenth1973</name><uri>https://forge.codesys.com/u/kenth1973/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Motion/thread/df2a09cc86/?limit=25#c943</id><summary type="html">My MC_Phasing FB was stuck in iPhasingState=1 and error output HIGH on one axis. I could manually overwrite the state to 0 in the instance data. During normal run I see the state change from 0 to 10 to 100 back to 0 (maybe more states that I couldnt catch with the naked eye) But - what are the states numbers and their different explenations? This is not explained in the FB guide on codesys. (the pictures show state = 0 after I reset)</summary></entry></feed>