Home Racing World

On another board someone asked me about using an iPhone. Safari is listed above. You can also install Chrome on an iPhone. In short, this works with any device that has a web browser that supports Speech Synthesis.

It isn't an app, it doesn't have to be bought or installed- it uses the software already on your smart device.

Because of potential problems for international users during the registration process, the file has been temporarily removed. Hope to have it back in a day or two.

Appreciate the updates sir. Nice work. Lot of hours.

v2.2.0.2 is now available at the link given above. It changed the registration process to fix a potential problem for international users. Other than that, no change.

Although I did find out from someone who downloaded 2.201 that the display server and TeamRadio work with the Amazon Silk browser. He is successfully serving race information and race audio to his Fire tablets. So this software will work with an iPad or iPhone, an Amazon Fire tablet, an android tablet or android phone as well as any laptop or PC. As long as the device is using a recent version of one of the following web browsers:

Apple Safari
Chrome
Microsoft Edge
Firefox
Amazon Silk

The display server will also work with Opera and Internet Explorer- but neither of them will support the TeamRadio function.

Next on the to-do list: add the ability to choose different voices for the TeamRadio function. Currently only the default voice is available.

v2.220 is up:

1. During lap counted races, if the box was ticked to 'End race on checkered flag lap' (which is the default), once the winner crossed the Start/Finish, the race was over when all active cars completed their current lap. The problem: if a car ran out of fuel before completing it's current lap, the car had to enter the pit, refuel, and come all the way around for it's lap to count. This has been changed in this release. Now, after the winner crosses the start/finish, a car is considered to have finished the race if it completes it's current lap or runs out of fuel.

2. TeamRadio added some fuel calculations when nearing the end of the race. In timed races, it will give you an estimate at 1:00 and :30. In lap counted races, with 12 laps and 6 laps left.

3. There is now a heat clock visible on attached remote devices. It is a bright red count in the lower right. Count down for timed races, up for lap counted races. Updates every second, as remote devices receive updates 2-3 times per second.

4. The nag screen for registration has been moved to the end of the search for a timing device. It will appear roughly 2/3 of the time the search is conducted. Since the search is run automatically at program start, you will get the nag screen roughly 2/3 of the time. All features are available w/o registration, but registration automates a few things and, of course, eliminates the nag screen.

5. Because of a TeamRadio calculation, if a car entered the pits to refuel before completing a lap, a divide by zero error was possible.

6. The program now implements an autosave of any race rotation. So if you have 14 folks running 14 heats and a PC or track disaster strikes in the middle of heat 4, the next time the software is run, it will ask if you want to complete the race. It will start at heat 4 using the same rotation, rules, length, drivers, cars- virtually everything- as used for the three completed heats. So you will still get proper race totals and results at the end of your round robin.

7. In a December 2017 release, a bug was introduced that could cause a user's results file to show Dec 30, 1899 as the race date for all recorded races. As of this release, race results now once again show the actual date they are run.

My PC on the track is old and not connected to the internet. Can I register the software without internet connection?

Also, I used the new version, (not this one but the previous release) and it has an "easy mode". I was planning to try to find out what that means but maybe you could give a short explanation here?

v2.221 is up. This release is generally bug fixes and a few cosmetic improvements.

The next release (hopefully no interim bug fixes needed before 2.3) will be a semi-major upgrade, as it will include a new damage module. Every track call will give you the chance to assign damage points to vehicles. One would assume you'd assign them to the car that caused the track call, but it will be up to you. If you are using remote display devices, any device that issues a track call will automatically have the damage assigned to it's ID. That can be changed before the race is resumed at the race director's discretion. Damage will slow the car and can only be removed by pitting. Repair time will be adjustable.

First, two bugs were introduced in the last release and fixed in this one:

1. Basic lap times were not being reported properly in TeamRadio. Only new best laps were being announced. Fixed.

2. Stopping or starting the race from a remote connected device would freeze the remote device. You could refresh the webpage to get it working, but this meant you had to go through the selection screens again. This used to work fine, but was broken in the last release with the addition of the heat time clock on remote devices. Fixed.

The big change:

3. Users with new versions of CU firmware (5.336 and above) were experiencing occasional laps in the 4 million second range. The CU internal clock is/was being reset. To fix this, the CU clock is no longer the only timer used to calculate lap times. The CU time is now checked against the computer's clock which is used to calculate the heat length. On laps where the CU clock has reset, the computer's time will be used. This change also means that lap times generated during laps with a track call will now more accurately reflect the race time elapsed. In the past, they showed the CU clock's elapsed time, which means all of the "dead time" used to clear the track call was included in the lap time. Those lap times will now show just the elapsed time in the race as calculated by the computer.

4. The median lap displayed on the race screen and on remote devices was not always correct. With this release, the median has been abandoned and replaced with a 'typical' lap. This is the average lap time for all laps that did not include a pit stop. The median required more and more processor time as races got longer, since all of those times had to be sorted. Since there are no longer any lap times inflated by dead time during a track call, the average will now represent a useful number. I think it is *more* useful to average only those laps that do not include a pit stop. Of course if you run w/o fuel, this will be exactly the same as the average.

5. If you clicked 'Cancel' on the Intro screen and this was the first race to be run (and no practice session had been run), an error message was generated. You had to click the 'End Race' button to continue. Fixed.

6. On systems using two monitors, the registration form could appear split between the two. Fixed.

7. Connected Apple devices using Safari did not properly display the buttons for changing the car's speed and brake values. They worked, but they were confusingly ugly. Fixed. Which, obviously (consider the source!), doesn't mean they are now pretty- just that they are functional.

8. Added a 'False start/Yellow flag' audio notification when someone jumps the start.

9. The distance to leader ("To Lead" column on race display) was no longer displaying correctly. Fixed.

10. If more than one user called for a track call at the same time (e.g., multiple remote displays hit the pause button simultaneously), the countdown would start immediately. Now at least 1 second must elapse before a second track call will be acknowledged.

This is a fantastic program Bruce offers to the Carrera Digital world. We have 5 tracks in Cincinnati that use it. I highly recommend it. The $6 is nothing compared to the amount of hours involved. You get your money back in hours of entertainment. Thank you Bruce for making this available for all to use.

Bruce

That new damage module sounds amazing.

I am eagerly awaiting this.

A new version fixes a bug introduced with TeamRadio.
Event and penalty conditions could not be cleared if fuel was turned off.
Fixed in v2.2.2.2.

v2.223 is up. Fixes bug with cars leaving penalty not having their speed restored to normal. This bug only surfaced when fuel was turned off.

For anyone happening to read this who lives in a region that uses something other than the '.' as a decimal separator, I have found the bug that would display lap times as 7.089 instead of 7,089. If a zero followed the separator, the time was incorrectly displayed. May be a few days until I post the version with the fix.