Charging Produces tiny motor pulses (Video) Space cell- SOLVED

In simple terms. If we build it we take full responsibility for faults first 12 months.

If we didn’t build it there must be proof it’s DOA / manufacturing fault provided in writing/video/photo in first 60 days.

This is the best we can offer at this stage.

How does one go about proving it though with electronics?

in 95% of cases DOA & manufacturing faults will be identified immediately, because they don’t work. If several weeks of product use have passed & a fault occurs it becomes difficult to prove it is DOA/Manufacturing. Which normally means it is not DOA or Manufacturing fault… Of course, every case is different.

Our long term goal is to offer instant replacement warranty on all faults for 12 months. But it will be on kits that we have assembled, so it starts moving away from DIY.

Many thanks for for the flag @Rye and your response @onloop.

To be frank, I don’t think that the quality of this remote equals its cost and I can see why you moved on from this one. The receiver and remote have both failed in under 3 weeks of actual riding time. The remote B button came loose (during shipping) which I repaired before I even used it for the first time, and this chip issue happened within the first 60km of riding. I had it in my possession for over 4 months but its only been actually used for 3 weeks.

I do understand the necessary limitations you need to put on DIY scenarios… you can’t be expected to cover user error or neglect. I for one would have taken Maytec to task over the build quality of this and asked for them to send you replacement parts to have on hand for these scenarios (Raptor or otherwise).

I will give it my best shot to try and bring it back to life with some amateur-yet inspired soldering. Wish me luck.

1 Like

So after a good 2+ Hours of very finicky soldering I came up with the attached solution. Actually is was @lox897 idea for the jumpers! The pulsing issue seems to have been resolved.

It looked like there could have been 1 or 2 small areas that potentially could have short circuited but it’s works again, with no apparent issues. I’ve added hot glue across the stress points as well.

1 Like

1 Like

great work, you should be proud of that effort.

1 Like

Thanks @onloop . I’ve just been charging it, and the pulsing thing still occurs while charging or just Turned on. It is in the same rhythm as the vesc lights too. Could be the receiver chip is just playing up? :thinking:

I’ve had 3 steeze receivers break like this… This, along with the poor braking curve, is why I’ve moved away from it and I’m now using the mini 2.4ghz remote many are selling on this forum. Had no issues so far with that remote, and it’s a fraction of the price.

1 Like

Well @evoheyax I took out the board for a quick blast today and it seems as though the chip has finally given up. Bummer though… thought I’d worked it out with the jumper solution. I am guessing its more than just the connection. Just glad it didn’t cut out when going top speed.

Bummer, I was hoping this might work. It looks like a nice solder job.

I still haven’t found the perfect solution in my mind. I like to solder everything for reliability, and that was easy with the steez. Just de-solder the ppm thing on the receiver, and solder straight through the pcb and straight through the vesc, most reliable connection I’ve ever had. But as I found out the hard way with the 2.4 ghz mini remote most are using, I tried, but the components as like epoxied to the case of the receiver, and when I tried to get it off, I ripped parts off the receiver board, so you have to using a ppm cable.

I wonder how the nano-x is…

Many thanks to @onloop for sourcing a replacement receiver chip for the steeze.

I’ve resorted to making my own case and additional hot glue to ensure a well supported chip. 3D printer pen to the rescue. It ain’t pretty but it will do.

3 Likes