Diem Turner
Yes...I have a Premium Member
Premium Member
Excellence Award
Rig of the Month Winner
Build Thread Contributor
I'm having a little trouble following the reasoning here...so if I'm understanding your concern correctly from the posts in this thread, there are reports from people who were using an XLX2 in sensored mode and it worked fine for a while and then, at some point, the motor and ESC would only work if the sensor wire was removed and just run in unsensored mode. In response to this, the idea is to, perhaps, just only run it unsensored so this doesn't occur? So in both scenarios, you arrive at the same end state of only being able to run unsensored but in one of the scenarios you get to drive sensored for a while and in the other you don't because you just never try it? Am I understanding this correctly?I‘m a little spooked by all of the reports lately as well. I was also thinking of running sensorless, which really sucks because I was very much looking forward to all the great things I’ve heard about sensored setups.
Glad you haven’t had problems. A couple here have done the motor disassembly and cleaned everything with contact cleaner, etc., as well as replace sensor cables to no avail. I really would prefer to run sensored. So many say it’s such a great upgrade and everything is just butter. I can’t say that it’s a definitive common denominator, but it seems as though most that have the problems are those using the rigs as bashers, not speed runners. Maybe repeated starts are the issue, or have some bearing on it?
And I think you mentioned in another thread that you’re now experiencing warranty issues, and that they said it was “user error” or something. That makes the whole thing a bit more concerning for sure.
If yes, then I cannot make sense of why you wouldn't use sensored for the time that you can (this, of course, is all under the presumption that it wouldn't just work continuously based on a couple of anecdotal reports), even if just to see what the difference is. Moreover, I don't quite understand the readiness to, essentially, throw in the towel and concede territory to Castle that they can just sell us a product for not little money where one of its core features can just stop working for no reason and that this is just assumed to be the consumer's problem...all before even trying it out? I don't get it. That makes no sense to me. This just makes me want to use my motors in sensored mode even more (I'm not sure that's possible because I'm pretty sure I always use my Castle motors in sensored mode as it already stands but I shall re-double my efforts to ensure I'm definitely doing it).
I'm sorry but, Castle can't just make, what clearly sounds like either a manufacturing or (more likely) programming/software/firmware issue, MY problem. That's not at all how this works. Their ESCs and motors are designed and advertised as being sensored setups and, if you want to use it as such, you shouldn't feel like you're walking on eggshells to use their product as advertised. You gave them your hard earned cash in exchange for a product that does this, this, this and this (as advertised). That's a binding agreement aka contract. You've upheld your end of the bargain and should have no trepidation about them upholding theirs.
Sorry, but I would have responded with, "Yeah that's fine. And you can stop sending me XLX2s as soon as you send me devices that work as advertised. I'm not doing anything out of the ordinary and you can't just make a fault in your product my problem like this. Your warranty has conditions and a framework and there aren't any clauses that stipulate if the schmuck, me, uses your product as intended, that you have the right to arbitrarily change the conditions of my warranty claim parameters and my parameters only. That's not how warranties work. I know my rights. I have no interest in making a legal matter out of this but I will if you force me to. I'm only asking to receive the product you advertise and I paid for. That's all I ask for and there's nothing unreasonable about that."I haven't contacted them since they replaced my xlx2 that was the replacement for the one that burst into flames. It was the 2nd time I had ever contacted them for warranty and they told me I should gear below stock and "we can't keep sending you xlx2's". He was interested in the data logs and I sent them, they showed the xlx2 died without even going above like 250 amps or so but I never heard anything back from him. I've been dreading having to contact them about an xlx2 again.
They can go pound sand if they think that's an acceptable solution to their problem. But that's just me.
Honestly, I wouldn't get all hot and bothered about it. Just use your ESC as though this conversation here had never occurred and just cross the bridge of how to deal with it should it become necessary when you get there. I can't exclude the possibility that it might, but I wouldn't operate under the assumption that it will. As I already wrote, I have two XLX2s in action, both running sensored mode 95% of the time and everything is fine. Don't pull an Amber Heard and the bed before it's time.This is concerning. Telling you to gear below stock is akin to saying "the stock esc was capable of gearing our xlx2 isnt". The "we can't keep sending you xlx2s" kind of suggests they know there is a problem, they know they haven't fixed it yet, therefore they also know the replacement won't last long either.
Dafuq I get myself into here?