Outcast stuttering with XLX2

[UncleDizzle]

So recently I dropped an xlx2 combo with the 1100kv motor into my outcast. No aftermarket parts in my drivetrain and have 30/47 gearing but everything’s pretty new. Ever since I put the castle set up in it’s been stuttering at low speeds like this. The sensor wire is plugged in properly. I’m wondering if anybody know if this is normal or if it’s even a motor/esc thing at all. Because I’ve opened all the transmission and everything seems normal. I even replaced the center driveshafts. So if anybody has seen this and recognizes it, I’d really appreciate it. I feel like it’s doing a number on my drivetrain.

 

[Hammer Down]

Definitely not normal. Maybe the sensor cable is bad.. have you tried running it without?

 

[UncleDizzle]

Definitely not normal. Maybe the sensor cable is bad.. have you tried running it without?

No that’s a really good idea though. I do have the sore sensor wire that came the combo. Thank you I’m gonna try that right now.

 

[dure16]

If that didn’t fix the issue then I’d call Castle. Something seems very wrong.

 

[rotauq]

This is casued either the sensor cable or the hall sensors on the motor.
If it does the same without the sensor cable (which i doubt) it would be the esc itself.

 

[yaboyhamz]

ok so that started happening to my k8 with xlx2 and 800kv at low speeds, within the next two sessions my red wire came out unsoldered of the chip board. Castle said I had like 13v ripple vs about 2.5v and that made the connections loose. might be that?

 

[UncleDizzle]

Okay great. Thanks for all the feedback guys. I was about to just buy a new sensor wire but that might not fix it. So I’m gonna leave it up to castle. It’s been like this from day one. I’m assuming they shouldn’t hassle me. I’ve had it for maybe 60 days.

This is casued either the sensor cable or the hall sensors on the motor.
If it does the same without the sensor cable (which i doubt) it would be the esc itself.

Okay I actually pulled the sensor wire and gave it light throttle on my bench and it did indeed do the same thing as with the sensor cable.

 

[SrC]

If that didn’t fix the issue then I’d call Castle. Something seems very wrong.

+1

 

[rotauq]

Okay I actually pulled the sensor wire and gave it light throttle on my bench and it did indeed do the same thing as with the sensor cable.

hmm k, i'd seriously expected it to be a sensored mode problem, the cogging was way too consistant to be a bad phase(motor or esc)
But as it happens sensorless too, it's castle time. They are generally good on service/support so don't worry on that part.

If you'd have a second motor (any BL with the right connectors) you could try if it spins normally, castle rep might ask you the same

 

[UncleDizzle]

I actually don’t have any motors with that big of connectors. I do have link if that helps.
Haven’t contacted them yet. Almost home to my cpu. My mobile device doesn’t know my castle password. Neither do I. Lol. Thanks again for the advice fellas

 

[rotauq]

I actually don’t have any motors with that big of connectors. I do have link if that helps.
Haven’t contacted them yet. Almost home to my cpu. My mobile device doesn’t know my castle password. Neither do I. Lol. Thanks again for the advice fellas

You could have a look at the logs, zoom in on few seconds to see what it's acting up. But it's not gonna change anything

 

[SrC]

Yeah, the CC data logs are the first place to check. If you have a sensor connection issue, or just a bad lead, it would show up if you look over the Data logs closely. Need the CC PC link to access the logs.
Sensored Motors, are not supposed to cog at all.
Sensor leads and their Pin outs at both ends are delicate and and the slightest dirt or corrosion can make them fail.
Need to rule that out first, by removing it and running in Non sensored mode. If it runs fine that way, you know it is the sensor circuit at fault.
Always have spare sensor leads around and out in the field with you. They can fail out of no where. Consumable item. Sometimes even a brand new Lead can be DOA. Been there. And they are NOT water proof at all.
Hopefully it is just the Sensor lead. Protect it well on the chassis. They are easily damaged. Even the slightest fine tear in a wire not visible can wreak havoc.

 

[rotauq]

Yeah, the CC data logs are the first place to check. If you have a sensor connection issue, or just a bad lead, it would show up if you look over the Data logs closely. Need the CC PC link to access the logs.
Sensored Motors, are not supposed to cog at all.
Sensor leads and their Pin outs at both ends are delicate and and the slightest dirt or corrosion can make them fail.
Need to rule that out first, by removing it and running in Non sensored mode. If it runs fine that way, you know it is the sensor circuit at fault.
Always have spare sensor leads around and out in the field with you. They can fail out of no where. Consumable item. Sometimes even a brand new Lead can be DOA. Been there. And they are NOT water proof at all.
Hopefully it is just the Sensor lead. Protect it well on the chassis. They are easily damaged. Even the slightest fine tear in a wire not visible can wreak havoc.

"Okay I actually pulled the sensor wire and gave it light throttle on my bench and it did indeed do the same thing as with the sensor cable."

It was already estabilished it acted the same on sensorless mode.
Still good approach for future readers with simular problems though
Also analysing cc datalogs does require some skill. If you don't know what you are looking at you wont see what could be wrong either.

 

[SrC]

Absolutely is a steep learning curve with the CC data logs.
@rotauq, you got this stuff down anyway. You eat this stuff for breakfast.
I was just providing info for others reading here.

 

[UncleDizzle]

Okay I have the data link cable but it sounds like I wouldn’t have a clue what I’m looking at. I contacted castle on Wednesday still waiting to hear back tho. Thank you all you guys have been very informative and helpful.