PyTmcStepper 0.8.0__tar.gz → 0.9.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (63) hide show
  1. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/LICENSE +5 -4
  2. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/PKG-INFO +45 -28
  3. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/README.md +40 -22
  4. pytmcstepper-0.9.1/pyproject.toml +52 -0
  5. pytmcstepper-0.9.1/setup.cfg +4 -0
  6. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/PyTmcStepper.egg-info/PKG-INFO +45 -28
  7. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/PyTmcStepper.egg-info/SOURCES.txt +9 -2
  8. pytmcstepper-0.9.1/src/tmc_driver/_tmc_logger.py +221 -0
  9. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/_tmc_math.py +18 -0
  10. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/_tmc_stallguard.py +4 -4
  11. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/_tmc_stepperdriver.py +26 -14
  12. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/com/_tmc_com.py +18 -30
  13. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/com/_tmc_com_spi.py +3 -21
  14. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/com/_tmc_com_spi_base.py +12 -16
  15. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/com/_tmc_com_spi_ftdi.py +4 -12
  16. pytmcstepper-0.9.1/src/tmc_driver/com/_tmc_com_spi_micropython.py +94 -0
  17. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/com/_tmc_com_uart.py +3 -8
  18. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/com/_tmc_com_uart_base.py +13 -15
  19. pytmcstepper-0.9.1/src/tmc_driver/com/_tmc_com_uart_micropython.py +120 -0
  20. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/enable_control/_tmc_ec.py +3 -2
  21. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/enable_control/_tmc_ec_pin.py +3 -3
  22. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/enable_control/_tmc_ec_toff.py +1 -1
  23. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/motion_control/_tmc_mc.py +11 -10
  24. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/motion_control/_tmc_mc_step_dir.py +399 -389
  25. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/motion_control/_tmc_mc_step_pwm_dir.py +4 -5
  26. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/motion_control/_tmc_mc_step_reg.py +65 -65
  27. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/motion_control/_tmc_mc_vactual.py +33 -8
  28. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/reg/_tmc220x_reg.py +1 -1
  29. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/reg/_tmc224x_reg.py +1 -1
  30. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/reg/_tmc_reg.py +5 -6
  31. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/tmc_2209.py +12 -8
  32. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/tmc_220x.py +6 -8
  33. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/tmc_2240.py +15 -15
  34. pytmcstepper-0.9.1/src/tmc_driver/tmc_gpio/__init__.py +81 -0
  35. pytmcstepper-0.9.1/src/tmc_driver/tmc_gpio/_tmc_gpio_board_base.py +92 -0
  36. pytmcstepper-0.9.1/src/tmc_driver/tmc_gpio/_tmc_gpio_board_ftdi.py +148 -0
  37. pytmcstepper-0.9.1/src/tmc_driver/tmc_gpio/_tmc_gpio_board_gpiozero.py +94 -0
  38. pytmcstepper-0.9.1/src/tmc_driver/tmc_gpio/_tmc_gpio_board_micropython.py +108 -0
  39. pytmcstepper-0.9.1/src/tmc_driver/tmc_gpio/_tmc_gpio_board_periphery.py +73 -0
  40. pytmcstepper-0.9.1/src/tmc_driver/tmc_gpio/_tmc_gpio_board_rpi_gpio.py +153 -0
  41. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc_com_spi.py +1 -2
  42. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc_com_uart.py +1 -2
  43. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc_math.py +7 -0
  44. pytmcstepper-0.8.0/pyproject.toml +0 -6
  45. pytmcstepper-0.8.0/setup.cfg +0 -47
  46. pytmcstepper-0.8.0/src/tmc_driver/_tmc_gpio_board.py +0 -542
  47. pytmcstepper-0.8.0/src/tmc_driver/_tmc_logger.py +0 -179
  48. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/PyTmcStepper.egg-info/dependency_links.txt +0 -0
  49. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/PyTmcStepper.egg-info/requires.txt +0 -0
  50. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/PyTmcStepper.egg-info/top_level.txt +0 -0
  51. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/__init__.py +0 -0
  52. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/_tmc_exceptions.py +0 -0
  53. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/com/__init__.py +0 -0
  54. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/enable_control/__init__.py +0 -0
  55. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/motion_control/__init__.py +0 -0
  56. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/reg/__init__.py +0 -0
  57. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/reg/_tmc2209_reg.py +0 -0
  58. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/src/tmc_driver/tmc_2208.py +0 -0
  59. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc2209.py +0 -0
  60. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc2240.py +0 -0
  61. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc_ec_pin.py +0 -0
  62. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc_modules.py +0 -0
  63. {pytmcstepper-0.8.0 → pytmcstepper-0.9.1}/tests/test_tmc_move.py +0 -0
@@ -2,10 +2,11 @@ Copyright (C) 2010-2018 Mike McCauley
2
2
  Copyright (c) 2020 troxel
3
3
  Copyright (c) 2014 The Python Packaging Authority (PyPA)
4
4
  Copyright (c) 2014 Mapbox
5
-
6
-
7
-
8
-
5
+ Copyright (c) 2013, 2014 micropython-lib contributors
6
+
7
+
8
+
9
+
9
10
  GNU GENERAL PUBLIC LICENSE
10
11
  Version 3, 29 June 2007
11
12
 
@@ -1,19 +1,18 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: PyTmcStepper
3
- Version: 0.8.0
3
+ Version: 0.9.1
4
4
  Summary: This is a Python libary to drive a stepper motor with a Trinamic stepper driver and a single board computer like a Raspberry Pi
5
- Home-page: https://github.com/Chr157i4n/PyTmcStepper
6
- Author: Christian Köhlke
7
- Author-email: christian@koehlke.de
5
+ Author-email: Christian Köhlke <christian@koehlke.de>
6
+ License-Expression: GPL-3.0
7
+ Project-URL: Homepage, https://github.com/Chr157i4n/PyTmcStepper
8
8
  Project-URL: Bug Tracker, https://github.com/Chr157i4n/PyTmcStepper/issues
9
9
  Classifier: Programming Language :: Python :: 3
10
- Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
11
10
  Classifier: Operating System :: POSIX :: Linux
12
11
  Classifier: Development Status :: 4 - Beta
13
12
  Classifier: Intended Audience :: Developers
14
13
  Classifier: Natural Language :: English
15
14
  Classifier: Topic :: System :: Hardware :: Hardware Drivers
16
- Requires-Python: >=3.7
15
+ Requires-Python: >=3.10
17
16
  Description-Content-Type: text/markdown
18
17
  License-File: LICENSE
19
18
  Requires-Dist: pyserial
@@ -99,6 +98,7 @@ Jetson.GPIO | NVIDIA_JETSON | Nvidia Jetson
99
98
  pheriphery | LUCKFOX_PICO | Luckfox Pico
100
99
  OPi.GPIO | ORANGE_PI | Orange Pi
101
100
  pyftdi | - | Windows/Linux
101
+ machine | - | Pico, Pico2, ESP32, etc.
102
102
 
103
103
  Those libraries are needed for this library to work. You can either install the correct library yourself.
104
104
  You can also install the needed GPIO library by specifing the Installation Parameter while installing this library:
@@ -126,21 +126,21 @@ is split into their own classes to be able to support the diverse methods.
126
126
 
127
127
  The EnableControl module controls the motor current output. It has a function `set_motor_enabled` with one boolean parameter. This function is used to enable or disable the Motor current output.
128
128
 
129
- EnableControl | Class | Driver | Notes
130
- -- | -- | -- | --
129
+ EnableControl | Class | Driver | Notes
130
+ -- | -- | -- | --
131
131
  Pin | [TmcEnableControlPin](src/tmc_driver/enable_control/_tmc_ec_pin.py) | all | the EN Pin of the Driver needs to be connected to a GPIO of the Pi
132
- TOff | [TmcEnableControlToff](src/tmc_driver/enable_control/_tmc_ec_toff.py) | all | the EN Pin needs to be connected to GND.<br />On the TMC2209 this enables current Output on Startup!<br />On the TMC2240 this works fine, because TOff is per default 0 (off).
132
+ TOff | [TmcEnableControlToff](src/tmc_driver/enable_control/_tmc_ec_toff.py) | all | the EN Pin needs to be connected to GND.<br />On the TMC2209 this enables current Output on Startup!<br />On the TMC2240 this works fine, because TOff is per default 0 (off).
133
133
 
134
134
  ### MotionControl
135
135
 
136
136
  The MotionControl module controls the motion of the motor. Before a movement the motor current output needs to be enabled by the [EnableControl](#enablecontrol) module.
137
137
 
138
- MotionControl | Class | Driver | Notes
139
- -- | -- | -- | --
140
- STEP/DIR | [TmcMotionControlStepDir](src/tmc_driver/motion_control/_tmc_mc_step_dir.py) | all | the STEP and DIR pin of the driver must each be connected to a GPIO of the Pi
141
- STEP/REG | [TmcMotionControlStepReg](src/tmc_driver/motion_control/_tmc_mc_step_reg.py) | all | only the STEP pin needs to be connected to a GPIO of the Pi.<br />The direction is controlled via the Register.
142
- VACTUAL | [TmcMotionControlVActual](src/tmc_driver/motion_control/_tmc_mc_vactual.py) | TMC220x | the Direction and Speed is controlled via Register. But VActual does only allow setting a speed and therefore cannot control positioning of the Motor.
143
- STEP_PWM/DIR | [TmcMotionControlStepPwmDir](src/tmc_driver/motion_control/_tmc_mc_step_pwm_dir.py) | all | In contrast to STEP/DIR, the step pin is controlled by PWM. This reduces the load on the CPU, but does not allow precise positioning (similar to the VACTUAL).<br />STEP must be connected to a PWM-capable pin for this purpose
138
+ MotionControl | Class | Driver | Notes
139
+ -- | -- | -- | --
140
+ STEP/DIR | [TmcMotionControlStepDir](src/tmc_driver/motion_control/_tmc_mc_step_dir.py) | all | the STEP and DIR pin of the driver must each be connected to a GPIO of the Pi
141
+ STEP/REG | [TmcMotionControlStepReg](src/tmc_driver/motion_control/_tmc_mc_step_reg.py) | all | only the STEP pin needs to be connected to a GPIO of the Pi.<br />The direction is controlled via the Register.
142
+ VACTUAL | [TmcMotionControlVActual](src/tmc_driver/motion_control/_tmc_mc_vactual.py) | TMC220x | the Direction and Speed is controlled via Register. But VActual does only allow setting a speed and therefore cannot control positioning of the Motor.
143
+ STEP_PWM/DIR | [TmcMotionControlStepPwmDir](src/tmc_driver/motion_control/_tmc_mc_step_pwm_dir.py) | all | In contrast to STEP/DIR, the step pin is controlled by PWM. This reduces the load on the CPU, but does not allow precise positioning (similar to the VACTUAL).<br />STEP must be connected to a PWM-capable pin for this purpose
144
144
 
145
145
  Further methods of controlling the motion of a motor could be:
146
146
 
@@ -150,10 +150,10 @@ Further methods of controlling the motion of a motor could be:
150
150
 
151
151
  ### Com
152
152
 
153
- Com | Class | Driver | Notes
154
- -- | -- | -- | --
155
- UART | [TmcComUart](src/tmc_driver/com/_tmc_com_uart.py) | all | Communication via UART (RX, TX). See [Wiring](#uart)<br />[pyserial](https://pypi.org/project/pyserial) needs to be installed
156
- SPI | [TmcComSpi](src/tmc_driver/com/_tmc_com_spi.py) | TMC2240 | Communication via SPI (MOSI, MISO, CLK, CS). See [Wiring](#spi)<br />[spidev](https://pypi.org/project/spidev) needs to be installed
153
+ Com | Class | Driver | Notes
154
+ -- | -- | -- | --
155
+ UART | [TmcComUart](src/tmc_driver/com/_tmc_com_uart.py) | all | Communication via UART (RX, TX). See [Wiring](#uart)<br />[pyserial](https://pypi.org/project/pyserial) needs to be installed
156
+ SPI | [TmcComSpi](src/tmc_driver/com/_tmc_com_spi.py) | TMC2240 | Communication via SPI (MOSI, MISO, CLK, CS). See [Wiring](#spi)<br />[spidev](https://pypi.org/project/spidev) needs to be installed
157
157
  SPI over FT232H | [TmcComSpiFtdi](src/tmc_driver/com/_tmc_com_spi_ftdi.py) | TMC2240 | Communication via SPI using a FT232H. This can be used on any OS.<br />[pyftdi](https://pypi.org/project/pyftdi) needs to be installed
158
158
 
159
159
  ## Wiring
@@ -251,6 +251,21 @@ For me these baudrates worked fine: 19200, 38400, 57600, 115200, 230400, 460800,
251
251
  If the TMC2209 driver is connected to the Vmotor, the internal voltage regulator will create the Vio for the chip.
252
252
  So you don't need to connect anything to the Vio pin of the driver.
253
253
 
254
+ ### Micropython
255
+
256
+ The lib is also compatible with MicroPython. For using it with Micropython the VSCode addon [MicroPico](https://marketplace.visualstudio.com/items?itemName=paulober.pico-w-go) is used. Use the Upload Project function to upload the src folder and the needed lib folder.
257
+
258
+ the needed libs, which are not builtin in Micropython are:
259
+
260
+ Lib | available on MIP
261
+ -- | --
262
+ abc | yes
263
+ enum | no
264
+ threading | yes
265
+ types | yes
266
+
267
+ You can also use MicroPico to run the demo script by opening one and then pressing Run on the bottom left corner
268
+
254
269
  ## Usage
255
270
 
256
271
  The library currently uses functions to access the TMC registers, but Python properties for internal getters/setters.
@@ -285,15 +300,15 @@ If you encounter any problems, feel free to open an issue (ENG/GER).
285
300
  Please don't send any E-Mails to me. Pls use Github, so that i don't need to answer the same question multiple times.
286
301
  I reserve the right not to answer E-Mails.
287
302
 
288
- Problem | Solution
289
- -- | --
290
- FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial0' | depending on your Raspberry Pi version, you need to enable the Serial Port <br /> run `sudo raspi-config` in your terminal. <br /> there go to '3 Interface Options' -> 'P3 Serial Port' <br /> Would you like a login shell to be accessible over serial? No <br /> Would you like the serial port hardware to be enabled? Yes <br /> Finish and then reboot
291
- PermissionError: [Errno 13] <br /> Permission denied: '/dev/serial0' | you need to give the permission to acces the Serial Port to your current user <br /> You may need to add your user (pi) to the dialout group with `sudo usermod -a -G dialout pi` and then relog. <br /> If that does not work, make sure that your user has read/write permissions on the dev file `/dev/serial0` by calling `sudo chmod 660 /dev/serial0`.
292
- "TMC2209: UART Communication Error" | You can use the 'debug_script_01_uart_connection' script to get a better reading on the received bytes and troubleshoot your problem
293
- "TMC2209: UART Communication Error: 0 data bytes \| 4 total bytes" | only 4 total bytes received indicates, that the Raspberry Pi receives its own data, but nothing from the TMC driver. This happens if RX and TX are connected properly, but the TMC driver has no power
294
- "TMC2209: UART Communication Error: 0 data bytes \| 0 total bytes" | 0 total bytes received indicates, a problem with your wiring or your Raspberry Pi. This happens if TX is not connected
295
- "TMC2209: UART Communication Error: 4 data bytes \| 12 total bytes" | this indicates, the Raspberry Pi received only zeroes. This happens if only RX is connected and TX not
296
- "the Raspberry Pi received only the sended bits" or<br /> inconsistent received bits | Make sure the UART ist properly connected to the TMC driver and the driver is powered and working. <br /> Make sure login shell (console) over serial is disabled.
303
+ Problem | Solution
304
+ -- | --
305
+ FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial0' | depending on your Raspberry Pi version, you need to enable the Serial Port <br /> run `sudo raspi-config` in your terminal. <br /> there go to '3 Interface Options' -> 'P3 Serial Port' <br /> Would you like a login shell to be accessible over serial? No <br /> Would you like the serial port hardware to be enabled? Yes <br /> Finish and then reboot
306
+ PermissionError: [Errno 13] <br /> Permission denied: '/dev/serial0' | you need to give the permission to acces the Serial Port to your current user <br /> You may need to add your user (pi) to the dialout group with `sudo usermod -a -G dialout pi` and then relog. <br /> If that does not work, make sure that your user has read/write permissions on the dev file `/dev/serial0` by calling `sudo chmod 660 /dev/serial0`.
307
+ "TMC2209: UART Communication Error" | You can use the 'debug_script_01_uart_connection' script to get a better reading on the received bytes and troubleshoot your problem
308
+ "TMC2209: UART Communication Error: 0 data bytes \| 4 total bytes" | only 4 total bytes received indicates, that the Raspberry Pi receives its own data, but nothing from the TMC driver. This happens if RX and TX are connected properly, but the TMC driver has no power
309
+ "TMC2209: UART Communication Error: 0 data bytes \| 0 total bytes" | 0 total bytes received indicates, a problem with your wiring or your Raspberry Pi. This happens if TX is not connected
310
+ "TMC2209: UART Communication Error: 4 data bytes \| 12 total bytes" | this indicates, the Raspberry Pi received only zeroes. This happens if only RX is connected and TX not
311
+ "the Raspberry Pi received only the sended bits" or<br /> inconsistent received bits | Make sure the UART ist properly connected to the TMC driver and the driver is powered and working. <br /> Make sure login shell (console) over serial is disabled.
297
312
 
298
313
  ![wiring photo](docs/images/wiring_photo.jpg)
299
314
 
@@ -303,6 +318,8 @@ The code to run the stepper motor is based on the code of the [AccelStepper Libr
303
318
 
304
319
  The code for the UART communication is based on this [code from troxel](https://github.com/troxel/TMC_UART).
305
320
 
321
+ For the implementation of Python-stdlib for micropython [micropython-lib](https://github.com/micropython/micropython-lib)
322
+
306
323
  My goal is to make a library, that can run a stepper motor with a TMC2209 stepper driver and can write the setting in the register of the TMC2209, entirely in Python.
307
324
  The main focus for this are Test setups, as Python is not fast enough for high motor speeds.
308
325
 
@@ -68,6 +68,7 @@ Jetson.GPIO | NVIDIA_JETSON | Nvidia Jetson
68
68
  pheriphery | LUCKFOX_PICO | Luckfox Pico
69
69
  OPi.GPIO | ORANGE_PI | Orange Pi
70
70
  pyftdi | - | Windows/Linux
71
+ machine | - | Pico, Pico2, ESP32, etc.
71
72
 
72
73
  Those libraries are needed for this library to work. You can either install the correct library yourself.
73
74
  You can also install the needed GPIO library by specifing the Installation Parameter while installing this library:
@@ -95,21 +96,21 @@ is split into their own classes to be able to support the diverse methods.
95
96
 
96
97
  The EnableControl module controls the motor current output. It has a function `set_motor_enabled` with one boolean parameter. This function is used to enable or disable the Motor current output.
97
98
 
98
- EnableControl | Class | Driver | Notes
99
- -- | -- | -- | --
99
+ EnableControl | Class | Driver | Notes
100
+ -- | -- | -- | --
100
101
  Pin | [TmcEnableControlPin](src/tmc_driver/enable_control/_tmc_ec_pin.py) | all | the EN Pin of the Driver needs to be connected to a GPIO of the Pi
101
- TOff | [TmcEnableControlToff](src/tmc_driver/enable_control/_tmc_ec_toff.py) | all | the EN Pin needs to be connected to GND.<br />On the TMC2209 this enables current Output on Startup!<br />On the TMC2240 this works fine, because TOff is per default 0 (off).
102
+ TOff | [TmcEnableControlToff](src/tmc_driver/enable_control/_tmc_ec_toff.py) | all | the EN Pin needs to be connected to GND.<br />On the TMC2209 this enables current Output on Startup!<br />On the TMC2240 this works fine, because TOff is per default 0 (off).
102
103
 
103
104
  ### MotionControl
104
105
 
105
106
  The MotionControl module controls the motion of the motor. Before a movement the motor current output needs to be enabled by the [EnableControl](#enablecontrol) module.
106
107
 
107
- MotionControl | Class | Driver | Notes
108
- -- | -- | -- | --
109
- STEP/DIR | [TmcMotionControlStepDir](src/tmc_driver/motion_control/_tmc_mc_step_dir.py) | all | the STEP and DIR pin of the driver must each be connected to a GPIO of the Pi
110
- STEP/REG | [TmcMotionControlStepReg](src/tmc_driver/motion_control/_tmc_mc_step_reg.py) | all | only the STEP pin needs to be connected to a GPIO of the Pi.<br />The direction is controlled via the Register.
111
- VACTUAL | [TmcMotionControlVActual](src/tmc_driver/motion_control/_tmc_mc_vactual.py) | TMC220x | the Direction and Speed is controlled via Register. But VActual does only allow setting a speed and therefore cannot control positioning of the Motor.
112
- STEP_PWM/DIR | [TmcMotionControlStepPwmDir](src/tmc_driver/motion_control/_tmc_mc_step_pwm_dir.py) | all | In contrast to STEP/DIR, the step pin is controlled by PWM. This reduces the load on the CPU, but does not allow precise positioning (similar to the VACTUAL).<br />STEP must be connected to a PWM-capable pin for this purpose
108
+ MotionControl | Class | Driver | Notes
109
+ -- | -- | -- | --
110
+ STEP/DIR | [TmcMotionControlStepDir](src/tmc_driver/motion_control/_tmc_mc_step_dir.py) | all | the STEP and DIR pin of the driver must each be connected to a GPIO of the Pi
111
+ STEP/REG | [TmcMotionControlStepReg](src/tmc_driver/motion_control/_tmc_mc_step_reg.py) | all | only the STEP pin needs to be connected to a GPIO of the Pi.<br />The direction is controlled via the Register.
112
+ VACTUAL | [TmcMotionControlVActual](src/tmc_driver/motion_control/_tmc_mc_vactual.py) | TMC220x | the Direction and Speed is controlled via Register. But VActual does only allow setting a speed and therefore cannot control positioning of the Motor.
113
+ STEP_PWM/DIR | [TmcMotionControlStepPwmDir](src/tmc_driver/motion_control/_tmc_mc_step_pwm_dir.py) | all | In contrast to STEP/DIR, the step pin is controlled by PWM. This reduces the load on the CPU, but does not allow precise positioning (similar to the VACTUAL).<br />STEP must be connected to a PWM-capable pin for this purpose
113
114
 
114
115
  Further methods of controlling the motion of a motor could be:
115
116
 
@@ -119,10 +120,10 @@ Further methods of controlling the motion of a motor could be:
119
120
 
120
121
  ### Com
121
122
 
122
- Com | Class | Driver | Notes
123
- -- | -- | -- | --
124
- UART | [TmcComUart](src/tmc_driver/com/_tmc_com_uart.py) | all | Communication via UART (RX, TX). See [Wiring](#uart)<br />[pyserial](https://pypi.org/project/pyserial) needs to be installed
125
- SPI | [TmcComSpi](src/tmc_driver/com/_tmc_com_spi.py) | TMC2240 | Communication via SPI (MOSI, MISO, CLK, CS). See [Wiring](#spi)<br />[spidev](https://pypi.org/project/spidev) needs to be installed
123
+ Com | Class | Driver | Notes
124
+ -- | -- | -- | --
125
+ UART | [TmcComUart](src/tmc_driver/com/_tmc_com_uart.py) | all | Communication via UART (RX, TX). See [Wiring](#uart)<br />[pyserial](https://pypi.org/project/pyserial) needs to be installed
126
+ SPI | [TmcComSpi](src/tmc_driver/com/_tmc_com_spi.py) | TMC2240 | Communication via SPI (MOSI, MISO, CLK, CS). See [Wiring](#spi)<br />[spidev](https://pypi.org/project/spidev) needs to be installed
126
127
  SPI over FT232H | [TmcComSpiFtdi](src/tmc_driver/com/_tmc_com_spi_ftdi.py) | TMC2240 | Communication via SPI using a FT232H. This can be used on any OS.<br />[pyftdi](https://pypi.org/project/pyftdi) needs to be installed
127
128
 
128
129
  ## Wiring
@@ -220,6 +221,21 @@ For me these baudrates worked fine: 19200, 38400, 57600, 115200, 230400, 460800,
220
221
  If the TMC2209 driver is connected to the Vmotor, the internal voltage regulator will create the Vio for the chip.
221
222
  So you don't need to connect anything to the Vio pin of the driver.
222
223
 
224
+ ### Micropython
225
+
226
+ The lib is also compatible with MicroPython. For using it with Micropython the VSCode addon [MicroPico](https://marketplace.visualstudio.com/items?itemName=paulober.pico-w-go) is used. Use the Upload Project function to upload the src folder and the needed lib folder.
227
+
228
+ the needed libs, which are not builtin in Micropython are:
229
+
230
+ Lib | available on MIP
231
+ -- | --
232
+ abc | yes
233
+ enum | no
234
+ threading | yes
235
+ types | yes
236
+
237
+ You can also use MicroPico to run the demo script by opening one and then pressing Run on the bottom left corner
238
+
223
239
  ## Usage
224
240
 
225
241
  The library currently uses functions to access the TMC registers, but Python properties for internal getters/setters.
@@ -254,15 +270,15 @@ If you encounter any problems, feel free to open an issue (ENG/GER).
254
270
  Please don't send any E-Mails to me. Pls use Github, so that i don't need to answer the same question multiple times.
255
271
  I reserve the right not to answer E-Mails.
256
272
 
257
- Problem | Solution
258
- -- | --
259
- FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial0' | depending on your Raspberry Pi version, you need to enable the Serial Port <br /> run `sudo raspi-config` in your terminal. <br /> there go to '3 Interface Options' -> 'P3 Serial Port' <br /> Would you like a login shell to be accessible over serial? No <br /> Would you like the serial port hardware to be enabled? Yes <br /> Finish and then reboot
260
- PermissionError: [Errno 13] <br /> Permission denied: '/dev/serial0' | you need to give the permission to acces the Serial Port to your current user <br /> You may need to add your user (pi) to the dialout group with `sudo usermod -a -G dialout pi` and then relog. <br /> If that does not work, make sure that your user has read/write permissions on the dev file `/dev/serial0` by calling `sudo chmod 660 /dev/serial0`.
261
- "TMC2209: UART Communication Error" | You can use the 'debug_script_01_uart_connection' script to get a better reading on the received bytes and troubleshoot your problem
262
- "TMC2209: UART Communication Error: 0 data bytes \| 4 total bytes" | only 4 total bytes received indicates, that the Raspberry Pi receives its own data, but nothing from the TMC driver. This happens if RX and TX are connected properly, but the TMC driver has no power
263
- "TMC2209: UART Communication Error: 0 data bytes \| 0 total bytes" | 0 total bytes received indicates, a problem with your wiring or your Raspberry Pi. This happens if TX is not connected
264
- "TMC2209: UART Communication Error: 4 data bytes \| 12 total bytes" | this indicates, the Raspberry Pi received only zeroes. This happens if only RX is connected and TX not
265
- "the Raspberry Pi received only the sended bits" or<br /> inconsistent received bits | Make sure the UART ist properly connected to the TMC driver and the driver is powered and working. <br /> Make sure login shell (console) over serial is disabled.
273
+ Problem | Solution
274
+ -- | --
275
+ FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial0' | depending on your Raspberry Pi version, you need to enable the Serial Port <br /> run `sudo raspi-config` in your terminal. <br /> there go to '3 Interface Options' -> 'P3 Serial Port' <br /> Would you like a login shell to be accessible over serial? No <br /> Would you like the serial port hardware to be enabled? Yes <br /> Finish and then reboot
276
+ PermissionError: [Errno 13] <br /> Permission denied: '/dev/serial0' | you need to give the permission to acces the Serial Port to your current user <br /> You may need to add your user (pi) to the dialout group with `sudo usermod -a -G dialout pi` and then relog. <br /> If that does not work, make sure that your user has read/write permissions on the dev file `/dev/serial0` by calling `sudo chmod 660 /dev/serial0`.
277
+ "TMC2209: UART Communication Error" | You can use the 'debug_script_01_uart_connection' script to get a better reading on the received bytes and troubleshoot your problem
278
+ "TMC2209: UART Communication Error: 0 data bytes \| 4 total bytes" | only 4 total bytes received indicates, that the Raspberry Pi receives its own data, but nothing from the TMC driver. This happens if RX and TX are connected properly, but the TMC driver has no power
279
+ "TMC2209: UART Communication Error: 0 data bytes \| 0 total bytes" | 0 total bytes received indicates, a problem with your wiring or your Raspberry Pi. This happens if TX is not connected
280
+ "TMC2209: UART Communication Error: 4 data bytes \| 12 total bytes" | this indicates, the Raspberry Pi received only zeroes. This happens if only RX is connected and TX not
281
+ "the Raspberry Pi received only the sended bits" or<br /> inconsistent received bits | Make sure the UART ist properly connected to the TMC driver and the driver is powered and working. <br /> Make sure login shell (console) over serial is disabled.
266
282
 
267
283
  ![wiring photo](docs/images/wiring_photo.jpg)
268
284
 
@@ -272,6 +288,8 @@ The code to run the stepper motor is based on the code of the [AccelStepper Libr
272
288
 
273
289
  The code for the UART communication is based on this [code from troxel](https://github.com/troxel/TMC_UART).
274
290
 
291
+ For the implementation of Python-stdlib for micropython [micropython-lib](https://github.com/micropython/micropython-lib)
292
+
275
293
  My goal is to make a library, that can run a stepper motor with a TMC2209 stepper driver and can write the setting in the register of the TMC2209, entirely in Python.
276
294
  The main focus for this are Test setups, as Python is not fast enough for high motor speeds.
277
295
 
@@ -0,0 +1,52 @@
1
+ [build-system]
2
+ requires = [
3
+ "setuptools>=42",
4
+ "wheel"
5
+ ]
6
+ build-backend = "setuptools.build_meta"
7
+
8
+ [project]
9
+ name = "PyTmcStepper"
10
+ version = "0.9.1"
11
+ authors = [
12
+ { name = "Christian Köhlke", email = "christian@koehlke.de" }
13
+ ]
14
+ description = "This is a Python libary to drive a stepper motor with a Trinamic stepper driver and a single board computer like a Raspberry Pi"
15
+ readme = "README.md"
16
+ license = "GPL-3.0"
17
+ requires-python = ">=3.10"
18
+ classifiers = [
19
+ "Programming Language :: Python :: 3",
20
+ "Operating System :: POSIX :: Linux",
21
+ "Development Status :: 4 - Beta",
22
+ "Intended Audience :: Developers",
23
+ "Natural Language :: English",
24
+ "Topic :: System :: Hardware :: Hardware Drivers",
25
+ ]
26
+ dependencies = [
27
+ "pyserial",
28
+ ]
29
+
30
+ [project.urls]
31
+ Homepage = "https://github.com/Chr157i4n/PyTmcStepper"
32
+ "Bug Tracker" = "https://github.com/Chr157i4n/PyTmcStepper/issues"
33
+
34
+ [project.optional-dependencies]
35
+ RASPBERRY_PI = ["RPi.GPIO"]
36
+ RASPBERRY_PI5 = ["gpiozero"]
37
+ NVIDIA_JETSON = ["Jetson.GPIO"]
38
+ LUCKFOX_PICO = ["python-periphery"]
39
+ ORANGE_PI = ["OPi.GPIO"]
40
+
41
+ [tool.setuptools.packages.find]
42
+ where = ["src"]
43
+
44
+ [tool.pylint."messages control"]
45
+ disable = "C0103,W0511,W0012,R0801"
46
+
47
+ [tool.pylint.main]
48
+ ignored-modules = "machine"
49
+ unsafe-load-any-extension = true
50
+
51
+ [tool.pylint.format]
52
+ max-line-length = 160
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
@@ -1,19 +1,18 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: PyTmcStepper
3
- Version: 0.8.0
3
+ Version: 0.9.1
4
4
  Summary: This is a Python libary to drive a stepper motor with a Trinamic stepper driver and a single board computer like a Raspberry Pi
5
- Home-page: https://github.com/Chr157i4n/PyTmcStepper
6
- Author: Christian Köhlke
7
- Author-email: christian@koehlke.de
5
+ Author-email: Christian Köhlke <christian@koehlke.de>
6
+ License-Expression: GPL-3.0
7
+ Project-URL: Homepage, https://github.com/Chr157i4n/PyTmcStepper
8
8
  Project-URL: Bug Tracker, https://github.com/Chr157i4n/PyTmcStepper/issues
9
9
  Classifier: Programming Language :: Python :: 3
10
- Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
11
10
  Classifier: Operating System :: POSIX :: Linux
12
11
  Classifier: Development Status :: 4 - Beta
13
12
  Classifier: Intended Audience :: Developers
14
13
  Classifier: Natural Language :: English
15
14
  Classifier: Topic :: System :: Hardware :: Hardware Drivers
16
- Requires-Python: >=3.7
15
+ Requires-Python: >=3.10
17
16
  Description-Content-Type: text/markdown
18
17
  License-File: LICENSE
19
18
  Requires-Dist: pyserial
@@ -99,6 +98,7 @@ Jetson.GPIO | NVIDIA_JETSON | Nvidia Jetson
99
98
  pheriphery | LUCKFOX_PICO | Luckfox Pico
100
99
  OPi.GPIO | ORANGE_PI | Orange Pi
101
100
  pyftdi | - | Windows/Linux
101
+ machine | - | Pico, Pico2, ESP32, etc.
102
102
 
103
103
  Those libraries are needed for this library to work. You can either install the correct library yourself.
104
104
  You can also install the needed GPIO library by specifing the Installation Parameter while installing this library:
@@ -126,21 +126,21 @@ is split into their own classes to be able to support the diverse methods.
126
126
 
127
127
  The EnableControl module controls the motor current output. It has a function `set_motor_enabled` with one boolean parameter. This function is used to enable or disable the Motor current output.
128
128
 
129
- EnableControl | Class | Driver | Notes
130
- -- | -- | -- | --
129
+ EnableControl | Class | Driver | Notes
130
+ -- | -- | -- | --
131
131
  Pin | [TmcEnableControlPin](src/tmc_driver/enable_control/_tmc_ec_pin.py) | all | the EN Pin of the Driver needs to be connected to a GPIO of the Pi
132
- TOff | [TmcEnableControlToff](src/tmc_driver/enable_control/_tmc_ec_toff.py) | all | the EN Pin needs to be connected to GND.<br />On the TMC2209 this enables current Output on Startup!<br />On the TMC2240 this works fine, because TOff is per default 0 (off).
132
+ TOff | [TmcEnableControlToff](src/tmc_driver/enable_control/_tmc_ec_toff.py) | all | the EN Pin needs to be connected to GND.<br />On the TMC2209 this enables current Output on Startup!<br />On the TMC2240 this works fine, because TOff is per default 0 (off).
133
133
 
134
134
  ### MotionControl
135
135
 
136
136
  The MotionControl module controls the motion of the motor. Before a movement the motor current output needs to be enabled by the [EnableControl](#enablecontrol) module.
137
137
 
138
- MotionControl | Class | Driver | Notes
139
- -- | -- | -- | --
140
- STEP/DIR | [TmcMotionControlStepDir](src/tmc_driver/motion_control/_tmc_mc_step_dir.py) | all | the STEP and DIR pin of the driver must each be connected to a GPIO of the Pi
141
- STEP/REG | [TmcMotionControlStepReg](src/tmc_driver/motion_control/_tmc_mc_step_reg.py) | all | only the STEP pin needs to be connected to a GPIO of the Pi.<br />The direction is controlled via the Register.
142
- VACTUAL | [TmcMotionControlVActual](src/tmc_driver/motion_control/_tmc_mc_vactual.py) | TMC220x | the Direction and Speed is controlled via Register. But VActual does only allow setting a speed and therefore cannot control positioning of the Motor.
143
- STEP_PWM/DIR | [TmcMotionControlStepPwmDir](src/tmc_driver/motion_control/_tmc_mc_step_pwm_dir.py) | all | In contrast to STEP/DIR, the step pin is controlled by PWM. This reduces the load on the CPU, but does not allow precise positioning (similar to the VACTUAL).<br />STEP must be connected to a PWM-capable pin for this purpose
138
+ MotionControl | Class | Driver | Notes
139
+ -- | -- | -- | --
140
+ STEP/DIR | [TmcMotionControlStepDir](src/tmc_driver/motion_control/_tmc_mc_step_dir.py) | all | the STEP and DIR pin of the driver must each be connected to a GPIO of the Pi
141
+ STEP/REG | [TmcMotionControlStepReg](src/tmc_driver/motion_control/_tmc_mc_step_reg.py) | all | only the STEP pin needs to be connected to a GPIO of the Pi.<br />The direction is controlled via the Register.
142
+ VACTUAL | [TmcMotionControlVActual](src/tmc_driver/motion_control/_tmc_mc_vactual.py) | TMC220x | the Direction and Speed is controlled via Register. But VActual does only allow setting a speed and therefore cannot control positioning of the Motor.
143
+ STEP_PWM/DIR | [TmcMotionControlStepPwmDir](src/tmc_driver/motion_control/_tmc_mc_step_pwm_dir.py) | all | In contrast to STEP/DIR, the step pin is controlled by PWM. This reduces the load on the CPU, but does not allow precise positioning (similar to the VACTUAL).<br />STEP must be connected to a PWM-capable pin for this purpose
144
144
 
145
145
  Further methods of controlling the motion of a motor could be:
146
146
 
@@ -150,10 +150,10 @@ Further methods of controlling the motion of a motor could be:
150
150
 
151
151
  ### Com
152
152
 
153
- Com | Class | Driver | Notes
154
- -- | -- | -- | --
155
- UART | [TmcComUart](src/tmc_driver/com/_tmc_com_uart.py) | all | Communication via UART (RX, TX). See [Wiring](#uart)<br />[pyserial](https://pypi.org/project/pyserial) needs to be installed
156
- SPI | [TmcComSpi](src/tmc_driver/com/_tmc_com_spi.py) | TMC2240 | Communication via SPI (MOSI, MISO, CLK, CS). See [Wiring](#spi)<br />[spidev](https://pypi.org/project/spidev) needs to be installed
153
+ Com | Class | Driver | Notes
154
+ -- | -- | -- | --
155
+ UART | [TmcComUart](src/tmc_driver/com/_tmc_com_uart.py) | all | Communication via UART (RX, TX). See [Wiring](#uart)<br />[pyserial](https://pypi.org/project/pyserial) needs to be installed
156
+ SPI | [TmcComSpi](src/tmc_driver/com/_tmc_com_spi.py) | TMC2240 | Communication via SPI (MOSI, MISO, CLK, CS). See [Wiring](#spi)<br />[spidev](https://pypi.org/project/spidev) needs to be installed
157
157
  SPI over FT232H | [TmcComSpiFtdi](src/tmc_driver/com/_tmc_com_spi_ftdi.py) | TMC2240 | Communication via SPI using a FT232H. This can be used on any OS.<br />[pyftdi](https://pypi.org/project/pyftdi) needs to be installed
158
158
 
159
159
  ## Wiring
@@ -251,6 +251,21 @@ For me these baudrates worked fine: 19200, 38400, 57600, 115200, 230400, 460800,
251
251
  If the TMC2209 driver is connected to the Vmotor, the internal voltage regulator will create the Vio for the chip.
252
252
  So you don't need to connect anything to the Vio pin of the driver.
253
253
 
254
+ ### Micropython
255
+
256
+ The lib is also compatible with MicroPython. For using it with Micropython the VSCode addon [MicroPico](https://marketplace.visualstudio.com/items?itemName=paulober.pico-w-go) is used. Use the Upload Project function to upload the src folder and the needed lib folder.
257
+
258
+ the needed libs, which are not builtin in Micropython are:
259
+
260
+ Lib | available on MIP
261
+ -- | --
262
+ abc | yes
263
+ enum | no
264
+ threading | yes
265
+ types | yes
266
+
267
+ You can also use MicroPico to run the demo script by opening one and then pressing Run on the bottom left corner
268
+
254
269
  ## Usage
255
270
 
256
271
  The library currently uses functions to access the TMC registers, but Python properties for internal getters/setters.
@@ -285,15 +300,15 @@ If you encounter any problems, feel free to open an issue (ENG/GER).
285
300
  Please don't send any E-Mails to me. Pls use Github, so that i don't need to answer the same question multiple times.
286
301
  I reserve the right not to answer E-Mails.
287
302
 
288
- Problem | Solution
289
- -- | --
290
- FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial0' | depending on your Raspberry Pi version, you need to enable the Serial Port <br /> run `sudo raspi-config` in your terminal. <br /> there go to '3 Interface Options' -> 'P3 Serial Port' <br /> Would you like a login shell to be accessible over serial? No <br /> Would you like the serial port hardware to be enabled? Yes <br /> Finish and then reboot
291
- PermissionError: [Errno 13] <br /> Permission denied: '/dev/serial0' | you need to give the permission to acces the Serial Port to your current user <br /> You may need to add your user (pi) to the dialout group with `sudo usermod -a -G dialout pi` and then relog. <br /> If that does not work, make sure that your user has read/write permissions on the dev file `/dev/serial0` by calling `sudo chmod 660 /dev/serial0`.
292
- "TMC2209: UART Communication Error" | You can use the 'debug_script_01_uart_connection' script to get a better reading on the received bytes and troubleshoot your problem
293
- "TMC2209: UART Communication Error: 0 data bytes \| 4 total bytes" | only 4 total bytes received indicates, that the Raspberry Pi receives its own data, but nothing from the TMC driver. This happens if RX and TX are connected properly, but the TMC driver has no power
294
- "TMC2209: UART Communication Error: 0 data bytes \| 0 total bytes" | 0 total bytes received indicates, a problem with your wiring or your Raspberry Pi. This happens if TX is not connected
295
- "TMC2209: UART Communication Error: 4 data bytes \| 12 total bytes" | this indicates, the Raspberry Pi received only zeroes. This happens if only RX is connected and TX not
296
- "the Raspberry Pi received only the sended bits" or<br /> inconsistent received bits | Make sure the UART ist properly connected to the TMC driver and the driver is powered and working. <br /> Make sure login shell (console) over serial is disabled.
303
+ Problem | Solution
304
+ -- | --
305
+ FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial0' | depending on your Raspberry Pi version, you need to enable the Serial Port <br /> run `sudo raspi-config` in your terminal. <br /> there go to '3 Interface Options' -> 'P3 Serial Port' <br /> Would you like a login shell to be accessible over serial? No <br /> Would you like the serial port hardware to be enabled? Yes <br /> Finish and then reboot
306
+ PermissionError: [Errno 13] <br /> Permission denied: '/dev/serial0' | you need to give the permission to acces the Serial Port to your current user <br /> You may need to add your user (pi) to the dialout group with `sudo usermod -a -G dialout pi` and then relog. <br /> If that does not work, make sure that your user has read/write permissions on the dev file `/dev/serial0` by calling `sudo chmod 660 /dev/serial0`.
307
+ "TMC2209: UART Communication Error" | You can use the 'debug_script_01_uart_connection' script to get a better reading on the received bytes and troubleshoot your problem
308
+ "TMC2209: UART Communication Error: 0 data bytes \| 4 total bytes" | only 4 total bytes received indicates, that the Raspberry Pi receives its own data, but nothing from the TMC driver. This happens if RX and TX are connected properly, but the TMC driver has no power
309
+ "TMC2209: UART Communication Error: 0 data bytes \| 0 total bytes" | 0 total bytes received indicates, a problem with your wiring or your Raspberry Pi. This happens if TX is not connected
310
+ "TMC2209: UART Communication Error: 4 data bytes \| 12 total bytes" | this indicates, the Raspberry Pi received only zeroes. This happens if only RX is connected and TX not
311
+ "the Raspberry Pi received only the sended bits" or<br /> inconsistent received bits | Make sure the UART ist properly connected to the TMC driver and the driver is powered and working. <br /> Make sure login shell (console) over serial is disabled.
297
312
 
298
313
  ![wiring photo](docs/images/wiring_photo.jpg)
299
314
 
@@ -303,6 +318,8 @@ The code to run the stepper motor is based on the code of the [AccelStepper Libr
303
318
 
304
319
  The code for the UART communication is based on this [code from troxel](https://github.com/troxel/TMC_UART).
305
320
 
321
+ For the implementation of Python-stdlib for micropython [micropython-lib](https://github.com/micropython/micropython-lib)
322
+
306
323
  My goal is to make a library, that can run a stepper motor with a TMC2209 stepper driver and can write the setting in the register of the TMC2209, entirely in Python.
307
324
  The main focus for this are Test setups, as Python is not fast enough for high motor speeds.
308
325
 
@@ -1,7 +1,6 @@
1
1
  LICENSE
2
2
  README.md
3
3
  pyproject.toml
4
- setup.cfg
5
4
  src/PyTmcStepper.egg-info/PKG-INFO
6
5
  src/PyTmcStepper.egg-info/SOURCES.txt
7
6
  src/PyTmcStepper.egg-info/dependency_links.txt
@@ -9,7 +8,6 @@ src/PyTmcStepper.egg-info/requires.txt
9
8
  src/PyTmcStepper.egg-info/top_level.txt
10
9
  src/tmc_driver/__init__.py
11
10
  src/tmc_driver/_tmc_exceptions.py
12
- src/tmc_driver/_tmc_gpio_board.py
13
11
  src/tmc_driver/_tmc_logger.py
14
12
  src/tmc_driver/_tmc_math.py
15
13
  src/tmc_driver/_tmc_stallguard.py
@@ -23,8 +21,10 @@ src/tmc_driver/com/_tmc_com.py
23
21
  src/tmc_driver/com/_tmc_com_spi.py
24
22
  src/tmc_driver/com/_tmc_com_spi_base.py
25
23
  src/tmc_driver/com/_tmc_com_spi_ftdi.py
24
+ src/tmc_driver/com/_tmc_com_spi_micropython.py
26
25
  src/tmc_driver/com/_tmc_com_uart.py
27
26
  src/tmc_driver/com/_tmc_com_uart_base.py
27
+ src/tmc_driver/com/_tmc_com_uart_micropython.py
28
28
  src/tmc_driver/enable_control/__init__.py
29
29
  src/tmc_driver/enable_control/_tmc_ec.py
30
30
  src/tmc_driver/enable_control/_tmc_ec_pin.py
@@ -40,6 +40,13 @@ src/tmc_driver/reg/_tmc2209_reg.py
40
40
  src/tmc_driver/reg/_tmc220x_reg.py
41
41
  src/tmc_driver/reg/_tmc224x_reg.py
42
42
  src/tmc_driver/reg/_tmc_reg.py
43
+ src/tmc_driver/tmc_gpio/__init__.py
44
+ src/tmc_driver/tmc_gpio/_tmc_gpio_board_base.py
45
+ src/tmc_driver/tmc_gpio/_tmc_gpio_board_ftdi.py
46
+ src/tmc_driver/tmc_gpio/_tmc_gpio_board_gpiozero.py
47
+ src/tmc_driver/tmc_gpio/_tmc_gpio_board_micropython.py
48
+ src/tmc_driver/tmc_gpio/_tmc_gpio_board_periphery.py
49
+ src/tmc_driver/tmc_gpio/_tmc_gpio_board_rpi_gpio.py
43
50
  tests/test_tmc2209.py
44
51
  tests/test_tmc2240.py
45
52
  tests/test_tmc_com_spi.py