Hello everyone,
I am currently designing my own vesc hardware.
Now my question is, if the voltage readings also have a plausibility check, similar to the current measurements, implemented in the firmware? So that a disconnected or stuck sensor signal can be detected by the firmware or do I have to safeguard against such failures in hardware.
Hello to everyone! I have Enertion Raptor 2.0 that I had to replace the remote since the Nano-X on/off switch broke. I purchased a Flipsky Remote VX1 with the receiver and installed it. It works but with an issue.
The motors are braking without input. The wheels free spin only when I apply lite power. I guess the signal must be calibrated.
I download VESC and connect to the original Raptor 2.0 (dual) focbox. The software claims that my VESC has too old firmware, possible 2.80 and for that only limited communication is allowed.
Hi,
I'm having issues with trying to program my vesc. I don't know where to start and support wasn't helpful, just sent me a video from 5 years ago.
Any help would be appreciated. TIA
Hi, I have a Flipsky 75100 V2 with modified R005 shunts
I can see this specific version was added in "bldc /hwconf /flipsky":
But it's not showing up on the tool in the compatible firmware list:
How could I load this firmware to my VESC?
(Sorry if this is a stupid question, I tried to fix it by myself, but I'm running out of ideas)
Based on the documentation , you can send all the commands specified in commands.c by dividing the command over multiple frames. My question is how to format the frames? My understanding so far is to send a frame with the id: COM_CAN_FILL_RX_BUFFER << 8 | CAN_ID and then send another frame with the id COM_CAN_PROCESS_RX_BUFFER << 8 | CAN_ID to process the command in the rx buffer.
Hello,
I designed a custom ESC based on the 60_mk6 minus a few features. I am trying to build the latest firmware, but am running into issued when following the steps on the fit repo readme. I'm running windows 10.
The choco install and "choco install make" ran with no issues. I did not use an elevated powershell, but my user accout does have admin privleges.
The issues start when I try and run "make arm_sdk_install" Here are the results:
PS C:\Users\ttyle\vscode_projects\vesc\bldc> make arm_sdk_install
Hi fellow Vesc users,
I am experiencing negative current when in full duty - what is the cause maybe somebody knows?
I am using Ubox 100V 100A board,
Motor is Crystalyte 5305 v2
Battery is 24s LiFePo4
This is my eBike:
Hi, using V6.02, running in BLDC-mode ( as I still have trouble with watchdog-resets) I quite often get FAULT_CODE_UNDER_VOLTAGE. Checking the errors with Android, I sometimes get the following output
Fault : FAULT_CODE_UNDER_VOLTAGE
Motor : 1
Current : -0.8
Current filtered : -0.0
Voltage : 0.30
Duty : 0.011
RPM : 4.8
Cycles running : 2
TIM duty : 179
Motor : 1
TIM duty : 188
Hello I have the Focbox Unity and it was working fine with my old motor setup and wheel. But I recently have upgraded to a 12s battery and a 6368 motor and 120mm wheel size.
Hi,
I described the issue a year ago here, https://vesc-project.com/node/4260 but unfortunately got no response. So I did a lot of testing during the last year to narrow the reason but with only little usable results. And I want to mention that I am very familiar with HW and SW- debugging.
