YoDog

iTrader: (28)

If you are running "Blinky mode", there is no ramping RPM value to set. You can only adjust the motor timing on the can. Take a look at either the RC10r thread or the CRC WGT thread for rollout suggestions as I recall it discussed frequently.

I.T.Guy

iTrader: (1)

Funny - Randy posted almost at the exact same time haha. You know, it almost makes sense to have a "beta" section @ teamtekin.com's download page to eliminate any possible question. We see this all the time in the software world. If your daring enough to run the latest (bleeding edge) release, then you take the risks on. But at least no one will cry foul when there is a question of a limited "test" release in the wild during big races. Pretty simple really!

Randy_Pike

iTrader: (6)

It's not simple though. Apple was sued and lost when people wanted their jail broken phones warranted. Apple said no, supreme court said yes.

We have a racing team that tests the latest and greatest software and hardware, under contract with confidentiality agreements intact. We do not use our customers for any testing, even if they wanted to and volunteered.

I.T.Guy

iTrader: (1)

understood, unfortunately with this model your customers will always question what advantage your "team drivers" have over them during big races. Also the reason most software companies use beta programs is to thoroughly test their products before hitting the shelves. I have no clue how many team drivers tekin has, but lets say its 100. Can 100 users thoroughly test and report bugs and glitches better than say 5000? This model has been proven time and time again.

I do understand the warranty factor, but can loading a different firmware release fry your esc? If so, maybe that's another issue.

Buckaroo

iTrader: (3)

Yes, certain releases of software can fry things in certain combinations, especially if things like drive frequencies, boost ramps, current limits, and other things are pushed near or beyond the envelope. Often parts of things like this are left with higher than max normal adjustments in teh Beta release to testers to help figure out where the mean failure is for a particular setting (or if a particular line of programming or feature even has merit or value to the end user), so that a safety margin can be spec'd for the general public release.

History has shown that the grossly untrained will invariably break the weakest link, and then invariably blame the software guy for their own lack of understanding (you're the IT Guy, how many trouble calls do you field that are user error? ). I'm with Tekin on this one, limit your liability by testing as close to in-house as possible. THAT model has brought us stable updates that are easy to understand and that the common fool has to work hard enough to destroy things with that it's obviously his own fault.

Nightmare scenario: Joe Cool gets his foot in the door Beta testing ESC software, and it slips from his hands (accidently or intentionally, doesn't matter). Now it's 'general release' before being finished, and it has a flaw or performance envelope test that causes motors to burn up in certain combinations, thus exposing Tekin to liability to persons (and here's the key part) WITHOUT their consent and understanding in writing. Following that damage to the brand name is someone willing to file a class action suit whereby Tekin has to replace/refurbish the ESC and all motors allegedly burned up by the software. That's the 'writing on the wall' if you will about the Supreme Court decision about the Iphones.

With a limited test team, they can also easily tag software releasese, if necessary, to certain users or types of racers so that if anything does make it out, they know 100% who did it!

You and I, Joe Consumer, then has to pay by way of increased prices to pay the settlement for Joe Cool's mistake. No thanks.

In light of the major manufacturers not having had any real trouble with things melting down (or other problems), I'd say that they've got a pretty robust process in place for testing.

slsspark

I am looking for both blinky and boost. and I would think that a rollout would be fairly specific to the ESC and timing/boost combos, if it were blinky only I would think that the rollout would be kind of "generic" by motor manuf/model, not so much ESC.

goots

iTrader: (20)

I would like to know also. Specifically Hara's RS settings at the iic

Randy_Pike

iTrader: (6)

Hara's 17.5 SS or Super Stock settings. He was Fdr's at 6.3

MikeXray

iTrader: (73)

Actually those 100 (probably more like 20) drivers can more reliably test and provide feedback than 5000 random racers. Its more important to get feedback from people who can run the same laps for 6-10 mins straight and take out the driver and setup variable that many normal racers try and fix with esc settings.

goots

iTrader: (20)

Randy with your setup sheet you posted what kind of motor temps did you see. Also I was taking a look at his TCX iic 2011 setup sheet on petitrc. If im not mistaken he was geared up at 5.69fdr 108 spur 37pinion. Also the pictures on his Sonic motor has his timing set at the last mark. lol im confused

303slowdown

iTrader: (24)

Sorry but I don't think most team drivers give their true setups. Some might but not all.
I'm guessing that's why theirs discreptencies.

goots

iTrader: (20)

Thats true, but... Im still confused as what I should use as a reference for the 17.5 sonic motor. Boost, turbo, and gearing on the setup sheet sounds right. But the rpm range has me confused. Can someone school me on having such a narrow start and end rpm range for the Sonic motor and the characteristics of the Sonic motor itself.

Im currently running a d3 with a more broader RS rpm range (hara iic 2010 RS setup for starting reference)

303slowdown

iTrader: (24)

The narrow rpm range will kick the boost in faster . I don't have any experiance with the reedy motor yet sorry.

Randy_Pike

iTrader: (6)

Hara did try gearing as low as 5.7 at one point but after watching the car and talking to him he went with my suggestion and went back towards the 6's. I take notes when I'm at larger races and working with team drivers. I track each run and note any changes we make both to esc and the car.

This gearing may not work at your home track. IF it's not the IIC 2011 layout I'd say you'll have to find your own gearing but my suggested range is a suitable starting point. Oh yeah..you have to drive like Atsushi also

Randy_Pike

iTrader: (6)

This is also not true, at least with Tekin. All of our drivers know up front that they will share their setups with the public after the event is over. Part of being on our team. Believe it or not..your call.