I believe the processor and/or board and/or software (delete as appropriate) needs to be configured, so as to tell it what to use the pins for. I have come to understand that the F446RE, while it has physically a duplication of the Uno pin-out pattern on the board, does not necessarily constrain itself to using these pins in the same way the Uno does. While I do get some sort of signal when I run my code, which has some vague correlation to the motor (the signal changes when I spin the motor by hand), the signal is extremely “noisy” and nothing like I was reading through the Uno. I am attempting to use the same pins I use on the Uno (digital 10-13), which I think it the primary “SPI1” on the Nucleo. In more detail: the first thing which I know is not working correctly with the Nucleo board is the SPI signal (that is to read the AS5147). This was about two weeks ago, and since then I’ve spent about six years (it’s non-linear) pressing buttons, reading forums, downloading softwares and engaging in heated, one-sided debates with everything from “the internet” to my coffee mug, and all to little avail. In my naivety I hoped I could then just make a version of the project where I set the board to the F446RE in the. Whilst a bit of a step up, some serendipitous keyboard mashing was enough for me to get my program recompiled and downloaded (maybe not the right technical terms) onto the Uno from within PlatformIO, and it seems to work just as well as it did when built in the Arduino IDE. At this point, based on various things I’ve read across this forum, I also decided to switch from the Arduion IDE to PlatformIO. Knowing very little about these things, I decided the STM32 nucleo64 boards looked like a popular and capable choice, so I ended up with a nucleo-f446RE. This works great too.Īt this point, I was using 90% of the Uno memory, and since I intend to add at least 1 more motor to get my project working, I decided it was time to switch up to a more capable board. I also added an ADX元45 accelerometer (communicating on I2C), and set that up as a “proportional switch” to set the target torque of the motor. So far things went pretty well - closed loop control in each of torque, position and velocity modes all operate as expected.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |