Post by Wß on Jul 18, 2017 23:18:26 GMT
I ran across a very well written post and wanted to share it here, everything on F1 forums should be this good! Full credit to DeltaEcho5... wherever you are!
F1 timing, a function of F1 Timekeeping using a variety of proprietary software, custom developed Tx (transponders) and other sensor specific onboard equipment.
The differences in F1 really stop there compared to other sanctioned events, such as FIAWEC, FormulaE, IMSA, Indycar, NASCAR, TransAM, SCCA, etc. (Additionally, MotoGP, Cycling, 10k's and even RC cars are also timed with transponders as well)
Amateur events and professional events are timed very similarly, with the major difference being with the type of transponder and track equipment.
For those interested I will try to break it down a bit here:
F1, Like FIAWEC and IMSA currently utilize a more advanced transponder, such as an AMB X2 data transponder. AMB is part of MyLaps, an equipment manufacturer as well as a software manufacturer.
What's a Tx?
The current X2 transponder (Tx) is an onboard vehicle powered transponder that emits a constant digital signal (this was previously referred to correctly, and then incorrectly assumed it was RFID. RFID it is not. RFID will work, but the SNR is woefully inadequate for racing purposes). The space the Tx occupies on each car, the height to track, the location from the front axel are all sanction specific, but due to ACO and FIA similarities/crossover, mostly the same in most professional motorsport for sports cars, and in F1, Indy and NASCAR are proprietary to those rule sets.
Loop?
The digital signal is received via a timing loop (also in almost all cases made by AMB/MyLaps, for reasons described in a bit) that is cut into the track. This loop, a specific size and depth, (typically 24"xtrack width) has proprietary resisters at each end, and culminates in a BNC fitting that is connected to a trackside box (TSB) that contains a decoder (AMB), a network controller, a battery controller and a DFO (fiber optic) TX/RX modulator (S/F and S/F pit are different as I will explain later).
The decoder also has an input for a GPS puck. The GPS signal is synchronized among all decoders on the track so that the exact time signal accurate to .001 is shared by all TSB's.
The signal then travels via either a fiber connector, a CAT5 cable, or a CAT5 cable to a NanoStation (a RF transmitter via WiFI/Nettalk to a tower receiver).
To the tower...
So, the basic system starts with a Tx, say on car 10, whose Tx # is a 7-8 digit number. That number is received at a particular loop on the track. Literally, the Tx signal is measured but the decoder in signal strength as it passes over as "hits" and the highest strength "hit" is recorded as the cars "passing". Each car Tx has many "hits" and this is recorded in the MyLaps X2 managers as a selectable graph, and looks just like a bell curve...low signal hits at the left of the graph and as the car passes over the loops, the signal strength is greater and the "hit" strength goes up, and as it passes the absolute center of the loop, the highest hit is recored as the passing...
In amateur, AmPro racing (SCCA, TransAm, HSR, etc.) there is typically only two loops of interest to the timekeeper for scoring laps, and that's the S/F and the S/F Pit. Basically one line. For professional racing, there are as many as 24-40 loops in a track, all with TSB's, decoders seeking the data. The TSB's are located around the track, at specific places of necessary interest to score the race. The S/F and S/F Pit are almost always hard wired straight to the tower due to their location, and therefore those decoders are rack mounted in the T&S room.
In additional to S/F, S/F Pit, typically there is Pit In, Pit Out, Pit Speed, additionally P1-P7 at most tracks (loops along pit lane), S1,S2 (Sector loops), data loops for X2 data acq. and also S/F Backup, S/F Pit Back Up, and various track limits, back door entrances and testing loops.
Tracks?
Tracks such as Daytona and COTA for instance have fiber rings, so there is a limited use of nano stations to xmit data to the tower. The decoders are centrally located at some tracks with fiber, so access to the rack to a switch to connect all the decoders to the x2 manager is handled versus a central bullet receiver on the tower to pick up the signal of a myriad of decoders using RF WiFi. Street circuits such as Monaco, Mexico, Detroit and the like require a temporary fiber ring and in some cases nano stations for RF WiFi. Road Atlanta has partial fiber, so we still have to set up nano's on most of the track (some with repeaters to get around the hills and trees!).
Drivers?
So the equipment side is a complicated maze of a very simple system. Loops > decoder > tower. The info each car sends isn't limited to just a car specific "phone number"...Tx 1234567 for instance, also xmits alternate side bits designating things such as driver (pilot #). Each "team" driven car (Sebring, LeMans, Daytona for sports cars) has driver changes which are handled via a rotary dial or a multi switch or a specific pin in a driver comm plug that tells the Tx to sent 0-5 as a side code to the decoder as well. In this way as the Tx passes a loop (say Pit Out) it alerts the system as to which drive is plugged in.
NASCAR for instance uses a proprietary Tx that sends the actual car number as the unique number to the decoder, as has been the case in F1 in the past. In FIAWEC as well as F1, the Tx is formed in the car tub, and is not removable. In the event of failure a back up Tx takes over the function, and in a worse case scenario, the car returns to the pits to receive a battery operated Tx as a loaner.
Both Tx's are transmitting constantly, but in X2 Admin Manager, the timekeeper is made aware of which Tx is to be used as primary, and the alternate Tx # is blocked or hidden from the timekeeping software via the data stream.
2-way?
The most recent X2 Tx's used in F1, FIAWEC and IMSA have two-way communication capability. Typically bits of data can be sent to the Tx as a question, and bits of data can be received from the car. In essence - Q:"Are you over boosting?", A: "No" (0) or "Yes" (1), etc. This can be done via the timing loop, or in the case of F1 and FIAWEC, via alternate data loops specifically set a slow portions of the track to be able to accurately communicate on one loop to another. X2 Tx settings are known as CAN settings and are set prior to the event and are set to specific codes for Tx and Rx. This is done during the safety check/scrutineering, along with all other checks (Yes, in FIAWEC, Burt's car, IMSA and Indy, all safety cars, EV's and even pace cars have transponders so they can be hidden from the system as competitors).
F1, like IMSA and FIAWEC, uses a proprietary system to xmit safety information and other track conditions to the driver, FIAWEC uses a separate system from the Tx. Delphi, Magneti Marelli, and Bosch to name a few used in Pro. In addition, in INDYcar and IMSA, the Position lights system (Pos. digit) started out as an RF system and is evolving to be sent via Tx, but in FIAWEC (three lights) is still being sent via Marelli RF.
How does it know?
Ultimately, even the best timekeeping software (search Orbits, Alkamel, TimeGear or SMT) still relies on this digital phone number passing the start finish loop to score a lap for the competitor. When a Tx is received, it's logged at the decoder with it's info, a timestamp from the GPS and the decoder it passed. This is info is matched with a database record - e.g., Car 10 is driven by driver 1,2,3 etc, engine type, constructor, sponsor, owner, team, etc. Each passing is then sent via the data stream to another piece of software (the actual scoring/timing part) where an operator is watching. The passing shows as a line item, along with a lap time, (calculated with math: this time stamp - last time stamp at this loop = lap time), which car has the longest distance with the shortest time (position) and how many pit stops, fastest sectors etc.
It quickly becomes a wealth of information with each passing, and live reports can be requested in separate windows for a particular car, driver, lap of the race, etc. This is often used by Race Control to determine issues...
What if?
So even the best equipment breaks, fails or trips up. In the past, an operator of the laptop with the software timing the race had to be vigilant by watching each car as it passed the S/F and compare it to the passings appearing on the S/F loop. People called "tapers" also worked in race control, T&S to watch the S/F, and get this, right down each car number as it passed in a list, and then turn the page when the leader started another lap. Often 2-10 tapers were required for enduro's, and typically 2-3 at a time so you could collect the "tapes" in case something was amiss with timing software...like a Tx not getting a hit, but the car completing the lap none the less. In this case, a high speed light sensor (photocell) is employed (Tag Heuer) and each cars passing is recorded (sometimes as a group of cars as one) and then compared in the software electronically to the passing made by the Tx timestamp. If the number is reasonably close (like .002 e.g., , a setting that is adjustable for rain) it blanks out the photocell and accepts the Tx. If there is a photocell and a Tx and there is no relationship, the timekeeper can look at the car, see the number, modify the photocell record to the correct car and accept it as the official passing. If you miss the car, you get the "tapes" and see what car showed up in the fray among the Tx's you got hits on!
Currently, tapers have gone the way of the dodo, and we use high speed camera systems located on S/F, Pit In Pit Out and other Track Limits areas, as well as rely on TV broadcast feed (12-30 cameras around the track) and update the information. Software has become very adept at using the input from all of these networked devices and comparing the information received and weeding out the bogey's.
Some aspects of X2 Timing Manager and other software also display a sequencer, which allows the operator to see a specific car travel around the track as it hits each loop. This info is fed into an algorithm (last lap time, predicted lap time) and is often used to display a track map with the cars circulating on it. The more loops used to build the sequencer, the more accurate the info as to position, lap traffic and passes on track.
Teams?
In addition to this information being sent via a data stream (believe it or not, an "RMon" feed, using $ lingo and just text) it is sent to the announcers, TV and the teams. For the teams, they can also see their specific cars individually as well as the whole race. And BTW, since this "stream" is captured live, using the software, you can actually "playback" the entire race, second by second, lap by lap, over and over.
Costs?
Typical X2 packages for teams with wiring and looms can run as much as $12,000, while AMB Tx's for Amateur racing is under $800. A fully equipped decoder TSB can run upwards of $10,000, not including the battery system needed. The average # needed? About 32, so $32,000 just to hook up to the track. Each venue typically is responsible for maintaining the loops, but in some cases, we need to repair them, cut in new ones, or move them. This is done in the week leading up to the event. Timing at FIA F1 tracks is wonderful, because the tracks by requirement have the entire system from loops to decoders already up and running and we only need connect our computers to the system via their network. Other tracks, street circuits and older venues require days in advance to set up, install systems, cameras and decoders before we can go live.
Most timekeeping crews travel long hours, work long hours, live all over the world 26+ weeks a year, and often don't get a chance to shine a little light on the magic that happens in the tower. We are part of the circus, rub elbows with drivers, teams, fans and bosses, and are just as smitten with racing as anyone. A crew of 6-10 people are responsible for bring the races to the public via timing and another 10-15 for race control, and we all take our work very seriously when the lights go out. The data is always analyzed and the correct information is put forth. There's nothing else I'd rather do.
The differences in F1 really stop there compared to other sanctioned events, such as FIAWEC, FormulaE, IMSA, Indycar, NASCAR, TransAM, SCCA, etc. (Additionally, MotoGP, Cycling, 10k's and even RC cars are also timed with transponders as well)
Amateur events and professional events are timed very similarly, with the major difference being with the type of transponder and track equipment.
For those interested I will try to break it down a bit here:
F1, Like FIAWEC and IMSA currently utilize a more advanced transponder, such as an AMB X2 data transponder. AMB is part of MyLaps, an equipment manufacturer as well as a software manufacturer.
What's a Tx?
The current X2 transponder (Tx) is an onboard vehicle powered transponder that emits a constant digital signal (this was previously referred to correctly, and then incorrectly assumed it was RFID. RFID it is not. RFID will work, but the SNR is woefully inadequate for racing purposes). The space the Tx occupies on each car, the height to track, the location from the front axel are all sanction specific, but due to ACO and FIA similarities/crossover, mostly the same in most professional motorsport for sports cars, and in F1, Indy and NASCAR are proprietary to those rule sets.
Loop?
The digital signal is received via a timing loop (also in almost all cases made by AMB/MyLaps, for reasons described in a bit) that is cut into the track. This loop, a specific size and depth, (typically 24"xtrack width) has proprietary resisters at each end, and culminates in a BNC fitting that is connected to a trackside box (TSB) that contains a decoder (AMB), a network controller, a battery controller and a DFO (fiber optic) TX/RX modulator (S/F and S/F pit are different as I will explain later).
The decoder also has an input for a GPS puck. The GPS signal is synchronized among all decoders on the track so that the exact time signal accurate to .001 is shared by all TSB's.
The signal then travels via either a fiber connector, a CAT5 cable, or a CAT5 cable to a NanoStation (a RF transmitter via WiFI/Nettalk to a tower receiver).
To the tower...
So, the basic system starts with a Tx, say on car 10, whose Tx # is a 7-8 digit number. That number is received at a particular loop on the track. Literally, the Tx signal is measured but the decoder in signal strength as it passes over as "hits" and the highest strength "hit" is recorded as the cars "passing". Each car Tx has many "hits" and this is recorded in the MyLaps X2 managers as a selectable graph, and looks just like a bell curve...low signal hits at the left of the graph and as the car passes over the loops, the signal strength is greater and the "hit" strength goes up, and as it passes the absolute center of the loop, the highest hit is recored as the passing...
In amateur, AmPro racing (SCCA, TransAm, HSR, etc.) there is typically only two loops of interest to the timekeeper for scoring laps, and that's the S/F and the S/F Pit. Basically one line. For professional racing, there are as many as 24-40 loops in a track, all with TSB's, decoders seeking the data. The TSB's are located around the track, at specific places of necessary interest to score the race. The S/F and S/F Pit are almost always hard wired straight to the tower due to their location, and therefore those decoders are rack mounted in the T&S room.
In additional to S/F, S/F Pit, typically there is Pit In, Pit Out, Pit Speed, additionally P1-P7 at most tracks (loops along pit lane), S1,S2 (Sector loops), data loops for X2 data acq. and also S/F Backup, S/F Pit Back Up, and various track limits, back door entrances and testing loops.
Tracks?
Tracks such as Daytona and COTA for instance have fiber rings, so there is a limited use of nano stations to xmit data to the tower. The decoders are centrally located at some tracks with fiber, so access to the rack to a switch to connect all the decoders to the x2 manager is handled versus a central bullet receiver on the tower to pick up the signal of a myriad of decoders using RF WiFi. Street circuits such as Monaco, Mexico, Detroit and the like require a temporary fiber ring and in some cases nano stations for RF WiFi. Road Atlanta has partial fiber, so we still have to set up nano's on most of the track (some with repeaters to get around the hills and trees!).
Drivers?
So the equipment side is a complicated maze of a very simple system. Loops > decoder > tower. The info each car sends isn't limited to just a car specific "phone number"...Tx 1234567 for instance, also xmits alternate side bits designating things such as driver (pilot #). Each "team" driven car (Sebring, LeMans, Daytona for sports cars) has driver changes which are handled via a rotary dial or a multi switch or a specific pin in a driver comm plug that tells the Tx to sent 0-5 as a side code to the decoder as well. In this way as the Tx passes a loop (say Pit Out) it alerts the system as to which drive is plugged in.
NASCAR for instance uses a proprietary Tx that sends the actual car number as the unique number to the decoder, as has been the case in F1 in the past. In FIAWEC as well as F1, the Tx is formed in the car tub, and is not removable. In the event of failure a back up Tx takes over the function, and in a worse case scenario, the car returns to the pits to receive a battery operated Tx as a loaner.
Both Tx's are transmitting constantly, but in X2 Admin Manager, the timekeeper is made aware of which Tx is to be used as primary, and the alternate Tx # is blocked or hidden from the timekeeping software via the data stream.
2-way?
The most recent X2 Tx's used in F1, FIAWEC and IMSA have two-way communication capability. Typically bits of data can be sent to the Tx as a question, and bits of data can be received from the car. In essence - Q:"Are you over boosting?", A: "No" (0) or "Yes" (1), etc. This can be done via the timing loop, or in the case of F1 and FIAWEC, via alternate data loops specifically set a slow portions of the track to be able to accurately communicate on one loop to another. X2 Tx settings are known as CAN settings and are set prior to the event and are set to specific codes for Tx and Rx. This is done during the safety check/scrutineering, along with all other checks (Yes, in FIAWEC, Burt's car, IMSA and Indy, all safety cars, EV's and even pace cars have transponders so they can be hidden from the system as competitors).
F1, like IMSA and FIAWEC, uses a proprietary system to xmit safety information and other track conditions to the driver, FIAWEC uses a separate system from the Tx. Delphi, Magneti Marelli, and Bosch to name a few used in Pro. In addition, in INDYcar and IMSA, the Position lights system (Pos. digit) started out as an RF system and is evolving to be sent via Tx, but in FIAWEC (three lights) is still being sent via Marelli RF.
How does it know?
Ultimately, even the best timekeeping software (search Orbits, Alkamel, TimeGear or SMT) still relies on this digital phone number passing the start finish loop to score a lap for the competitor. When a Tx is received, it's logged at the decoder with it's info, a timestamp from the GPS and the decoder it passed. This is info is matched with a database record - e.g., Car 10 is driven by driver 1,2,3 etc, engine type, constructor, sponsor, owner, team, etc. Each passing is then sent via the data stream to another piece of software (the actual scoring/timing part) where an operator is watching. The passing shows as a line item, along with a lap time, (calculated with math: this time stamp - last time stamp at this loop = lap time), which car has the longest distance with the shortest time (position) and how many pit stops, fastest sectors etc.
It quickly becomes a wealth of information with each passing, and live reports can be requested in separate windows for a particular car, driver, lap of the race, etc. This is often used by Race Control to determine issues...
What if?
So even the best equipment breaks, fails or trips up. In the past, an operator of the laptop with the software timing the race had to be vigilant by watching each car as it passed the S/F and compare it to the passings appearing on the S/F loop. People called "tapers" also worked in race control, T&S to watch the S/F, and get this, right down each car number as it passed in a list, and then turn the page when the leader started another lap. Often 2-10 tapers were required for enduro's, and typically 2-3 at a time so you could collect the "tapes" in case something was amiss with timing software...like a Tx not getting a hit, but the car completing the lap none the less. In this case, a high speed light sensor (photocell) is employed (Tag Heuer) and each cars passing is recorded (sometimes as a group of cars as one) and then compared in the software electronically to the passing made by the Tx timestamp. If the number is reasonably close (like .002 e.g., , a setting that is adjustable for rain) it blanks out the photocell and accepts the Tx. If there is a photocell and a Tx and there is no relationship, the timekeeper can look at the car, see the number, modify the photocell record to the correct car and accept it as the official passing. If you miss the car, you get the "tapes" and see what car showed up in the fray among the Tx's you got hits on!
Currently, tapers have gone the way of the dodo, and we use high speed camera systems located on S/F, Pit In Pit Out and other Track Limits areas, as well as rely on TV broadcast feed (12-30 cameras around the track) and update the information. Software has become very adept at using the input from all of these networked devices and comparing the information received and weeding out the bogey's.
Some aspects of X2 Timing Manager and other software also display a sequencer, which allows the operator to see a specific car travel around the track as it hits each loop. This info is fed into an algorithm (last lap time, predicted lap time) and is often used to display a track map with the cars circulating on it. The more loops used to build the sequencer, the more accurate the info as to position, lap traffic and passes on track.
Teams?
In addition to this information being sent via a data stream (believe it or not, an "RMon" feed, using $ lingo and just text) it is sent to the announcers, TV and the teams. For the teams, they can also see their specific cars individually as well as the whole race. And BTW, since this "stream" is captured live, using the software, you can actually "playback" the entire race, second by second, lap by lap, over and over.
Costs?
Typical X2 packages for teams with wiring and looms can run as much as $12,000, while AMB Tx's for Amateur racing is under $800. A fully equipped decoder TSB can run upwards of $10,000, not including the battery system needed. The average # needed? About 32, so $32,000 just to hook up to the track. Each venue typically is responsible for maintaining the loops, but in some cases, we need to repair them, cut in new ones, or move them. This is done in the week leading up to the event. Timing at FIA F1 tracks is wonderful, because the tracks by requirement have the entire system from loops to decoders already up and running and we only need connect our computers to the system via their network. Other tracks, street circuits and older venues require days in advance to set up, install systems, cameras and decoders before we can go live.
Most timekeeping crews travel long hours, work long hours, live all over the world 26+ weeks a year, and often don't get a chance to shine a little light on the magic that happens in the tower. We are part of the circus, rub elbows with drivers, teams, fans and bosses, and are just as smitten with racing as anyone. A crew of 6-10 people are responsible for bring the races to the public via timing and another 10-15 for race control, and we all take our work very seriously when the lights go out. The data is always analyzed and the correct information is put forth. There's nothing else I'd rather do.