Rangefinder remote servo, controller or battery issue

boogie

New Hunter
I've recently got myself a boba helmet with a servo fitted to the rangefinder. Sometimes when I first switch the servo on in the helmet the rangefinder goes a bit mad - flicking up and down quickly before settling and working normal, or sometimes not working at all. There's a faint electrical feedback noise from inside the helmet. When it's working normally there's no noise. Does anyone have any suggestions where I should start to investigate, is it bad batteries, the remote control switch or the servo itself?
 
We would need to see the setup inside the helmet before we could offer any ideas.
 
We would need to see the setup inside the helmet before we could offer any ideas.


I'm not sure if I've picked up the right bits on these photos but this is what's inside, plus the battery holders (AAA) but I figured you wouldn't need to see this part.

20151104_200035_zpsnqwsf51r.gif


20151104_200027_zpskpkgfzzh.gif
 
I don't think it's the batteries or the servo. Servos run off of PWM signals and whatever is sending those signals to the servo is more than likely the culprit. One of the white wires looks frayed, and that could be prt of the problem. Another is how all the electronics are exposed, so any moisture or static electricity could fry just about everything.
There is a lot going on there parts wise so it is going to be difficult trying to figure out what does what. Do you have lights in the rangefinder? Are there fans or anything else in the helmet? The small board with the blue capacitors looks like a light board, but I'm not sure what the silver thing is for.
 
I'd noticed the frayed white wire after I'd uploaded the picture and think I'll start with that. The rangefinder has lights which operate differently in the up position than down. No fans in the helmet though.

After that I'll have a look at the sender/button in the gauntlet

Sent from my SM-T210
 
This thread is more than 8 years old.

Your message may be considered spam for the following reasons:

  1. This thread hasn't been active in some time. A new post in this thread might not contribute constructively to this discussion after so long.
If you wish to reply despite these issues, check the box below before replying.
Be aware that malicious compliance may result in more severe penalties.
Back
Top