R/C Tech Forums - View Single Post - Lap Timing Decoder
View Single Post
Old 03-12-2013 | 08:17 PM
  #146  
Skruger's Avatar
Skruger
Tech Master
iTrader: (16)
 
Joined: Nov 2005
Posts: 1,535
From: AT YOUR TRACK
Default

Originally Posted by Skruger
9600,8,N,1,hardware flow control

I will post the spec's tonight 7pm PST and a raw HEX dump of the serial port of my IR system that works with the free programs including RCScoringPro (not free)

There are lots of free programs out on the web.
I will post the ones I have and use for Family racing.
time stamps in HEX from My IR Decoder
it is not quite 100% amb compatable but it works with
Free programs already out there

theses programs simply ignore the Csum at the end
Iridium ( the maker of the IR system I use)
alycat/lapsFree/jlaps/

it does not work with B&B's autoscore (Autoscore needs csums to be correct) and I am lousy at figuring out 16bit csums

Can any body help me with the 16bit csum's ?


this HEX does not include the ^A at the begining instead it uses the older (SOH) Ox01 and (CR,LF)
sh = start of heading
@ = transponder
# = unit status (sent every 4 seconds)
09 = tab used as a delimeter
device id = 202 for my unit
frame = 0 to ~ prolly used to keep track of lap times after a race
transponder number 7 digit cannot use 3000000 to 3999999 <-house transponder numbers only that i know of
time in seconds . hundreths seconds <-- could use of hit counts and average time to get thousands calculated
hun = Hundreths of a second
thousands of a second possible or even tenths of thousands but not used on my decoder unit
hits = how many times the transponder war counted under the loop per pass <--Max 255 and must leave the loop for one second before restarting hit count
Dummy = normaly used for rf signal strenth <- not used so for compatibility set to 111db
0 = loop and battery indicator <-- I have not played with this one yet
x = end of data field or start of Csum or both
checksum displayed in ascii format <-- I have not figured out how to compute for other programs to work with (autoscore/RCtimer/ect)
checksum is not used by most Timing Software

sh_@_|_devicID___|__frame #_|__transponder number_|__time____.__hun___|__hits__|_dummy__|__0_ |__x checksum in ascii (cr,lf)
01 40 09 32 30 32 09 31 35 39 09 31 30 30 33 30 39 34 09 33 32 37 2E 36 35 09 31 39 09 31 31 31 09 30 09 78 35 37 32 34 0D 0A
01 40 09 32 30 32 09 31 36 30 09 31 30 30 33 30 39 34 09 33 32 37 2E 39 35 09 33 30 09 31 31 31 09 30 09 78 35 37 32 34 0D 0A
01 40 09 32 30 32 09 31 36 31 09 31 30 30 33 30 39 34 09 33 32 38 2E 32 36 09 33 31 09 31 31 31 09 30 09 78 35 37 32 34 0D 0A
01 40 09 32 30 32 09 31 36 32 09 31 30 30 33 30 39 34 09 33 32 38 2E 38 35 09 35 37 09 31 31 31 09 30 09 78 35 37 32 34 0D 0A
01 40 09 32 30 32 09 31 36 33 09 31 30 30 33 30 39 34 09 33 32 39 2E 31 33 09 31 36 09 31 31 31 09 30 09 78 35 37 32 34 0D 0A
01 40 09 32 30 32 09 31 36 34 09 31 30 30 33 30 39 34 09 33 32 39 2E 34 32 09 31 33 09 31 31 31 09 30 09 78 35 37 32 34 0D 0A
01 40 09 32 30 32 09 31 36 35 09 31 30 30 33 30 39 34 09 33 32 39 2E 37 36 09 32 36 09 31 31 31 09 30 09 78 35 37 32 34 0D 0A

These strings sent once every 4 seconds indicating the decoder is alive ,kinda like a watch dog timer
lets the pc know it is connected and working properly
01 23 09 32 30 32 09 31 36 36 09 30 09 78 43 32 34 39 0D 0A

01 23 09 32 30 32 09 32 34 30 09 30 09 78 43 32 34 39 0D 0A

Last edited by Skruger; 03-13-2013 at 12:30 AM. Reason: format
Skruger is offline