Looking forward to the sector time addition :) At this stage, a full drag race timer might be feasible, with start line sensors giving reaction times, an optional half track split time, but then jiggling the code to have 2 sensors close together at the track end for an actual speed trap (known distance/time = speed). The 2nd speed trap sensor would also be the "end of lap" sensor so could be parallelled with the start line sensor. There's a few drag racers out there, especially with the current Autoworld drag sets which only give a win light. To anyone not familiar with Dave's work, he's been building Race Coordinator for ages and working very closely with several races around the world, to implemement a HUGE amount of functionality into the software. We've successfully run fuel/pitstop races and built all sorts of LED indicators for various functions here in Perth, Western Australia. I'm not affilliated with Dave or Viasue etc in any way, just followed the RC development from the start and am amazed at what it's become. Hats off to ya mate.
Thanks and sorry for the slow response. I'm much faster responding to forum posts over at SlotForum.com. FYI, RC can be bent into doing a drag strip fairly easily, but I'm working on "RCDrag" which is an RMS built specifically for drag racing. No ETA on it but its bound to happen eventually.
Thanks for this Dave, we use and love Race Coordinator and it is amazing! I was wondering if there is a way to have multiple segments? I would love 3 segments on my setup if it is doable?
@daufderh thanks, I will have to try work out how to add the extra sensors as i couldnt see an option for it in the arduino configuration, I guess its somthing I have to add myself? Having the extra sectors in the timing will be amazing, Thanks for the reply!
If I recall you just setup each segment pin a segment sensor is on as a segment sensor. So they all use the same configuration except on different pins. RC doesn't order the segment sensors, which can be a problem if you miss one when running a lap but that's the way it is.
Hey Dave, glad to see RC has this now. I was checking old emails from back when I asked for it. One of my original visions was to have 10 sectors (nine plus the startline) so that manually putting in the parts of a lap after a heat would no longer be necessary. As well as each bridge being a speed trap and means to calculate elapsed time between sectors, they'd enable the software to 'put the parts in itself'. Does your prog in fact do this? Also, I note on this vid the race day screen shows only one sector, and wipes to the latest each time the car passes under a new one. Can that screen show more than 1 sector? Does the data dump show all the sector times for a heat?
Segment timing is really for display only. RC does nothing with the data other than displaying it on the screen and exporting it to xls. Realtime RC will show the segment time between each segment except the last segment and the start line. This is because the next lap starts basically showing its segment times. If you want to see all the segment times for a lap you can use a XAML like the practice lap xaml. It shows the last N laps and shows up to 3 segment times for each lap, but could be changed to show 10 or more if you wanted. You can't display MPH between segments. That would require configuring distance between the segments and I don't allow you to do that to keep things simple.
@@daufderh Thanks. Does the xls show *all* the segment times? Is there raceday XAML able to show each sector, if you have, say, three with the startline (ie F1 style)? Is my idea of using segments to automate part laps something you'd consider?
@@deanewalpole9577 The practice screens will show up to 3 segment times per lap. Any of the XAMLs can be modified to show as many as you want. The xls export shows all the segment times no matter how many you have. I'm not thinking about using segment times for anything "real". As done right now if a segment is missed, the time simply goes into the next segment. So your data is a little weird but there are no other issues. If we start using it for things like auto segments we need to guarantee they trigger and trigger in the right other. Right now I don't do any of that.
@@daufderh Thanks. So, when a car goes under the, say, 6th bridge, there is no way for RC to 'know' it is the 6th one - if the car misses a bridge during the lap RC will think the 6th bridge is in fact the 5th one?
Looking forward to the sector time addition :)
At this stage, a full drag race timer might be feasible, with start line sensors giving reaction times, an optional half track split time, but then jiggling the code to have 2 sensors close together at the track end for an actual speed trap (known distance/time = speed). The 2nd speed trap sensor would also be the "end of lap" sensor so could be parallelled with the start line sensor.
There's a few drag racers out there, especially with the current Autoworld drag sets which only give a win light.
To anyone not familiar with Dave's work, he's been building Race Coordinator for ages and working very closely with several races around the world, to implemement a HUGE amount of functionality into the software.
We've successfully run fuel/pitstop races and built all sorts of LED indicators for various functions here in Perth, Western Australia.
I'm not affilliated with Dave or Viasue etc in any way, just followed the RC development from the start and am amazed at what it's become. Hats off to ya mate.
Thanks and sorry for the slow response. I'm much faster responding to forum posts over at SlotForum.com. FYI, RC can be bent into doing a drag strip fairly easily, but I'm working on "RCDrag" which is an RMS built specifically for drag racing. No ETA on it but its bound to happen eventually.
I now have "Drag Race Coordinator" which is a totally different application specific to drag racing. It has everything you're looking for.
Thanks for this Dave, we use and love Race Coordinator and it is amazing! I was wondering if there is a way to have multiple segments? I would love 3 segments on my setup if it is doable?
You can have as many as you want. You might have to customize your race screens to see all the data real time but any number of them will work.
@daufderh thanks, I will have to try work out how to add the extra sensors as i couldnt see an option for it in the arduino configuration, I guess its somthing I have to add myself? Having the extra sectors in the timing will be amazing, Thanks for the reply!
If I recall you just setup each segment pin a segment sensor is on as a segment sensor. So they all use the same configuration except on different pins. RC doesn't order the segment sensors, which can be a problem if you miss one when running a lap but that's the way it is.
@daufderh excellent, I understand the mission! Will give that a go, thats for the help!
Hey Dave, glad to see RC has this now. I was checking old emails from back when I asked for it. One of my original visions was to have 10 sectors (nine plus the startline) so that manually putting in the parts of a lap after a heat would no longer be necessary. As well as each bridge being a speed trap and means to calculate elapsed time between sectors, they'd enable the software to 'put the parts in itself'. Does your prog in fact do this? Also, I note on this vid the race day screen shows only one sector, and wipes to the latest each time the car passes under a new one. Can that screen show more than 1 sector? Does the data dump show all the sector times for a heat?
Segment timing is really for display only. RC does nothing with the data other than displaying it on the screen and exporting it to xls. Realtime RC will show the segment time between each segment except the last segment and the start line. This is because the next lap starts basically showing its segment times. If you want to see all the segment times for a lap you can use a XAML like the practice lap xaml. It shows the last N laps and shows up to 3 segment times for each lap, but could be changed to show 10 or more if you wanted. You can't display MPH between segments. That would require configuring distance between the segments and I don't allow you to do that to keep things simple.
@@daufderh Thanks. Does the xls show *all* the segment times? Is there raceday XAML able to show each sector, if you have, say, three with the startline (ie F1 style)? Is my idea of using segments to automate part laps something you'd consider?
@@deanewalpole9577 The practice screens will show up to 3 segment times per lap. Any of the XAMLs can be modified to show as many as you want. The xls export shows all the segment times no matter how many you have. I'm not thinking about using segment times for anything "real". As done right now if a segment is missed, the time simply goes into the next segment. So your data is a little weird but there are no other issues. If we start using it for things like auto segments we need to guarantee they trigger and trigger in the right other. Right now I don't do any of that.
@@daufderh Thanks. So, when a car goes under the, say, 6th bridge, there is no way for RC to 'know' it is the 6th one - if the car misses a bridge during the lap RC will think the 6th bridge is in fact the 5th one?
@@deanewalpole9577 Correct. That's by design to keep things simple
Hi I am going through all TH-cam info .
And I can not find any info on rc boat racing timing and scoring system.
Using transponder. Can you help???
Sorry, RaceCoordinator does not work for RC boat racing with transponders. It's for Slot Car racing.
I want to hear cars zooming by every time a lap is completed and some crowds cheering sometimes
You can add any sounds you want when a car crossed the SF line. You just have to be careful what you do as it can get noisy fast
You can change all the default audio to anything you want so playing crowds cheering is easy enough if you have the audio track.