KevinOConnor

> I think this is going to come down to whether or not Kevin wants to maintain low level SDIO support in Klipper that is only functional for this specific...

Interesting. I agree this functionality would be good to add to Klipper. At a high-level, the code doesn't look correct to me - at a minimum, the `set_pwm()` command has...

> So basically, it is not safe to call ....send([self._oid, clock, v], minclock=minclock, reqclock=clock) I'm not sure about the above. My comments were referring to the `self._th.note_synchronous_command(print_time)` call from `set_pwm()`...

This should be fixed (by removing spi3) in commit e4c8a247. -Kevin

On Sun, Jan 21, 2018 at 04:03:58AM +0000, GitHub1712 wrote: > Using SET_PIN for laser raster engraving is very slow. > Same code runs much faster on marlin using m42...

It's worth noting that the SET_PIN command was not intended as a mechanism for high speed updates. A SET_PIN command has a minimum time of 100ms - if multiple commands...

In issue #152 Lucas wrote: > As the title says, the printer stops with a 'timer too close' error. > > Now, before anything else, I should mention 2 things:...

On Tue, Jan 30, 2018 at 11:30:54PM +0000, Lucas wrote: > I've been reading some code but I don't think I'm understanding this correctly. > Let's see. For each pin...

On Sun, Feb 18, 2018 at 01:00:03PM -0800, Lucas wrote: > Sorry to bother you again. > > > As earlier, the way I would address it would be to...

I'm not aware of any progress on this topic. I don't have any short term plans to work on this myself. -Kevin