Release date: 17th November 2012
(1) Added ‘No Decimal’ in “Settings”. When on, you can save time by entering distances and speeds (only kmph, not minutes) without the decimal place. e.g. 43.85 can be entered by pressing , , , , [EXE]. Any distance or speed (kmph only) value which has more than 3 digits and without a decimal point will have a decimal automatically placed. Default is off.
(2) Press [VARS] in “Rally” to goto “Penalties”.
(3) Option to show whether penalties are ‘late’ or ‘early’. Default is off.
(4) Option to show penalties in HH:MM:SS format. Default is on.
(5) Made speed change warning configurable. Default is 200m.
(6) [F4] in “Settings” reverts all settings to default values.
We are a bunch of rally navigators, software developers and rock stars who are passionate about TSD rallying.
It was exactly a year ago that we discovered the FX9860GII. We were thrilled of course; this was the first piece of programmable hardware that fit all our requirements. Big numeric keyboard, inexpensive, large screen, battery life that ran into days. While programming in BASIC was the easy way to go, we knew from the beginning that our product had to have a kickass UX and that BASIC was not up to the task. C and ASM it was, and after dusting off the old K & R and with a little prayer to the pointer Gods, we wrote the first main() we had in more than 20 years.
Half a bottle of Old Monk and five Pearl Jam albums later, the alpha version of TSDMeter was born.
We knew ‘TSD Rallying’ was a niche market. There was no money to be made making a product for it and we had no business plan or model. But we did have a clear goal: ‘make TSD Rallying an easy sport to get into’. After more than 9000 lines of code, many iterations to the product, countless rally wins and helping many a novice come into the sport, we are proud to have lived up to that goal!
But the success is not ours alone, it is yours too, our passionate customers! It is you who helped us through all of last year to improve the product and market it.
“We are all rockstars” -:)
1st – Satish Gopalkrishnan / Savera D’Souza (PRO)
2nd – Ganesh Murthy / Nagarajan (BASIC PLUS)
3rd – Sanjay Takale / Mohd. Musthafa (PRO)
4th – Karthik Maruthi / Shankar Anand (BASIC)
1st – Suresh Kumar / Bhaskar Gupta (PRO)
2nd – A K Ramesh / Raja Natarajan (BASIC)
3rd – Gopalakrishnan / V Sekar (BASIC)
2nd – Wilson Padayattil / Kuriakose Elias Paarel (PRO)
3rd – Vijayakumar / Murugan (BASIC)
1st – Philip Balkin / David Sharon (PRO)
2nd – Sudharshan / Gunashekar (PRO)
1st – Sandeep Dodhiwala / Mudra Dodhiwala (BASIC)
Congratulations to all the winners!
All programmable calculators support the BASIC language (albeit in different flavours). It is trivial to implement TSD functionality in BASIC. Below is the listing of a rudimentary program that calculates ideal times for a given speed chart (test it here):
020 INPUT "Total speed zones: "; N
030 DIM BE(N)
040 DIM EN(N)
050 DIM SP(N)
060 BE(0) = 0
070 FOR I = 0 TO N - 1
080 PRINT (I + 1); " of "; N
090 PRINT "Begin (KM): "; BE(I) / 1000
100 INPUT "End (KM): "; EN(I)
110 INPUT "Speed (KMPH): "; SP(I)
120 SP(I) = SP(I) * 1000
130 EN(I) = EN(I) * 1000
140 IF I < N - 1 THEN BE(I + 1) = EN(I)
160 INPUT "Start time at TC (HH): "; HH
170 INPUT "Start time at TC (MM): "; MM
180 INPUT "Start time at TC (SS): "; SS
190 INPUT "ODO reading at TC (KM): "; KM
200 KM = KM * 1000
210 INPUT "Distance (KM, 0 for TC): "; D
220 IF D = 0 THEN GOTO 160
230 D = D * 1000
240 SECS = 0
250 PRSD = 0
260 PART = 1
270 J = 0
280 GOTO 370
290 PART = 0
300 GOTO 440
310 DT = EN(I) - KM
320 PART = 1
330 GOTO 420
340 SECS = SECS + (DT / SP(I))
350 PRSD = PRSD + DT
360 GOTO 440
370 FOR I = 0 TO N - 1
380 J = I
390 DT = EN(I) - BE(I)
400 IF KM >= EN(I) THEN GOTO 290
410 IF PART = 0 THEN GOTO 310
420 IF D > EN(I) THEN GOTO 340
430 GOTO 450
450 SECS = SECS + ((D - KM - PRSD) / SP(J))
460 SECS = SECS * 3600 + HH * 3600 + MM * 60 + SS
470 H = INT(SECS / 3600)
480 M = INT((SECS - H * 3600) / 60)
490 S = INT(SECS - H * 3600 - M * 60)
500 IF H >= 24 THEN H = H - 24
510 PRINT "Time: "; H; ":"; M; ":"; S
520 GOTO 210
It is left to the reader to do input validation, handle boundary conditions, optimize, make it more user friendly, port to target device etc.
If you are a TSDMeter customer, you get all software upgrades free of cost. Check your version number by going to “About” in the app. If it doesn’t match the latest version listed here, mail us at firstname.lastname@example.org for instructions on how to upgrade.
TSD rallyists in India have always been partial to Casio. The Casio calculators were cheaper than their HP and TI counterparts and more importantly, easily available locally.
Since the late 80’s, rallyists have gone through a lot of models: Casio FX-880P, PB-100, PB-200, PB-700, PB-1000, Z-1.. the list is endless. They ran with home-grown BASIC programs.
Then along came FX-9860GII. It was sexier, had a bigger display, well laid out keybaord, backlight, higher processing power, was currently in production and most importantly gave developers the ability to write apps. Though the community moved to the new hardware, they still used the same old BASIC programs. They ran faster, but still had crappy user experience.
That is until TSDMeter happened. A bunch of us, fed up with the ‘PBs’, decided to get together and make something useful. Not just useful, but a product that would blow away the current crop of rally calculators! We were lucky that our team had a great synergy and members who brought in complimentary skills – good navigators with domain expertise, rockstar programmers who weren’t afraid of system programming in C and ASM and some of the fastest pizza orderers in the world. End result is of course a kick-ass product!
Bangalore, Rishikesh, Visakhapatnam, Kolkata, Panjim, Shillong, New Delhi, Guwahati, Chandigarh, Kochi, Shimla.. TSDMeter users are all over the place!
Release date: 28th July 2012
(1) ‘Raja keys’ in “Settings”: Pressing [EXE]/[(-)] in “Rally” adds 100m/50m to odo value. Default is off.
(2) ‘Arindam effect’ in “Settings”: Presing [EXE] in “Speed Chart” makes the cursor go row-by-row. Default is off.
(3) [F3]/[F4] and [F2]/[F5] decreases/increases odo values by 10m and 100m respectively in “Odometer” (PRO only).
(4) UI change – fixed alignment bug in “Time Control”.
(5) Adjusted ideal time calculation to match INRC results tabulation logic.
We are always looking to hear from you, our customers. Whatever feedback you give us, if it makes sense for the product, we will add it to the next release so that everyone can benefit from it. And to thank you, we will name the feature after you in the app!