hi @ludwig_bre, I got a kit an without a gps, but i changed my mind and i am looking to add a bn-220 module.
I have connected the gps on the uart as described in the github for VESC and enabled the GPS on the TX and RX configuration but so far i got no speed on the TX screen.
am i missing something?
?printGPS gives me the following even though the GPS has been booted for a while:
----- GPS Satellite Status -----
Satellites in view: 0
HDOP (Horizontal Dilution of Precision): Invalid
Location validity: Invalid
Date/Time validity: Invalid
Course validity: Invalid
Chars processed: 1303082
Sentences with fix: 0
Failed checksum: 0
Thanks in advance!
EDIT: I got it working, i updated the RX firmware to the logger, i am looking forward to test the logging features 
1 Like
Happy you got it working
As background information, the firmware without logger is still expecting a NEO-6M GPS module, that’s why it was not working
BN-220 modules need the logger firmware
1 Like
Hi all,
Can someone please remind me how I can recalibrate left, right and centre on the Bremote v2? I already have it calibrated but want to do it again as think it is a bit off. I’ve checked the videos but can only see reference to the first time.
Many thanks.
Described on GitHub 
Option 1: Hold left toggle pressed while turning on
Option 2: Just set the “cal_ok” variable in the config to 0 and reboot
how did i miss this … i used your calibration method and it was exactly what i was looking for.
Today i did my first run with logging enabled. Unfortunately i cannot open the logs. When i upload them to logtrc i get
“Could not decode this binary log file. Please check the file type/layout. Records: 4035, decoded rows: 0, dropped: 4035.”
I don’t really want to use the beta android app and i do not have an iPhone 
And since they are binary an Texteditor does not work either.
Please send me the files as PM so I can check
Until then, you can also open Terminal and send
“?list” then pick one and send “?download <filename.log>” to get a csv representation.
EDIT: Thanks for the data. Since your VESC does not deliver any data (probably incorrect connection) and logtrc deletes every row until the first throttle is detected from VESC (to cut away idle time before entering the water) the log is reported as “empty”.
You can send ?dbit0 to enable VESC debug data and make dure the connection is working.
Alternatively use this log viewer for the GPS data only (no input filtering): LINK