Hi, I'm saying that the actual steps are generated by the PRU (the orange section of the diagram linked to above), while the position generation is done on the main processor (the pink section), and still further more work is done outside the picture. The PRU and main processors are separate from each other and communicate step and speed information between themselves.
The real fix would be in the PRU code. A work around is by adding the PID stuff in the HAL file. The dithering DIR line should not affect the actual position of the stepper motor. What it can do, depending on the actual hardware, is change the way the drive handles recirculating current in the transistors. This can end up making a frequency that can be heard as a ticking or buzzing noise. Jeff On Thursday, May 11, 2017 at 11:11:19 AM UTC-7, Nick Collier wrote: > > @Jeff Pollard > > My machine seems to be working fine, I would like to fix the bug because > it is making me feel like I need to understand the system more. > > So I can modify the PID using the stepgen command in the hal config file? > > Are you saying that the stepgen algorithm is using several different > processors? > > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
