Even if an extended pins-header (the type that allows for wire-wrapping or another receptacle to plug over) was used, the height profile of the combo would increase. Moreover, the exposed pins increases the chance of accidental shorts by touchy-feely fingers or dropping metallic screwdrivers -- which is another goal of mine to reduce exposed components and traces on Juice's topside.ROTFL. I'll ramble here I wish my comments below can go public for a good fun time
I was an electronics/PCB designer of the '90s (1991~1998) from junior to managerial, designing from peripherals to consumer stuff to embedded computers: connectors and headers on PCB layouts were always our bane. For small and compressed form-factors, they're so big in PCB estate space! . We used to balk at our supervisors; and then when I progressed up the ranks, I used to balk at our execs. Even today, I can meet PCB designers who can say the same thing
(First, a tiny history: I'm a robotics hobbyist wannabee for many years now).RaspberryPiBeginners wrote:I don't get it what is it
Hi densipe,densipe wrote:It says it is a Kit - Not assembled?
In my earlier days of this I2C dev for this Juice, I've seen this style of errors before. I think it was caused by a missing, shorted or grounded I2C pin. I'll attempt to re-create it...magic_man185 wrote:when I issue a i2cdetect -y 0 command, every position on the i2c shows its corresponding number, like every position is occupied
a. The SDA snd SCL are bussed to all chips, so it doesn't matter. On Raspy Juice, there is an I2C debugging pinout JD1, alongside the GPIO header, those are the test-points I perform the grounding. (For HW testing only: Grounding SDA/SCL permanently will not cause damage. However, tying SDA/SCL to +3.3V must be done briefly because it will stress the "talking" chip output drivers).Which chip did you short SDA to ground in order to get this to happen, or does it matter?
b. For a good PCBA unit: The poor status is only shown for the duration whilst SDA is grounded. When this grounding is removed, the status returns to normal.When you do this does it permanently cause this status, or just while the pin is grounded
c . With your un-powered unit, you could check with a multimeter to see if SDA is shorted to ground. However, I suspect that it will not show as a short, because I have just one unit here that shows the same symptom but it has no hardware error of a grounded line. I too have re-flashed this unit with the upgraded firmware.Should I check the two chips and see if for some reason SDA is connected to ground?
Hi Dennis,densipe wrote: can you make a recommendation on a case that will accommodate the RPi/RaspyJuice combination?
Thank you, magic_man185, that'd be really nice.magic_man185 wrote: If you would prefer, I can just cut the spines off of the one I already have and test it, that way you don't have to order one and wait for it to arrive. I should be able to do this on Monday.
Oh, this is a disappointment: I've just tried to mount the Raspberry Pi - Raspy Juice combination into the above enclosure and they will not fit. The JST headers are 1.5mm too high for the enclosure to snap shut. The inner spines that I've nibbled off to allow a Pi-piggyback board, also serves as height-control standoff for the enclosure's front side. So if these are missing, the enclosure's front-side may "over-close".The casing was "MULTICOMP - MC-RP001-WHT - ENCLOSURE, RASPBERRY PI, WHITE" from element14
Things I had to do to Raspy Juice to make the above enclosure snap shut:The casing was "MULTICOMP - MC-RP001-WHT - ENCLOSURE, RASPBERRY PI, WHITE" from element14
I AM going to use this Raspberry Pi - Raspy Juice - MC-RP001-WHT combo as my living room showpiece. Thanks again! catmakerThe casing was "MULTICOMP - MC-RP001-WHT - ENCLOSURE, RASPBERRY PI, WHITE" from element14
Hi magic_man185, and Allmagic_man185 wrote:I received a Raspy-Juice board, and have been trying to get the RTC module working. I built a custom kernel to add support for the PCF8523 device, and finally got it recognized as hwclock. Unfortunately, shortly after it started messing up. I received errors that it had an invalid date/time, and it wouldn't let me set it. Even stranger, now when I issue a i2cdetect -y 0 command, every position on the i2c shows its corresponding number, like every position is occupied, when it should show -- for everything except 48 and 68. Before it was showing it correctly, but now all positions look occupied. Any idea what could be causing this? I already tried re-writing the firmware to the AVR (had to do the manual reset).
Code: Select all
svn checkout -r 134 http://raspy-juice.googlecode.com/svn/trunk/ raspy-juice.134
Hi stuarty,stuarty wrote:I think the Juice has all that I am looking for. I need to run from a 12V supply and communicate with a master over RS485. The master is using a mode similar to MODBUS RTU, so I need to detect End Of Transmission with 3.5 character silent intervals. That will require some work with the AT Mega - this device is new to me, but as I've developed a complete solution on 8051 based dev's previously, this shouldn't be impossible (I hope)..
The pitch of the JST and Molex connectors is 2.5mm with 0.9mm holes in the PCB. I have found before Screw Terminal Blocks which are 100mil pitch, through-hole PCB-mounted: something like this http://www.digikey.sg/product-detail/en ... ND/1153264 . I hope this helps.I will need to replace power and RS485 connectors with screw terminals though