|
|
 Rank: Beginner Level 2 Groups: Registered
Joined: 22/12/2018 Posts: 16 Points: 48 Location: London
|
Admins,
As per my original post here: https://forum.model-spac...spx?g=posts&t=30527
New Samsung 30Q batteries (even though the ones shown in the photo's Issue 100 - which I bought are 26F's)
New ones are as supplied by 18650.uk which other seem to have had success with as per here: https://18650.uk/product/samsung-30q-button-top/
Same behaviour. So, no change based on new batteries, same as per below:Startup:
Jerks forward, left motor stronger than right, no head movement.
Status Indicator stays red.
Front Arm tick, I guess checking closed. R2 whistles and Projector comes on with Luke on loop. No Audio.
Arms button works but Lightsaber doesn't. All others are fine.
App:
App connects and R2 whistles. Only tried direct mode so far, can't get to Local Mode as I can't get to the blue light flashing point, stuck on Red.
Battery shows 100% on App.
In Video Control Mode:
Video works.
Can 'drive' R2 but head movement is jerky and sometimes goes to the stops of it's own accord. Every now and again the head goes to one of the stops.
In Manual Control Mode:
Projector still stuck on Luke, no audio from the startup even if I choose Leia or Luke.
Shake Head and LCD not working either.
Whistles for projector, shake head and LCD but no action.
On any movement the left motor seems to have more movement so R2 turns slightly right (just like jerk forward test Right motor less effective than left).
Randomly after any App command the head goes to one of the stops again if I reposition it in App. This is common on Video and Manual modes.
Charging Mode:
If I switch R2 on with charger plugged in his head does the calibration thing from the Startup sequence and then the projector flashes white, no video. Does now exhibit normal charging behaviours.
Does that help at all? My gut says the MCU or the Orange Pi are faulty but open to suggestions here as after 3 rewires I'm pretty frustrated.I have again rewired him, just in case. Pretty sure it wasn't the 26F's.
I'm now pretty certain its the MCU or the Pi... Any thoughts?
|
|
|
|
|
At least you now have good Amperage batterys, contact C/S for a replacement MCU and PI. The C/S number can be found on the inside of the 1st page of the magazine. Current builds:-C57,Zero, Lamborghini Countach, Caldercraft HMS Agamemnon,Robi,R2-D2, MFH Cobra .
|
|
|
Rank: Beginner Level 2 Groups: Registered
Joined: 22/12/2018 Posts: 16 Points: 48 Location: London
|
arpurchase wrote: At least you now have good Amperage batterys, contact C/S for a replacement MCU and PI. The C/S number can be found on the inside of the 1st page of the magazine. Thanks, both ordered.
|
|
|
Rank: Beginner Level 2 Groups: Registered
Joined: 22/12/2018 Posts: 16 Points: 48 Location: London
|
Admins,
Just fitted new MCU and new Orange Pi.
Same behaviour exactly as before. No head movement on startup and indicator stays red. I'd be surprised if I have managed to get a second faulty MCU and Pi. Could it be the sensor control board that has been faulty all along?
Is there any way to troubleshoot these issues? Any way we can tell from indications on the head and what he does in sequence thet can give any hints. Going to do a total strip and check all sensors and systems again anyway just in case.
I have buzzed out all of the cabling I can and checked the batteries, battery box and everything again.
As you can guess its getting pretty frustrating.
Thanks.
|
|
|
|
|
Could you check the the battery box voltage across the batterys in situ and also at the cable end please, just so we are sure your getting full power. Order the sensor control board from C/S. Out of interest did your projector under test show both Luke and Leah. Current builds:-C57,Zero, Lamborghini Countach, Caldercraft HMS Agamemnon,Robi,R2-D2, MFH Cobra .
|
|
|
 Rank: Amateur level 2 Groups: Registered
Joined: 13/07/2018 Posts: 41 Points: 141 Location: Slough
|
JaseGill, did you try swapping the head motor and one of the leg motors for a startup test? The process was mentioned in another thread, as a great troubleshooting way to determine if it's the MCU, cable, or head motor that's at fault.
|
|
|
|
Guest (3)
|
US
