Hi everyone! 😀
I need help configuring my setup.
I’m using an MN3110 KV470 motor (https://store.tmotor.com/product/mn3110-motor-navigator-type.html), which I control with a VESC 6 Edu (https://trampa.co.uk/product/vesc6-edu/). I connected a Radiomaster ER6G receiver (https://radiomasterrc.com/products/er6g-er6gv-2-4ghz-elrs-pwm-receiver) to the PPM slot of the VESC, and it communicate to a TX16S transmitter (https://radiomasterrc.com/products/tx16s-mark-ii-radio-controller?_pos=1...).
The control is configured so that the motor rotates within a 180-degree range. When the user moves the stick to one of the extreme positions, the motor also moves to the maximum in the corresponding direction and holds that position as long as the stick remains there. When the stick is released (or the receiver loses signal), the motor should return to the neutral position.
The problem:
The motor doesn’t always return to the neutral position. About 80% of the time it works correctly, but sometimes it stays in the last position or moves incorrectly. Occasionally, after moving the stick again, the motor will return to neutral, but this is obviously not the desired behavior.
Since the motor doesn’t have built-in sensors, I bought an AMT203-V encoder (https://www.mouser.pl/ProductDetail/Same-Sky/AMT203-V?qs=WyjlAZoYn51vfiQ...). I tested it previously with an Arduino Nano, and it worked fine, so I decided to connect it to the VESC. Unfortunately, I’m not sure how to do it properly.
I want to use SPI communication to be able to read the absolute position. In VESC Tool, the encoder doesn’t show any data – encoder detection often fails, and if it does show something, the results are incorrect and the motor starts behaving erratically.
Questions:
-
Do I need to write a special driver for this type of encoder?
-
How should I properly connect the AMT203-V to the VESC?
-
Has anyone used this specific encoder with a VESC and can share their configuration?
I’d be extremely grateful for any help and advice.
I’m quite new to this topic and have been struggling with the issue for over a week.
Draft.png.5289ad329b384468aedb1ae45685a57e.png
