misan
commented
4 years ago Hi Star,
The main memory eater is the array to be able to respond to S command. That may come in handy when tuning the PID but it is a big drag. If you make it smaller you can fit the code in the UNO.
Kind regards,
misan
On Wed, Mar 11, 2020 at 8:51 PM Star Holden notifications@github.com wrote:
Hi Miguel
Firstly many thanks for making your code available to the public. Ive made and tested the UNO version and its works really well! Im trying to add your trapezoidal motion profiles to the code on the UNO but cant seem to get it working. When compiling for a 328P it seems to run out of memory, guess thats why your using a 32U4 chip instead on the Pro Micro. Is it possible to get a UNO working with the trapeziodal motion curves or does it have to be the ProMicro or something more powerful?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/misan/dcservo/issues/65, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADRZSEIKA6DGLHXK37UYA3RG7TR3ANCNFSM4LF5NVDA .
Hi Miguel
Firstly many thanks for making your code available to the public. Ive made and tested the UNO version and its works really well! Im trying to add your trapezoidal motion profiles to the code on the UNO but cant seem to get it working. When compiling for a 328P it seems to run out of memory, guess thats why your using a 32U4 chip instead on the Pro Micro. Is it possible to get a UNO working with the trapeziodal motion curves or does it have to be the ProMicro or something more powerful?