Jump to content

Scorpius Headset comms and dashboard


aussieslotter

Recommended Posts

Scorpius design and functionality always refers to 1:1 racing to keep it as real as possible.
Radio comms in motorsport has been around since the late 40s. And kicked off big time by the 80s.

Its critical and handy to have important information.
SmartRace has Smart Connect which can do this but only for 6 cars and only for Carrera.

Screens are great but you can't look at a screen and race and concentrate on a race simultaneously.
Announcements are great but it is impossible to hear everyone's at once.

So how to do?

Apps can't do custom RF but can do Bluetooth and Wi Fi and phones don't accept dongles.
Your PC can do RF via dongle, Bluetooth and Wi Fi.


Our race program, Scorpius Race Management, already has all the required data. The work here will be only to port it to WiFi, nothing else. A relatively easy job. The other aspect is app work. Here we have a reliable consistent app already in place with a proven Bluetooth connection established. The app engineer will need to decode incoming data, make a configuration box to be able to select a car ID 1-24, and turn the incoming data into screen text and also employ text to send to headset using cable.

 

 

 

 

voice and send via cable.ScorpiusHeadsetComms.thumb.png.3246812de2ce657a44eed839dafb7414.png

My proposal is to send all information globally using Wi Fi. Each app can be customised to a certain car ID 1-24.

WiFi and RF both operate generally on 2.4Ghz and will ad traffic.
The limits won’t be known until testing. For example it may be that there is a limitation on this, 6 cars for example, maybe more or less. No one knows yet.


Each drivers app decodes the global message and using text to voice will hear only their information, no one else.  Voice includes countdown to race start, false start, lap times, laps to go, new race leader, best lap times. time to go, fuel and tyre status can be heard.

As a project manager I need to plan well in advance. This is a ten year product meaning once its released there will be no hardware changes for a decade like Scorpius Generation 1 did successfully. It's a winning formula for the end user.
So everything must be planned years ahead. This is one such function, even though we may not get to this in 2025. It will happen.
But discussion, a specification is paramount with all the relevant engineers to foresee issues is required now not later, and plan accordingly for long term success with minimal back tracking of work as the MPD will be released as a car decoder first and then the other 9 MPD products added AFTER the MPD is released.

Here the system will eventually employ RF, BT and WiFi to get the job done.

Here's a rough idea what the screen may look like.

 

R.thumb.jpg.6f067f5b1c1881237b4f81e20baad2ed.jpg

 

On chips, we have simply too many to create a video-log. As mentioned earlier in this thread, some were dead-on-arrival, some had no brakes, some had a range with the of about 30cm, some when hooked up to a light kit had only rear lights but not front lights (light kit and LEDs worked perfectly when tested with another chip) and so much more. 
 

 

 

 

www.scorpiuswireless.com

 

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...