This is a static archive of our old forum. Most features inc files and downloads work but some links are now dead
Please refer to Our Website or our Facebook Groupfor latest info.
Please refer to Our Website or our Facebook Groupfor latest info.
timing tag position
- dralphs
- Site Admin

- Posts: 553
- Joined: Fri Nov 14, 2014 11:50 pm
- Location: Oxford
- Team: Falcon Notnray
- Contact:
Re: timing tag position
removed fitting from the word censor, it was matching FITT* for some reason. No idea what context or slang that is.
- Mark Williams
- Site Admin

- Posts: 200
- Joined: Tue Aug 26, 2014 6:58 pm
- Location: East Yorkshire
Re: timing tag position
I think this might start to be a bit of a chase to get to(wards) 'counted every lap' heaven...
I'd got myself thinking that with the previous Identec input to get the parallel loops in place, using the system as designed to pick up counts with the second chance arrangement was at least one variable to discount. Where I'm stuck now is the fact that on occasion yes when multiple cars travel over the matt we lose one of them, the greater concern is that also on occasion a single car without anything seemly untoward travels over the matt, there's no beep. Nothing. Madness!
So back to basics, what goes awry in the simplest of situations?
Matt to Tag or Tag to Matt.
Matt says Hello. Tag wakes. Tag says Hello. Matt says Gotcha.....
Matt says Hello. Tag doesn't wake. Matt says Hello again (2nd Loop). Tag wakes. Tag says Hello. Matt says Gotcha.
Matt says Hello. Loop one gone. Tag wakes. Loop Two gone... missed at max 25mph.
Given we have two matts and as long as both can be "nailed" down with sticky tape in all weathers, I have wondered if Matt One Loop One could be used with Matt Two Loop Two. Currently as Dave said to me on Saturday, we would return to a narrower 5m set up. But would the longer active area help to counter the issues?
I was rather narked by the swebbelli tag position situation. Laying 45 degrees fixed at the top but now able to pivot to the horizontal is asking for trouble. Yes ok, it's been like that for the season but when in that moment it ain't working, best thing is to go back to first principles. Vertical and widest effect, palm forward if you like. I do think that fixed should mean fixed. No give to wobble, bounce or wander. Should this become the default requirement within 3inches of the ground without anything else between it and the loop?
In a lab we could remove all extraneous kit but clearly we'll always be fighting that.
I would also go along with Dave and the idea that the loop settings need to be "tuned".
That's me for starters...
I'd got myself thinking that with the previous Identec input to get the parallel loops in place, using the system as designed to pick up counts with the second chance arrangement was at least one variable to discount. Where I'm stuck now is the fact that on occasion yes when multiple cars travel over the matt we lose one of them, the greater concern is that also on occasion a single car without anything seemly untoward travels over the matt, there's no beep. Nothing. Madness!
So back to basics, what goes awry in the simplest of situations?
Matt to Tag or Tag to Matt.
Matt says Hello. Tag wakes. Tag says Hello. Matt says Gotcha.....
Matt says Hello. Tag doesn't wake. Matt says Hello again (2nd Loop). Tag wakes. Tag says Hello. Matt says Gotcha.
Matt says Hello. Loop one gone. Tag wakes. Loop Two gone... missed at max 25mph.
Given we have two matts and as long as both can be "nailed" down with sticky tape in all weathers, I have wondered if Matt One Loop One could be used with Matt Two Loop Two. Currently as Dave said to me on Saturday, we would return to a narrower 5m set up. But would the longer active area help to counter the issues?
I was rather narked by the swebbelli tag position situation. Laying 45 degrees fixed at the top but now able to pivot to the horizontal is asking for trouble. Yes ok, it's been like that for the season but when in that moment it ain't working, best thing is to go back to first principles. Vertical and widest effect, palm forward if you like. I do think that fixed should mean fixed. No give to wobble, bounce or wander. Should this become the default requirement within 3inches of the ground without anything else between it and the loop?
In a lab we could remove all extraneous kit but clearly we'll always be fighting that.
I would also go along with Dave and the idea that the loop settings need to be "tuned".
That's me for starters...
Mark
BFPCR Treasurer
East Yorkshire
BFPCR Treasurer
East Yorkshire
- dralphs
- Site Admin

- Posts: 553
- Joined: Fri Nov 14, 2014 11:50 pm
- Location: Oxford
- Team: Falcon Notnray
- Contact:
Re: timing tag position
I've a feeling its the old tolerance issue.
When all the tolerances are in your favour it works really well, when they are all against you its then you shear the critical bolt 2 minutes before race start
looking at Curborough cars doing 25km/H were dropping laps, slower cars seemed less affected. The census manual suggests a 2.5m loop width for 50km/H so presume (as there isn't a table) that you need approx 1.25m for 25km/H. We have about 600mm - gap - 600mm so speed could well be one factor.
Think we must set a reg that clarifies where and how the tag must be fitted and it must be away from moving parts and lights.
We then look to minimise interferance affecting the mat from gantry, monitor etc during setup
Then over winter we need to experiment with mat loop config to give us best reading ability. I suggest laying out a test loop in scout hut or car park. Over this loop run a taut string running around two pulleys so we can "run" a tag over the loop at a consistent height and speed. Then experiment to see what gives most consistent reading for spped against loop size.
Could be a nice science experiment for a school class
It would help if we knew what data is sent by the census box apart from tag id. mark can you enquire please.
When all the tolerances are in your favour it works really well, when they are all against you its then you shear the critical bolt 2 minutes before race start
looking at Curborough cars doing 25km/H were dropping laps, slower cars seemed less affected. The census manual suggests a 2.5m loop width for 50km/H so presume (as there isn't a table) that you need approx 1.25m for 25km/H. We have about 600mm - gap - 600mm so speed could well be one factor.
Think we must set a reg that clarifies where and how the tag must be fitted and it must be away from moving parts and lights.
We then look to minimise interferance affecting the mat from gantry, monitor etc during setup
Then over winter we need to experiment with mat loop config to give us best reading ability. I suggest laying out a test loop in scout hut or car park. Over this loop run a taut string running around two pulleys so we can "run" a tag over the loop at a consistent height and speed. Then experiment to see what gives most consistent reading for spped against loop size.
Could be a nice science experiment for a school class
It would help if we knew what data is sent by the census box apart from tag id. mark can you enquire please.
Re: timing tag position
I am going to get possibly slammed for this but...
Do the teams racing very hard at the front for overall or class position simply watch the timing a lot closer than others my perhaps do?
At the end of Curborough, we had the top 3 cars covered by 12 laps which is about 1 second per lap difference between all 3.
(Car 1 averaged 65.63s; car 2 66.66 and car 4 67.74s).
Where the gaps are bigger and the racing perhaps a little less intense perhaps people simply don't notice the occasional dropped score?
However, with an average speed well over 20mph the cars are probably touching 30 on that bit of track and it is the fastest loop position in the championship. Not that it can be sensibly moved at Curborough - we had it across the far side one year and it was a bit of a nightmare!
Do the teams racing very hard at the front for overall or class position simply watch the timing a lot closer than others my perhaps do?
At the end of Curborough, we had the top 3 cars covered by 12 laps which is about 1 second per lap difference between all 3.
(Car 1 averaged 65.63s; car 2 66.66 and car 4 67.74s).
Where the gaps are bigger and the racing perhaps a little less intense perhaps people simply don't notice the occasional dropped score?
However, with an average speed well over 20mph the cars are probably touching 30 on that bit of track and it is the fastest loop position in the championship. Not that it can be sensibly moved at Curborough - we had it across the far side one year and it was a bit of a nightmare!
- AlanGoodman
- Site Admin

- Posts: 424
- Joined: Thu Nov 06, 2014 9:13 am
- Location: Hemel Hempstead
- Team: Apollo Racing
- Contact:
Re: timing tag position
I think there is probably a lot of truth in that!!!!
- dralphs
- Site Admin

- Posts: 553
- Joined: Fri Nov 14, 2014 11:50 pm
- Location: Oxford
- Team: Falcon Notnray
- Contact:
Re: timing tag position
In our experience i'd say yes
We do look at the times, but don't count laps as such unless either its obvious we've dropped several or its close between us and our competition.
We do look at the times, but don't count laps as such unless either its obvious we've dropped several or its close between us and our competition.
- AlanGoodman
- Site Admin

- Posts: 424
- Joined: Thu Nov 06, 2014 9:13 am
- Location: Hemel Hempstead
- Team: Apollo Racing
- Contact:
Re: timing tag position
When we were running as Goodmaniacs I don't think we ever even looked at it until near the end of the race to see who was near to us.
- dralphs
- Site Admin

- Posts: 553
- Joined: Fri Nov 14, 2014 11:50 pm
- Location: Oxford
- Team: Falcon Notnray
- Contact:
Re: timing tag position
This is what i was thinking of for testing loop config and speed
It gives us consistancy, we can change the height and speed and loop size, but crucially can repeat the tests.
It gives us consistancy, we can change the height and speed and loop size, but crucially can repeat the tests.
Re: timing tag position
None of the top three cars dropped laps after 7:15PM. I don't know enough about EMC to postulate on the wiring issue except to say that we only had power to the gantry lights by the start of the race and nothing else. Its worth considering we have never used this mat at Curborough in anger before and I doubt we've been crossing the line at these speeds all year. It was super fast conditions and the wind was marginally helpful down the straight. the old mat, as we know, has a much wider loop.
Or, my instinct would question whether both loops were functioning fully, given how relatively severe the issue suddenly was across many of the lead cars.
Or, my instinct would question whether both loops were functioning fully, given how relatively severe the issue suddenly was across many of the lead cars.
- dralphs
- Site Admin

- Posts: 553
- Joined: Fri Nov 14, 2014 11:50 pm
- Location: Oxford
- Team: Falcon Notnray
- Contact:
Re: timing tag position
I will do some testing when i get chance in next few weeks and hopefully have some insight and a suggestion before the agm.
We may need to change the new mat to loops like the old on had and revert the old mat back as well (yes it was changed to one loop after the other as well)
At least we now have time to experiment, even if i have to lay it across our road, put tag on the volvo and drive over it at 30mph
We may need to change the new mat to loops like the old on had and revert the old mat back as well (yes it was changed to one loop after the other as well)
At least we now have time to experiment, even if i have to lay it across our road, put tag on the volvo and drive over it at 30mph
Re: timing tag position
Jes has a very good point - and a total nightmare for the amazing people who do the lap scoring. There were several really key battles on Saturday: 2 vs 1, 2 vs 4, 8 vs 22 etc.
Its just not practical for one or two to be picking up missed beeps AND making corrections for 20 - 30 cars. something is going to get missed through no-one's fault.
So yes as with all good systems solutions we need two fronts to this. One is ever improvement of the system (the new equipmemt is generally a big step forward). Secondly I want to quietly look at whether my post-race analysis can in anyway be replicated in near real-time.
I hasten to add I can never ever envisage auto corrections - that would be a recipe for disaster - but some additional flagging or logging of potential missed laps - rather than the counters having to refer a missed 'beep' to the last or penultimate lap time. This could then be referred to when / if a team comes and says "we think that..."
I will see what happens.
Its just not practical for one or two to be picking up missed beeps AND making corrections for 20 - 30 cars. something is going to get missed through no-one's fault.
So yes as with all good systems solutions we need two fronts to this. One is ever improvement of the system (the new equipmemt is generally a big step forward). Secondly I want to quietly look at whether my post-race analysis can in anyway be replicated in near real-time.
I hasten to add I can never ever envisage auto corrections - that would be a recipe for disaster - but some additional flagging or logging of potential missed laps - rather than the counters having to refer a missed 'beep' to the last or penultimate lap time. This could then be referred to when / if a team comes and says "we think that..."
I will see what happens.
- dralphs
- Site Admin

- Posts: 553
- Joined: Fri Nov 14, 2014 11:50 pm
- Location: Oxford
- Team: Falcon Notnray
- Contact:
Re: timing tag position
Chris
i don't know enough about the software Phil has built, but certainly it should be possible to set a delta lap time for each car and then if the next tag count doesn't occur within 75% to 150% of that time to highlight that as a suspected dropped lap.
Race control would have to confirm it or ignore it since as we know it could be a slow lap for various reasons
Phil has also suggested two tags per car, preferably in different locations and then use software to make sure teh car is only counted once.
i don't know enough about the software Phil has built, but certainly it should be possible to set a delta lap time for each car and then if the next tag count doesn't occur within 75% to 150% of that time to highlight that as a suspected dropped lap.
Race control would have to confirm it or ignore it since as we know it could be a slow lap for various reasons
Phil has also suggested two tags per car, preferably in different locations and then use software to make sure teh car is only counted once.
-
Darren Carter
- Provisional Driver

- Posts: 40
- Joined: Sat Nov 15, 2014 11:36 pm
Re: timing tag position
My technical knowledge of this is literally non existent, but I do recall Neil was surprised to see the one loop on the mat when rolling it out at Solihull and thought it may not be as effective as the original one (I still have painful memories of us both in the front garden making the original mat, me with a pot of glue in my hand!). But saying that, it didn't drop too many laps at Solihull and cars were crossing that at quite a high speed.
- dralphs
- Site Admin

- Posts: 553
- Joined: Fri Nov 14, 2014 11:50 pm
- Location: Oxford
- Team: Falcon Notnray
- Contact:
Re: timing tag position
I've just looked at the spreadsheet from curborough and checked the 1st 3 cars no. 1, 2 & 4
Drops were inconsistent, not regular intervals and the cars didn't drop at same time.
Interestingly as hinted at above, the drops tailed off after 6pm.
Looking at all rounds/races and taking the best speed and approx total drops
wombwell 21mph 1 drop
wombwell 21.5mph 1 drop
brunt 19.5mph a few drops until we had usb issue then stabilized
shen 21mph 25+ drops
solihull 25.5mph 15 drop
solihull 25.2mph 11 drop
solihull 23.6mph 7 drop
blackbushe sat1 22.5mph 1 drop
blackbushe sat2 22.4mph 1 drop
blackbushe sat3 21.8mph 0 drop
blackbushe sat4 21.4mph 0 drop
blackbushe sat5 22.4mph 2 drop
blackbushe sund 21.7mph 7 drop
curborough 23.4mph 30+ drops
I can't say for sure, but what time was the remote monitor turned off at curborough end of race or when it got dark say 7pm?
From memory the remote monitor was close to the mat at shenington, solihull & curborough. Might be clutching at straws but you never know.
Drops were inconsistent, not regular intervals and the cars didn't drop at same time.
Interestingly as hinted at above, the drops tailed off after 6pm.
Looking at all rounds/races and taking the best speed and approx total drops
wombwell 21mph 1 drop
wombwell 21.5mph 1 drop
brunt 19.5mph a few drops until we had usb issue then stabilized
shen 21mph 25+ drops
solihull 25.5mph 15 drop
solihull 25.2mph 11 drop
solihull 23.6mph 7 drop
blackbushe sat1 22.5mph 1 drop
blackbushe sat2 22.4mph 1 drop
blackbushe sat3 21.8mph 0 drop
blackbushe sat4 21.4mph 0 drop
blackbushe sat5 22.4mph 2 drop
blackbushe sund 21.7mph 7 drop
curborough 23.4mph 30+ drops
I can't say for sure, but what time was the remote monitor turned off at curborough end of race or when it got dark say 7pm?
From memory the remote monitor was close to the mat at shenington, solihull & curborough. Might be clutching at straws but you never know.
Re: timing tag position
The monitor was on all race - I took a phone picture of it after the flag dropped. Dave are these crossing speeds? Solihull is the fastest track but the mat is at the top of the hill from wherever you come. Having said that, Wombwell clockwise is pretty fast across there...

