RC Street Wars

Thanks for being a top engager and making it on to my weekly engagement list! You guys really shine!

Larry Puckett, Cole Clement, Buick King, Damian Murillo

Dynomite Dave Pittman, setting his 2.0 down for the first time!
3rd time pulling the trigger! 1.7’s! Boom 💥

CAROLINA MELTDOWN - THE ONE 2.0 MAKES ITS COMPETITION DEBUT

Team RC Street Wars rolled into the Carolina Meltdown at 803 Rock Hill NPRC this weekend with something new to prove.

The One 2.0.

And for its first real competition outing, we couldn't have asked for a much stronger debut.

Old Man Bob, Dynamite Dave, and Gary Karamikian showed up with the new platform and immediately began putting down competitive passes.

Dynamite Dave's story might say the most about the car. He actually finished assembling his One 2.0 at the event. He put the car on the starting line for the first time that morning, and by only its third pass, it was already running in the 1.70s.

That's the kind of baseline we were hoping this platform would have.

But as the day progressed, the challenge changed.

Track temperature climbed past 135°F.

And we quickly learned that Limited Prep racing isn't simply about finding more power or more traction.

It's about understanding the relationship between track temperature, tire temperature, prep application, prep temperature, available grip, and power delivery - and knowing how that relationship is changing from one round to the next.

That's where the weekend became especially valuable for us.

During competition, Gary's One 2.0 put down a 1.678 @ 88 MPH first-round winning pass - an extremely strong run considering the heat and deteriorating conditions.

As temperatures continued climbing, times across the field began moving toward the mid-1.70s.

Gary ultimately advanced all the way to the final.

The car was out front for much of that final run, but the decision was made to be conservative with power as the racing surface became increasingly difficult. The car came up just short at the stripe.

Gary summed it up afterward:

"The track was getting so hot, with measured temperatures above 135 degrees going into the final. I felt like I needed to play it a little safer. Unfortunately, I played it just a little too safe and didn't have enough power at the back to hold onto the lead."

That's racing.

And more importantly, that's data.

We now have an entire day's worth of information covering changing track temperatures, surface conditions, tire behavior, prep application, gearing, power delivery and vehicle response.

We'll take all of it home, analyze it, and start building a better model for the next race.

Dynamite Dave probably described the weekend best.

By the end of the event, he felt confident that we could make the car do essentially anything we asked of it.

The challenge wasn't figuring out how to make the car work.

The challenge was deciding what we needed to ask it to do for the conditions in front of us.

And that is an exciting problem to have.

But something else happened this weekend that we're equally proud of.

Throughout the event, racers from other teams came over asking questions.

What differential setup are you running?
What gear ratio?
What are you doing with the motor?
How are you approaching the tune?

We shared.

Differential settings. Gear ratios. Motor tuning ideas. Setup philosophy.

Why?

Because RC Street Wars has always believed something very simple:

You can only be as good as your best competitor.

We don't want to make racing better by keeping everyone else slow.

We want to help make everybody faster.

Better racers create better competition.

Better competition forces better engineering.

Better engineering pushes manufacturers, tuners and racers forward.

And ultimately, that improves the sport for everyone.

So we'll go back to work.

We'll study the data.
We'll study the track.
We'll study the prep.
We'll make changes.
And we'll come back better.

The One 2.0 has officially arrived.

First competition weekend.
1.678 @ 88 MPH.
A trip to the final.
And a tremendous amount learned.

This is only the beginning.

LET'S GO FAST - TOGETHER.
Dynomite Dave Pittman
Bob Belinda Roberts
Cole Clement

Castle Creations possible failure scenarios,
Ok so more than 30 people have contacted me directly about them burning up their esc "when plugging in the castle link" I'm here to say I have studied their published drawing and documents from the US Patent filings, and I have identified the most likely scenarios.
Quick Summary, the esc had already been failed from the prior run, plugging in the "Castle Link" with the battery - batteries still connected to the esc exposes the "Existing failure" because of how the esc turns on when the castle link energizes.

read my document, its factual, correct and a long read, but required to convey the point.

And yes, there is a scenario that is "item defect" but it's down the list.

There is a link to the document in the comments.

Castle ESC Failure During Programmer Connection
Core interpretation
The statement “the ESC failed when the programmer was plugged in” establishes the moment the failure became visible. It does not, by itself, establish the original cause.
The critical conditions are:
• Was the propulsion battery connected?
• Had the ESC previously been operated or electrically stressed?
• Was the correct Castle Link version used?
• Was the connector correctly oriented?
• Were any other powered devices connected?
• Where did the smoke or fire originate?
________________________________________
Scenario 1 — Previously used or suspected-damaged ESC, battery connected
State and conditions
• ESC has previously been run.
• Previous overcurrent, overheating or voltage stress is possible.
• Propulsion battery remains connected.
• Castle Link is attached and energizes or initializes the control circuitry.
• Battery supplies the high-energy fault current.
Most likely to least likely

Rank Possible explanation Classification Why it fits
1 Preexisting power MOSFET or gate-driver damage becomes catastrophic when control circuitry initializes Prior operational damage The programmer can wake the controller while the battery supplies substantial fault energy.
2 Preexisting phase-bridge damage produces shoot-through or a phase-to-bus short Prior operational damage A damaged high-side/low-side bridge can draw destructive battery current when initialized.
3 Damaged BEC, regulator or low-voltage rail is energized, allowing the battery to feed the fault Prior operational damage Operational overstress may affect more than the output MOSFETs.
4 Battery was connected in the wrong programming sequence User error/misuse Castle specifies Link first and then supplemental battery power for applicable HV controllers.
5 Motor, receiver, external BEC or another powered accessory creates an unintended current path Installation/user error Multiple connected power domains can change the failure mechanism.
6 Reversed or offset RX connector User error Incorrect pin alignment could apply power to the signal or wrong circuit node.
7 Damaged RX lead, Quick Connect or extension harness Equipment damage/installation A pinched, shorted or incorrectly wired harness could place power on the wrong conductor.
8 Defective or incompatible Castle Link programmer Programmer fault Possible, particularly if the adapter produces incorrect voltage or pin states but should be tested before concluding.
9 USB transient, grounding problem or electrostatic discharge External electrical event Technically possible but normally difficult to prove and less likely without supporting evidence.

Most probable general sequence
flowchart TD
A["Overcurrent, heat or voltage stress"] --> B["Latent ESC damage"]
B --> C["Castle Link initializes control circuitry"]
C --> D["Damaged switching path conducts"]
D --> E["Battery supplies high fault current"]
E --> F["Smoke or fire"]
Probable interpretation
In this scenario, Castle Link is more likely to be the triggering event than the original cause. The battery supplies the energy that turns latent damage into a catastrophic failure.
------------------------------------------------------------------------
Scenario 2 — Previously used or suspected-damaged ESC, battery disconnected
State and conditions
• ESC has previously been operated.
• Propulsion battery is positively disconnected.
• Motor may or may not remain connected, but it is not an energy source.
• Castle Link supplies low-voltage power through the RX/programming connection.
Most likely to least likely
Rank Possible explanation Classification Why it fits
1 Previously damaged BEC, regulator or low-voltage supply rail is energized Prior operational damage The programmer directly powers portions of the low-voltage circuitry described by the patent.
2 Previously damaged gate-driver IC or driver supply develops a low-voltage short Prior operational damage The driver may have been damaged during the last run but not visibly failed until repowered.
3 Power MOSFET has gate-related damage connected to the driver or logic rail Prior operational damage Gate oxide or gate-driver damage can provide a path from the low-voltage rail into the damaged power stage.
4 Carbonized PCB material or damaged trace creates a conductive path Prior operational damage Heat damage can leave a partial short that becomes hotter when repowered.
5 Shorted capacitor, protection diode or communication-interface component Prior operational/component damage These components can fail short and smoke when RX power is applied.
6 Reversed or offset programmer connector User error Incorrect polarity or pin alignment could damage low-voltage circuitry.
7 Damaged or incorrectly wired RX lead, extension or Quick Connect Equipment damage/user installation The programmer may be correctly oriented relative to a harness that is wired incorrectly.
8 Defective or incompatible Castle Link Programmer fault Requires measurement or repeatability with other ESCs before attribution.
9 USB overvoltage, ground transient or electrostatic discharge External electrical event Possible but should require positive supporting evidence.
Probable interpretation
This is the strongest scenario for the “Castle Link exposed an existing failure” explanation.
Because the propulsion battery is absent, a large drain-to-source short in the motor-output bridge alone may not explain the smoke. The affected path would probably involve:
• Low-voltage supply circuitry
• BEC or regulator
• Gate-driver circuitry
• MOSFET gate damage
• Communication circuitry
• PCB carbonization or contamination
The location where smoke first appears becomes extremely important.
________________________________________
Scenario 3 — New, never-run ESC, battery connected
State and conditions
• ESC is represented as new and has never been operated by the customer.
• Battery is connected during programming.
• The ESC may still have been electrically powered during factory production or testing.
• Castle Link initializes the controller while the battery energizes the power stage.
Most likely to least likely
Rank Possible explanation Classification Why it fits
1 Incorrect connection sequence, orientation or wiring User error/installation These must be eliminated first because the battery makes any error substantially more destructive.
2 Internal manufacturing or assembly defect Product defect A solder bridge, incorrect component or conductive contamination could become catastrophic under battery power.
3 Latent component defect Product/component defect A defective MOSFET, driver, regulator or capacitor may fail during its first customer power cycle.
4 Damage sustained during factory programming or electrical testing Pre-delivery damage “Never run by the customer” does not prove that the unit was never powered.
5 External BEC, receiver or accessory causes conflicting power sources User installation/system interaction Multiple power sources may feed one another if wiring or isolation is incorrect.
6 Shipping or handling damage Pre-delivery damage A cracked PCB or capacitor could create a short when first powered.
7 Wrong Castle Link version or incompatible accessory Compatibility/user error Cobra ESCs require Castle Link V4 according to Castle.
8 Defective Castle Link adapter or USB source Programmer fault Becomes more credible if the same programmer produces abnormal measurements or affects multiple ESCs.
9 Firmware or startup-state defect Product design/software defect Possible if initialization creates unsafe gate states, but it requires manufacturer-level analysis.
10 Random ESD or connection transient External electrical event Possible but generally difficult to rank highly without measurements.
Probable interpretation
The battery makes it difficult to determine whether the programmer supplied the destructive energy. More likely, the programmer or connection initiated a state change while the battery supplied the energy.
A new ESC does not eliminate a product defect, pre-delivery damage or connection error.
________________________________________
Scenario 4 — New, never-run ESC, battery disconnected
State and conditions
• ESC is genuinely new to the customer.
• It has never been powered or operated by the customer.
• Propulsion battery, receiver, external BEC and motor are disconnected.
• Only the correct Castle Link and USB connection are present.
• Connector orientation and compatibility are verified.
Most likely to least likely
Rank Possible explanation Classification Why it fits
1 Internal manufacturing or assembly defect in the RX-powered circuitry Product defect A solder bridge, misplaced component or contamination could short the low-voltage rail immediately.
2 Latent defective component Product/component defect A regulator, capacitor, protection device, driver or interface IC may have arrived internally defective.
3 Damage during factory testing, programming or rework Pre-delivery damage The component may have been weakened before reaching the customer.
4 Reversed or offset RX/programmer connector User error Must be eliminated through photographs and verified pin orientation.
5 Damaged, rearranged or incorrectly terminated RX connector Manufacturing or wiring defect Wire colors may look correct while the contacts are positioned incorrectly.
6 Shipping or handling damage Pre-delivery damage A cracked board or capacitor may fail on first power application.
7 Defective Castle Link adapter or USB cable Programmer fault Verify output voltage, polarity, pin behavior and operation with a safe test load.
8 Wrong or incompatible programmer version Compatibility error Particularly relevant because Cobra controllers require Castle Link V4.
9 USB source overvoltage or abnormal grounding External equipment fault Requires direct voltage measurements or repeatable evidence.
10 Electrostatic discharge during connection External event Technically possible but generally difficult to confirm after the failure.
11 Firmware startup defect Product design/software defect Possible, but with no propulsion battery the damage should primarily involve RX-powered circuitry.
Probable interpretation
If every stated condition is verified, an internal product defect or pre-delivery damage becomes the leading category.
This would be the scenario in which normal programming power appears most closely associated with the failure. Even then, the correct conclusion would be:
Applying programmer power exposed an abnormal condition in the ESC or programming system.
It would not automatically prove that the normal, properly functioning Castle Link design damaged an otherwise healthy ESC.
________________________________________
User-error and misuse category
These conditions should be investigated separately from ESC failure history.
Most likely to least likely
Rank User or installation condition What must be verified
1 Battery left connected when supplemental battery power was unnecessary Photograph complete wiring and identify ESC requirements.
2 Incorrect connection sequence on an ESC requiring battery assistance Determine whether Link or battery was connected first.
3 RX plug reversed Verify signal, positive and ground positions at both ends.
4 RX plug offset by one pin Inspect connector alignment and witness marks.
5 External BEC or receiver battery still connected Trace every red positive wire in the system.
6 Incorrectly wired extension, Quick Connect or adapter Perform pin-to-pin continuity testing.
7 Wrong Castle Link generation Confirm V3 versus V4 and exact ESC model.
8 Damaged RX cable or exposed conductors Inspect and test for intermittent shorts.
9 Conductive debris, moisture or contamination introduced during installation Inspect under magnification before cleaning.
10 Unsupported USB adapter, cable modification or nonstandard connection Document every device in the connection path.
11 Static-discharge event Review handling environment and grounding precautions.
Castle states that Cobra ESCs require Castle Link V4. Castle also specifies the signal, positive and negative orientation and describes supplemental-battery connection requirements for certain HV controllers. Castle Link versions and compatibility, Castle Link FAQ
Condensed decision table
ESC condition Battery state Leading explanation
Previously run or suspected damaged Connected Latent power-stage or driver damage exposed during initialization; battery supplies destructive energy
Previously run or suspected damaged Disconnected Latent BEC, regulator, gate-driver, gate-related or low-voltage damage exposed by RX power
New/never run by customer Connected Connection error, manufacturing defect, latent component defect or pre-delivery damage
New/never run by customer Disconnected Manufacturing/component defect, pre-delivery damage, wiring defect or abnormal programmer
Any condition with reversed/offset connector Either Connection error becomes a primary suspect
Multiple power sources present Either Power-source conflict or unintended back feed must be investigated
Same programmer involved in several failures Either Programmer, cable, USB source and procedure move substantially higher on the list
Different programmers but same ESC batch fails Either Manufacturing, component-batch or product-design defect moves higher
Recommended public-facing conclusion
Castle Link can be the moment at which an ESC failure becomes visible without necessarily being the original cause. In a previously operated ESC, latent damage from current, heat or electrical stress may be exposed when the programmer energizes the control circuitry. If the propulsion battery remains connected, it can supply the energy that turns a latent fault into smoke or fire. For a genuinely new ESC failing with only the correct programmer attached, manufacturing defects, latent component defects, pre-delivery damage, incorrect wiring, adapter faults and connection errors must all be investigated. The timing of the smoke alone does not establish root cause.

Who’s going Fast!

Heading to Texas, The Full Monty!
RC Street Wars custom built Drag Slash’s
Motor -ESC combo
Full race outlaw suspension
RC street wars 9900 Carbon Elite batteries
RC Street Wars ready to Race Voodoo pre-mounted wheels and tires.
And to top it off some custom fitted and painted bodies!

Ricardo is unstoppable!
Congratulations to Ricardo Granado on taking the grand prize! All the cash 💰
Ricardo is rocking a RC Street Wars Motor- ESC combo, and RC street wars 9900 Carbon Elite battery and he has been a dominant force for several seasons now.
Can anyone dethrone Ricardo?
I don’t know but I do know people are calling me to get his secret’s 🤐
My lips are sealed 🤐

Congratulations to Fredrick Todd on his win, thank you for trusting RC Street Wars to be part of your success!

We are appreciative of all your support.

Wings make you go fast! 😎

You know what I love about Caldwell Race Works wings.

You can prep your body, drill your holes (existing wing)
& when the new ones arrive, they just bolt up and look great.

There are many options out there, for us at RC Street Wars, we need performance, reliability, and quality.

Kevin delivers on all the above.

When time is tight, we count on wings that bolt right up and work every time

If you’re in the market for a RC wing, check out this website as he has so many options available and even custom painted bodies for your RC.

https://caldwellraceworks.com/

Thank you,

GK