BlueSCSI v2 is GREAT!

[TRyanPA]

I had a chance to try out the new v2 of BlueSCSI and I think it's a great upgrade. The RP Pico is so much faster than the Blue Pill. I already 3D printed a bracket for my SE. Very exicted about this upgrade. BTW, I did the kit and the soldering is very easy.

 

[3lectr1cPPC]

Good to hear. I will be picking up the PowerBook version sometime soon for my 170.

 

[macuserman]

As far as I can tell there is pretty much no difference between BlueSCSI V2 and ZuluSCSI, seems like a shameless ripoff which is a bit rich considering all the drama between blue and azul over naming. Anyhow should be a solid product since well it's a rebranded Zulu.

 

[joshc]

As far as I can tell there is pretty much no difference between that and ZuluSCSI, seems like a shameless ripoff which is a bit rich considering all the drama between blue and azul over naming. Anyhow should be a solid product since well it's a rebranded Zulu.

That's my take on it as well to be honest. BlueSCSI v2 seems to be an OK product but it's just a rehash of ZuluSCSI and to be honest I trust the engineers/designers behind ZuluSCSI a lot more than I do BlueSCSI. I've never had a problem with any products from @rabbitholecomputing

 

[macuserman]

That's my take on it as well to be honest. BlueSCSI v2 seems to be an OK product but it's just a rehash of ZuluSCSI and to be honest I trust the engineers/designers behind ZuluSCSI a lot more than I do BlueSCSI. I've never had a problem with any products from @rabbitholecomputing

Yep same, and after all the fuss over naming and then they come out with this V2 stuff I'm just over it like seriously no scruples. Plus what is the point exactly why would you even bother with v2 when you can just get something from the original dev team?

 

[3lectr1cPPC]

It’s honestly sad to see the conflict between the two sides in this community. I appreciate both the BlueSCSI team and Rabbithole for the stuff they provide for us, the SATA card is great, as is androda’s hybrid module. When it comes to what option I go with, it honestly just comes down to price. If two products fit my needs, I’m just going to end up with the more inexpensive option.
In my opinion, you can’t really complain about someone forking an open source project. It’s part of being open source, and I value it on both sides. Zulu is a heavily modified BlueSCSI in the first place, which was a modified ArduSCSIino or whatever it was called itself.
Have to say that I wasn’t a fan of BlueSCSI taking action against the AzulSCSI name though.

 

[joshc]

Yep same, and after all the fuss over naming and then they come out with this V2 stuff I'm just over it like seriously no scruples. Plus what is the point exactly why would you even bother with v2 when you can just get something from the original dev team?

Exactly, it's the attitude that is the biggest issue. There's been a lot of fuss over pretty much nothing and the BlueSCSI folks made themselves look very unprofessional.

Zulu is a heavily modified BlueSCSI in the first place

Not really. ZuluSCSI used some of the BlueSCSI firmware but its hardware is completely different and original !

 

[3lectr1cPPC]

thanks for the clarification on Zulu’s roots. I have to say though in regards to conduct, some members here have been less than respectful to the BlueSCSI people themselves.

 

[cheesestraws]

less than respectful

respect is a thing that is earned in engineering.

 

[macuserman]

It’s honestly sad to see the conflict between the two sides in this community.

Completely agree it would be great if that wasn't the case.

Have to say that I wasn’t a fan of BlueSCSI taking action against the AzulSCSI name though

And this is why they lost me as a customer, and the longer I am in the community and the more I hear the better and better I feel about my position. There is no real price difference 9 dollars less if you want fully assembled same price if you don't mind soldering on 2 headers.

Exactly, it's the attitude that is the biggest issue. There's been a lot of fuss over pretty much nothing and the BlueSCSI folks made themselves look very unprofessional.


Not really. ZuluSCSI used some of the BlueSCSI firmware but its hardware is completely different and original !

The way I understand it is Zulu ported the file management portion from the way bluescsi, rascsi, etc handles things. But the rest of the FW is completely original to Zulu. If it was the other way around bluescsi would not have forked the Zulu scsi code to rebrand for the V2.

 

[joshc]

thanks for the clarification on Zulu’s roots. I have to say though in regards to conduct, some members here have been less than respectful to the BlueSCSI people themselves.

I'm not so sure about that. People here pointed out numerous times to the BlueSCSI creators/supporters what the shortcomings of the product were and they never seemed willing to listen. Listening to what the problems are is usually a good place to start if one is actually interested in fixing those problems. Ironically BlueSCSI v2 does fix those problems but they still won't admit it. The lack of transparency speaks volumes.

 

[macuserman]

respect is a thing that is earned in engineering.

100% I'm a firmware engineer and I work with some prickly engineers so I'm used to it. But they have all more than earned it, they also aren't public-facing individuals either.....

 

[3lectr1cPPC]

There is no real price difference 9 dollars less if you want fully assembled same price if you don't mind soldering on 2 headers.

BlueSCSI V2 PowerBook kit is $35, ZuluSCSI PowerBook edition (no kit version available) is $70. That’s an incredibly significant difference for me.

 

[macuserman]

BlueSCSI V2 PowerBook kit is $35, ZuluSCSI PowerBook edition (no kit version available) is $70. That’s an incredibly significant difference for me.

Fair, I didn't price those because I have never used one.

 

[3lectr1cPPC]

I'm not so sure about that. People here pointed out numerous times to the BlueSCSI creators/supporters what the shortcomings of the product were and they never seemed willing to listen. Listening to what the problems are is usually a good place to start if one is actually interested in fixing those problems. Ironically BlueSCSI v2 does fix those problems but they still won't admit it. The lack of transparency speaks volumes.

One or two people in particular have insulted Eric in particular to the point where he no longer visits this forum. There is productive discussion in talking over the known design flaws, none of which exists in just insulting the other side rudely.

 

[3lectr1cPPC]

Fair, I didn't price those because I have never used one.

Yeah, desktop version is likely different in terms of that, but I’m the weird one who collects laptops…

 

[cheesestraws]

One or two people in particular have insulted Eric in particular to the point where he no longer visits this forum.

Eric takes any bad review of anything he does as a personal insult, though. The man cannot take even very mild criticism.

 

[3lectr1cPPC]

I haven’t seen this attitude personally, but I haven’t seen everything to do with the situation. He has dismissed the termination issue as unimportant, which is perhaps not entirely unfair as widespread BluePill death hasn’t been seen (yet) but I agree that it should be fixed, and now has been.
I’ve personally brought up the issue in the past when he was in Mac84’s stream chat, and he responded fairly to me at least.

 

[joshc]

I have built my own BlueSCSIs (v1) and had issues with termination that I haven't had with other devices. The same goes for a BlueSCSI PowerBook I have in my 165c which won't play at all when another SCSI device is introduced on the same chain, so there's definitely something iffy with it, there's no doubt about it. It's not even a case of worrying about the Bluepill dying - it's that it doesn't even work in some scenarios that it should. Not only that, but the creators have dismisssed and shunned anyone who gave this feedback including a technical explanation to them.

Anyway, we could go round in circles on this one and I hope BlueSCSI v2 customers enjoy their product but I am personally sticking with other solutions.

 

[3lectr1cPPC]

The same goes for a BlueSCSI PowerBook I have in my 165c which won't play at all when another SCSI device is introduced on the same chain, so there's definitely something iffy with it, there's no doubt about it.

I had the same issue on my 180c (internal BlueSCSI F4Lite), when using my external RaSCSI. Fixed by turning termination off on the RaSCSI.
I’d love to go with other options sometimes, just can’t justify double the price for basically the same thing unfortunately.