![]() ![]() But I do not know, which way is used in RaceRender and other programs - accelerometer sensor data or calculations from GPS. Frontal acceleration calculation (in direction of moving) is very easy (from 2D speed), lateral acceleration is more tricky (there have to be used also longitude and latitude). On the other hand, accelerations can be calculated also from GPS data. Due to high frequency of acceleration data, such smoothing can be done, but even then there may be some fluctuations. These data have heavy noise (see second picture, data taken directly from video file by /free) with amplitude around 8G which is caused probably by different kind of vibration and need strong smoothing before they can be used. As we can see, the acceleration numbers are quite close to Dashware results (6% difference) and far apart from RaceRender data (24% difference).Īlongside the GPS data, GoPro camera video has also stream of 3-axis accelerometer sensor data with frequency 200Hz. On the first picture there is the same video frame as in previous pictures. Gauges were used almost "as is" without big arrangement, main focus was to the acceleration data. ![]() To check data, I created video file using Telemetry Overlay (trial) program. Dashware data look anyway interpolated, because in csv file, data are changeing every 0.05 sec (20 Hz), but AFAIK GoPro cameras refresh GPS data with 18Hz, acceleration data probably more frequently. Now I will try to look, if I can see something in RR_data file. Hovewer Date-Tme clock itself was surprisingly off by abovementioned 0.04 sec (or two frames). As expected, coordinates, speed and accelerations changed accordingly. Then I tried RR with GPS data from dashware (picture 3). To find out, what is reason of these differences, I checked GPS data from Dashware using csv file. In Dashwaree start/finish line crossing times are set manually, so they may differ from RR times. Difference in speed by 1kph and also in current lap time are normal. Here is something wrong, kart must have aerodynamic wings like formula cars to reach such numbers.Ĥ. RR shows 2.47G (around 2.5G during whole corner). That shows that I can not go there much faster. Normal racing kart can reach here around 2.1G. Dashware shows here 1.9G in top of corner. Big difference is in acceleration data, more visible in lateral acceleration. May be the same time shift is also with other data, but with lat/long it is clearly visible.ģ. Closer look shows, that differnce is not in coordinates as such, but RR data stream is ahead by 0.04 sec (2 videof rames), these data appears on Dashware video 2 frames later. The clock is probably the same, RR just rounds seconds, Dashbord shows full seconds.Ģ. Date-Time clock output is different, apparently by 0.5sec. Second one is from RR output (exactly the same frame with same number). Slight differences in data were expected, but surprisingly there were some strange differences.įist picture is from Dashware output. Now I got RaceRender and tried to compare Racerender and Dashware outputs using last year GoPro files. So far I used GoPro 5 Black with Dashware. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |