Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Scorpius RF and CU BT to SmartRace using Wifi
#1

So………how to integrate Scorpius data with a race app?

Firstly a smart device can talk to 7 devices but can only listen to one at a time when using BT. But they are good at processing wifi and BT simultaneously. 
So let’s make a converter. An MPD straight into an ESP32 (hardwired), battery powered. Stand alone, no cables. Now into a nice enclosure.
The MPD listens on channel 25 and passes it to the ESP32 using SPI. Here the MPD is able to be used as a dongle as USB is not required and we can use the data port.

After speaking to Marc at SmartRace this is definitely doable.

Obviously the app receives basic race info from the Carrera CU using their BT dongle.
But the opportunity exists to take any or all of the possible Scorpius data. So what’s available?

We have 3 sites of telemetry.
1. Controller.
2. Track.
3. Car.

1. Controller: The car reads the track beacons and  processes controller data simultaneously. In the controller we gather and use this data:
Controller ID
Controller PIN 
Lane change status yes/no?
Throttle speed 
Brake sensitivity
Driver name.

2. Track: 
Sector or LB ID number.
Lane number 
Start finish line.

Each lane changer broadcasts a message continuously from the track LED we call a beacon. The car gathers this info and uses it for various functions. 

So far we have 2 lots of important data. But about car data? 

3. Car:
Car specific telemetry.
Throttle speed after being mapped.
Firmware version number.
Tacho reading.
Hall sensor.
Accelerometer X axis.
Accelerometer Y axis.
Accelerometer Z axis.
Sound preference.

So around 16 lots of data within the telemetry stream. Some of this data is useless and others look promising.
Like having your automatically entered into the app ala Scorpius RMS. 
Collision detection between any amount of cars. From what direction. And how much for.
So now we can detect who shunted who, who caused a collision at any lane changer, detect deslots, detect roll overs. 
Tacho for tuning and testing. Even fuel usage.
More accurate throttle readings more often for working out fuel useage. Same with brakes using brake telemetry.
Of our transmission window we dedicate around 30% for telemetry so that’s around 30 transmissions per second which equates to a maximum 10 complete packages per second. This gives a true and accurate picture to pass to to the software/appware guys.

Welcome to the new era.

   
Quote
#2

I’ve dumped this idea due to space issues inside the car. Plus too many radio waves conflict with each other.

Instead for Carrera users we will concentrate on track telemetry which will be a new thread.
Quote
#3

24 hours and its back on the table. I woke up this morning and the first thing that entered my mind was I wonder if the nRF52832 can switch backwards and forwards between RF proprietary and BLE because even though the chip can do both it cannot do both simultaneously.
I asked Grok and got the answer I wanted. Yes I can switch backwards and forward between RF as much as I like and for any interval I like in fact up to 99.99%.
So it is possible to control a Scorpius car and supply car telemetry to the SmartRace app as well as talk to Lane Brains on channel 26 (RF).
So now Carrera  users can get all of the Scorpius telemetry.
Switching time is just a millisecond if that so car control will not be affected.
The limitations are not yet known but definitely we can get some car telemetry to the app. 
We could dedicate 98 or 99% of the time to RF car control and then switch to BLE for the other 1 or 2%.
This opens up a whole new kit of possibilities and from a  developers point of view is very exciting.
As we already have the telemetry it’s probably 2 days work plus debugging to complete it. 
It just keeps on getting better.
Quote


Possibly Related Threads...
Thread / Author Replies Views Last Post

Forum Jump:


Users browsing this thread: 1 Guest(s)