›

Problem report: RaceBox Mini S together with $RC3 WiFi -- missing data

DrMotorDrMotor
in DIY builds
I send $RC3 at 10 Hz update rate via WiFi -- the rate is consistent (and reported by RaceChrono) as long as I leave RaceBox disabled.
Problem: When I enable RaceBox (BLE), then I get a low and inconsistent update rate of $RC3.
HW and SW: Oscal S80 Android phone with RaceChrono Pro v8.0.8.

The problem is not present when testing it on a Samsung Galaxy (which I prefer not to use while racing).

Is there a setting or something I should try in order to make this work better?
e.g. $RC2 messages instead of $RC3, or a different update rate....

Comments

  • DrMotorDrMotor
    Update: The $RC3 messages appear normal and steady in a WiFi terminal app on the phone, untill I start RaceChrono and connect it to the RaceBox, then the $RC3 messages in the terminal will start arriving in batches of 10 or more messages (the terminal adds timestamps, and each batch arrives within a single millisecond). All the $RC3 messages still arrive in the correct order. This behaviour is the same on all the phones I tested.

    When I enable both RaceBox and $RC3 WiFi in RaceChorono, then RaceChrono reports an inconsistent $RC3 update rate, and data is missing (or misplaced?) also in the log.

    What can be causing the problems?
  • DrMotorDrMotor
    Update 2: It works better with 25 Hz rate of sending $RC3, that is same rate as the RaceBox GPS data. It still occasionally freezes/buffers for several seconds the real time display of my sensor data (several seconds = 100 or more $RC3 messages), but now the data gets stored (synchronized to the GPS?) and can be viewed after driving.

    I will try to use another app to connect to the RaceBox (instead of RaceChrono) -- to check if that one also blocks/buffers the WiFi ($RC3 messages).

    BTW: very little support there -- no reply for more than a month.
Sign In or Register to comment.