heathkid had the box last and was awaiting contact with touch. Failing that, he was asked to ship the box to me for the split. He got that request but didn't reply. He also hasn't responded to my email attempts. In any case, once I received the box I was to split it to components and parts. With this recent event, I assume the best approach would be to start a component box under it's thread (http://http://dangerousprototypes.com/forum/viewtopic.php?f=2&t=4843), and a new parts box, continuing the list from it's last position. If anyone can start a component box (no 'parts' in this one), you should volunteer in it's thread so we don't get several started at once by mistake. For the parts box (no 'components' in this one), it should continue on the existing list noted below once someone volunteers to start one out. Here is the current list:
As reminder, components are ICs, resistors, capacitors, tubes, LEDS, etc. Parts are PCBs, kits, demo boards, programmers, solder, gears, motors, etc. See the respective threads for discussion of box size to be used for each of these packages.
Quote
Did anybody plot a route on google maps to see how many kilometers (miles) the box went across the continent? Would be a funny thing to see.
As the box traveled "anonymously", each person only knew where it came from, then where it went next. The locations were never disclosed for privacy. Going forward, I'd propose that each recipient disclose their zipcode or nearest major city for a very generalized tracking of the packages. Anyone agree or object to this idea?
[quote author="drjeseuss"]My message is still unread for heathkid. It looks like this box has stalled again. heathkid, are you out there?[/quote]
heathkid still has not checked the message I sent him about ths 4-11. I also sent an email with no reply. This box may be lost. Does anyone know another way to reach heathkid to check on this?
[quote author="drjeseuss"]Just an update, I PMd heathkid last Thursday to see if he's shipped the box yet. The PM is still unread. Hopefully this box will get going again soon.[/quote]
My message is still unread for heathkid. It looks like this box has stalled again. heathkid, are you out there?
[quote author="systemstech"]Hi heathkid; If touch does not respond by the end of the week keep the box moving send it to drjeseuss so that the split can take place. touch can always be added back to the list if and when he comes back.[/quote]
heathkid, have you heard back from touch yet? Either way, when will you be shipping the box to its next stop?
[quote author="heathkid"]drjeseuss if you're going to do the "split" I highly recommend you put yourself in at #24 since you'll be covering for systemstech.[/quote]
This is already done, though not reflected by the list directly. touch knows to send to me after his turn and has my shipping info already. The list continues to grow and grow, still showing the very first stop. Might I suggest we start trimming the list so the #1 spot is always whoever is next in line, then counting down the list from there. We can always browse back through the thread to trach history if needed. Anyone object to this? If not, I'll rewrite the list to count from my turn down, eliminating the spots already visited.
One more stop to touch, then it's back to systemstech when the box is being split down to the components box and parts box. That should alleviate a lot of the over stuffing issue (for now). Also, I just noticed I haven't rejoined this list...
Thanks Ian. After reading into the issue further, I figured the D1/D2 parts were to blame. I looked on mouser and found a few with lower drop, but also lowwer current capacity. So far no fuctional issues, so as the old saying goes... 'If it's not broke, don't fix it'.
Was this ever resolved? I'm having a similar issue with my BPv4 build. I used the recommended part for D1, D2 (78-BAT54W-V). For Q1, Q2 I used BCV26 (http://http://www.mouser.com/ds/2/149/BCV26-104632.pdf). Below are my self-test results. As far as I can tell, things are working ok, but I haven't fully excercised the board yet, just a few simple I2C tests using onboard VPU. Anything to worry about with these results?
Last Friday I got the CD4066 chip I was missing for this build. I hand soldered it using a fine tip 25w pencil iron. Last Friday I also got the parts needed to build by PicKit2 Clone to program this BPv4 board. This allowed me to program the bootloader to the board. Once the bootloader was in, I added the latest firmware. All this went without issue.
Once the firmwae was on, I connected to the BP with PuTTY. I ran the self-test. Two tests failled: 5V VPU(4.13) FAIL 3.3V VPU(2.46) FAIL All other tests passed. I've used the board to connect to a few parts and haven't seen any issues so far. If anyone has suggestions about why the two VPU tests fail (I know the voltages are low, but why?), I'd appreciate it.
This BP4.0c build presented me with the 'chicken or egg' dilemma. My answer to this... 'Who cares, build both!' Actually in my case it went a bit further than that. I had to build a serial JDM 'pin wiggler' (a few years old at this point) to program a PIC18F2550. I then built a PicKit2 clone using the PIC18F2550 to program the PIC24FJ256GB106 on the BPv4, a chip that can't be programmed using a JDM style device.
I got the parts this past Friday for my PicKit2 Clone build. I spent $8.20 on Mouser for the parts. A few things like the USB cable and header were used from my part bin. I could have saved more if I would have dug out resistors and caps from my bin also, but was in a hurry when I placed the order and wanted to be sure I had all I needed for this build. After the first two connections, I decided to abandon the idea to do this in wire-wrap. I forgot how slow that process can be. I decided instead to 'dead bug' the parts on the perfboard. It looks terrible, but it works. Most of the jumps were component legs insulated with heat shrink, but a few of the longer runs use actial insulated wire.
After completing the build, I programmed the PIC18F2550 with the PicKit2 firmware using a JDM pin wiggler. I connected to the PicKit2 Clone using both the MPLab IDE, and the dedicated PicKit2 application. Both connected to the unit properly. I loaded up the bootloader hex for the BPv4.0c. I then connected the PK2 to my BPv4.0c through the ICSP header and programmed the bootloader. It worked on the first try! Success!
Overall, while very messy, this was an easy build and adds another multifunctional piece of kit to my toolbox. Well worth the time spent on this. If I had to do it all over though, I would choose to etch a board for this as the 'dead bug' approach got a bit crazy toward the end with wires going everywhere. It became challenging to keep track of what connections were in place and what needed jumpers, etc.
Thanks for the recommendations. I saw the design for micros-designs and almost went with it, but decided on the version I posted above. Originally I was going to breadboard a one-shot programmer, but decided to go with perf-board and wire-wrap for something a bit more permanent. As such, Ilike the design I chose as it retains most of the original PK2 features, including IDE adjustable voltages instead of fixed voltage, as most others have. Also, I'll be adding a header to allow me to add a module for the EEPROM down the road if I decide to use the ToGo programming function. Having the memory on a seperate module will also allow me to tinker with it using my BP, or to pop into other projects. I'll try to keep this thread updated as I go along on this build.
