BREmote - DIY Remote

Not sure how to PM you if you prefer.

Could it be that it needs a data cable to upload instead of a recular USB?
I had that problem using VESCtool.

Sketch uses 4724 bytes (15%) of program storage space. Maximum is 30720 bytes.
Global variables use 735 bytes (35%) of dynamic memory, leaving 1313 bytes for local variables. Maximum is 2048 bytes.
Error: cannot set com-state for \.\COM5
Error: unable to open port COM5 for programmer arduino
Failed uploading: uploading error: exit status 1

Usually you make the USB cable yourself, so if it has 4 wires and they are in the right order it should be fine

That seems to be the problem, some driver or operating system error
Check in device manager if the com port is correctly found

Hey everyone,

For those following along with the development here, I’m excited to announce that a massive upgrade is almost ready: BREmote v2.5.0-Evo (Beta).

Building on the incredible foundation from LudwigBre and Janrusher, v2.5.0-Evo is a huge leap forward. Here is a quick teaser of what is included:

  • Fully Working TX/RX GPS: Real-time speed directly on the handheld remote.
  • GPS Anti-Spoofing & Safety Gates: Rigorous coordinate cross-checking between the remote and the board.
  • Flash Data Logging: Onboard logging of VESC telemetry, GPS, and voltage, downloadable over WiFi.
  • V3 Config Studio: A brand-new offline HTML config tool.
  • Return-to-Me (RTM) & Follow-Me (FM): The compass and GPS logic for autonomous tracking are fully operational!

šŸ› ļø Beta Testers Needed: My dual-motor buggy is waiting on a new VESC, so I need a few people with working setups to help test the hardware in the wild. If you're interested, please sign up via this Google Form.

āš ļø Please Note: Because v2.5-Evo introduces so many new features and architectural changes, follow updates and discussion here.šŸ‘‰ (https://foil.zone/t/bremote-future-development-topic/20820/267)

Please head over to the new thread to read the full release details, grab the source code, and leave any questions, thoughts, or feature requests. Let's keep all v2.5-Evo discussion over there so it's easy to track!

P.S.: I also have to biuld my Nano kit. so that will be next. but the v2.5-Evo already supports M10 GPS chip (in addition to the BN220). So RX will use the BN880 with compass, and the Nano could fit a micro HGLRC M100 (M10 Chip) GPS.

2 Likes

Super excited! Thanks for pushing this
Will look into it for sure, may I ask though to rethink the name? V3 in my mind will be the next hardware revision, so maybe we can call it V2.3 or V2-evo or something? :slight_smile:

love it, it will be v2.5.x-Evo and on!

2 Likes