Welcome Guest Search | Active Topics | Log In | Register

r2d2 not starting up Options
mattology
#1 Posted : 05 February 2019 12:45:07

Rank: Beginner Level 1

Groups: Registered

Joined: 01/02/2019
Posts: 6
Points: 18
Hi there

I have completed my r2d2 build. When I fire him up, he moves a few cm forward, the front red light comes on and he makes a few noises, but the head unit doesn't spin and the other buttons (road, lightsaber, arms, wifi) don't do anything

I have ordered new batteries (https://www.ecoluxbatteries.co.uk/ampsplus-18650-30q-3000mah-15a-battery) but still have exactly the same problem

Has anyone else experienced this problem or is there anything obvious i should check for. I have gone through all the wiring and am almos 100% sure its correct

Thanks

Matt
rdlk72
#2 Posted : 05 February 2019 13:15:22

Rank: Newbie

Groups: Registered

Joined: 05/02/2019
Posts: 3
Points: 9
Location: United Kingdom
Hi,
I have exactly the same issue with my R2.. and the same batteries.

I'm also pretty sure i plugged everything in correctly, and ran the tests on the various components as described in each magazine.

Could it be that one of the circuit boards is faulty or damaged?

Any help would be very welcome as i'm currently very disappointed that i've spent two years making something that does't work :-|

thanks
Richard.
Tomick
#3 Posted : 05 February 2019 13:53:54

Rank: Pro

Groups:

Joined: 24/08/2009
Posts: 48,827
Points: -13,348
Did the initial individual battery charging in the Test charger go as per the instructions and properly/fully charged?

If so, can you double check that all of the batteries within the battery box are in full in contact with the terminals at both end of the each battery slot., If so, can you check the output voltage of the battery box (using a multimeter) that the output voltage is 12.3 volts?




mattology
#4 Posted : 05 February 2019 17:10:24

Rank: Beginner Level 1

Groups: Registered

Joined: 01/02/2019
Posts: 6
Points: 18
Hi Tomick

Thanks for such a quick reply. All batteries (both sets) were charged until the display showed FUL and appear to be connected properly in the battery box.

I just went to test with a multimeter but when I touched the battery box it created a small spark and small burning smell (not sure if I tested in the wrong part). The bits that did work, still worked for a few mins afterwards but now when I turn on I am getting absolutely nothing - and now worried I have created a totally different second problem

Thanks

Matt
mattology
#5 Posted : 05 February 2019 17:12:34

Rank: Beginner Level 1

Groups: Registered

Joined: 01/02/2019
Posts: 6
Points: 18
Update - I have just re-primed the batteries and I am back to how things were - power comes on, R2 moves but head doesn't spin...

Please can you let me know what points I should be checking with the multimeter...many thanks
Tomick
#6 Posted : 05 February 2019 17:21:03

Rank: Pro

Groups:

Joined: 24/08/2009
Posts: 48,827
Points: -13,348
Disconnect the battery box terminals from the MCU, then put the prongs on the multimeter in the black ended terminal of the cable from the battery box. You can see on that cable it has two terminals which is positive and negative, red and black cable feeding into the black end of the wire.

If should give a reading of 12.3v and full voltage coming out of the battery box.

You must disconnect the battery box from the MCU first before carrying out the test.
mattology
#7 Posted : 05 February 2019 18:02:03

Rank: Beginner Level 1

Groups: Registered

Joined: 01/02/2019
Posts: 6
Points: 18
Hi Tomick

Thanks again for a quick response

I am getting c12.2v reading

Does this sound about right?

Thanks

Matt
Tomick
#8 Posted : 05 February 2019 18:11:26

Rank: Pro

Groups:

Joined: 24/08/2009
Posts: 48,827
Points: -13,348
Yes, then if the wiring plugged into the MCU is correctly plugged, it’s likely to be the MCU at fault and in need of replacement, contact customer services to obtain this.
mattology
#9 Posted : 05 February 2019 19:20:03

Rank: Beginner Level 1

Groups: Registered

Joined: 01/02/2019
Posts: 6
Points: 18
thank you - will do
luigione
#10 Posted : 11 February 2019 18:49:29

Rank: Pro

Groups: Registered

Joined: 27/10/2012
Posts: 146
Points: 427
Location: London
I had the same problem, turns out I had put the dome motor cable the wrong way round, refitted it correctly, and now nearly everything works as it should, the problem I have now is the head spinning too fast and crashing into the end stop, I believe quite a few people have had this issue, fixed by changing the motor.
mattology
#11 Posted : 18 February 2019 08:15:30

Rank: Beginner Level 1

Groups: Registered

Joined: 01/02/2019
Posts: 6
Points: 18
Hi all

Just to confirm/update - the new MCU did the job. Everything now works as expected with 2 small problems:

1. Head spinning too fast. I see from this and other threads I need a new motor. I will order now

2. I can get direct wifi to work but not local. I will keep trying

Thanks for all your help

Matt
Markwarren
#12 Posted : 18 February 2019 10:11:38

Rank: Super-Elite

Publisher Medal: Featured Build of the MonthActive Service Medal: 500 post active service MedalPurple Medal: Super active service medal for 1000 postsTurquoise Medal: Turquoise Medal for model making know-how contributionOutstanding Build: An award for an outstanding buildBuild-Diary Medal: Build-Diary Medal of HonourRed Medal: Red Medal
Groups: Registered, Administrators, Global Forum Support, Moderator, Forum Support Team, Official Builds

Joined: 04/01/2016
Posts: 6,544
Points: 19,949
Location: Northamptonshire, England
Hi Matt

Glad to hear the mcu is working. The next move will be to fit a new motor, hopefully that will resolve the head spinning.

If you are getting local Wi-fi then I’m sure the local will resolve itself once the head has been resolved. You could als try scanning the QR code in a semi darkened room.

Also make sure you have the up to date App installed

Regards
Mark
stwood6
#13 Posted : 18 February 2019 17:35:28

Rank: Beginner Level 3

Groups: Registered

Joined: 30/05/2017
Posts: 29
Points: 93
Location: USA
I've spent a lot of time trying to work the Local WIFI thing. First of all, why they resorted to a barcode scan is completely beyond me - way to complicate things! A direct connection could have been used to set the local wifi settings in so R2 easily without all this time consuming mess.

But - given we have to use that barcode, here's what I've found after spending hours on this.

1 - You need a wifi password. If you have a router without a password, the Iphone will let you leave the password blank (android won't) and generate a barcode. But, when you eventually get R2 to read the barcode, he will reject it by flashing red.

2 - Remove the bezel that covers the camera. I was never able to get it to read the barcode with the bezel on, no matter the lighting of the room. Once he reads the barcode successfully, put it back on.

3 - Set your phone screen brightness up. The dimmer screen seems to be harder for him to read.

4 - There is a sweet spot in front of R2 for the barcode to be read. For my Iphone it is about 3 to 4 inches away from his camera, angled forward slightly. I wore my arm out trying to find the right spot. I'm sure it differs based upon your screen size and brightness. But when you find it, he reads it easily.

Good luck!
Current Builds: R2D2, Millenium Falcon
Users browsing this topic
Guest (5)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2009, Yet Another Forum.NET
This page was generated in 0.308 seconds.
DeAgostini