I hate to bring this topic up again, ( its been about a year )
Back last year I put two SuperCap rated 1.5f @ 5v in series ( 1.5f 10v ) on EZB's input servo power ( 6v Battery ) to prevent brownouts and its been very successful, and worked well. ( Stopped brownouts ).
But since converting some of InMoov's large scale HS-805BB servo's over to EZ-Robots HDD Servo's I've been getting Brownouts? So I tried various things but still kept getting brownouts.
I then put one of the 1.5f 5v caps on the 3.3v rail of the EZB as you recommended last year, but for some reason it prevents me from connecting to the EZ Builder in Client mode? I've checked and double check and its wired up correctly and as soon as I've removed it, it connects OK! I've carried this out a number of times powering off and back on in-between and get the same results.
I also tried other supercaps, just in-case these two have gone faulty, but still get the same result, regarding the wifi connection.
I measured the 3.3v rail, when the supercap is connected and its still 3.3v, so its not being pulled down at all?
Upgrade to ARC Pro
ARC Early Access will give you immediate updates and new features needed to unleash your robot's potential!
Power the servos from the power source directly using modified peripheral cables or something like the inmoov servo breakout board.
The ezrobot servos will logically use more current than a larger servo. This is simply because the gear ratios are less than half that of a larger servo. Simple math means the servo motor has to work nearly twice as hard. Thus, drawing more current.
Yes, I should of done this in the beginning but was to eager to get started and finish, which is a bit of a joke, as it took me nearly a year to complete in the end, but to be fair to me I was diagnosed with a terminal illness in-between!
As you suggested I should done this from the start.
But I still don't understand why putting a super cap on the 3.3v rail, stopped the wifi connecting? I know other have done this including yourself and haven't had this problem, hence why I've gone over and over it again to check I having made any mistakes or done something stupid.
I do understand what you are saying and wasn't criticizing the HDD servo in any way, it a GREAT servo! I'm more interested in the above about stopping connecting to wifi in client mode with the cap on the 3.3v rail.
The Supercap mod was recommended by your own hardware engineer Jeremie to help deal with servo inrush current causing brownouts. See post 15 in this thread: http://www.ez-robot.com/Community/Forum/Thread?threadId=8686&page=2
All the best.
Doc says its gone. God i hope so!
As far as your power issue. I have to validate what others have said. Power the servos direct from your power source. You will never have a power issue again.
I wish I knew why the addition of the caps are keeping your wifi from working. Only a EZ Robot expert would know. I could speculate but it would only be a guess (power surge when the Wifi tries to operate?).
I did some tests today with my 2 x 1F 2.7V caps in series (0.5F 5.4V) on the 3.3V line, a EZ-Bv4.1/2, and 20 x HDD servos. I didn't have any trouble connecting in client mode. What does your setup consist of?
One thing to note is that once power is removed or reset you have to wait a full 15 seconds (probably longer for you since you have a bigger cap) for the Super cap to completely drain before powering back on, otherwise the chips get stuck into a weird low power state and you won't be able to connect. You can instantly recognize if the chips are in this state if you don't hear any audio on boot-up.
P.S. I'm so sorry to hear about your terminal illness. We are very glad to have you here. Thanks for your contributions to this forum!
Thanks for testing it out, much appreciated.
It works with my IOTiny and another EZB/2. I've disconnected everything on the EZB and it will not initialize with the cap on the 3.3 rail. Take it off and it's works fine, bizarre!
Anyway I'm thinking of re-doing the whole power for my Inmoov, and have a separate supply for the EZB's, as Richard had suggested.
Building the InMoov and having EZ-Robots has been extremely beneficial regarding my illness, Its really been a real life line and kept my mind busy!
I just wanted to quickly clarify with you. This is with a EZ-Bv4.1/1? The older EZ-B version? By "initialize" do you mean that the RGB LED on the WiFi board flashes green but doesn't do anything, stays solid green on boot, or doesn't come on at all. Is there any Audio?
Did you have a chance to try powering down the EZ-B for, let's say, 30 seconds and then powering it back on?
I understand you are likely going to try a different power configuration but I'd love to figure out what's going on.
i had hodgekin canser.still get chemo x6.canser was gone allreddy after 4 chemo's.
when you take a petscan.the doc can say and see 100% sure its gone.
he can show you on a pc that the cancer is gone.petscan takes 10 min time.
cem keep building your inmoove.you are great.
Yes this is the older EZ-B version, with the upgraded comm's board, like the other one I have.
The WiFi board flashes green but doesn't do anything, and doesn't connect to ARC, take the cap off, power back on and it connects straightaway, I can repeat this over and over again, it's always the same.
I've waited for over a min before powering on when I put the cap on, although it's pretty much discharged as I leave it on after powered down, and can see the light slowly fading and goes out.
I'm wondering as I'm using a 1.5f cap, that on power up the in-rush current created by the cap, causes the EZB to go into this state? May be on this particular EZB It's on the its limits? I need to do some more testing, with lower values caps and see. But I'm going away for 4 days tomorrow, so it will have to wait until I'm back.
thats sounds very serious.i get contrast too before the scan.
i find you very brave.i have hodgekin cat 4 of 5.so i gess i was lucky.
ive seen many whit canser growing old,it has many faces.
50% of tumors are good.
Good to know that 1.5F Super caps on the 3.3V pins can cause issues in some instances.