Check out: https://drive.google.com/file/d/1m-P4rdffjTJMjf6-ddHLrFED4w7u5a35/view
Page 10-11 describes error codes (not sure how up to date this is though.) I hear these also from my xlite V3 and to be honest, I’ve not yet pinned down what they are (not put in too much effort) as it’s hard to count the beeps while riding. I often hear them just after I get underway, just cruising at around 10mph. I’m not aware that the VESC will pick up on these via Canbus but I really don’t know enough about it.
Hi Nico, or anyone else who can help,
I developed an led controller using a PCA9685 chip using I2C-Bus for communication.
lib_pca9685 is the driver written in lisp.
GitLitApp is the vesc_pkg containing led balance controller written in lisp and ui.qml for AppUi.
Problem:
I have to load a modified version of the FloatUi.qml containing an additional tabButton in the model and a columnLayout for my controls i.e. on/off, dimming. This is because as a separate pkg it will overwrite the float appui.
Questions:
Is it possible to import the qml from lisp which will just insert a tabButton into the float tabBar model and append a page to the float stacklayout?
I know the floatUi architecture for the tabBar will have to be changed to handle this using ObjectModel instead of TabButton but im not sure if the lisp Import will handle the dynamic loading of a qml correctly and target the float AppUi or if it will always erase and upload.
I can send you code samples and build details if it helps. Let me know.
D
1 Like
afaik right now only a single package/lisp can be loaded at a time - so your best bet is just to fork your own version of the Float package for the time being
This kind of question would be best asked in the official VESC Discord
Now that I know about the Discord and checked it out I agree. Far more appropriate channel. Thanks for the tip! Didn’t really know the best way to reach out to you guys.
D
v1.2b (Aug-10): Floatwheel owners can now set their odometer backwards to remove the 170 miles Tony accidentally added in the memory of some of the early models
Can someone explain to do that? I’d love to reset my odometer to a proper value!
Thanks
Was trying to test the haptic buzz on continuous currents and the 5 second delay is making it kinda difficult to use for safety and testing. I don’t know what the delay should be but similar to how it is on the gt when nose dragging.
The delay is suitable for the intended purpose of that feature, being warnings of high continuous current. It’s not intended to provide haptic buzz for pushing the current limit in real time, like the haptic buzz on FM boards does. I would like to look into this for the future (it’s a bit more complicated since you need headroom current to produce the intended buzz/noise), but for now, this functionality is not present in the Float Package.
1 Like
I’m having some issues getting the brake force where I need it. It seems both brake angle rate p seems to have very little influence. Any suggestions?
You could try Torque Tiltback Strength (Regen) in Tune Modifiers.
Does anyone know to which VESC pin the LEDs should be connected for the Float package? I checked the source code of the Float package and according to that it should be PB7 which corresponds to servo. I removed the cap on the servo/ppm pin, connected data in of a ws2812B LED strip and chose RGB under LED. Did the reboot, no light. I wonder if PB7 is the right pin as it is mentioned that thor300 and littleFoccer4 use dedicated LED pins (but which ones then?). I’m using a diys “FreeDrive” VESC: GitHub - nordstream3/FOC