LeafLabs Garden

A place to share, learn, and grow...

1. 

   bubulindo
   Member

   Hello,

   I'm working on the encoder mode for the Maple timers and I'm wondering whether to change the HardwareTimer class, or implement a separate one for this.
   Especially because there is more functionality to the encoder mode that would make sense to put in a HardwareTimer class.
   What are your suggestions?

   Also, while I'm at it, does anyone know of an optical encoder model that works with 3,3V? I'm using one of those PCB thumbwheel encoder and the bounce, despite the digital filter in the STM chip, is extremely hard to get rid of and confuses the whole thing to the point that I don't know if it's a bounce problem or something wrong with the code. (I may just put an Arduino simulating an encoder signal for test purposes).

   Thanks in advance for any help or suggestions.

   Posted 2 years ago #
2. 

   feurig
   Member

   Can you subclass HardwareTimer and add the functionality?

   As much as I dislike C++ there are instances where it may actually help.

   Posted 2 years ago #
3. 

   gbulmer
   Moderator

   bubulindo - There has been a long-running discussion about changing the Timer classes. So I would probably steer clear of them at first, at least until the encoder code is working reliably.

   AFAIK, much of the encoder is mutually exclusive to the timer's PWM functionality. So it isn't clear to me that there'd be much reuse. However, it might be easier to detect the user is using the same hardware for two different purposes, and try to do something helpful, if they have a common root. Even then, the code may be able to read a few values from the peripheral hardware and detect conflicts.

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.