Harry's GPS Suite Forum

forum.gps-laptimer.de
http://forum.gps-laptimer.de/

RaceBox micro support

http://forum.gps-laptimer.de/viewtopic.php?t=6825

Page 1 of 1

RaceBox micro support

Posted: Tue Dec 17, 2024 8:42 pm
by jbt_se
Hi Harry,

Will RaceBox Micro be supported by Harry’s lap timer?

Re: RaceBox micro support

Posted: Wed Dec 18, 2024 10:00 am
by Harry
You need to test this yourself (and please report once you have done that). Our contact to Racebox has vanished, and we have not received replies to other mail addresses. Not sure why but it is as it is. As we do not receive support by them any more, we keep Racebox support "as is" currently.

Re: RaceBox micro support

Posted: Sun Dec 29, 2024 8:34 pm
by jbt_se
I have done some testing and now and it won't connect to the racebox micro.
Racebox micro is not shown in the list of available GPS receivers.
Is there anything that I can provide you with so you can make it work?

Re: RaceBox micro support

Posted: Mon Dec 30, 2024 9:57 am
by Harry
jbt_se wrote: ↑Sun Dec 29, 2024 8:34 pm I have done some testing and now and it won't connect to the racebox micro.
Racebox micro is not shown in the list of available GPS receivers.
Is there anything that I can provide you with so you can make it work?
Well, we can try, but it is always odd to work without proper manufacturer support...

Please install the free LightBlue app and check the Micro's peripheral name and BT LE read characteristic UUIDs. For the existing models, it is

Code: Select all

peripheralnamepattern = "RaceBox Mini (S )?[0-9]+"
readcharacteristic = sensor.btle.addcharacteristic( "6E400001-B5A3-F393-E0A9-E50E24DCCA9E", "6E400003-B5A3-F393-E0A9-E50E24DCCA9E", true)
My assumption is you can deal with this terms when using a Micro. ;-)

The simplified phrasing is "let me know the exact BT LE name of the Micro as shown in LightBlue; check if you see a service UUID 6E400001-B5A3-F393-E0A9-E50E24DCCA9E and a read characteristic 6E400003-B5A3-F393-E0A9-E50E24DCCA9E.

I assume the Micro will use these UUIDs but the name does not follow the "RaceBox Mini" pattern...

Re: RaceBox micro support

Posted: Mon Dec 30, 2024 10:34 pm
by jbt_se
This is the data I got from lightblue.

Advertisement Data

Advertised namne
RaceBox Micro 3242703208

Advertised service UUID
0000180a-0000-1000-8000-00805f9b34fb
6e400001-b5a3-f393-e0a9-e50e24dcca9e

Raw advertisment package
0x020106190952616365426F78204D6963726F203332343237303332303803030A1811079ECADC240EE5A9E093F3A3B50100406E0000000000000000000000


Generic access

device name
UUID: 00002a00-0000-1000-8000-00805f9b34fb

Apperance
UUID: 00002a01-0000-1000-8000-00805f9b34fb

Peripheral Preferred connection parameters
UUID: 00002a04-0000-1000-8000-00805f9b34fb

Service UUID
00001800-0000-1000-8000-00805f9b34fb

central address resolution
UUID: 00002aa6-0000-1000-8000-00805f9b34fb


Generic attributes
6e400001-b5a3-f393-e0a9-e50e24dcca9e

6e400002-b5a3-f393-e0a9-e50e24dcca9e
properties: write

6e400003-b5a3-f393-e0a9-e50e24dcca9e
properties: notify

Re: RaceBox micro support

Posted: Tue Dec 31, 2024 12:56 pm
by Harry
This looks like a changed name pattern but the same API. I will add the “Micro” option to the next release that will get available in Spring. In case you want to test that front up, you need to join the HarrysLua developer program. See viewtopic.php?t=4572 for more information.

Re: RaceBox micro support

Posted: Tue Jan 28, 2025 10:06 pm
by Albert
Hallo,
Ich habe immer wieder Verbindungsprobleme mit der Racebox mini und nachdem es jetzt die Micro gibt, würde es auch auf meinem Wunschzettel stehen, dort eine Integration zu haben. Ich habe die Hoffnung, dass diese stabiler in der Verbindung ist.

Die Entwicklerumgebung ist eher nix für mich, Anwendungsbenutzung ist besser für meine Nerven :D

Albert
PS.: Danke für die App, hatte schon viele schöne Runden damit

Re: RaceBox micro support

Posted: Sun Apr 13, 2025 4:30 pm
by fluppie00
I've got a Racebox Micro as well, from the Kickstarter at the time.

Code: Select all

985BBA9A-7773-5AD9-11B7-EA0CF2BB9051

17:20:35.863 - Connecting to nearby peripheral: RaceBox Micro 3242701427 
17:20:36.380 - Connected to nearby peripheral: RaceBox Micro 3242701427 
17:20:37.033 - Characteristic (2A29) read: <52616365 426f7820 4d6f746f 7273706f 7274204c 4c4300> 
17:20:37.093 - Characteristic (2A24) read: <52616365 426f7820 4d696372 6f000000 00000000 00000000 00000000 0000> 
17:20:37.154 - Characteristic (2A25) read: <33323432 37303134 32370000 00000000 00000000> 
17:20:37.213 - Characteristic (2A27) read: <312e34> 
17:20:37.274 - Characteristic (2A26) read: <332e3400> 
17:20:37.720 - 10 peripherals discovered 
17:20:39.720 - 12 peripherals discovered 
17:20:40.116 - 13 peripherals discovered 
17:20:43.720 - 14 peripherals discovered 
17:20:45.720 - 15 peripherals discovered 
17:20:55.720 - 16 peripherals discovered 
17:20:58.117 - 17 peripherals discovered 
17:20:59.412 - Stopping search for nearby peripherals 
17:20:59.412 - Starting search for nearby peripherals 
17:20:59.412 - Scanning on Main Thread 
17:21:00.301 - 6 peripherals discovered 
17:21:02.116 - 7 peripherals discovered 
17:21:05.417 - 8 peripherals discovered 
17:21:07.417 - 9 peripherals discovered 
17:21:07.476 - Disconnected from nearby peripheral RaceBox Micro 3242701427 
17:21:08.116 - 10 peripherals discovered 
17:21:12.116 - 12 peripherals discovered 
17:21:14.116 - 14 peripherals discovered 
17:21:16.116 - 19 peripherals discovered 
17:21:18.117 - 20 peripherals discovered 
17:21:27.387 - 21 peripherals discovered 
17:21:33.388 - 22 peripherals discovered 
17:21:34.116 - 23 peripherals discovered 
17:21:42.906 - Stopping search for nearby peripherals 
17:21:51.024 - Starting search for nearby peripherals 
17:21:51.025 - Scanning on Main Thread 
17:21:58.116 - 24 peripherals discovered 
17:21:58.569 - Connecting to nearby peripheral: RaceBox Micro 3242701427 
17:21:59.298 - Connected to nearby peripheral: RaceBox Micro 3242701427 
17:21:59.388 - 25 peripherals discovered 
17:21:59.536 - Characteristic (2A29) read: <52616365 426f7820 4d6f746f 7273706f 7274204c 4c4300> 
17:21:59.593 - Characteristic (2A24) read: <52616365 426f7820 4d696372 6f000000 00000000 00000000 00000000 0000> 
17:21:59.656 - Characteristic (2A25) read: <33323432 37303134 32370000 00000000 00000000> 
17:21:59.716 - Characteristic (2A27) read: <312e34> 
17:21:59.776 - Characteristic (2A26) read: <332e3400> 
17:22:08.115 - 26 peripherals discovered 
17:22:10.116 - 28 peripherals discovered 
17:22:15.387 - 29 peripherals discovered 
17:22:17.388 - 30 peripherals discovered 
17:22:29.855 - Disconnected from nearby peripheral RaceBox Micro 3242701427

Re: RaceBox micro support

Posted: Wed Apr 16, 2025 8:17 am
by Harry
Thanks for providing this information. Although the RaceBox guys stopped supporting us, I will try get the Micro working for the Spring release. Without access to an actual device, I will not be able to test it physically, but I can do some theoretic checking against their documentation.

Re: RaceBox micro support

Posted: Fri Apr 18, 2025 9:54 am
by Harry
I reimplemented the RaceBox Integration based on their API documentation and added Micro support. Actually I found several issues with the original integration, operation should be very stable with the new one. During testing, I discovered regular disconnects / timeouts in case the BT signal has been too weak. This is interesting because peer driver's RaceBox devices often create trouble because they advertise over really long distances - leading to connects to other cars. On the other hand, for stable operation, they need to be near by. Strange.

The new integration will be released as part of LapTimer's Spring release in a few weeks. Thanks for feedback once it is getting available.
All times are UTC+01:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited