On 15 November 2013 10:44, Peter C. Wallace <[email protected]> wrote:
> its possible to home to index at full motor speed to within 1 encoder count, > as the actual capture of the encoder count at index is done in hardware, so > Motor speed is immaterial. Yes, but, well... The bldc component only gets to see the "rawcounts" pin, which doesn't respond to encoder index. This is important, as you really don't want to lose commutation any time that index-enable is set/reset. So, the bldc component uses the value of rawcounts that it sees on the next servo-cycle after the index-enable reset. I can see an argument for adding a pin to connect the "counts" value from the encoder. This could be connected to the bldc component so that the component can see how much further the encoder has moved since the index was seen. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
