I've been working for a while to get my Teensy 3.1 based controller board to manage four Quadrature Encoders, and provide PID position control for four DC motors. This was completed a month or so ago, and I've since downloaded, and finally successfully compiled and installed Teacup_firmware on the Teensy. My Quadrature decoder routines use two separate methods, Hardware flextimer modules run X/Y axis, and hardware interrupts for two Z axis decoders. Thought being that movement of the Z-Axis is less critical to path planning. All decoder routines are interrupt driven, and run autonomous of anything else on the processor. They simply provide global variables for the current exact position and direction of each axis. The DC motor PIDs today use the metro timing library and a version of the arduino PID library, and also run autonomous of anything else on the processor. Fill a global variable with the next target position, and it goes there. What is missing currently is the velocity profiling to have smooth X/Y path control. So.. long story short, I'm looking for a method to use the functionality of Teacup_firmware to control my servos as if they were steppers. in other words, the macros that are in teacup to WRITE direction and step, I wish to replace with macros that assign +1 or -1 to an axis direction variable. (ie: XAXIS_DIR=-1) then when a STEP command is issued, that macro would ADD the axis direction variable to the axis target position value (ie: XAXIS_TARGET += XAXIS_DIR) . If DIR was negative, the addition would result in decrementing the target position. The axis position PID would then update it's position based on this in real time. And yes, at some point, I would expect to use dda_clock() to control timing of the PIDs. Am I way off track here? Is there an easier way to integrate? In my mind, I simply need to include my two files and their headers. Encoders are interrupt driven, and feed global variables. Motors read global variables and use interrupts to sync position. two macros need to be replaced per axis. One for WRITE Direction one for WRITE Step. Thoughts? Guidance please... https://reprap.org/forum/read.php?147,486936,486936#msg-486936 Fri, 04 Sep 2026 12:50:23 -0400 Phorum 5.2.23 https://reprap.org/forum/read.php?147,486936,489232#msg-489232 https://reprap.org/forum/read.php?147,486936,489232#msg-489232 Miguel Sanchez (MISAN) and I have been talking for quite a while now. He is doing some incredible work!

He recently developed a two dc-motor controller on one arduino with Step/DIR control!]]> unix_guru Firmware - experimental, borrowed, and future Fri, 27 Mar 2015 08:06:37 -0400 https://reprap.org/forum/read.php?147,486936,489108#msg-489108 https://reprap.org/forum/read.php?147,486936,489108#msg-489108
Seems you solved it, but mey u want to take a look Misan work in [forums.reprap.org]

Sorry if not.

I´m not english.]]> SergioMC Firmware - experimental, borrowed, and future Thu, 26 Mar 2015 20:56:09 -0400 https://reprap.org/forum/read.php?147,486936,487289#msg-487289 https://reprap.org/forum/read.php?147,486936,487289#msg-487289
That said, I'm working through the X-axis pin remapping and macro replacements etc... Hope to have X-Axis running later tonight.

Cheers.]]> unix_guru Firmware - experimental, borrowed, and future Mon, 23 Mar 2015 09:30:33 -0400 https://reprap.org/forum/read.php?147,486936,486936#msg-486936 https://reprap.org/forum/read.php?147,486936,486936#msg-486936
This was completed a month or so ago, and I've since downloaded, and finally successfully compiled and installed Teacup_firmware on the Teensy.

My Quadrature decoder routines use two separate methods, Hardware flextimer modules run X/Y axis, and hardware interrupts for two Z axis decoders. Thought being that movement of the Z-Axis is less critical to path planning.

All decoder routines are interrupt driven, and run autonomous of anything else on the processor. They simply provide global variables for the current exact position and direction of each axis.

The DC motor PIDs today use the metro timing library and a version of the arduino PID library, and also run autonomous of anything else on the processor. Fill a global variable with the next target position, and it goes there. What is missing currently is the velocity profiling to have smooth X/Y path control.

So.. long story short, I'm looking for a method to use the functionality of Teacup_firmware to control my servos as if they were steppers.
in other words, the macros that are in teacup to WRITE direction and step, I wish to replace with macros that assign +1 or -1 to an axis direction variable. (ie: XAXIS_DIR=-1) then when a STEP command is issued, that macro would ADD the axis direction variable to the axis target position value (ie: XAXIS_TARGET += XAXIS_DIR) . If DIR was negative, the addition would result in decrementing the target position.

The axis position PID would then update it's position based on this in real time.
And yes, at some point, I would expect to use dda_clock() to control timing of the PIDs.

Am I way off track here? Is there an easier way to integrate? In my mind, I simply need to include my two files and their headers.
Encoders are interrupt driven, and feed global variables.
Motors read global variables and use interrupts to sync position.
two macros need to be replaced per axis. One for WRITE Direction one for WRITE Step.

Thoughts? Guidance please...]]> unix_guru Firmware - experimental, borrowed, and future Sun, 22 Mar 2015 11:59:12 -0400