Awesome video as always, this comprehensive guide was a much needed resource for the community 🙏 Few extra notes for people to keep in mind as well that could potentially be missed from this video: 48:33 - For Observer Gain, I just wanted to note for incoming Floatwheel ADV riders, we don't yet know if this should be tweaked or not. The detected value comes out as close to 0.75, so there's a chance it may not need to be halved. I would leave alone for now on Floatwheel ADV's until more testing is done on what works best. 54:10 - Generally, the recommended Field Weakening settings also include setting ramp time to 500ms. Full disclaimer, I personally haven't tried a quicker ramp time, so I can't speak on it kicking in too suddenly to be noticeable or anything like that, very possible it may work just fine. 500ms is just more "tried and true" in this case, so if you have any weird experiences leaving it at 200ms where you notice any weird behavior at that 60% duty cycle transition point, it may be worth bringing it up to 500ms. 59:56 - When Mario mentions 832Hz for the Sample Rate, this is true for the Little FOCer v3.1 (which uses an LSM6DS3 IMU), but may not be true for all setups! Some IMU's like the one in the Floatwheel ADV use 800Hz, some use 1000Hz, etc. Make sure this Sample Rate (App CFG -> IMU) matches that of your IMU, and if not 832Hz, you must also have Loop Hertz match this, found under Float CFG -> Specs (Once Float Package is installed later; he mentions this parameter at 1:17:59). So for example, if you have a Floatwheel ADV, you need to set both Sample Rate (App CFG -> IMU) and Loop Hertz (Float CFG -> Specs) to 800Hz. 1:10:32 - After IMU setup, when checking if it's functioning on the RT Data tab (scroll down to IMU screen), make sure you're looking at the values! Specifically, Roll should read near 0 when not rolled, Pitch should read about positive 20-30 or so for nose up, and negative for nose down, and they should both be about 0 when level. If this is not true, something went wrong and you may need to re-visit IMU Calibration, possibly from a clean slate to be safe like Mario explained how to do. 1:14:09 - When installing the Float Package, even if it shows up already on the Packages tab, I would still recommend hitting Update Archive to make sure you're installing the latest version of the Float Package, with the latest features and bug fixes!
Thanks heaps you two for all the info! Got my adv pro setup and riding well! only odd thing id a really high pitch whiniing noise whenever riding and my battery percentage even at fully charged will display 80%. cant see whats causeing it haha
@corevena4664 Battery percentage I really wouldn't trust anyways, I prefer to just reference the voltage on the RT Data screen above that one. But that's likely due to some battery information being input wrong during motor setup, you can check them under Motor CFG -> Additional Info. For the high pitch whine, there's no great way to fully get rid of it, but you can try different Zero Vector Frequency values to see what sounds best. This is under Motor CFG -> FOC -> Advanced. Tony recommends 26kHz, but try different values between 25-30 and see what sounds best when engaged. Can try lower too but it usually makes the whine more noticable, and I'm not sure what the controller is rated for so I probably wouldn't push it much past 30kHz, or at least not above 35kHz if you really want to try a bit higher.
@@Adoptme646 Accel Temp Decrease should be set to 0% to prevent current limiting before Temperature Tiltback kicks in. For the cutoff temps, I personally set both Motor and MOSFET to have Cutoff Start 80°C and Cutoff End 90°C
What a wealth of information here! Thanks so much. I’ve been a VESC rider for a year now, and I still reference this video to gain a little more knowledge every time.
Thank you Mario. This video, your write up on rewiring a GT Battery, and the video where you rebuilt a Quart battery, gave me the confidence I needed to bring my dead GT back to life. It's been out of action for most of the summer, and without these resources I never would have taken the plunge to buy a Vesc and get it all working again. I live in the UK and the Shipping alone back to FM was more expensive than just buying the Vesc and BMS. I have never worked on a LiPo Battery pack before, but with a load of research, days of soldering in my spare time, it feels like I have a brand new board again. Hat's off to you sir, I never would have finished (or started it for that matter) without you.
these instructions were invaluable to getting my floatwheel working. I messed up the imu, and it was impossible to mount with out the board shooting out from under me. resetting the imu in app cfg let me recalibrate from whatever bad state it was in.
Mario thank you!! This video is amazing. I feel like a student again i learned so much. Ill probably listen/watch this 20 times to much sure I retain all this wonderful information. Can't thank you enough for this 🤙👍
Thank you Thank you Thank you!! Your Video is the perfect setup guide. Got my GT-V kit installed and worked great, until i messed with settings in VESC and did not back anything up. The board was bucking me off and was wild. Followed your video in-depth instructions and the board feels great, plus i learned a ton about VESC. Great Video!
FloatWheel values for motor set up differ from this video as follows: Max Power Loss: 700W Sensorless ERPM: 1500 Battery Capacity: 8.0 for adv and 8.4 for adv pro Battery Current Regen: -70A Battery Current Max: 70A Wheel Diameter: 293mm Motor Current Max/Brake: 120A/-120A Absolute Max Current: 180A Battery Voltage Cutoff Start: 50V Battery Voltage Cutoff End: 40V Zero Vector Frequency: 26kHz He makes no recommended changes to the General FOC parameters I find that the default observer works fine on the adv pro Field Weakening Current Max: 50A Field Weakening Duty Start: 70% Field Weakening Ramp Time: 1000ms IMU Type: BMI160 Loop Hz: 800Hz High Voltage Threshold: 86V Low Voltage Threshold: 60V Angle I:/Mahoney KP: unchanged These are Tony's values from his V2 Motor set up. Any issues, take them up with him!
For the foward and reverse motor direction detection, i always put the onewheel on the floor and let it run to see if fowards is fowards, its hard to see visualy and unintuitive when on a bench. Newbs get it wrong all the time, and even pros get it wrong sometimes. If you put it on the floor and watch it run, youll never get it wrong. Just make sure you have 6ft of runway in either direction.
Video Summary/Keypoints: 00:00 📺 This video is a tutorial on setting up a VESC-based one-wheel board, focusing on the software setup. 01:25 📱 An Android device is recommended for configuring VESC-based personal electric vehicles (PEVs) like one-wheel boards due to more stable Bluetooth connectivity with VESC tool. 04:51 🔄 Reflashing the firmware can resolve certain issues with VESC-based devices, but be cautious not to interrupt the process. 10:35 🔋 Understanding battery parameters, like full voltage, nominal voltage, empty voltage, and the S count (series count) of your battery pack, is crucial for configuring your PEV correctly. 18:12 🏎 Performing motor detection, especially for larger outrunner motors, is a crucial step in configuring VESC-based devices and should be done with care. 21:35 📊 Inputting accurate battery information into VESC settings ensures accurate real-time data display, and this information should be provided by the battery or device manufacturer. 24:48 ⚡ Battery regen braking power can be set using the "battery current regen" parameter, with a recommended value of around -25 amps. 25:14 🔌 Don't use cell datasheet figures to set battery current; it's unrealistic. Set battery current based on practical usage and context. 26:39 📏 Measure your wheel diameter accurately for optimal speed readings; guesswork can lead to inaccurate data. 28:27 🛠 After motor detection, test the motor direction to ensure it's correct; incorrect motor direction can lead to problems. 31:11 🕹 Check the motor's functionality in the controls tab after detection, setting it to forward and reverse to ensure proper operation. 34:20 📝 When configuring motor settings, prioritize the critical values for motor functionality before fine-tuning for optimization. 37:57 🛇 Disable BMS-related settings if you have a VESC-connected BMS to prevent motor cutoff due to battery state inaccuracies. 42:48 ⚡ Set battery voltage cutoffs (start and end) well below your pushback or tilt back voltage to avoid sudden motor cutoffs when battery levels drop. 47:00 ⚙ Adjust motor resistance and observer gain values for optimization based on the specific motor type (e.g., hyper core, superflux). Consult references for precise values. 50:40 🛠 Adjust sensorless erpm to 2000 and Hall interpolation erpm to 200 for motor optimization. 51:37 📊 Increase zero Vector frequency to 27 kHz for improved performance on certain motors. 52:16 🔍 Consider changing the Observer type to "Ortega original" for the hyper core motor in VESC firmware 6.02 for better results. 54:07 🚀 Enable field weakening by setting the field weakening current Max to 30 amps and the field weakening Duty start to 60 percent for increased top speed. 56:10 🧭 Calibrate the IMU (Inertial Measurement Unit) to ensure accurate board orientation data. 59:02 💡 Use a Bubble Level to ensure the board's pitch and roll axes are level during IMU calibration. 01:00:12 ⚙ Check and manually set the IMU sample rate to 832 Hertz in app config to match the float package frequency. 01:14:06 📦 Install the float package and reconnect the VESC tool GUI to access package-specific settings. 01:15:43 📊 When checking float app RT data adc1 and adc2, they should be near zero initially, but go above three volts when you press on one side and then both sides. 01:16:24 🛠 To ensure your foot pad works, press both switches to prime it for startup. This verifies it's registering above three volts. 01:17:03 🔄 Before tuning balance values, set appropriate voltage thresholds in float config: high voltage threshold (to warn of overcharging) and low voltage threshold (for empty battery). 01:18:14 🔋 Set the high voltage threshold based on your battery's full voltage, typically 1-1.5 volts above full charge voltage. For an 84V 20s battery, set it to 85V. 01:20:16 🚫 Configure the low voltage threshold for tilt back to 60 volts for a 20s battery (3 volts per cell). Adjust accordingly for different battery configurations. 01:22:04 🧤 It's advisable to test the board's functionality on the floor or with hand tests before standing on it to ensure safety. 01:23:18 🛴 Once the default tune is set and the board is functional, you can fine-tune the ride feel by adjusting values in the float package, including angle P, rate P, angle I, and Mahoney KP. 01:24:25 🏞 Test the board in a safe area to ensure it responds to your leans and movements as expected before making advanced adjustments to the tuning settings.
Wahoooo, yeah finally a wonderful guide, for Hypercore OR superflux... I just finished my built, again.. it's a "Vxwheel", with Ubox100. Just now I can't watch the video, i am to tired, I ll sleep for sure, but when I can I watch it full to configurate my board... She's functionning,, but I am sure it can be upgraded with better parameters.
1:15:18 I'm having trouble here. my ADC1 and ADC2 is showing a constant 1.7 volts and nothing changes when I press the pads. Anyone know what's up with that?
I bought a never installed VESV based little focker and 3D printed box off craigslist but I don't know where to begin. I bought a soldering iron that attaches to my Milwaukee M18 battery though so I'm heading in the right direction. 😁
Do you happen to have a recommended battery current figures for the 18s2p torque pack from zbattery solutions? I didn’t find it in the link you provided; only the speed pack was there, I believe.
PS: when a VESC gets bricked, you can use another VESC as an SWD debugger with the full VESC tool and i believe with the full android version aswell (tablet) in which case you don't need an STLink
@@NoahZimmerman No you use a working vesc, connect scl, sda and gnd up to the bricked vesc and give both power or if it says swd sdio or something those it really depends on what model vescs you have i personally use an stlink but you can do it with a vesc aswell it is not easy, you need to find the correct pins for that specific vesc, i think you can find them by checking out the firmware though or may just take some trial and error
So does it matter which order you install the float package? I'm wondering because in surfdados long setup video it seems like he already has it installed before he starts his setup video. I tried following his video on a freshly built vesc and the APPUI tab wouldn't appear for me. I was told later that it's because I didn't have a float packaged installed.
My fireware update is 6.05. And I haven't done any other setup yet (I got busy), and I've been following this tutorial along with Surfdado's videos and all of them seem to be the 6.2 update. Will this effect anything in the long run by following this video or Surfdado's videos?
Great video…but there’s a much easier and more accurate way to get your actual tire diameter instead of guessing or using sticks. Use a string and wrap it around the tire at the center. Mark the spot the ends meet up, then take and measure the string length in mm. Then, simply divide that value by pi, and you have the diameter: D = C / π Where π (pi) is approximately equal to 3.14159.
i have a longshot and sort of stupid question. could i pay you to make me a vesc based xr i could buy everything i just dont trust myself to make it myself.
![#008-1: VESC Setup for eFoil [Flipsky 65161 & 75200]](/img/1.gif)
Awesome video as always, this comprehensive guide was a much needed resource for the community 🙏 Few extra notes for people to keep in mind as well that could potentially be missed from this video:
48:33 - For Observer Gain, I just wanted to note for incoming Floatwheel ADV riders, we don't yet know if this should be tweaked or not. The detected value comes out as close to 0.75, so there's a chance it may not need to be halved. I would leave alone for now on Floatwheel ADV's until more testing is done on what works best.
54:10 - Generally, the recommended Field Weakening settings also include setting ramp time to 500ms. Full disclaimer, I personally haven't tried a quicker ramp time, so I can't speak on it kicking in too suddenly to be noticeable or anything like that, very possible it may work just fine. 500ms is just more "tried and true" in this case, so if you have any weird experiences leaving it at 200ms where you notice any weird behavior at that 60% duty cycle transition point, it may be worth bringing it up to 500ms.
59:56 - When Mario mentions 832Hz for the Sample Rate, this is true for the Little FOCer v3.1 (which uses an LSM6DS3 IMU), but may not be true for all setups! Some IMU's like the one in the Floatwheel ADV use 800Hz, some use 1000Hz, etc. Make sure this Sample Rate (App CFG -> IMU) matches that of your IMU, and if not 832Hz, you must also have Loop Hertz match this, found under Float CFG -> Specs (Once Float Package is installed later; he mentions this parameter at 1:17:59). So for example, if you have a Floatwheel ADV, you need to set both Sample Rate (App CFG -> IMU) and Loop Hertz (Float CFG -> Specs) to 800Hz.
1:10:32 - After IMU setup, when checking if it's functioning on the RT Data tab (scroll down to IMU screen), make sure you're looking at the values! Specifically, Roll should read near 0 when not rolled, Pitch should read about positive 20-30 or so for nose up, and negative for nose down, and they should both be about 0 when level. If this is not true, something went wrong and you may need to re-visit IMU Calibration, possibly from a clean slate to be safe like Mario explained how to do.
1:14:09 - When installing the Float Package, even if it shows up already on the Packages tab, I would still recommend hitting Update Archive to make sure you're installing the latest version of the Float Package, with the latest features and bug fixes!
Thanks heaps you two for all the info! Got my adv pro setup and riding well! only odd thing id a really high pitch whiniing noise whenever riding and my battery percentage even at fully charged will display 80%. cant see whats causeing it haha
@corevena4664 Battery percentage I really wouldn't trust anyways, I prefer to just reference the voltage on the RT Data screen above that one. But that's likely due to some battery information being input wrong during motor setup, you can check them under Motor CFG -> Additional Info.
For the high pitch whine, there's no great way to fully get rid of it, but you can try different Zero Vector Frequency values to see what sounds best. This is under Motor CFG -> FOC -> Advanced. Tony recommends 26kHz, but try different values between 25-30 and see what sounds best when engaged. Can try lower too but it usually makes the whine more noticable, and I'm not sure what the controller is rated for so I probably wouldn't push it much past 30kHz, or at least not above 35kHz if you really want to try a bit higher.
Under general and temperature did you change any value like mosfet temp cut off and cut off start also the accelaration temp decrease
@@Adoptme646 Accel Temp Decrease should be set to 0% to prevent current limiting before Temperature Tiltback kicks in. For the cutoff temps, I personally set both Motor and MOSFET to have Cutoff Start 80°C and Cutoff End 90°C
first time ever i understood how battery voltage is actually calculated 😊 yes, i am very new to pev's. awesome video, thank you Sir
Well done serving the community with this quality resource.
What a wealth of information here! Thanks so much. I’ve been a VESC rider for a year now, and I still reference this video to gain a little more knowledge every time.
Thank you Mario. This video, your write up on rewiring a GT Battery, and the video where you rebuilt a Quart battery, gave me the confidence I needed to bring my dead GT back to life. It's been out of action for most of the summer, and without these resources I never would have taken the plunge to buy a Vesc and get it all working again. I live in the UK and the Shipping alone back to FM was more expensive than just buying the Vesc and BMS. I have never worked on a LiPo Battery pack before, but with a load of research, days of soldering in my spare time, it feels like I have a brand new board again. Hat's off to you sir, I never would have finished (or started it for that matter) without you.
You're the hero that we dont deserve, Mario ❤
Outstanding video. Thanks for taking the time to put this together. I'm new to VESC and this was very helpful.
these instructions were invaluable to getting my floatwheel working. I messed up the imu, and it was impossible to mount with out the board shooting out from under me. resetting the imu in app cfg let me recalibrate from whatever bad state it was in.
Mario thank you!! This video is amazing. I feel like a student again i learned so much. Ill probably listen/watch this 20 times to much sure I retain all this wonderful information. Can't thank you enough for this 🤙👍
Thank you Thank you Thank you!! Your Video is the perfect setup guide. Got my GT-V kit installed and worked great, until i messed with settings in VESC and did not back anything up. The board was bucking me off and was wild. Followed your video in-depth instructions and the board feels great, plus i learned a ton about VESC. Great Video!
FloatWheel values for motor set up differ from this video as follows:
Max Power Loss: 700W
Sensorless ERPM: 1500
Battery Capacity: 8.0 for adv and 8.4 for adv pro
Battery Current Regen: -70A
Battery Current Max: 70A
Wheel Diameter: 293mm
Motor Current Max/Brake: 120A/-120A
Absolute Max Current: 180A
Battery Voltage Cutoff Start: 50V
Battery Voltage Cutoff End: 40V
Zero Vector Frequency: 26kHz
He makes no recommended changes to the General FOC parameters
I find that the default observer works fine on the adv pro
Field Weakening Current Max: 50A
Field Weakening Duty Start: 70%
Field Weakening Ramp Time: 1000ms
IMU Type: BMI160
Loop Hz: 800Hz
High Voltage Threshold: 86V
Low Voltage Threshold: 60V
Angle I:/Mahoney KP: unchanged
These are Tony's values from his V2 Motor set up. Any issues, take them up with him!
This is incredible. I hope you make more content like this.
incredibly helpful mario. Great explanations on setup and what each thing does.
For the foward and reverse motor direction detection, i always put the onewheel on the floor and let it run to see if fowards is fowards, its hard to see visualy and unintuitive when on a bench. Newbs get it wrong all the time, and even pros get it wrong sometimes. If you put it on the floor and watch it run, youll never get it wrong. Just make sure you have 6ft of runway in either direction.
Got my thor up and running last night on a stock xr battery for now, thanks Mario!
A true hero.
Video Summary/Keypoints:
00:00 📺 This video is a tutorial on setting up a VESC-based one-wheel board, focusing on the software setup.
01:25 📱 An Android device is recommended for configuring VESC-based personal electric vehicles (PEVs) like one-wheel boards due to more stable Bluetooth connectivity with VESC tool.
04:51 🔄 Reflashing the firmware can resolve certain issues with VESC-based devices, but be cautious not to interrupt the process.
10:35 🔋 Understanding battery parameters, like full voltage, nominal voltage, empty voltage, and the S count (series count) of your battery pack, is crucial for configuring your PEV correctly.
18:12 🏎 Performing motor detection, especially for larger outrunner motors, is a crucial step in configuring VESC-based devices and should be done with care.
21:35 📊 Inputting accurate battery information into VESC settings ensures accurate real-time data display, and this information should be provided by the battery or device manufacturer.
24:48 ⚡ Battery regen braking power can be set using the "battery current regen" parameter, with a recommended value of around -25 amps.
25:14 🔌 Don't use cell datasheet figures to set battery current; it's unrealistic. Set battery current based on practical usage and context.
26:39 📏 Measure your wheel diameter accurately for optimal speed readings; guesswork can lead to inaccurate data.
28:27 🛠 After motor detection, test the motor direction to ensure it's correct; incorrect motor direction can lead to problems.
31:11 🕹 Check the motor's functionality in the controls tab after detection, setting it to forward and reverse to ensure proper operation.
34:20 📝 When configuring motor settings, prioritize the critical values for motor functionality before fine-tuning for optimization.
37:57 🛇 Disable BMS-related settings if you have a VESC-connected BMS to prevent motor cutoff due to battery state inaccuracies.
42:48 ⚡ Set battery voltage cutoffs (start and end) well below your pushback or tilt back voltage to avoid sudden motor cutoffs when battery levels drop.
47:00 ⚙ Adjust motor resistance and observer gain values for optimization based on the specific motor type (e.g., hyper core, superflux). Consult references for precise values.
50:40 🛠 Adjust sensorless erpm to 2000 and Hall interpolation erpm to 200 for motor optimization.
51:37 📊 Increase zero Vector frequency to 27 kHz for improved performance on certain motors.
52:16 🔍 Consider changing the Observer type to "Ortega original" for the hyper core motor in VESC firmware 6.02 for better results.
54:07 🚀 Enable field weakening by setting the field weakening current Max to 30 amps and the field weakening Duty start to 60 percent for increased top speed.
56:10 🧭 Calibrate the IMU (Inertial Measurement Unit) to ensure accurate board orientation data.
59:02 💡 Use a Bubble Level to ensure the board's pitch and roll axes are level during IMU calibration.
01:00:12 ⚙ Check and manually set the IMU sample rate to 832 Hertz in app config to match the float package frequency.
01:14:06 📦 Install the float package and reconnect the VESC tool GUI to access package-specific settings.
01:15:43 📊 When checking float app RT data adc1 and adc2, they should be near zero initially, but go above three volts when you press on one side and then both sides.
01:16:24 🛠 To ensure your foot pad works, press both switches to prime it for startup. This verifies it's registering above three volts.
01:17:03 🔄 Before tuning balance values, set appropriate voltage thresholds in float config: high voltage threshold (to warn of overcharging) and low voltage threshold (for empty battery).
01:18:14 🔋 Set the high voltage threshold based on your battery's full voltage, typically 1-1.5 volts above full charge voltage. For an 84V 20s battery, set it to 85V.
01:20:16 🚫 Configure the low voltage threshold for tilt back to 60 volts for a 20s battery (3 volts per cell). Adjust accordingly for different battery configurations.
01:22:04 🧤 It's advisable to test the board's functionality on the floor or with hand tests before standing on it to ensure safety.
01:23:18 🛴 Once the default tune is set and the board is functional, you can fine-tune the ride feel by adjusting values in the float package, including angle P, rate P, angle I, and Mahoney KP.
01:24:25 🏞 Test the board in a safe area to ensure it responds to your leans and movements as expected before making advanced adjustments to the tuning settings.
Wahoooo, yeah finally a wonderful guide, for Hypercore OR superflux... I just finished my built, again.. it's a "Vxwheel", with Ubox100. Just now I can't watch the video, i am to tired, I ll sleep for sure, but when I can I watch it full to configurate my board... She's functionning,, but I am sure it can be upgraded with better parameters.
1:15:18 I'm having trouble here. my ADC1 and ADC2 is showing a constant 1.7 volts and nothing changes when I press the pads. Anyone know what's up with that?
I bought a never installed VESV based little focker and 3D printed box off craigslist but I don't know where to begin. I bought a soldering iron that attaches to my Milwaukee M18 battery though so I'm heading in the right direction. 😁
Any chance there's video for an AdV pro for us that are not vesc savy?
Do you happen to have a recommended battery current figures for the 18s2p torque pack from zbattery solutions? I didn’t find it in the link you provided; only the speed pack was there, I believe.
Thanks, huge resource!
fantastic content! thanks
Thank you so much!
PS: when a VESC gets bricked, you can use another VESC as an SWD debugger with the full VESC tool and i believe with the full android version aswell (tablet) in which case you don't need an STLink
Hey. Do you happen to have any more info on this? Do you just use usb type c on the bricked Vesc? What if it doesn’t show up?
@@NoahZimmerman No you use a working vesc, connect scl, sda and gnd up to the bricked vesc and give both power
or if it says swd sdio or something those
it really depends on what model vescs you have
i personally use an stlink but you can do it with a vesc aswell
it is not easy, you need to find the correct pins for that specific vesc, i think you can find them by checking out the firmware though or may just take some trial and error
So does it matter which order you install the float package? I'm wondering because in surfdados long setup video it seems like he already has it installed before he starts his setup video. I tried following his video on a freshly built vesc and the APPUI tab wouldn't appear for me. I was told later that it's because I didn't have a float packaged installed.
I guess I kind of answered my own question there didn't I
My fireware update is 6.05. And I haven't done any other setup yet (I got busy), and I've been following this tutorial along with Surfdado's videos and all of them seem to be the 6.2 update. Will this effect anything in the long run by following this video or Surfdado's videos?
Not so much. 05 adds some functionality and fixed some bugs. Core principles like those in these videos will remain the same.
Great video…but there’s a much easier and more accurate way to get your actual tire diameter instead of guessing or using sticks.
Use a string and wrap it around the tire at the center. Mark the spot the ends meet up, then take and measure the string length in mm. Then, simply divide that value by pi, and you have the diameter:
D = C / π
Where π (pi) is approximately equal to 3.14159.
Man this is just about like setting up a race drone on betaflight lol. But that's one of my things lol
Can you emulate Delirium on VESC?
48:33 When adjusting Motor Resistance, isn’t it a good idea to also match Current KI to the Motor Resistance value?
It can be, but in practice, it hasn’t shown to be necessary with the Hypercore or Superflux.
i have a longshot and sort of stupid question. could i pay you to make me a vesc based xr i could buy everything i just dont trust myself to make it myself.
I can do custom builds and conversions, feel free to email the shop:
info@theboardgarage.com
Can I hire you to build me a 84v vesc onewheel ? I'm in VA
Sure, you can send me an email. info@theboardgarage.com
Нужно сделать ЧТОБ по сугробам проезжал, гусинетцу сделать😊
Is it possible for you to build me a board like yours and how much would you charge?
You can reach out to me on my site and we can discuss it.
Soon we shall free ourselves from the trash that is FM
⚡👏🏼👏🏼⚡
Lame i just wanted a pile of broken parts anyways
Getting sensorless under the sensors category.
Sensor connector could be disconnected, or the wiring somehow damaged.