It sounds like you might have heats assigned by class. Keep in mind
that there can be a heat "zero". Try to clear the run/work heat
assignments.
This is from the autox/TS manual:
3 ... Event Control Menu
1 ... Assign Run Heats by Class
If your event is run in heats assigned by class, you can use this option
to automatically set the run heat of all drivers in a class (or a group
of classes). You may need to remove the heat assignment for those
driver's not competing.
Type in the class names to assign to a particular heat, separating the
classes with commas (i.e. AS,BS,CS). In the Heat field, type the run
heat for these classes, then hit [F7] to assign heats.
2 ... Assign Work Heats by Class
If you assign work heats by class, this option automatically sets the
work heat of all drivers in a class (or a group of classes). You may
need to remove the work heat assignment for those driver's not
competing.
Type in the class names that you want to assign to a work heat,
separating the classes with commas (i.e. AS,BS,CS). In the Heat field,
type the work heat for these classes, then hit [F7] to assign heats.
3 ... Clear Run/Work Heats and Work Assignments
This option allows you to clear the Run/Work Heats and Work Assignments
in the driver file. You can run this option on selected drivers using
the following selection fields.
Paul Andrews
# 42 STX2 Really Blue 94 Miata
------------------------------
Date: Tue, 31 May 2005 11:23:24 -0400 (EDT)
From: Mark Andy <mark@sccaprepared.com>
Subject: AutoX/TS weirdness... Help!
Howdy,
At our events this past weekend, we saw some autoX/TS weirdness... I was
hoping someone had run into it before and could tell us what we're doing
wrong.
We registered everyone for the event, assigning all entrants to run heat
1. We also had some drivers with no heat assignment who weren't at the
event. Then we run the heat assignment wizard to figure out and assign
the heats for everyone.
Some classes were apparently being left off the heat assignment wizard
altogether, weren't assigned a run heat, etc.
We can't really figure out what we're doing wrong here and this is the
first time we've had this issue in the last few years we've been running
autoX/TS.
Stuff that's different from last year (when we didn't have these
problems)... I've re-entered all the classes, supplying a new name
(with
up four characters, since we don't have mirrored ladies classes), no
extended class names, and two "local" indexed classes with single letter
identifiers.
Anyone know of any bugs related to four letter classes or multiple
indexed
classes or ??
Thanks!
(we'd also like to hear recommendations for other timing systems that
have
AutoX/TS's general functionality for event setup, grid/manual recording
sheets, interoperation with a JACircuits timer w/ChronoMode, etc. but
that
supports a windows interface & windows printer drivers, and perhaps uses
some kinda JDBC compliant backend db so that we can more easily write
points generation software, etc. I've not heard a resounding
recommendation for any software yet (or if it was resounding, there was
an
equally resounding recommendation against it)).
Thanks a ton!
Mark
SCR Solo Chair
------------------------------
End of ax-digest V1 #1612
*************************
|