Neu and Castle Motors Working with Newer Schulze Controllers POSITIVE UPDATE

[RaceMechaniX]

Guys,

I have some surprising good news. I went to the local pond yesterday to test one of the new Fightercat esc's. I thought I would also give the late model Schulze and Neu/Castle motor combo another try too. Not only did the Fightercat esc work great but so did three Schulze controllers. All three are the newer style V16 software esc's. I tried a 24.150wk, a 40.160wk and a 32.200wk. The motors used were a 2215 1.5Y, Castle 1515 1Y, a Neu 1521 1.5D and a Castle 2028. I also had a 1527 1D, but did not have a chance to try and run that combo with a Schulze controller. Overall, every combo worked great which was a nice surprise.

The 40.160 and 32.200 have been back to Schulze at least once for repairs, however the 24.150 was brand new. I am happy to say everything worked. It was a great day of testing!

Tyler

[NativePaul]

Isn't it only the 1Ds that they ever had problems with?

[Anbjorn]

Tyler,
That is good news. Thank you for letting us know!

Anbjørn

[RaceMechaniX]

I was having problems with every Neu motor I had including 1.5D, 1D's, 1Y's and 1.5Y's. I have upgraded connectors from the 200A to 300A versions and I am sure at least one software revision since the last time I swore I would not try a Schulze + Neu combo every again.

Tyler

[RaceMechaniX]

I was having problems with every Neu motor I had including 1.5D, 1D's, 1Y's and 1.5Y's. I have upgraded connectors from the 200A to 300A versions and I am sure at least one software revision since the last time I swore I would not try a Schulze + Neu combo every again.

Tyler

[Fluid]

It is true that the previous versions were problematic with many Neu motors - but the v16 has been out for at least four years. I have run many Neu motors with the v16 Schulzes for years without problems - for example my 1527/1Y has been 100% reliable for a long time with both my 32-170/v16 and 40-160/v16. The only motors which were problematic for me were the 1D motors. Brian had the same experience. The problem is the low impedance of the 1D motors - the Schulzes could not reliably read the rotor position. I could get a few passes just fine, but eventually the motor would stutter and stop.

I spent considerable time corresponding with Schulze about this, but their response was pretty much 'too bad, don't run the 1D motors'. Anyway, I'm glad you have things working for you.


.

[RaceMechaniX]

Jay,

It was the very early V16 units that I had problems with. Primarily a 40.160wk with extra caps. Perhaps it was a software update that solved some of the issues. I'll try a 1D cautiously and see what happens.

From what I have gathered the older Pre-V16 versions worked with the 1D winds. Perhaps this was hit and miss?

Tyler

[Punisher 67]

I spent considerable time corresponding with Schulze about this, but their response was pretty much 'too bad, don't run the 1D motors'. Anyway, I'm glad you have things working for you.
.

Isn't that great when a manufacturer goes right out of there way to deal with a problem .

Tyler and Anbjorn I have 4 of the V16 40/160's and have never had a problem running any of the Y wind motors , Sorry thats no consolation with the D winds

[RaceMechaniX]

Yeah,
At least the Castle ICE and Fightercat esc's so far have been working good on 1D motors. I will try and test some D wind motors next. I know several guys are successfully running the 1D motors in very hot set-ups on the older style systems. Based on the set-up list from the RC-SAW event several were running 1D and 1.5D motors with Schulzes on pretty hot set-ups.

TG