Ticket
| Project | RCM Ultimate |
|---|---|
| Summary | Handling of new CarId value from RC4 transponder |
| Sequence | 1219 |
| Classification | Change Request |
| Priority | Medium |
| Status | Done |
| Kickoff date | Jun 10, 2013 |
| Maturity date | Jun 10, 2013 |
| Responsible | |
| Version | 2.0.1 |
| Expense | 0 |
| Description | My son was registered in the software with Tx 4577740 and timed with this transponder on previous races. However this is a car_ID tranponder (#3) and the club installed the new version of your software last week in which you implemented car_id. On the first session last weekend the system did not record my sons laps, as the system was detecting 4577740-3 while he was registered with 4577740-0. We fixed it for the following sessions, by adding the correct car_id.
Current situation is that a racer who now buys and uses an extra car_id transponder is "punished" even though his base number is known in your system. The idea behind car_id is that all transponders with same base number belong to the same person. So in case you see a number on the track with a base number that is assigned to a racer, I think you should use that transponder for that racer. Only in case of 2 car_id transponders with same base number on the track, should the operator be informed and asked which car_id should go to which racer. |
Change history
| Timestamp | Who | Modification |
|---|---|---|
| Jun 10, 2013 2:53:47 PM | Ticket created | |
| Jun 10, 2013 2:53:52 PM | Felix Romer | Field: StatusOld value: Opened New value : Running |
| Jun 21, 2013 7:12:31 AM | Felix Romer | Field: StatusOld value: Running New value : Done |

Always there for you - support response time of max. 24 hours