Hi:
Just got back on after being in South Dakota for a few weeks with no internet connections.
Anyway, on the capacitor thing. If possible, try to use a tantalum capacitor of 100 ufd or so. The tantalum has much lower impedance and does a better job of bypassing than a standard electrolytic. Also, they are much smaller than an electrolytic.
It may be necessary to use a 100 ufd cap AND a .1 ufd capacitor. This bypasses both low and high frequency oscillation. Note that both of these can be low-voltage caps. 6 vdc or so, as they are on the 3.3 vdc side of the regulator.
IdunBenhad wrote:It may be necessary to use a 100 ufd cap AND a .1 ufd capacitor. This bypasses both low and high frequency oscillation. Note that both of these can be low-voltage caps. 6 vdc or so, as they are on the 3.3 vdc side of the regulator.
Oops... all the caps are on the 5v side -- so it's probably better to have a bit more headroom than just 6v. The only component that gets 3.3v is the XBee radio and it has its own internal caps.
Hi:
I may be wrong, but I think the bypass cap belongs on the output side of the regulator. If fact, is that not where you showed to put it? from the 3.3 volt test point to ground?
Maybe I'm the one that's brain-dead. Been traveling too much!!!!!!
Oh, yeah; Hi Dave
The 100uf cap is on the input side -- it was intended to be a bit of a buffer for the regulator. Ren-W pirates power from the controller and at times when the controller is using a lot of current, the cap helps keep the 3.3v regulator supplied with juice. The regulator on an SS24, for example, is only 500ma. A Ren-W in receive mode uses about 60ma; in transmit mode it can up upwards of 290ma (XBee Pro), so I thought a little cap there would be helpful. In fact, I really considered a much beefier one (2200uf), but 100uf seemed to work in all my testing, so I decided to leave it alone.
There are some 1uf caps around various pins of the MAX232 chip that help reduce noise, but the MAX232 is all 5vdc.
FWIW, I considered making the board completely 3.3v and using a 3.3v version of the MAX232, but I wasn't comfortable that the output voltages offered by it provided enough headroom to ensure a good signal into the controller's input, so I dumped the idea.
I also considered using a couple diodes in series to drop the voltage down for the XBee, and I think that would work in place of the voltage regulator's connection to pin-1 of the XBee, but that doesn't guarantee a rock-solid 3.3v to the XBee. I thought about using a 3.3 Zener in place of the 3.3 regulator, too, but that also dropped the voltage to the MAX232 which I didn't like. In retrospect, a 3.3 Zener coupled with a 1N4001 might work, but I never tried it.
I've checked everywhere for substitute parts, but they're preciously difficult to locate. Mouser has a couple thousand of the 3.3v regulators that should arrive around the 27th of September, well in time for folks to put their Ren-Ws into action for this season. Just build-up the rest of it and wait on the regulator...
Hey -- all you Ren-W builders who are looking for the 3.3 regulator. I just received a shipping confirmation from Mouser on 250 of the 595-UA78M33CKCSE3 regulator. So apparently their shipment has come in early. I bought a bunch just to have them as a future supply for DIYC members in case Mouser comes up short later on...
So at this point, there should be no shortages of any Ren-W parts from Mouser. Go for it. Make it happen. Wireless is bigger than big, it's... it's....
...Release the power of untethered blinky-flashy!!!
Looks great, one question. Why does the mouser BOM list 4 Female SL connectors but the BOM in the wiki only lists 2? How many do we actually need per Ren-W?
Dave, you've been doing this to long now. Its time to take a break and not so many cups of coffee.
Its nice to have a good laugh once in a while. Glad to see I'm not the only one that does this. I'm also glad I got all of my parts months ago and have everything built.
Oh, I also found out, when you are testing your Ren-W's, do not have them less than two feet from each other. They really make the controllers go nuts, and it will drive you crazy trying to figure out why your sequence is not working correctly. I figured this out when I was testing all 18 Ren-W at once on the same table. It was very interesting to watch.
Thanks again for coming up with this design. You have no idea how much setup time you have saved me this year.
Jrd wrote:Looks great, one question. Why does the mouser BOM list 4 Female SL connectors but the BOM in the wiki only lists 2? How many do we actually need per Ren-W?
That's a really good question, and I'll have to ask somebody why I did that. :rolleyes:
Actually, you need only two, and if you really get down to it, you don't need any of them if you make a +5v connecting cable out of two open jumper shunts and a single strand of cat5. Those SL connectors are just to make a cable with two female ends that will fit over one of the JP3 header pins so you can connect it to another header pin that carries +5vdc on the controller board.
Ok thanks, I will change the quantity to 2 on my copy then.
I am having some missed transmissions and I am trying to figure out which end it is on, the recieve or transmit side. I tried the troubleshooting steps but when I open the terminal window and try to view the hex vixen says "Access to Port 'COM5' is denied" (COM5 is my explorer board). If I run vixen first X-CTU says basically the same thing.
Wrong driver installed? It did take a few different driver tries to get it (USB Explorer Board) to communicate with X-CTU.
EDIT: I reinstalled the driver and it now shows the same title as the wiki page but I still get the same results from trying to watch the hex values.
