Search results

I'm not an expert on the 170. But a short should be causing a lot of heat to be generated by the component which failed. Could be a chip, a capacitor, a mosfet, a resistor, tons of possibilities.

I'm pretty sure it should drop the output voltage when the current limit is reached. If it's dropping to 1.1v then either the adapter is bad or there's actually a short and it's protecting the system.

November 11 2023 Board Meeting Attendance: Christian (fogWraith), Jacob (Androda), Eric (eric), Justin (jdmcs), Kai Robinson Absent: Josh (Drake), Ron (Ron’s Computer Videos), Bruce (Branchus) Agenda: Item 1: Calendar Competition Notes: We've totally lagged behind schedule on this...

The Mac Portable Battery Eliminator is available now, assembled only, in low quantity. HIDHopper for ADB will hopefully be next, just needed to update the PCBs a bit to handle part clearances. So those PCBs will be ordered soon and then it's a matter of designing printable cases.

Assuming your power adapter actually has a 1.5 amp current limiter that works properly, you'll be fine. The 1.5 amp current limit is for a few reasons: The original lead acid battery charge current was not allowed to exceed 1.5 amps Apple's battery charge circuitry might not be able to...

Hardware and Project Updates: BlueSCSI Desktop Hardware: The updated and more affordable BlueSCSI Desktop 50 Pin design has passed my local testing on a PowerMac 7300, Beige G3, and Mac Portable. It removes the microSD slot and USB-C power connector, but in doing so also cuts the cost enough...

My only suggestion is to add a diode, to avoid possible back-power issues in the future. Don't want your external device feeding termpower to try and run the entire laptop.

With the Vendors section going away, this thread will serve several purposes: * Reference to my store's URL * New product announcements * Product Suggestions * Product Support Tech by Androda, LLC website link This is my side business / hobby company dedicated toward trying to solve problems...

You can look with a hex editor, yes. Check between offset 0x8000 and 0xBFFF, that's where the SCSI driver partition lives. Some possible landmarks (pulled from a 6.0.8 image): * "CMS_SCSI" near the beginning * "RM 7.4" around 0x8780 * SCSI Driver version around 0x9EB7 * HFS Manager version...

This is interesting, and strange. I believe there have been reports in the past of SCSI drivers not playing nicely together and causing corruption like this. If you use SCSI Director Pro and install the same driver on both images, does this data copy corruption issue still happen? The SCSI...

A Pico W that does not have the firmware installed cannot function as a BlueSCSI. The firmware is what makes everything work. Did that Pico W have firmware installed when you first tested in the IIci?

As mentioned before, I regularly update the firmware on test units without removing the Pico from the board. Generally I remove it from the SCSI bus, then do the USB update method.

Correct. As mentioned on the Updating Firmware page of the Wiki, the ".uf2" files are the firmware. You can tell that it's installed onto your Pico by applying power without an SD card present. The Pico's LED will flash 5 times, pause (with LED off), and then loop again with the 5 flashes...

Allow me to explain. The RP2040 microcontroller used on these Pico boards has one design decision that strikes me as fairly dumb with how modern systems work. When the chip initializes and starts up, every GPIO pin is set up in "pull down" mode. This means every pin tries to pull the signal...

The super cool thing about this release is that it works across all existing BlueSCSI V2 Hardware. We don't have separate builds for WiFi, or separate builds for Initiator hardware. One binary for all, no confusion, no mess. And speaking of Initiator hardware, that's merged into the BlueSCSI V2...

Additional commentary around this decision is available in the minutes: https://tinkerdifferent.com/threads/2023-10-07-tinker-different-board-meeting-minutes.3030/#post-26022

October 7 2023 Board Meeting Attendance: Bruce (Branchus), Christian (fogWraith), Jacob (Androda), Eric (eric), Justin (jdmcs) Absent: Kai Robinson, Josh (Drake), Ron (Ron’s Computer Videos) Agenda: Item 1: Access Control Considerations Notes: A Moderator had been granted more...

whistles innocently

My initial reaction is that RAM Doubler would be faster overall. Compression uses CPU cycles, yes, but those CPU cycles are likely still dramatically faster than reaching all the way out to a hard drive. Even if that hard drive is an SSD.

There's one adapter board left as a kit, if you feel like assembling it. I have more of these on the way from the PCB manufacturer, and will then have some assembled available.