Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Autocross\s+Timing\/Scoring\s+Software\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Autocross\s+Timing\/Scoring\s+Software\s*$/: 68 ]

Total 68 documents matching your query.

41. Re: Autocross Timing/Scoring Software (score: 1): Author: dennis@raceamerica.com; Date: Tue, 28 Sep 1999 09:52:22 -0700; John's point of having to reset the PC time-of-day is right on. A PC is driven by an interrupt system and the I/O ports where sensors are connected and the internal time-of-day clock are the lowest; /html/autox/1999-09/msg01829.html (11,422 bytes)
42. Re: Autocross Timing/Scoring Software (score: 1): Author: Paul Foster <pfoster@gdi.net>; Date: Wed, 29 Sep 1999 11:39:16 -0400; Dennis Laczny of RACEAMERICA Timing Systems states: <<<John's point of having to reset the PC time-of-day is right on. A PC is driven by an interrupt system and the I/O ports where sensors are connec; /html/autox/1999-09/msg01871.html (10,546 bytes)
43. Re: Autocross Timing/Scoring Software (score: 1): Author: "Clay Horste" <clay@metashock.com>; Date: Wed, 29 Sep 1999 11:07:18 -0500; Wouldn't environmental variables such as elevation, surface, humidity etc. give more accuracy error from event to event than the hardware or OS. I would think that as long as precise within the same; /html/autox/1999-09/msg01874.html (9,781 bytes)
44. Re: Autocross Timing/Scoring Software (score: 1): Author: dennis@raceamerica.com (racky@pop.iex.netdennis@209.238.91.186); Date: Wed, 29 Sep 1999 13:15:11 -0700; You are absolutely right, there are OSes and external clock devices which would provide accuracy from the raw PC clock. The raw PC clock is an accurate crystal controlled device. You must consider t; /html/autox/1999-09/msg01893.html (10,350 bytes)
45. Re: Autocross Timing/Scoring Software (score: 1): Author: dennis@raceamerica.com (racky@pop.iex.netdennis@209.238.91.186); Date: Wed, 29 Sep 1999 13:15:14 -0700; When you consider the big picture, I'd have to agree with your observation. Dennis; /html/autox/1999-09/msg01894.html (10,129 bytes)
46. Re: Autocross Timing/Scoring Software (score: 1): Author: dennis@raceamerica.com; Date: Wed, 29 Sep 1999 13:18:18 -0700; You are absolutely right, there are OSes and external clock devices which would provide accuracy from the raw PC clock. The raw PC clock is an accurate crystal controlled device. You must consider t; /html/autox/1999-09/msg01895.html (10,199 bytes)
47. Re: Autocross Timing/Scoring Software (score: 1): Author: Paul Foster <pfoster@gdi.net>; Date: Wed, 29 Sep 1999 16:23:43 -0400; There have been numerous times where millisecond resolution was necessary to determine the outcome of an autocross. Speaking of nitpicking there is a difference between precision and accuracy. What i; /html/autox/1999-09/msg01897.html (9,403 bytes)
48. Re: Autocross Timing/Scoring Software (score: 1): Author: Paul Foster <pfoster@gdi.net>; Date: Wed, 29 Sep 1999 16:24:42 -0400; If your software is dependent upon the clock speed of the processor it is flawed. IMHO Paul Foster; /html/autox/1999-09/msg01898.html (9,311 bytes)
49. Re: Autocross Timing/Scoring Software (score: 1): Author: "Steve Ashcraft" <ashcraft2@home.com>; Date: Wed, 29 Sep 1999 16:43:14 -0400; YES--And who cares if the timing equipment is 50% off if it is 50% off for all of the competitors and is always about 50% off for all of the events. The only interesting comparisons between drivers a; /html/autox/1999-09/msg01899.html (10,534 bytes)
50. Re: Autocross Timing/Scoring Software (score: 1): Author: "Steve Ashcraft" <ashcraft2@home.com>; Date: Wed, 29 Sep 1999 16:48:51 -0400; The IBM PC has a interval timer that is programmable to (and don't quote me on this) to 65,000 interrupts/second. This is the interrupt generator that generates the interrupts which Windows/DOS only; /html/autox/1999-09/msg01900.html (11,891 bytes)
51. Re: Autocross Timing/Scoring Software (score: 1): Author: Paul Foster <pfoster@gdi.net>; Date: Wed, 29 Sep 1999 16:58:41 -0400; This is exactly why I stated that precision is more important than accuracy. As long as a run of xx.yyy seconds is exactly the same duration for all competitors then the timer can do the job it needs; /html/autox/1999-09/msg01901.html (9,472 bytes)
52. Re: Autocross Timing/Scoring Software (score: 1): Author: Jeff Blankenship <jblanken@itds.com>; Date: Wed, 29 Sep 1999 16:31:29 CDT; '89 Nationals - I don't think I've heard that story. (groan from the audience, I'm sure) Yes, precision is more important than accuracy for this application, but really both are important. If you had; /html/autox/1999-09/msg01904.html (10,907 bytes)
53. Re: Autocross Timing/Scoring Software (score: 1): Author: "Steve Ashcraft" <ashcraft2@home.com>; Date: Wed, 29 Sep 1999 19:10:53 -0400; Yes it would be very "educational" to find out how these folks verify their etc. I very; /html/autox/1999-09/msg01906.html (11,694 bytes)
54. Re: Autocross Timing/Scoring Software (score: 1): Author: "John A. Carriere" <jacircts@mich.com>; Date: Wed, 29 Sep 1999 20:38:17 -0400; I agree with Dennis Laczny that a PC system can not provide accurate timing. It is a combination of the internal clock and the interrupt system. In the DOS environment, the kernel can be modified to; /html/autox/1999-09/msg01910.html (13,229 bytes)
55. Re: Autocross Timing/Scoring Software (score: 1): Author: "Steve Ashcraft" <ashcraft2@home.com>; Date: Wed, 29 Sep 1999 21:02:42 -0400; Very good point about the latency due to how fast the operating system responses to interrupts. Does anyone know how fast DOS responds to an interrupt on a serial port. Windows is way too busy to be; /html/autox/1999-09/msg01911.html (14,972 bytes)
56. Re: Autocross Timing/Scoring Software (score: 1): Author: dennis@raceamerica.com; Date: Wed, 29 Sep 1999 19:46:15 -0700; Given the points already discussed, there are faults to the hardware side that would be common to any timing system. For those interested in a technical discussion of the hardware, read on. The repe; /html/autox/1999-09/msg01917.html (11,510 bytes)
57. Re: Autocross Timing/Scoring Software (score: 1): Author: "Jeff Lloyd" <jslz3@hotmail.com>; Date: Thu, 30 Sep 1999 02:54:48 GMT; but Steve the Latency Is insignificant in a timing device enviornment, simply the latency will effect the start and finish beams equally, therefor recording the correct run time, kinda like extending; /html/autox/1999-09/msg01918.html (16,624 bytes)
58. Re: Autocross Timing/Scoring Software (score: 1): Author: Alan Dahl <adahl@eskimo.com>; Date: Wed, 29 Sep 1999 17:57:17 -0700; As P5 at the ProFinale proved very well. Imagine two drivers (myself and Kevin Bailey) tied to the thousandth of a second and a third driver (Matthew Braun) .002 seconds behind us! - Alan Dahl -- ___; /html/autox/1999-09/msg01926.html (9,633 bytes)
59. Re: Autocross Timing/Scoring Software (score: 1): Author: "Steve Ashcraft" <ashcraft2@home.com>; Date: Thu, 30 Sep 1999 05:39:55 -0400; What you said would be true if the latency is the same every time. This is the real problem. The timing heads do not respond exactly the same every time and the computer doesn't either. The latency; /html/autox/1999-09/msg01927.html (18,235 bytes)
60. Re: Autocross Timing/Scoring Software (score: 1): Author: "Mark J. Andy" <marka@telerama.com>; Date: Thu, 30 Sep 1999 10:16:43 -0400 (EDT); Sitting out here in the cheap seats (its been quite some time since I played with DOS and any sorta realtime stuff), I can't see how what DOS does or doesn't do would really matter, since you're gon; /html/autox/1999-09/msg01935.html (10,113 bytes)

Current List: 41 - 60
Page: [1] [2] [3] [4]