Hello...
As you may or may not recall, I've been teaching myself motion since mid-summer. I've started a new job and got a call in from a customer saying that, when trying to run a MSO Motion Direct Command, they get an error stating that the "motion group is not in the synchronized state." (using a K350, CIP)
I've done some research and there isn't much on the subject besides saying that the cause is possibly a configuration issue.
I tried a theory that I had, that the axis did not belong to a motion group, this morning on a K2000 but that error was pretty specific in stating that the axis wasn't assigned [to a motion group].
Besides being just a 'motor not configured' type of thing, I was wondering if anyone else has saw this.
The customer was supposed to call me back yesterday but must have got caught up. Not sure if they figured it out on their own but I am just curious since I don't have their program in front of me and can't re-create the error.
As you may or may not recall, I've been teaching myself motion since mid-summer. I've started a new job and got a call in from a customer saying that, when trying to run a MSO Motion Direct Command, they get an error stating that the "motion group is not in the synchronized state." (using a K350, CIP)
I've done some research and there isn't much on the subject besides saying that the cause is possibly a configuration issue.
I tried a theory that I had, that the axis did not belong to a motion group, this morning on a K2000 but that error was pretty specific in stating that the axis wasn't assigned [to a motion group].
Besides being just a 'motor not configured' type of thing, I was wondering if anyone else has saw this.
The customer was supposed to call me back yesterday but must have got caught up. Not sure if they figured it out on their own but I am just curious since I don't have their program in front of me and can't re-create the error.