Editing SPI protocol of VSD-E/XE
| Your changes will be displayed to readers once an authorized user accepts them. (help) |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
[[VSD-E and VSD-XE]] features [https://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus SPI] serial communication bus for parameterization and control. SPI is used by [[GDtool]] to communicate with the drive. | [[VSD-E and VSD-XE]] features [https://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus SPI] serial communication bus for parameterization and control. SPI is used by [[GDtool]] to communicate with the drive. | ||
| − | The actual SPI protocol is largely undocumented, however a sample implementation is available in the [[SimpleMotion | + | The actual SPI protocol is largely undocumented, however a sample implementation is available in the [[SimpleMotion]] V0.x library source codes. By default the SM library supports the FTDI TTL232R USB adapter in bit-bang mode to communicate to the SPI bus. |
The source code has template/skeleton for general purpose [[bit bang]] I/O control to achieve the same functionality also on other devices such as MCUs. | The source code has template/skeleton for general purpose [[bit bang]] I/O control to achieve the same functionality also on other devices such as MCUs. | ||
| − | |||
| − | |||
| − | |||
