I have an internal blueSCSI v2 (50 pin ribbon cable version) and an external BlueSCSIv2 (DB-25).
Both work trouble free with a Mac LCIII (connected to the internal and external SCSI ports respectively).
When I try to connect them to an Amiga 3000, the internal version works fine if connected to the internal SCSI, but I'm having some issues when trying to use the external DB-25 port. Note that I have a terminated HDD inside the internal amiga SCSI (providing termination on that end) and the termination resistor packs are also removed from the amiga PCB (to allow connection of external devices).
I've tried to attach my BlusSCSIs DB-25 to the DB25 port. It won't work at all.
I've tried to attach my BlueSCSI internal to the DB-25 port, using an external enclosure (which converts DB-25 to centronics, and then to a standard ribbon cable, which I connect to the blueSCSI). The strange thing here is that if I try to enable the termination jumper on the blueSCSI, it does not work. However, if I disable the jumper and provide a passive SCSI terminator at the end of the chain, it works (I did not try with an active terminator because I don't have one).
I guess the root cause for the onboard termination not working on either device should be the same. It if would be fixed on the internal version, then that would also help getting the external version to work.
I have an internal blueSCSI v2 (50 pin ribbon cable version) and an external BlueSCSIv2 (DB-25). Both work trouble free with a Mac LCIII (connected to the internal and external SCSI ports respectively).
When I try to connect them to an Amiga 3000, the internal version works fine if connected to the internal SCSI, but I'm having some issues when trying to use the external DB-25 port. Note that I have a terminated HDD inside the internal amiga SCSI (providing termination on that end) and the termination resistor packs are also removed from the amiga PCB (to allow connection of external devices).
I guess the root cause for the onboard termination not working on either device should be the same. It if would be fixed on the internal version, then that would also help getting the external version to work.