Thanks, Jon. Indeed, it was a great starting point. Btw: I like your versioning system. One remark: those rotary switches come in two variants: the solid versions intended for CNC machining and else actually show a quadrature signal. The cheap input switches often output a clock/direction signal. It can be decoded as a quadrature signal, but then four state changes stand for one increment.
The smart pins are just great. They do the dirty work in real time and you fetch a result whenever needed. It's like watching a tanker passing by and just take it, if you are in the mood.
Just a short question: I'm trying to use debug() on a P2 using a PropPlug, but lose debug communication. Another board with an USB-C works fine. Is this a known issue and is there a workaround? (I still use the outdated Propeller Tool 2.9.3
Old Propeller Tool can be twitchy; you could try PNut or Spin Tools (for a nicer environment). If you really want to use Propeller Tool, you could try lowering the DEBUG baud rate using the DEBUG_BAUD constant).
Debug_baud didn't solve the problem. I have a KISS board and a PropPlug. I'm looking to attach a display to the prop2, I normally use as debug output, but as there is no driver, I can not display status information. But I have to stop writing the driver, as the documentation is about 200 pages and the esp example is huge, so I'll fall back on my small display for now.
Comments
I've attached my quadrature encode object that uses smart pins. Perhaps it will help you get started.
Thanks, Jon. Indeed, it was a great starting point. Btw: I like your versioning system. One remark: those rotary switches come in two variants: the solid versions intended for CNC machining and else actually show a quadrature signal. The cheap input switches often output a clock/direction signal. It can be decoded as a quadrature signal, but then four state changes stand for one increment.
The smart pins are just great. They do the dirty work in real time and you fetch a result whenever needed. It's like watching a tanker passing by and just take it, if you are in the mood.
Just a short question: I'm trying to use debug() on a P2 using a PropPlug, but lose debug communication. Another board with an USB-C works fine. Is this a known issue and is there a workaround? (I still use the outdated Propeller Tool 2.9.3
Old Propeller Tool can be twitchy; you could try PNut or Spin Tools (for a nicer environment). If you really want to use Propeller Tool, you could try lowering the DEBUG baud rate using the DEBUG_BAUD constant).
Debug_baud didn't solve the problem. I have a KISS board and a PropPlug. I'm looking to attach a display to the prop2, I normally use as debug output, but as there is no driver, I can not display status information. But I have to stop writing the driver, as the documentation is about 200 pages and the esp example is huge, so I'll fall back on my small display for now.
Dodgy USB cables have caused no end of trouble in the past. Make sure you've swapped to a known good cable before looking elsewhere.