AthleticSB Data Outputs
This is an advanced feature. 99.9% of the time, an AthleticSB board is what you want for your physical display. If you have a compelling reason to send raw data to an external data source, this is how you can do it.
As of version 2.0.10 released in November 2025, AthleticSB now supports sending data to custom outputs via LSS files. This means you can send data from AthleticSB to ResulTV, Dak, CharacterWorks, or other systems.
Use existing FinishLynx or FieldLynx LSS files or create your own.
Starting with version version 2.1.18 data only outputs can output JSON instead of needing to create LSS scripts.
All data comes from AthleticLIVE, so these outputs work as long as you have the correct data uploaded from your meet management and FAT systems.
Getting Started
- Open AthleticSB.
- Click "Edit Default Settings" in the main menu.
- Click "Show LSS Data Output Boards"
- Save.
- From the AthleticSB Dashboard, click "Create Data Only Output" and fill out the form. Send data via UDP, TCP, or write to a file.
Operation
- From the AthleticSB dashboard, go to your the data output and click the Green Play button. Data should now be streaming.
- If a board uses pagination, you can use the "Paging" button to update paging while the board is open.
Supported Board Types
See the Downloads page for example LSS files for all supported boards types.
- Live Track Standings
- Compiled Standings (entries, results, track team scores, etc)
- XC Summary (Team Scores Only)
- Field Result
JSON Data Format
Formats listed below are auto generated from internal data formats and are subject to change. Not all fields may be populated and value types may change depending on the data source selected. Always be sure to test the data outputs for your specific situation.
Compiled Results
Example Horizontal Field Event
{
eventName;
record1Name;
record1Mark;
record1Conversion;
record2Name;
record2Mark;
record2Conversion;
bubbleTime;
results: {
name;
teamAbbreviation;
affiliation;
id;
mark;
conversion;
place;
firstName;
lastName;
personalRecords; // PR, SB, =PR, =SB
rankings; // best ranking. ex US #1
brokenRecords; // best record or time standard. ex. Meet
photoUrl;
logoUrl;
fieldSeriesMarks; // list of horiztonal marks or vertical heights
fieldSeriesWind; // list of winds for horizontal marks
fieldSeriesVerticalAttempts; // list of vertical x's and o's
}[];
messageText;
}Live Track Standings
{
official;
eventName;
wind;
eventNumber;
roundNumber;
heatNumber;
autoManual;
numParticipants;
armedRunning;
distance;
numHeats;
bubbleTime;
results: {
place;
lane;
id;
name;
affiliation;
time;
deltaTime;
cumulativeSplitTime;
lastSplitTime;
lapsToGo;
license;
reacTime;
speed;
pace;
bestSplitTime;
user1;
user2;
user3;
firstName;
lastName;
multisPoints;
personalRecords;
rankings;
brokenRecords;
photoUrl;
logoUrl;
}[];
messageText;
}Field Result
{
official;
eventName;
eventNumber;
roundNumber;
heatNumber;
measurement; // Metric or English
type; // Horizontal or Vertical
verticalHeights; // Bar Heights // metric, 2.00, english - 48.00 for 4 feet
results: {
resultPlace;
resultAttempt;
resultId;
resultName;
resultAffiliation;
resultMark;
resultWind;
resultMarkConverted;
resultMarkOnly; // Mark only - no vertical attempts
resultVerticalAttempts; // Only vertical mark attempts for the current mark (XO, etc)
resultFieldSeriesMarks; // Field series marks (hundredths precision for horizontal events, jump results for vertical events (e.g. xxo, xo, o, ppp, ppp, xxx))
resultFieldSeriesWind; // Field series wind (for horizontal jumps)
nextPlace;
nextAttempt;
nextId;
nextName;
nextAffiliation;
nextFirstName;
nextLastName;
resultFirstName;
resultLastName;
// AField only
resultConversionOnly; // Conversion only - no vertical attempts
resultBestMark; // Current best mark
resultConvertedBestMark; // Current converted best mark
resultBoardNumber; // Board number
resultMultisPoints; // Multis Points
resultPersonalRecords; // PR, SB, =PR, =SB
resultBrokenRecords; // best record or time standard. ex. Meet
resultPhotoUrl;
resultLogoUrl;
}[];
messageText;
}Track Team Scores
Track team scores data comes from compiled standings data only outputs with the data source set to team scores
{
scoreName;
numScoredEvents;
numTotalEvents;
results: {
affiliation;
teamAbbreviation;
place;
points;
projectedPoints;
logoUrl;
}[];
messageText;
}XC Team Scores
{
eventName;
eventNumber;
roundNumber;
heatNumber;
eventRoundHeat;
results: {
affiliation;
teamAbbreviation;
place;
points;
scorers;
maxScorers;
totalTime;
avgTime;
gap;
placeChange;
logoUrl;
teamPoints[];
runners: {
id;
name;
team;
teamAbbrev;
lapSplit;
cumulativeSplit;
place;
placeChange;
points;
}[];
}[];
messageText;
}