Jump to content

vtjballeng

Members
  • Content Count

    231
  • Joined

  • Last visited

  • Days Won

    4

vtjballeng last won the day on December 20 2018

vtjballeng had the most liked content!

Community Reputation

425

About vtjballeng

  • Birthday 06/22/1979

Contact Methods

  • Website URL
    http://www.bmotorsports.com

Profile Information

  • Gender
    Male
  • Location
    Mechanicsville, VA

Recent Profile Visitors

1,618 profile views
  1. I'll offer up something else... We installed an infrared brake temperature sensor pointed at our left front rotor for the first time this race with some interesting results. We also switched to a less aggressive brake pad compound which increases our time on the brakes slightly but improves feel greatly. We found that our green driver (colors based on plots) was overheating the brakes at key points during his stint but not continuously. We had covered some of our brake cooling earlier in the day under the false notion that we were overcooling our brakes. During our next driver's stint, the blue driver, we found that his temperatures were even higher despite opening up significant additional cooling. I took a dive into the data and found that the blue driver was on the brakes for 19.4s per lap vs the green driver at 13s. That's 49% more time on the brakes but I didn't feel this offered up a complete picture. Fig1. 3 drivers colored as blue, green, red. Top part is BrakeLapTotal or total time on the brakes per lap in seconds. Bottom part is Brake Temperature in degF You can see part of the issue below at T10a where the blue driver is applying more braking force for much longer. Fig 2. Top part is TPS. Bottom part is inverse Brake Pressure. Brake Pressure is inverted to showcase throttle to brake transitions. I had to create some new channels that better represent the issue. The integral of the Brake Pressure would give me a good idea of cumulative force applied to the brakes over a lap by the driver. The integral of the Brake Temperature would give me a good view of the energy over a lap with the caveat that the green and red drivers had 33% of their cooling blocked while the blue driver had maximum cooling available. When we look at the Brake Pressure integral or summation below, we can see that the blue driver applies 84% more pressure throughout the lap than the green driver and 106% more than the red driver. It's also worth noting that the blue driver is slower by several seconds and slowest in this group. The green driver is the fastest so the additional braking is not due to additional speed the blue driver needs to dissipate. When we look at the Brake Temperature integral or summation, we can see that the blue driver is 69% hotter than the green driver and 86% hotter than the red driver. This despite the additional cooling the blue driver had in place. I was tempted to but didn't bother to correct for airflow. Sufficed to say, the blue driver is dumping far too much energy into the brakes. Fig 3. The top is the Brake Temperature summation over the course of a lap. The bottom is the brake pressure summation over the course of a lap. We conclude that the blue driver is braking earlier, braking harder, overslowing, and dangerously overheating the brakes. This massive delta is problematic and a tough case to design for. Some solutions are driver training/improvement, improved cooling, change back to the more aggressive but non-preferred pad compound, and a warning system based on brake temperatures.
  2. Great idea! Very interested to see this tool at VIR. A pit efficiency measurement based on average lap + 5min + out lap margin. We calculate this afterwards and sometimes during the race to make sure we're staying on point in the pits. Difficulty with real time calculations is filtering yellows and outliers. Outliers are simple enough and iirc there is an api variable for flag.
  3. We realized we didn't have enough room to store all the NOS we needed, so we've tested a pulsed arc discharge nitrogen dioxide generator. It's only 5% efficient and weights 300 lbs but that push to pass button is great! We definitely need it. Adding another temp sensor and soon some position sensors, so our wiring ball is growing faster than Akira. The rules lack for specificity in some places for sure. I think that one falls under common sense and most kits come with nozzles. There are other places where I agree with your assertion. Writing a universally applicable rule book is difficult though there is some good reference work out there. You could have just a single page with all parameters vague as possible. Or you could have 1000 pages describing how many sheets of toilet paper and which direction you should use each time you wipe your ass. In this case, if you find a rule you don't like you can craft a petition in order to clarify this rule.
  4. Yes, and it does. The failing was a series of cascading human events unfortunately. 😢 LOL, the scrotum shocker feature idea is making a comeback! We have a lot of tools available. A seat taser may find it's way in that set of tools. We sell Race Capture telemetry which works great for many! This was yet another human failing unfortunately in our cascading series of blunders. People are surprised by this or don't seem to understand that it can be done. Fundamentally you can learn a lot with just a few simple measurements and tools. Simple tools and good, consistent procedure go a long way imo. Yes! I love the design freedom and creativity here. The Parts Badger team read the rules. Jay had a good look over them. Mike and I had a discussion briefly about it since so many racers were concerned. I felt that pulling the valve covers would offer a super simple check. You can use a digital caliper to gain some simple insight. Sure, degreeing the cam gives you better information but we can get most of the information we need without full teardowns imo. @Team Infiniti is on point here, you can use a stick and a marker to get stroke with a pulled spark plug for all that it matters. Yes. It seems so many good builds have to go through this battle if they succeed. It's a toxic and disappointing reality. These guys showed up with such a strong build out of the box, they ruffled peoples feathers before people knew who they are. When we started our team in 2014, we went back & forth on Miata vs 240SX. We ended up with 240SX because we have some tall guys and because someone was offering a "free" chassis (it wasn't). We ended up 240SX but my experience was with the Miata. While many details are different, this is close to the car I was planning. I believe, if anything, they are running slower than a maximized aero Miata with good power. This thing should beat SM times substantially imo. I think we'll see this car continue to improve and continue to get faster within the ruleset. I understand their driving was less than perfect but their build sacrifices some top speed for handling. This means they will be passing in the corners and under brakes, upsetting some regardless of driving quality. From all the information I've gathered here, in private conversations, and in my Miata experience this seems to be a fully legal car in which the builders read the rule book and built to the rules. They are at the beginning of their development cycle and have seconds to gain going forward. Good show guys! If you've ruffled this many feathers with a legal build, then you're doing something right.
  5. Yep. This is development testing. Alpha hardware to come. Beta hardware thereafter. Final rollout there after. We're taking this slow and steady as a false or unreliable rollout of final product would pose so many problems. Thanks everyone for working with us as we sort out the details!
  6. No, it's successive iterative design improvements over time. Our current engine is a 1995. Several changes were made to the VQ over the years and the 350z gets a series of design fixes and improvements that solve a lot of issues. The VQ35HR & VQ37VHR fix most of the design issues in the earlier engines. So I'm saying that our engine version is 1.0, the VQ35 v2.0, and the VQ37VHR is v 2.7 and it's finally stable. It seems it just took Nissan a surprisingly long time to get all the issues worked out. That and the VQ35 and later engines have much better replacement parts availability and support. The VQ30 died on the vine and we have a hard time getting basic parts for our car now and, as time passes, the older engine. With that said, most of our failures are due to mistakes or correctable human error so I'm hopeful we'll get past this failure hump.
  7. We have a VQ30. I really wish we had a VQ35. The VQ35 has so many improvements (besides the displacement) over the VQ30, I don't think we would have gone through the three engines we've gone through with the VQ30s we've run after our 1UZ V8 value was raised. The engine failure at this race had a red herring as a driver money shifted and it failed 3 laps later. Going through video & data we found that oil pressure was low in the downhill esses and Turn12. We had several systems in place to catch the problem and correct it and cascading human failure happened at a comically bad level. The top end is now suspect, #3 connecting rod bearing done, crank done, & there are big sparkly bits in the oil pickup. Sadly, we've had more engine failures with this VQ30 than in all prior races combined with our 1UZ & KA24 going back to 2014. Interestingly, looking through the logs, we can see from the knock sensor data where the rod let go and it's failure arc during the race.
  8. Not Banned Yet had a race day of highs and lows. We had a great time racing with friends pitting with and around us. Pitting with @MR2 Biohazard & crew next to @Hurljohn & crew & @Huggy & crew was a good time. Glad to see @Lethal Cliff & NLS make the race this year. The pro paddock has tons of room in the pits and we had one team member who decided to come to this race purely on not having to lug our pit box up that massive club paddock hill! As always, the ChampCar officials ran a great show that we're happy to be a part of. We've been working heavily in 2018 and into 2019 on ergonomics, driver comfort, driver requested improvements, driver development, & team preparation. For the most part, the focus on logistics and driver have offered our biggest improvements to our consistency. It's made our events more fun and less hectic. I can't stress enough how important the undervalued side of racing logistics, practice, & driver development is to this sport. We're still chasing @Huggy with their near perfect execution at so many recent races, congratulations on the win! We're finally getting more comfortable with all our logistics improvements and this race felt more at ease for me than prior events. @mindspin311 started off and had an amazing battle with Cone Crushers, going tit for tat lap by lap. @macheesy had a great stint and put down our FTD. He's an amazing driver and strategist. Our other guys showed marked improvements this year and we're going to keep pushing them hard. Lot's of simulation, Virtual Racing School data feedback, AiM data feedback, coaching, & more. We're excited for 2019! Unfortunately, our day was ended early with a series of cascading failures that led to the untimely demise of our engine. With the systems we have in place, the failure we had should never have happened but did. We'll have to put in some serious effort to make sure we don't repeat the mistake. We're rushing to make VIR South and I hope we will as there's not much time left! Regarding the fender rule, pulling them out to meet the rules made ours sharp and more dangerous than the original problem in my opinion. Here is the Cone Crushers miraculous save some asked us for:
  9. Thanks for the feedback! There is a photo sensor present to automatically adjust based on ambient lighting conditions. It sounds like there was a failure in your unit, which has historically been rare so we will have to look into it. The current development units are using some off the shelf components not intended for racing and our next revision with only our own custom hardware is coming soon. There is a power button on the side that can be cycled or simply turned off to attempt recovery or just disable it respectively. I should add that the box should not be installed where the photo sensor is facing a light source as this will increase the screen brightness. We'll need to create a quick set of instructions as some users never turned the unit on or experienced a too bright screen when the photo sensor faced a light source. It's extremely helpful when you can't see the flagging stations for a variety of reasons. It's also helpful for a litany of reasons enumerated here:
  10. vtjballeng

    2019 Official Michelin Raceway Road Atlanta 14-Hour

    I'll expect @Bill Strong to stink. No way he's climbing that hill to get clean. Or for any reason.
  11. Prepping the next revision of development boxes for Road Atlanta! We're concurrently developing the alpha hardware for use later this year. We will have local flagging capability at this event and will be working with the track and CCES to roll this capability out.
  12. vtjballeng

    Db9 or ethernet/rf45 cables for engine harness?

    As far as connectors go, Deutsch plastic connectors are a solid, inexpensive option that work very well. We recommend them for most budget applications. I'll take the rest from a prior response I gave on the subject (TLDR; never use weatherpack for any new work):
  13. vtjballeng

    2019 Official Michelin Raceway Road Atlanta 14-Hour

    Good thing we're running dev testing at this race .
  14. A common thread we've seen in some of the announcement feedback is a request for situations in which in car flagging is helpful. Perhaps this will help some. There are many other scenarios not outlined here specifically. Maybe there are other scenarios you can think of? Fills in coverage holes between flag stations Gets dangerous cars who are unresponsive to black flags off track Improve all drivers flag observation percentage Helps first time novice drivers (lemons/champcar/hpde/etc) avoid wrecks Allows messages to dangerous drivers red misting around track Greatly improves night flagging Greatly improves low visibility flagging in conditions like fog or heavy rain Allows flagging when drivers line of sight to flag stand is obscured Capable of notifying race control of a stopped car or wreck Gives team flag information in the pits for improved strategy & safety Capable of providing blue flag to improve safety passing Pit Timer capability Pit speed Warning Emergency services may be dispatched to accident Tow truck may be dispatched to disabled vehicle Purple Flag speed warning (VIR 35 as example) Color Blind supplementation as many color blind drivers can't distinguish existing flags Avoid Black Flag confusion where multiple cars pit for the Black flag event of one car
  15. This works in concurrence with properly training drivers and helps greatly in that specific task. Display should be mounted in line of sight. This is a driver aid that assists driver flag diligence (among other things). We had discussed, jokingly, a private bits shocker for racers to REALLY get their attention. A common thread among detractors seems to be a request for this "feature." If you really want this option, we can provide it .
×