what OS are you using? Do you see the VCP (virtual COM Port) in the Devicemanager/ports (Windows) or a /dec/tty Interface (Linux)? Else the tool could not connect to the VESC.
The Driver comes from ST (=SGS Thomson) the mfc of the uC. Maybe Ben should enable a simple driver section for Windows people.
Linux has a generic driver afaik build into and could cope with the VCP anyway.
Cheers
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC
no the throttle is not needed, nor HALL, or Motor or anything. Only a Vcc with about 8V+, GND and the USB. Did your VESCtool see the COM port as well (there's an autodetection for the VCP integrated).
Without the ST Software (the drivers to be exact), no windows should be able to see a COM port, so you must have installed it before. Else the VCP resides as "unknown USB device" and waits for the driver. Maybe a unfitting driver has taken control over the VCP and does not handle it well. If you work with different embedded systems such things can happen.
Cheers
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC
That would explain the no connect for one thing. Could you do a screenshot of just your Devicemanager port section (and to be sure) of your USB section; the small snippets should be enough.
Cheers
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC
Hi
what OS are you using? Do you see the VCP (virtual COM Port) in the Devicemanager/ports (Windows) or a /dec/tty Interface (Linux)? Else the tool could not connect to the VESC.
The Driver comes from ST (=SGS Thomson) the mfc of the uC. Maybe Ben should enable a simple driver section for Windows people.
Linux has a generic driver afaik build into and could cope with the VCP anyway.
Cheers
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC
Hi, Yes i see the com ports. Led is blue and tried several USB cables, nothing seems to work. No Connection with vesc, using Windows 7
cheers
I did not connected the throttle, maybe that’s the problem?
Hi
no the throttle is not needed, nor HALL, or Motor or anything. Only a Vcc with about 8V+, GND and the USB. Did your VESCtool see the COM port as well (there's an autodetection for the VCP integrated).
Without the ST Software (the drivers to be exact), no windows should be able to see a COM port, so you must have installed it before. Else the VCP resides as "unknown USB device" and waits for the driver. Maybe a unfitting driver has taken control over the VCP and does not handle it well. If you work with different embedded systems such things can happen.
Cheers
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC
Hi, i didn’t install any other then vesc tool, No st software downloaded or so.
Cheers
Hi
That would explain the no connect for one thing. Could you do a screenshot of just your Devicemanager port section (and to be sure) of your USB section; the small snippets should be enough.
Cheers
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC
Sam, dowmloaded the virtual port files, now i can connect to vesc.
Thank you so much, cheers
Matthew van Ratingen
Hi Matthew
I'm glad I'd help. Maybe Frank could include it into the documentation as the VESC depends on the VCP files (under windows)
Cheers
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC