expand the use of RFID [done v5.22]

After having implemented and tested the RFID driver change solution we are very impressed, this works perfectly and the RFID offers a lot of extra features that could be used in both digital and analog racing, here my thoughts:

1. if we install an RFID reader at each driver station the driver could be inserted automatically in the heat of PCLC - no longer necessary to setup races manually2. drivers could have a card for each car they race, when using this all laptimes from the past could be automatically put in a database and this way give great information about setup progress etc.

Is i very difficoult to implement further functions to the RFID side of PCLC?

I think those are both great ideas. I was also wondering if you are doing a team race, with 4 teams ( 4 lanes analog) do I need an RFID reader for each lane to change drivers, or will one reader automatically change drivers since the program knows what team they are on ?

Since RFID chips are so cheap now, less then a dollar, and tiny, I would love the option to glue one into the chassis of all the 1/24th cars, so you just hold the car up to the reader and it populates the race. Maybe I`ll add a reader under every lane !?Thanks to PC Lap Counter we can do some really neat stuff.

Simply because I'd like to be able to have an RFID interface if I sell a new ID Card on by the main PC, and a 2nd one for dealing with any enurance challenges etc, which would be suited for driver changeovers.

Only possible bug I've come across is sayDriver "A" moves from Lane B to Lane C.

Then when i try to allocate a new driver, driver "B" to Lane B, I get the error buzz. I had a nosey at the manual update screen, and it turns out I had two instances of Lane C, one of which overwrote Lane B. Manually changing it so I had one instance of each lane seemed to fix the issue, but obviously when drivers hop between lanes could be an issue in heat based races.

However, I do note that you say it's partially done so I was expecting a couple of hiccups.

Only possible bug I've come across is sayDriver "A" moves from Lane B to Lane C.

Then when i try to allocate a new driver, driver "B" to Lane B, I get the error buzz. I had a nosey at the manual update screen, and it turns out I had two instances of Lane C, one of which overwrote Lane B. Manually changing it so I had one instance of each lane seemed to fix the issue, but obviously when drivers hop between lanes could be an issue in heat based races.