H2 Ctrio2

[DLTimmons]

I am seeing a strange issue. I have a Crtio2 that is running a pair of Sure servos one on each channel. I appears after a power up on the first run after I first run a CTAXCFG the Initial position is set correctly I then run a CTAXTRAP to the first target position that shows the correct target but the Output position winds up at zero not the target position. This run the machine the wrong direction.

After the first move it works correctly

[BobO]

Controller?

[BobO]

Duh...must be Do-more.

[DLTimmons]

H2-DM1E

[Greg]

Can you send me your .DMD file? It would be easier than asking for clarification on the forum. I'll then post answers to the forum. Please send to support@hosteng.com

[DLTimmons]

Did you get the e-mail with the code?

[DLTimmons]

All I have to do to get to repeat is cycle power to the system.  It acts like the CTAXCFG is not initialize to the correct value leaving it at zero but when it starts running the pulse output position show it the be going one direction but the output is going the wrong direction. I get the same thing on both channels of the ctrio one counting positive the other is counting negative as the drives are mirrored.

[Greg]

Got the email. Sorry so slow. Had a rush of customer programs to evaluate lately. Probably be Monday before I can get to the details. But looking at it now...

[DLTimmons]

I'm stepping thru the start up got some more screen shots but fail to get the shot  after Trap move it faulted the drive from hitting the over travel stops. It sure looks like the initial position is correct and the target position show to be correct but it just runs the wrong direction and you can see the pulse output position showing it is moving the wrong direction away from the target position. I reset the drive fault and all move after that work correctly.

[DLTimmons]

I come up with a sledge hammer fix. I do a very short move as part of a startup program I added very slow speed and short distance 1" out 4000" for a very short time 4 sec it actually times out before the move reaches target this disables the trapezoidal move. This is enough that the next actual move works correctly. The move distance and speed is short enough and slow enough that if it does hit the over travel stops it will not damage anything.

[DLTimmons]

Got get a bigger hammer. It failed this morning when the wrong direction again after powerup.

[DLTimmons]

With CTAXCFG does have to move before you can send another CTAXCFG or does the last CTAXCFG set the configuration of the CTRIO or are they buffered?

[BobO]

With CTAXCFG does have to move before you can send another CTAXCFG or does the last CTAXCFG set the configuration of the CTRIO or are they buffered?

Last one is it. Can send as many as you like.

[Greg]

DLTimmons, I duplicated what you are seeing. Until the firmware is fixed, there is a workaround.

1. Do a CTAXCFG and set the Initialize Output Position = 0
2. Do a CTAXTRAP and set the Target Position = 0

These two steps will do absolutely nothing except complete without error.

Then proceed to do your normal CTAXCFG with your normal Initialize Output Position value, and your normal CTAXTRAP with your normal Target Position value.

This workaround will continue to work even after the up-and-coming fixed firmware is loaded.

Let me know if you have any more problems, or if this doesn't work for you.

[DLTimmons]

I feel much better that you could duplicate the issue. Was starting think I was loosing my mind

What can I say about your support!! It sure nice dealing with someone that does not blame everyone else for an issue.

I had added a startup doing a very short move at very slow speed and time delay on letting it jump out of the stage from completion set bit. I will try the 0 initial 0 target trick.

Thanks