Welcome Guest Search | Active Topics | Log In | Register

Dome not turning 180 degrees on power-up Options
hanseater
#1 Posted : 05 June 2019 01:09:33

Rank: Beginner Level 1

Groups: Registered

Joined: 05/06/2019
Posts: 7
Points: 21
Location: Fountain Hills, AZ
I've recently completed my build and for the first two days the 180 degree head spin on power-up worked fine. Now it now longer makes this motion. I get the little roll forward, then silence for approx 15 seconds and then the head lights flash and R2D2 whistles. I can control the dome from the app just fine, but the dome doesn't move during patrol mode. Any advice?
Moderator
#2 Posted : 05 June 2019 15:42:20
Rank: Administration

Groups: Forum Support USA, Moderator

Joined: 27/03/2019
Posts: 49
Points: 149
Hello,

Well, this is a new one! It sounds as though the initialization process has gone haywire. I would suggest you check the connections, particularly those to the right leg motor, and to the head motor. Both of these are "checked" during start-up. The fact that it works during app usage, but not autonomously,seems to further indicate a failure during boot-up.

Have any other R2-D2 builders encountered this? Lets see what the hive mind has to offer as well.
hanseater
#3 Posted : 05 June 2019 16:24:11

Rank: Beginner Level 1

Groups: Registered

Joined: 05/06/2019
Posts: 7
Points: 21
Location: Fountain Hills, AZ
Thanks for the advice. I assume when you say the "right" leg, you are facing the front of R2D2. I fashioned a "test stand" from a box to keep him from rolling off the table at power-up. The right wheel does turn for a second or so at start-up, so I think we're OK there. I'll check the dome connections tonight. At one pint I did remove the batteries hoping that cutting the power to the microchips would force a reload of whatever boot code is used. This is similar to pulling the battery on a misbehaving to clear CMOS memory. It didn't seem to make a difference. I'll post an update tonight...cheers
hanseater
#4 Posted : 08 June 2019 20:03:24

Rank: Beginner Level 1

Groups: Registered

Joined: 05/06/2019
Posts: 7
Points: 21
Location: Fountain Hills, AZ
OK, I've pulled and reconnected every cable involved with the head. I still does not perform the 180 degree spin on power up. I've also tested every function using the smartphone app and noticed that "shake head" does not work. I can still spin the head using the app, so the motor seems fine. I have seen the head move a bit on it's own during patrol mode, but it only is an occasional twitch. Any ideas? I'm scheduled to give R2D2 to my grandson for his 5th birthday in 5 days, so any advice would be appreciated. Thanks...Pete
Markwarren
#5 Posted : 09 June 2019 08:55:19

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
The fact that it turned 180 degrees initially, could point to one of the pins on one of the two long cables that connect to the board is not sitting right. When the head originally moved it may have dislodged part of the cable that performs the startup.
Check the cables making sure that the connections are firmly in and push the pins down using a wooden skewer, do not use anything metallic as this may cause a short circuit. Sometimes the connection is firm but one of the pins has not connected.

Hope that helps.

Mark
hanseater
#6 Posted : 09 June 2019 15:46:25

Rank: Beginner Level 1

Groups: Registered

Joined: 05/06/2019
Posts: 7
Points: 21
Location: Fountain Hills, AZ
Thanks Mark, I'll give that a try. Do you know which cable is used for startup? I recall there is a red and a white cable connection to the motherboard. Just trying prioritize. I wish model-space furnished a schematic or a diagnostic app. I'll try this morning and let you know how things turn out. Thanks again.

Pete
Giggsy
#7 Posted : 10 June 2019 21:10:37

Rank: Newbie

Groups: Registered

Joined: 17/05/2019
Posts: 3
Points: 9
Location: Tampa
Hey Pete,

I have the same issue except it never worked. I posted the question in these forums but never really got an answwer.
We check all the connections and the leads for any breakages.

I contacted DeAgostini and spoke to an engineer. He said could be a problem with MCU or possibly the head motor which has a chip in it.
Waiting for parts to arrive to see if that makes him work 100%.
hanseater
#8 Posted : 11 June 2019 00:51:05

Rank: Beginner Level 1

Groups: Registered

Joined: 05/06/2019
Posts: 7
Points: 21
Location: Fountain Hills, AZ
OK, Hi All, some interesting developments and clues.

After reading lots of other posts (to be honest, I got much better access to forum posts using a google search), one post had an interesting comment. The person described a function not working , but when he plugged R2D2 into the charger and powered up, that function worked! I tried that today and when I pushed bottom power switch, then the on/off switch, R2D2 performed the 180 degree head test. Interestingly, it did not perform the forward lurch from the right leg motor.

Another point, R2D2 will not pair with phone app while on the charger. I have to be honest here, I have not checked the documentation to see if this is normal. I've been in computers for over 42 years and we're notorious for not reading the bloody manual BigGrin .

When I disconnect the charger (and the head "boot" has completed), I am able to wifi pair the phone app and now the shake head function works.

So I've seen that every R2D2 function works, except functionality seems to change based on whether I'm using the charger, or not, or a sequence of the two.

Now, having said that, after reading all the posts, there is a common thread from the experts and they concern the batteries. All the responses suggest checking the batteries with most customers responding with something like "but almost everything works, it obviously has power, so why do I have to check the batteries...there must be something else wrong...circuit board, motor, etc:.

So, here's my battery history:

I purchased 6 Samsung 30Q 18650 3000mAh 15 A button top batteries from the 18650batterystore.com

I put them into the battery pack and charged them with the R2D2 charger. To be honest, I didn't know, what I eventually learned was the individual battery charger , was when I received it with issue 100. I looked at it and thought it was a phone cradle, because of the USB cable. I don't recall seeing any documentation on this charger.

As my thread stated earlier, the 180 degree test originally worked. When it stopped, I did pull the batteries and checked each of them with a multi-meter and the checked out as charges.

I've since read that people have been advised to charge the batteries singly and use the Model-space charger. My plan is to pull the battery pack tonight and check each battery individually.

So, the question is, since I have a fully functioning R2D2, but under different power options, do I have a power issue, and what do I do to resolve it?

I want to thank the experts for their timely responses and advice.

Cheers...Pete
Moderator
#9 Posted : 11 June 2019 02:05:36
Rank: Administration

Groups: Forum Support USA, Moderator

Joined: 27/03/2019
Posts: 49
Points: 149
For some reason, charging individually seems to be the ticket. I used a gang charger the first go, and my R2 didn’t work. So, I topped off the batteries with the single battery charger, and everything functioned as it should have. There is a thread someplace that emphasizes the need to use the single charger, but no solid rationale was given. (At least that I remember, and I can’t seem to find that thread)

Hope this helps!
hanseater
#10 Posted : 11 June 2019 02:58:37

Rank: Beginner Level 1

Groups: Registered

Joined: 05/06/2019
Posts: 7
Points: 21
Location: Fountain Hills, AZ
I've been a software engineer for over 30 years. It's the same with code. Sometimes applications just heal themselves for no traceable reason at all. We'd have users ask "what happened?", our standard answer was "gamma rays hitting the chips."
hanseater
#11 Posted : 11 June 2019 04:20:05

Rank: Beginner Level 1

Groups: Registered

Joined: 05/06/2019
Posts: 7
Points: 21
Location: Fountain Hills, AZ
My bad, and red-faced. Issue 92 has detailed battery prep documentation. I'm positive my issue 92 thought process went like "Oh, whatever, battery box, what's in the next issue so I can build something." Lesson learned. Now recharging each cell with the supplied charger. I recall reading that if one cell is out of spec, the rest will run at the level of the weakest. Rather like a convoy only being as fast as the slowest ship. So yes, lack of battery charge could be the reason for many issues, despite thinking you have power.
Users browsing this topic
Guest
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.246 seconds.
DeAgostini