Not signed in (Sign In)

Vanilla 1.1.5a is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthoroktrg600
    • CommentTimeOct 18th 2009
     
    Is it possible to suggest what time rate we're looking at before we can expect the hardware and software to be good enough for release? 2 months? 4 months? 6 months? More? I need the capabilities of the hardware logger very bad and it would be nice to know if I can plan on using this the next season, or if I should look for an expensive solution I really can't afford. Thank you.
    • CommentAuthormattnj
    • CommentTimeNov 12th 2009
     
    Hi,

    As soon as possible is the timescale...It is being worked on currently, the first physical unit is complete and fully functional and tested, it is now just a case of the integration with racechrono and and debugging. I am reluctant to give a timescale of when it will be available until we have a fully working prototype (working with racechrono on a track!)

    Matthew
  1.  
    That's brilliant news! Good work.
    • CommentAuthormpl
    • CommentTimeNov 16th 2009 edited
     
    Just signed in to this forum and this project sounds interesting. I have used race chrono in our race car and it is working well. If it is possible to include some extra information in it with this device what you are talking about I am also very interested to buy it! Our vehicle is historic race car so the OBD-II reader is out of question.
    • CommentAuthormattnj
    • CommentTimeNov 24th 2009
     
    coming along nicely, will be available to pre-order soon at www.racelogger.com
    • CommentAuthormattnj
    • CommentTimeJan 1st 2010
     
    hi, just to update everyone, we now have a working version of racechrono and racelogger, (thanks to aol for my custom version or racechrono!) a bit of debugging needed but it is looking good and will be ready to go soon.
    • CommentAuthormattnj
    • CommentTimeFeb 22nd 2010
     
    ok, so, we have a fully working solution, i am looking for a couple of beta testers for this, please contact me via www.racelogger.com if you are interested....be quick.. Matthew
    • CommentAuthoralfadriver
    • CommentTimeFeb 24th 2010 edited
     
    Brand new member, too- and JUST like MPL, I'm tyring to put together a system for a vintage race car that only needs a handful of inputs. It appears that I should have been reading this group a lot earlier, but me and a buddy here at work are putting together a single unit that will have analog inputs, an rpm input, a compass (to see if the car is not pointing the direction it's travelling), accelerometers, and GPS- all on one single unit.

    We've got the unit working right now, bluetooth, and using a basic serial logger, it logs all the data as we need.

    I found this site just looking for software to use on my pda/laptop to take and read the data.

    So, I guess I'm wondering if there's a format that we should be outputting so that the racechrono will work? Again, unlike mattnj's quite cool separate unit, this has all the info on one box, just like the DL-1.

    FYI- the cost is pretty cheap, too- we are mainly using components from a site called sparkfun.com- and my buddy is having fun putting this all together. His overall goal is to have a compact and light system he can put on his remote control airplanes, while mine is to have a good data acquisistion system for the car + driving data.

    So- the summary question- where can I find the format to output the information from our fully contained logger so that racechrono can input?

    Thanks
    Eric
    • CommentAuthoraol
    • CommentTimeFeb 24th 2010 edited
     
    Hi Eric!

    I guess the format we're using with RaceLogger is no secret, as it's clear text ASCII from the device :-). You can make your home brew device to use same format (or just by Mattnj's device if you don't want to go through the pain developing your own device).

    I'll try to explain it here:

    $RC1,<time>,<count>,<xacc>,<yacc>,<zacc>,<xgyro>,<ygyro>,<zgyro>,<rpm>,<a1>,<a2>,<a3>,<a4>,<a5>*checksum

    - Each line are separated with CR LF
    - Checksum is two digit hexadecimal value, calculated same as in NMEA 0183.
    - Count is a sentence count between 0-65535, rolls back to zero after hitting 65535.
    - Time stamp is same as used in NMEA 0183.
    - Timestamp can be left empty in real time mode (RaceChrono connected to the device and logging the data). If you want to import the data to RaceChrono afterwards, you need to have standar NMEA 0183 GPS data in between the $RC1 sentences, and precalculated timestamp for $RC1 sentences.
    - If timestamp is left empty (no GPS on board), RaceChrono will estimate the time from its own time from separate GPS device.
    - If timestamp is left empty, it's important that every sentence comes with consistent intervals.
    - Gyro and AccZ values are currently not saved by RaceChrono.
    - Acceleration values are in 1/100ths of G force. AccX is Lateral G and AccY is Longitudinal G in RaceChrono.

    Example sentences with no timestamp:

    $RC1,,5609,-3,-0,,,,,875,14,36,118,85,99*26
    $RC1,,5610,-2,-0,,,,,840,35,53,149,5,102*26

    Example sentences with timestamps, and some NMEA 0183 in between:

    $GPGGA,124341.400,5049.7753,N,00023.0818,W,1,9,0.92,10.5,M,47.1,M,,*71
    $GPGSA,A,3,20,04,17,23,13,11,12,31,32,,,,1.80,0.92,1.54*03
    $GPGSV,3,1,10,20,76,068,41,23,58,173,49,17,44,258,45,32,44,072,41*7F
    $RC1,124341.818,6384,8,-5,,,,,1960,0,14,96,110,230*22
    $RC1,124341.862,6385,2,16,,,,,1960,0,54,130,208,224*0D
    $RC1,124341.907,6386,3,3,,,,,1960,0,0,37,74,227*04
    $RC1,124341.951,6387,-2,-3,,,,,1995,0,6,60,67,228*04
    $RC1,124341.995,6388,3,-1,,,,,2065,0,50,152,169,245*1F
    $RC1,124342.040,6389,13,-0,,,,,2100,0,0,17,43,238*18
    $GPGSV,3,2,10,11,33,148,42,13,30,195,42,04,30,301,40,37,28,152,*71
    $GPGSV,3,3,10,31,21,054,22,12,05,340,16*7E
    $GPRMC,124341.400,A,5049.7753,N,00023.0818,W,19.57,270.44,240210,,,A*4D

    RaceChrono v1.40 supports this just fine. If you have any problems or questions about the format, I can always help.
    • CommentAuthoralfadriver
    • CommentTimeFeb 24th 2010
     
    Thank you, thank you, thank you!!! That's pretty sweet. Just out of curiosity, if I don't use a signal, say the gyro- do I put spaces there, or just change the assigned name, and put whatever there? This is going to be fun! Eric
    • CommentAuthoraol
    • CommentTimeFeb 24th 2010 edited
     
    The gyro fields are not currently saved at all. For a channel you don't use, just leave it empty between commas. You can use the a1-a5 for what ever you wish. You can view those channels in RaceChrono's graphs. I recommend using RPM and Accelerations for their intended purpose, as there might be some extra features based on them.
    • CommentAuthoraol
    • CommentTimeFeb 24th 2010
     
    BTW, I don't think a compass will work on a race car at all. You'll probably have to use gyros for the drift angle.
    • CommentAuthoralfadriver
    • CommentTimeFeb 25th 2010
     
    It's kind of an experiment... One requirement to really process it is to compare the magnetic inclanation vs. the satillite true north. And since that's not at the north pole- it will have to be done at each location. Considering the cost of the digital compass, it's not a huge problem if it doesn't work. Like I said- it's going to be fun! Eric
    • CommentAuthormarac
    • CommentTimeApr 14th 2010
     
    Has anyone tryed this device from mattnj? When will you start selling this devices???
    • CommentAuthormarac
    • CommentTimeMay 3rd 2010
     
    Is there any info on Race Logger project???
    • CommentAuthoraol
    • CommentTimeMay 3rd 2010
     
    You can contact Matt directly http://www.racelogger.com/?page_id=38
    • CommentAuthormarac
    • CommentTimeMay 3rd 2010
     
    I tried that 10 days ago but no response :-(
    • CommentAuthoraol
    • CommentTimeMay 4th 2010
     
    Sorry to hear. The RaceLogger project is by Matt so I have no control over it.
    • CommentAuthorDani_Duke
    • CommentTimeJul 13th 2010 edited
     
    I just found this thread some days ago.
    First I planned to simulate the OBD reader protocol with a microcontroller to get rpm, throttle and brake data from my motorbike to RaceChrono.

    But this protocol described here is much less complex. :-)
    I'd like to build a simple device counting rpm and having 5 analog inputs.

    Actually there are a few open questions:
    Main question: What ranges are allowed for the data fields?
    Can <rpm> be a 5digit value or is it limited to 9999rpm?
    Whats the full scale range for <a1> to <a5>? Using a 10bit ADC the value 1023 would be nice. Or is there a limit from 0 to 100? (the example data say no, but where is the limit?)

    How can I activate or show the data in RaceChrono Graph? I thought this should be identical to an OBD logger, so I can toggle the displayed data in Liveview.

    Best regards,
    Dani
    • CommentAuthoraol
    • CommentTimeJul 13th 2010
     
    All values saved are signed 16bit, so from -32k to +32k. It should work identical to OBD-II. You can select the RaceLogger channels from Graph properties once they are logged.
    • CommentAuthorDani_Duke
    • CommentTimeJul 14th 2010
     
    Thanks for the answer.
    There were two little mistakes in my sentence. I added a "," after the last value and calculated the checksum shiftet by one. :(
    Now its working fine in RaceChrono and I will work on at the hardware part and do some testing.

    Actual, my datalogger (heavy prototype an eval-board) sends data every 200ms (timerbased with crystal). No timestamp is added, because I don't know the GPS's time. My suggestion is to send a GPGGA or GPRMC sentence to the datalogger once (once, because every sentence every 200ms may disturb the datalogging accuracy). Then it can synchronise to the clock an output sentences with timestamp.

    My goal is to make a little inexpensive hardware, to log data from motorbikes without OBD. The project should be simple to build by anyone who can solder SMD parts.
    Give me a few weeks and I'll post the "RaceDataLite" project somwhere in the www and drop a link here. ;)
    • CommentAuthoraol
    • CommentTimeJul 15th 2010 edited
     
    If you don't have the <time>, RaceChrono will estimate (guesstimate) the timestamp from the <count> field. This is how it's done for the GPSless RaceLogger too. Timestamp is for future GPS loggers.
    •  
      CommentAuthorhugos
    • CommentTimeJul 19th 2010
     
    Dani_Duke: Your project is interesting and very cool !
    • CommentAuthorDominique
    • CommentTimeJul 19th 2010
     
    Hi Dani_Duke: I'm sure this will also fit for go-kart. So, best luck to your project. And keep us informed of where you are.
    • CommentAuthordelirii
    • CommentTimeJul 29th 2010
     
    @Dani_Duke : I just want you to know that your device is exactly what I'm waiting for ! :-) And I'm not the only one here ;) Keep us informed please if it comes to reality ! I'm ready to solder everything needed :)
    • CommentAuthormark944
    • CommentTimeAug 1st 2010
     
    Anyone know if this product ever eventually made it to production? The www.racelogger.com website seems to be unresponsive. All a bit mysterious. Would seem a pity if things didn't come to fruition on this product after all the time and development that apparently went into it...

    I am very interested in running racechrono software, but I need a datalogger like this one in order to do so, as my car (1990 Porsche 944 S2) is pre-OBDII.

    Can anyone point to or recommend any other products that might be suitable?
  2.  
    This is the only product I'm aware of that has started development and will interface directly with RaceChrono. I was selected as a Beta tester for this hardware logger, but I'm yet to see one. I think the person running the project is very busy. He told me a month or two ago that he still plans to release the product. It's a shame it hasn't been made for sale yet as I'm sure there would be a good few sales from it. There's one sale here, for starters. If it's not forthcoming by the end of the season, I'll be buying a proper data logger as I need more than GPS and my race car doesn't have OBD.
    • CommentAuthorDani_Duke
    • CommentTimeAug 2nd 2010 edited
     
    Today I'd like to give an update of my work. I already ordered three PCBs for prototypes.
    My logger will be a very simple device. I use an Atmel Mega32 and a BTM112 Bluetooth Module from Rayson.

    It should look like this ;-)
    http://www.imagebanana.com/view/kxvw3mzd/RaceData_top.jpg
    http://www.imagebanana.com/view/q05m5mfq/RaceData_bottom.jpg

    Unfortunately I'm not able to sell complete devices later. I think I'll release the layout and firmware under creative commons license. Maybe I can offer PCBs with a programmed microcontroller soldered on it.
    For use in different environments there is a lot work to do on the software side, because for my needs I hardcoded all parameters (e.g. correction factor for rpm, adc range, bluetooth pin...).
    • CommentAuthormark944
    • CommentTimeAug 3rd 2010
     
    Looks good, Dani_Duke... but why SMD? That makes it hard to put together without special soldering equipment?
    •  
      CommentAuthorhugos
    • CommentTimeAug 4th 2010
     
    SMD for Surface Mount Device

    You have a guide for this here :
    http://www.infidigm.net/articles/solder/
    • CommentAuthormhoward1
    • CommentTimeAug 9th 2010
     
    Dani,
    Thanks for the update. Are there any budget or material roadblocks that need to be addressed?
  3.  
    We have a different project working right now- using parts from Sparkfun, but are having different problems. Logging voltage looks fine- although, I'll have to pre-process the information so that the numbers make some sense- not a big deal. Using the string that was posted in reply to one of my above questions got it going. But we are haveing speed and noise issues that I'll post in a new thread. Still, the data logger works fine, so far.
  4.  
    @alfadriver - is that the logomatic v2 you're using? I have one of them in a box that I've not got round to setting up yet.
    • CommentAuthoralfadriver
    • CommentTimeAug 10th 2010
     
    andylaurence I don't actually know- my friend is doing this, since he volunteered for fun. I'll ask, though. It's an interesting set up, that's for sure- we even have a serial accelerometer, but it's taking up valuable I/O on the main board, so if we want to run this as a stand alone SD card output, that's going to have to go. It's currently working well as a bluetooth connection, as was intended, but since RaceChrono is so good at importing data, then the stand alone option is very appealing. (less risk to a PDA or phone or whatever you use plus easy use for a laptop)
    • CommentAuthormark944
    • CommentTimeAug 19th 2010
     
    When trying to load the racelogger website, I'm getting the message: "Error establishing a database connection" Things seem to be quickly going from inauspicious to very inauspicious for this project :\ Very strange. I hope mattnj is OK.
    • CommentAuthorDani_Duke
    • CommentTimeAug 20th 2010
     
    The first two prototypes are ready for testing.
    Hardware looks good so far, obviously no layout errors.
    Bluetooth connetion is reliable. About 30m in our assembly hall and 10m inside the concrete building.
    All 5 analog channels and rpm fixed to 5Hz at the moment. I think 10Hz are possible with some firmware changes. But that's a task I have to do later.
    First of all I have to install one device in my motorbike for testing at Nurburgring next week :)

    Then I'll post an update.

    @aol, is it possible to give the Analog 1 to Analog 5 other names inside Racechrono?
    • CommentAuthormhoward1
    • CommentTimeAug 20th 2010
     
    I can volunteer as a tester if needed. We have a full Challenge series team with mulitple vehicles.
    • CommentAuthormark944
    • CommentTimeAug 22nd 2010
     
    Maybe Dani_Duke should start a new thread to discuss developments on his project, and leave this thread to discuss mattnj's racelogger? Might be less confusing.
  5.  
    Put me down for one if you're selling them. I've got a sprint on Monday in my ADR.
    • CommentAuthormark944
    • CommentTimeAug 29th 2010
     
    Antti, have you published (or are you intending to publish) the spec for the datalogger protocol you implemented for the Racelogger unit? Perhaps it would be a useful de facto standard for Racechrono dataloggers in case anyone else wants to build or develop their own logger unit.
    • CommentAuthoralfadriver
    • CommentTimeAug 30th 2010
     
    he did post it- read the reply to the same question I asked back in February. We've got it working perfectly. Interestingly enough, we are not using the data logging mode- by just adding the properly formatted RC1$, RaceChrono just reads it. Antti has done a great job at that. Eric
    • CommentAuthormark944
    • CommentTimeAug 30th 2010
     
    Thanks Eric -- if that's all there is to, it looks very straightforward! Cheers.
    • CommentAuthoralfadriver
    • CommentTimeAug 30th 2010
     
    mark- do note that extra characters or spaces will make it act funny. Since we were putting it together ourselves, we timed the a/d with the GPS, and used the same time stamp. Oh, and for some reason, my friend found that the RC line had to be inbetween two of the GPS line- no idea why, but it's working.....
    • CommentAuthoraol
    • CommentTime7 days ago edited
     
    Mark944: Well, it is already public, and can be used by anyone (look earlier this thread). If you mean do I plan to write better spec than in this thread, maybe.
    • CommentAuthormark944
    • CommentTime5 days ago
     
    Thanks, Antti. BTW, has anyone heard from mattnj lately? His racelogger dot com website seems to have fallen into a blackhole in the last few days... or at least I can't get it to come up. He did have a message on the website dated early August that said he was back on the case with the project, but no news or updates on the website since then. And now the website seems to be off the air. Strange, strange, strange.
  6.  
    Unfortunately the domain has the status "clientHold" which implies he hasn't renewed the domain in time. It may be an oversight from his side, but considering no one has heard from him it's not a great sign...

    EDIT: The domain name expired on the 1st of September btw.
  7.  
    I last heard from him a few months back. I'm compiling a list of other possible options, but it looks likely that this could be the end of my use for RaceChrono as I step up to something that delivers more than just GPS-based data.
    • CommentAuthortechieboy
    • CommentTime2 days ago
     
    Just recently had to make the same choice after finally giving up waiting for RaceLogger to ever appear. Have now moved onto a RaceLogic DriftBox and their Micro Input Module for capturing rpm and up to four other external analogue sensors. Should probably have never got rid of the DL1 that came with car but could never get to grips with it.

    A real shame nothing has come of the project as I've been using RaceChrono for a long time. On the bright side it does finally mean I can stop limiting myself to Nokia phones and their associated bugs.
    • CommentAuthoraol
    • CommentTime2 days ago
     
    To andylaurence and techieboy; I'm sure you'll be happy with the more serious/expensive data loggers you've chosen. Too bad RaceLogger didn't come to reality, but RaceChrono project continues :) Nokia is not doing too well in smart phones front and lot of users are moving to other platforms. I will have to make hard decision about the platform support, when I start making next generation of RaceChrono. Android platform seems very strong now.
  8.  
    Were you not rewriting it for qt, which is being ported to Android already?

    Multiplatform is a very nice way of not having to make too many hard choices after all!