ALLEYRATZ RACING

Since the lock wire is wire, we figured we could use it as a power tap since its there already. I was going to solder it to the rail but it was hard to get in test fitting so the test fit turned out to just be done.

I'm using a power tap hole in the track as my distance from power rail to shut down.

It's a toss up between the max and viper. I went back and forth a bunch of times. They are both unique in their own way. The continuous rail was my final choice. To be honest now that I actually see how everything goes together, if I had a table saw I like the kiwi gangs track. Especially now that I'm not scared about putting the rail in. Heck that was easy. Stay tuned for updates later today

This track is taking for ever to get together. Does decorating count as track set up lmaooooo.

May have to give Race Coordinator a try some time.

I got a new version to try out Mike. He said try at your own risk so let me be the tester and if it's good I'll put it up for everyone.

What I'm finding is segment sensors can read more than once, so they can get tripped multiple times. When they are tripped more than once it gives a crazy reading in all the segments. Start and finish are never effected so those are always correct just the segments get wacky. I tried like he'll to get him to have the sensors read once but no go. Main problem is he don't drag race or do slot cars. He says if he makes it trigger once ,then if we accidentally set off a sensor it will still mess the reading up. I said we'll it's alot harder and almost impossible to set it off accidentally but very easy to get more than one reading. He's just not understanding that.

I sent some screen shots to him of the glitch. We'll I guess when the program was written they didn't account for us running cars under a .5 et. That began us once again playing with Debounce. Now playing with Debounce you can dial in a car to register correct but what works on one car may not work on a different car. So playing with Debounce is not the answer I told him.
Running a race I can't be playing with Debounce between classes. He ended up writing this new version that does something with Debounce automatically to prevent a double reading on the same sensor. He has nothing to test the program but believes it will work for us. I told him I'll get back to him this weekend.

Communication is a bit of a hang up.
You can tell he is all about computers and computer language where I am not. Then when I talk about dragracing and slot cars I can tell he's not there.
So it's been a little tough on both are parts.

Worse comes to worse we can always just run the start ,finish and one segment sensor for an event but I'd really like them all working.

Also I have been playing around with the speed trap. I added a sped trap sensor 12 inches before the finish line.
The way drag race coordinator works is for segments it goes by start to the segment then gives you a mph to that segment. Then the last segment will read from the last segment to finish for mph. If you only have 1 segment, in the segment box is the mph from start to segment then in et it will show mph from seg to finish.

I've tried the speed trap as last sensor. I've tried 660 as last sensor and I tried 330 as last sensor. All have given me dam near the same mph in the E.T box. My thinking now is just ditch the speed trap I put in and just use the 660 sensor since they show the same anyway and maybe save some others some time if they are using drc because you won't need a speed trap saves on sensors wiring and a light above for the sensor.

Sam i have start,60, 660, finish. I had on occasion the 660 would only be a couple thousand difference from the 60, but everything else was ok. It didn't happen very often and i thought it was probably rfi. After messing with it awhile i have determined the 60 occasionally double trips. I have some ideas and will try some things this weekend.