Nice to meet you. I am new to this forum. Also, since I am Japanese, English is a little strange, but please forgive me.
I started to create Vesc6.5 (vesc plus) which is mentioned in the document for studying my circuit.
Also, when creating this circuit, we are trying to reduce costs and cutting some functions. (Nrf, mpu9250, etc.)
Good evening,
I am using two VESC 75/300 for an engine test rig.
Unfortunately one out of the two VESC 75/300 can´t be connected by USB to the laptop. I tried a lot of things, different cables and drivers.... makes no difference. The andorid phone app works well with both of them.
Both are release 3 hardware with FW 5.1.
Would be great if someone knows how to sole the USB-issue.
One funny thing is that the one with the USB issue has a mysterious red light near to the on/off switch. Does this mean anything?
Good evening,
With the VESC-tool the logged power value is available for .csv. logging files.
But I can´t find the power value in the .csv file itself or when .csv is imported in Excel.
Everything is logged but the power seems to be missing:
I'm using a VESC 75/300 in regen mode with a low-inductance motor to produce just over 2kW of power. The VESCs have worked well but we have seen intermittent ABS Overcurrent errors during operation and then some back-to-back ABS overcurrent errors followed by the ESCs frying. We've fried 2 ESCs so far, and we see the ABS Overcurrent errors on a couple others that have yet to fail. Any idea on what could be causing this? Could the VESC be losing sync and somehow be unable to protect itself?
Hi,
We have been using the VESC 75/300 for quite sometime now, but we are having trouble achieving the 300 A continues rating it says it can handle. Attached you may find a graph of real life usage of the VESC on our boat. One can see that after using the VESC puling a motor current of just above 100 A (mean) the maximum MOSFET temperature variable rises almost to 100 ºC (we have limited the temperature to 95 ºC).
Hi, I'm having issues setting my vesc 4.2 controller up. I've gone through the wizard setup and I keep getting an error that says no hall sensor detected. What am I missing here? All parts are new so I figure there's a small thing not quite right. Based on the pic or previous experience can anyone wager a guess to what's causing this issue. Thanks all!
Hi,
so I recently started my graduation project which consists of "tuning" an originally 1,9 kW scooter to 20 kW peak power :D
I already got the VESC 75 300 for that project (motor will be qs205 v3 and battery a diy 16S11P 21700 Molicell P42a with 300A peak BMS) and am currently working on the precharge because I want an automatic one (so no XT90S solution).
Hi all!
I have big problems with an stable connection between those devices.
i can successfully connect with my metr App to the Vesc and can read all data.
i can also write data to the vesc.
when I test it I got also some telemetry data to my app.
but when I drive longer the connection broken.
when I try to reconnect to the metr Dongle it also not possible.
i must totally stop and restart the app and I can again connect.
I'd like to output PWM signals on the Hall1 (GPIOB pin 6) and Hall2 (GPIOB pin 7) pins of my hardware version 4.12 VESC. I know about the existing code that allows this to be done for addressable ws2811 LEDs, but I'd like to simply output a duty cycle between 0 and 3.3 V. I was thinking of essentially taking code from servo_simple, which outputs a servo on GPIOB pin 5 using TIM3, and adapting it to output PWMs on pins 6 and 7. Are there any obvious reasons as to why this wouldn't work?
servo_simple uses the pad setup command:
Does anyone know if the gerbers are available for the 75/300? It doesn't even need to be the actual files, just PDF's. I'm most curious about the power section and layout of the FETs. What do the inner layers look like?
Thanks in advance!
