MyCricket Live Score can integrate with Bluetooth scoreboards. This requires the scoreboard provider to action the information below.
Our recommended scoreboard manufacturers are:
Service, characteristic & profile:
Service UUID: 5a0d6a15-b664-4304-8530-3a0ec53e5bc1
Characteristic UUID: df531f62-fc0b-40ce-81b2-32a6262ea440
Profile Type: GATT (Generic Attribute Profile)
Data points:
|
Name |
Key |
Description |
Example value |
|
Current Over |
COV |
Ball by ball display for the current over, with each ball separated by a single space |
. 1 2 . 4 wd . |
|
Overs bowled |
OVB |
Overs bowled in the current innings |
31.2 |
|
Overs remaining |
OVR |
Overs remaining in the current innings (if limited overs) |
18.4 |
|
Runs required |
RRQ |
Required runs (if applicable) |
123 |
|
Required run rate |
RRR |
Required runs per over rate (if limited overs) |
2.45 |
|
Batting Team Name |
BTN |
Name of the current batting team |
Team A |
|
Batting Team Score |
BTS |
Score for the current batting team |
5/245 & 0/10 |
|
Bowling (Fielding) Team Name |
FTN |
Name of the current bowling team |
Team B |
|
Bowling (Fielding) Team Score |
FTS |
Score for the current bowling team |
197 |
|
Batter 1 Name |
B1N |
Name of batter (1) |
A Batter |
|
Batter 1 Score |
B1S |
Score of batter (1) |
5 |
|
Batter 1 Balls Faced |
B1B |
Balls faced by batter (1) |
6 |
|
Batter 1 Strike |
B1K |
Does batter (1) have the strike? (1 = yes, 0 = no) |
1 |
|
Batter 2 Name |
B2N |
Name of batter (2) |
B Batter |
|
Batter 2 Score |
B2S |
Score of batter (2) |
2 |
|
Batter 2 Balls Faced |
B2B |
Balls faced by batter (2) |
4 |
|
Batter 2 Strike |
B2K |
Does batter (2) have the strike? (1 = yes, 0 = no) |
0 |
|
Current Bowler Name |
F1N |
Name of current bowler |
C Bowler |
|
Current Bowler Score |
F1S |
Figures and overs bowled for current bowler |
0/6 (1.2) |
|
Previous Over’s Bowler Name |
F2N |
Name of current bowler |
D Bowler |
|
Previous Over’s Bowler Score |
F2S |
Figures and overs bowled for current bowler |
1/13 (2.1) |
|
Last Wicket |
LWK |
Score when last wicket fell |
101 |
|
Duckworth Lewis Target Score |
DLT |
Target D/L score for the innings |
147 |
|
Duckworth Lewis Par Score |
DLP |
Par D/L score for the end of the current over |
101 |
|
Last Wicket Batter Name |
LWN |
Name of batter out in last wicket |
B Batter |
| Last Wicket Batter Score | LWS | Score/balls faced of batter out in last wicket | 16 (37) |
| Last Wicket Dismissal type | LWD | Dismissal type for last wicket | ro |
| Last Wicket Bowler | LWB | Bowler of last wicket (if applicable) | C Bowler |
| Last Wicker Fielder | LWF | Fielder of last wicket (if applicable) | D Fielder |
Receiving data:
Data will be sent to the characteristic:
- Whenever a value has changed and needs to be updated on a scoreboard; or
- When a full refresh of the scoreboard is triggered from the Scoreboard settings page of the app (added in the v5.2 build of the app).
Data will be sent in a “KEYVALUE” format, where the first three characters in the string correspond to the Key and the remaining characters in the string are the Value.
For example:
- Overs bowled value to be set to 32: OVB32
- Batter 1’s Balls Faced increases to 11: B1B11
- Current over display update: 1 2 . 4 wd .
- Duckworth Lewis Target Score is set at 147: DLT147
- Batter 1 name to change to “D Batter”: B1ND Batter
Tips for scoreboard providers
- Ensure you have selected the ‘Generic’ and not ‘FSL’ option as the options use different UUIDs.
- Use a Bluetooth explorer (like Light Blue for iOS, or BlueSee BLE Debugger for Mac) and check that it can see the service & characteristic’s existence, and that both UUIDs that it is seeing match the ones in the documentation.
- An app like Light Blue for iOS also allows you to create a “virtual peripheral”, so create one with the service & characteristic UUIDs and check if the MyCricket LS app can connect to it.
Comments
0 comments
Article is closed for comments.