Thanks for the info! Any chance you can provide your full config?
>From the video I don't think it looks like a "roll-over" issue. It looks more like a "beat-frequency" issue between two asynchronous threads. This happens frequently when a PRU controlled pin is also configured as an output pin with the hal_bb_gpio driver (ie: two threads trying to set the same output pin), but there are other possible causes. There isn't enough detail in the pieces of your configuration files you posted to determine if this is the issue or if it's something else. On 1/27/2019 10:28 AM, Scott Nortman wrote: > Hi Charles, > > I am using a slightly modified version taken from config/ARM/BeagleBone/CRAMPS > > Here is a link: https://pastebin.com/spiURz5j > > Here is a video from my scope: https://www.youtube.com/watch?v=4nKZhipoK_c > > Note that I have the spindle speed value wired directly to the PWM value for > debug so using MDI I can enter any duty cycle, for example M3 S0.5 > > After switching to th Adafruit_BBIO.PWM library + Python, I am able to > generate perfect PWM on the same physical pin without any problems. > > Please let me know if you need more info... > -- Charles Steinkuehler [email protected] -- 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.
