You are here

Serial port error when Encoder detection is complete

4 posts / 0 new
Last post
VirtB
Offline
Last seen: 2 years 5 months ago
Joined: 2018-08-27 21:44
Posts: 4
Serial port error when Encoder detection is complete

Hello, 

Newbee 1st time connecting controller to BE8108-100KV motor.

Tool Version 0.95, Firmware 3.40 Hardware 60 Manufacturer FSESC 6.6 Encoder AMT102V

Sensorless fine, both BLDC and FOC using ADC current control but when I try to detect the encoder it steps through the slow motion in both directions then comes up with a serial port error and does not display the offset and ratio. Tried all different kinds of USB cables, ferrite beads, LiPo battery, external supply, a couple of PC's [ Windows 10] all give the same error. 

Tried to install under LINUX VM but could not gey it to run. 

ENCODER Connections:

GND, +5V, HALL1  to B, HALL2 to A Synch pulse (X) to HALL3 

 

Any help would be appreciated,

Bruno

 

 

 

VirtB
Offline
Last seen: 2 years 5 months ago
Joined: 2018-08-27 21:44
Posts: 4

I heard from the hardware manufacturer and they said to take out the HALL sensor 2K2 pull-up resistors. I did that now it works but I cannot reset the OVER_VOLTAGE error. I am using 3 2500mA Lipo Cells in series and they output 12.2V fully charged, I adjust the battery cut-off start and end voltages, write the configuration but it makes no diffreence. The only way I can make the motor run, is to use lab suppluy but that won't provide the current and it trips on under_voltage.

Any help would be appreciated

Bruno

 

Bruno

Danny Bokma
Offline
Last seen: 3 days 14 hours ago
VESC Original
Joined: 2017-05-24 12:11
Posts: 53

What voltage does the realtime data read? Does that correspond with the voltage that is actually supplied to the VESC? 

What did you set your voltage limits to?

VirtB
Offline
Last seen: 2 years 5 months ago
Joined: 2018-08-27 21:44
Posts: 4

The realtime data voltage is  reading correctly, I can make it work with a Lab supply between 10 and 12V Input. Trips on OV at 12.2V, The problem is that I set the Battery limits voltage ( the new version of VESC tool no longer sets the 8 & 57V limits. Those are now hardcoded in firmware) send ( save) the setting to the controller but there is no effect. Perhaps it is a bug in software but fixing that is not in my skill-set. Or more likely I am doing something wrong, setting not found etc. 

Bruno

Bruno