![]() ![]() Thanks again! Attachments 20091011-0106900.ldx (444 Bytes) Downloaded 1058 times 20091011-0106900.ld (584. Spa is among Formula 1 drivers most loved tracks, with its mix of long straights and challenging fast corners allowing them to push their cars to the edge. zip of the project files in a subsequent post but not sure if that's allowed on this board. Our Definitive Circuit Guide to Spa-Francorchamps dives into the detail of what it takes to be quick around this awesome circuit, analysed by our professional racing driver, Scott Mansell. ![]() I've attached the log files in case this would help - I've been trying to map Lap #2. Spa is, without doubt, one of the world’s most exciting tracks at which to drive. Why is the Generate Track Length different from the Details Venue Length? Is it being calculated from Corrected Distance? 6010m = 3.734 miles, yet my Corrected Lap Distance on my fast lap is listed as 3.27 miles - ? Since there are a number of conversions going on (Digital In 1 Speed mapped to "Vehicle Speed" which calculates Corrected Speed which generates Corrected Distance ), I wonder if there is some loss of accuracy? By the way, I set it as meters rather than miles because the Venue Length textbox in the Details dialogue only allows whole numbers (no decimal places), so the 3.56 miles that I wanted to set results in 4 instead so I set it as 5729 meters to get the granularity I wanted. the 5729m that I set up in the Details dialogue. Hi Jamie, thanks for responding! It is set up as a closed circuit - but you are correct, the Length shown in the Generate Track dialogue is 6010m vs. Generated Track map is completely bizarre - almost like it's "inside out" - and doubles back across itself several times, see below: All tracks are suitable on most standard sized 3D printers without the need to scale down. Venue is set to a closed circuit and Track Distance is set properly. Circuit de Spa-Francorchamps - 3D Topographic Track Collect and print all of our miniature racetracks from around the world. In I2: Dig In 1 Speed channel is mapped to "Vehicle Speed" using units km/hr Corrected Speed uses "Vehicle Speed" w/units=mph and looks to be exactly accurate for the logged data both Lat G and Long G sensors appear to be oriented properly (Lat G is showing positive for left turns, right hand force) Speed curve is smooth - no excessive noise apparent Long G has some noise, but Lat G noise is minimal and appears near zero on straights with realistic values in the turns (up to 1.5G). In Dash Manager: Wheel Speed is wired to Dig In 1 Speed (unitless) Beacon wired to Dig1 (pin 52) Lat G wired to AV1 (pin 45). I'm fairly new to I2 but have researched everywhere I know to resolve the problem. I cannot get a correct track map for Daytona (using infield) to be generated - using an M48 in a Porsche 911 race car w/ADL Dash Manager & I2. ![]()
0 Comments
Leave a Reply. |