1220801328 Posted September 24 Share Posted September 24 (edited) Hello everyone, I have recently encountered a problem, I use ACC-24E3, the guide has an incremental scale and a second absolute scale, through the absolute scale power up to obtain the commutation position and the position of the position loop position, and then use the incremental scale as the phase feedback address, so that the use of the work is normal! But there is a problem with my axis system, he will move out of the reading range for some reason, then the incremental scale signal will be lost, the absolute scale signal is still there (all of the above is the open-loop case, this situation is due to special process requirements). After the axis is run back through the other mechanism, the position ring is restored by the HOMEZ command. Phase position I don't know how to re-give the absolute scale position data to the PMAC to use as phase position without restarting the PMAC device (because there is a problem with the absolute scale signal, it can't be used as a continuous phase position), and he gets an exception when I execute the online $ command or set Motor[x].PhaseFindingStep to 1. I also tried multiplying the current absolute position plus the bias value by Motor[x].AbsPhasePosSf and then solving for the remainder and writing it to Motor[x].PhasePos, but the value calculated this way is wrong. Thanks in advance Edited September 24 by 1220801328 Quote Link to comment Share on other sites More sharing options...
steve.milici Posted September 24 Share Posted September 24 This is an English only website. Please repost in English. Quote Link to comment Share on other sites More sharing options...
1220801328 Posted September 24 Author Share Posted September 24 1 hour ago, steve.milici said: This is an English only website. Please repost in English. Sorry, I'm having trouble typing. Quote Link to comment Share on other sites More sharing options...
MoMo Posted September 25 Share Posted September 25 Based on your description, I believe the issue may be caused by incorrect parameter settings or an error in the commutation process. Please provide more detailed information; otherwise, it will be difficult to analyze the cause. 1.What absolute encoder are you using? 2.How many effective bits does your absolute encoder have? 3.What are the settings for your absolute encoder? 4.What is the pole pitch of your motor? What is the resolution of your incremental encoder? 5.How did you configure the parameters related to commutation? What type of driver are you using? 6.Is it a DPWM driver? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.