I pimped my RASCSI

[pfuentes69]

Fitted the OLED and a shutdown button. I had the idea of trying to develop a user interface, with just one button, to do basic things as mount images and shutdown... But I'm too lazy and this will take some time...

Maybe this can give some ideas to @PotatoFi

 

[PotatoFi]

Nice! v2 of the RaSCSI Slim and RaSCSI Pro will have an optional spot for a screen on the front, just like you've done here. I think a one-button or rotary encoder on the front is a good idea. Having a complicated user interface with a bunch of buttons seems very "un-Mac-like" to me.

As for me, I just use my phone.

Other planned features:
- Raspberry Pi 2/3 and 4 versions
- Display version
- Video out port
- Spot for a fan, if the user wants to install one
- Same width as an external floppy drive

 

[pfuentes69]

Nice! v2 of the RaSCSI Slim and RaSCSI Pro will have an optional spot for a screen on the front, just like you've done here. I think a one-button or rotary encoder on the front is a good idea. Having a complicated user interface with a bunch of buttons seems very "un-Mac-like" to me.

As for me, I just use my phone.

Other planned features:
- Raspberry Pi 2/3 and 4 versions
- Display version
- Video out port
- Spot for a fan, if the user wants to install one
- Same width as an external floppy drive

That would be a great thing!
For the buttons or rotary interface the main issue is the limited GPIO pins… the RASCSI has three but checking about it and asking to @landogriffin , apparently only one is really available, so this would only allow a one-button interface, which could be enough with a clever usage of short-press and long-press actions.
For now I’m only using the button to trigger a shutdown.

 

[PotatoFi]

I'm going to put my "Software and Hardware Product Owner" (my day job) hat on here for a second, and suggest that a user interface based on one button might not be worth it. The situation sounds a lot like a "just because you can doesn't mean you should" scenario.

Part of my reasoning for this is the ease of administering a RaSCSI with a smartphone, tablet, or laptop. The web interface just works with basically no compromises, and I always have my phone in reach while I'm playing with my vintage machines.

If you don't mind, I'd like to make a few more suggestions and comments:

1. I think a dedicated soft shut-down button is a fantastic idea! To keep with the "theme" of vintage Macs, I'd stick it on the back of the case (and make it very easy to find with just your fingers).
2. If there's I2C available, a rotary encoder could be a great way to do menu navigation and selection. That's how my Prusa MINI works, and it is brilliant. I fear that I2C is not available though. Additionally, I don't think a rotary encoder on the front of the RaSCSI is very "Mac-like".
3. If you can't cram in user interaction buttons, a screen could still be useful for showing the current hardware config. You could also display a dynamic QR code on the display to point your smartphone to the web interface - no more looking up the RaSCSI IP address on your network! Your phone will navigate to it for you! We do something similar to this on the other hardware product I am involved in, the WLAN Pi.

Thanks for letting me voice some thoughts and opinions - I hope that it's helpful and thought-provoking!

 

[pfuentes69]

I'm going to put my "Software and Hardware Product Owner" (my day job) hat on here for a second, and suggest that a user interface based on one button might not be worth it. The situation sounds a lot like a "just because you can doesn't mean you should" scenario.

Part of my reasoning for this is the ease of administering a RaSCSI with a smartphone, tablet, or laptop. The web interface just works with basically no compromises, and I always have my phone in reach while I'm playing with my vintage machines.

If you don't mind, I'd like to make a few more suggestions and comments:

1. I think a dedicated soft shut-down button is a fantastic idea! To keep with the "theme" of vintage Macs, I'd stick it on the back of the case (and make it very easy to find with just your fingers).
2. If there's I2C available, a rotary encoder could be a great way to do menu navigation and selection. That's how my Prusa MINI works, and it is brilliant. I fear that I2C is not available though. Additionally, I don't think a rotary encoder on the front of the RaSCSI is very "Mac-like".
3. If you can't cram in user interaction buttons, a screen could still be useful for showing the current hardware config. You could also display a dynamic QR code on the display to point your smartphone to the web interface - no more looking up the RaSCSI IP address on your network! Your phone will navigate to it for you! We do something similar to this on the other hardware product I am involved in, the WLAN Pi.

Thanks for letting me voice some thoughts and opinions - I hope that it's helpful and thought-provoking!

The one-button thing is because it seems that only one GPIO port is available, not because I'd prefer it.

The management with the web interface is quite nice, and the normal thing to do, but that's creating dependencies with other devices, while an autonomous thing (like the floppy-emu) seems quite interesting to me... but that's just a personal thing... I don't even know if I'll do it anytime soon, because the only thing that for me is a must is the shutdown button. I added it also to your SE bracket and it's super useful.

The button I have put is hideous, but it's not easy to fit a button in the back with the current design (unless you glue an small PCB button in the outside), because the most empty space is in the front area. Making the window for the screen with the Dremel and a file was already pushing my "bricolage" skills to the limit, so for the button I just did something easy.

Indeed, the QR-Code idea is just a great thing to add!