Jump to content
OMRON Forums

Motor Setup on CK3A-G305L with AX1313N


Recommended Posts

I am trying to setup two motors on these PWM drivers using the AX1313N.

Neither motor type seems to be able to be configured by the wizard. The wizard does a terrible time with the Phase scaling calculation and seems to not use the brake properly.


First motor is a linear motor with 3 cycles in 2 mm of travel with a linear encoder with 0.0001 mm resolution. It is a 3->1 UVW transition for the hall sensors. I hence set -170.6667 for AbsPhasePosSf. PhasePosSf is found to be about 0.0019999. This gives me good plots of UVW vs phase position when hand pushing the motor. This these settings it can get through the voltage 6 step test but fails out on the current loop.


I know this motor works fine as I ran it with an ACS controller this morning to verify proper operation.


Second motor is a rotary motor with 16 poles per rotation and 40,000 encoder counts. Also 3->1 UVW transition. PhasePosSf is on the order of 1.599e-5 to provide approximately close match between the phase cycles and the UVW when manually moving the motor. I will note that the units for this position are in REV compared to mm for the other motors and I have to use 4 million user units to get the proper alignment between revs and physical motion of the motor. This motor refuses to go through the 6 voltage step test. I have check that the motor resistances are correct and not shorted or broken.

Link to comment
Share on other sites

  • 2 weeks later...
To Update this based on work with Support. I have found that there is some non obvious setting that is messing up both the Automatic and Manual Test and Set box for this combination of amplifier and controller when using quad encoder feedback. The 6 set voltage test passes but the current loop will not work. If you go and manual tune the current loop then do the 6 step current test, the motors move properly to where they are supposed to go (verified by watching the encoder positions and the hall sensors during the process) but the software is trying to read the encoder positions from somewhere different and just reads out essentially 0 all the time for the position. This is likely also the problem with the current loop test as it tries to move the stage to a position and I think it is not seeing the motion so fails the test out.
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...