BlueSCSI V2 - works with SASI but with issues.

[spectreman]

@kanjiology, did the recent update fix any of your problems?

Also, does anyone know how to get the HDD led to work with X68000 and the BlueSCSI desktop version?

Is the flat cable you purchased a rainbow colored 20 PIN, with a red wire sticking out?

If so, you must connect the red wire that protrudes out to the positive LED pin (+) found in the center of the three pins at the top on your left.

[incrediblehark]

Thank you, I'll try that

[spectreman]

Thank you, I'll try that

In case the flat cable you have has no external wire disconnected already prepared for HDD LED:

The 50 PIN side flat cable is divided into two groups of wires, one group of 11 and another of 9, disconnect the innermost wire by starting to count from the outside of the connector towards the center until 9, that wire corresponds to the HDD LED (usually red).
Remove it and extend it with a piece of wire to reach the top center pin on your left, the positive pin is in the center between the three (+) of your BlueSCSI V2.

Guide valid only for OG, ACE, EXPERT models.

[incrediblehark]

This is the cable I have:

https://www.ebay.com/itm/115869753264

[spectreman]

This is the cable I have:

https://www.ebay.com/itm/115869753264

Sorry, I forgot you have a PRO.
In this case the situation changes.

If you want, you can disconnect the HDD's original LED wires, and connect the BlueSCSI V2 wires directly to it, so you can use the original LED, paying attention to the polarity.

I think it's the most practical solution.

[kanjiology]

@kanjiology, did the recent update fix any of your problems?

Also, does anyone know how to get the HDD led to work with X68000 and the BlueSCSI desktop version?

Unfortunately BlueSCSI V2 has a bug right now where it can't be updated via SD card so I'll have to open the entire computer to update it.

Have used the SD Card Formatter.

The ini file looks like this:
[SCSI]
System=X68000
EnableParity=0 ; Off

[incrediblehark]

Just wanted to add that after testing a bit more, I am also having the too low error message on the sxsi loader, testing both internally and externally with different ini settings. Seems it will have more luck working with on a cold boot but fails 99% of the time when i do a reset either with button or key combo.

[spectreman]

@incrediblehark Some power supplies may not provide enough power to the Raspberry Pico.
Pico requires a 5V/1A power supply.

Can you report any errors contained in the log.txt file?

Did you buy the version with WIFI?

Check following points:
For X68000 with SCSI interface

Turn termination off on the board.
Use the following bluescsi.ini file settings:

[SCSI]
System="X68000"

For X68000 SASI ( OG/ACE/PRO II ) external centronics 50 pin connector marked "HARD DISK"

https://shop.onegeekarmy.eu/index.php/product/bluescsi-v2-centronics-2/

Turn termination off on the board.
Install the SxSI bootloader (include in master disk V3).
Use external power.
Use the following bluescsi.ini file settings:

[SCSI]
System="X68000"
EnableParity = 0

https://bluescsi.com/docs/Compatibility

[spectreman]

The BlueSCSI v2 Centronics ( external connector ) version without WIFI is suitable for those with X68000 PRO II.

https://shop.onegeekarmy.eu/index.php/product/bluescsi-v2-centronics-2/

BlueSCSI v2 Desktop and BlueSCSI v2 DB25 will not work properly.

[amazin]

I have *JUST* tested a BlueSCSI V2 external DB25 on a X68000 Pro last night, updated the firmware to the latest release (2024-05-21) and it won't work. Still have a plethora of "Chk.Conn" and "So Low SCSI level".

Mine is a DB25 unit made by Flamelilly in the UK.

The thing is:

If you power the X68000 first THEN the BlueSCSI V2 second, it gets recognized and it works. You may reset the X68000 afterwards and it'll work fine. Until you do that, it won't get recognized.

If you power off the X68000 but not the BlueSCSI V2, when you power the X68000 up, it won't recognize the BlueSCSI V2 anymore, until  you power it off then back on.

Another thing I noticed is that it sometimes fails to load Akumajo Dracula, and sometimes the music plays slow while the game is loading. Both things do not occur on the BlueSCSI V1 with the ArdSCSIno-STM32 firmware.

[incrediblehark]

Thanks for the detailed explanation, the power situation with the bluescsi v2 is what I noticed with the centronics 50 model on an ace.

[spectreman]

Thanks for the detailed explanation, the power situation with the bluescsi v2 is what I noticed with the centronics 50 model on an ace.

You can find any power errors and more in the log.txt file which is automatically created and updated at each startup on the SD memory.

[spectreman]

Brief insight:

SCSI2SD (Recommended version 5.1, later versions not compatible, successor ZuluSCSI V6.4):

it is a device that requires firmware updates, the use of programs to copy the HDD image into the SD memory, and a careful evaluation of the X68000 model on which to mount it, as they are not specifically designed for this system.

BlueSCSI:

BlueSCSI V1 with the firmware dedicated to X68000 ArdSCSIno-STM32 works correctly, with the right configuration.

BlueSCSI V2, uses Raspberry Pico which requires firmware updates and a 5V/1A power supply.
The version with WIFI (with greater electricity consumption) is ONLY useful for older Apple computers and users who intend to use the DaynaPORT function.
HDD images can be copied directly to SD memory by naming it correctly.

Typical power problem is Low SCSI level error.
By consulting the log.txt file in the SD memory you can make sure of this.

https://bluescsi.com/

Cable diagram:
https://gamesx.com/wiki/doku.php?id=x68000:don_t_have_a_sasi_scsi_cable

HENKAN BANCHO PRO or V4:

The best choice in my opinion, designed for X68000, Fujitsu FM Towns and NEC PC-98.
a ready to use device does not require you to do anything beyond simple installation.
HDD images can be copied directly to CF memory.
The mounting kit for both SASI and SCSI is sold separately. For the X68000 PRO it must be connected via a dedicated connector internally.

The only flaw is the price, but losing money on poorly functioning devices turns out to be more expensive.

Internal model:
https://buyee.jp/item/yahoo/auction/p1150049472

Installation kit:
https://buyee.jp/item/yahoo/auction/k1153915262
https://buyee.jp/item/yahoo/auction/j1150050988

External model:
https://buyee.jp/item/yahoo/auction/n1142753050

[spectreman]

Additional Information:

Unfortunately it seems that some products are not available for all territories, for example the BlueSCSI V2 Centronics model ( recommended for X68000 OG/ACE/PRO II ), only available from the official seller in Belgium at the moment.

https://shop.onegeekarmy.eu/index.php/product/bluescsi-v2-centronics-2/

[kanjiology]

Something weird happened to me, I started getting "So low SCSI level" all of a sudden on all my SCSI emulator devices, BlueSCSI v1/v2 and even Henkan Banchou, this is internally on the PRO. I tried the external centronics port and it works fine... go figure. BlueSCSI V2 works really well now for me, every game loads fine.

[spectreman]

@kanjiology The SCSI low level message appears when the device is not receiving enough power.

You can check if the voltage is correct in the log file on the SD of your BlueSCSI.

It looks like this:
INFO: Pico Voltage: 3.254 V.

[kanjiology]

@kanjiology The SCSI low level message appears when the device is not receiving enough power.

You can check if the voltage is correct in the log file on the SD of your BlueSCSI.

It looks like this:
INFO: Pico Voltage: 3.254 V.

I see, I am using this PSU https://github.com/leaded-solder/x68000-pro-picopsu and it had been working fine. Maybe the PhantomX is consuming too much juice? Maybe I should upgrade the PicoPSU inside.

[spectreman]

@kanjiology Check the BlueSCSI operating voltage in the Log file, It is updated at every system startup.

The hardware acceleration offered by the PhantomX, consumes significantly more energy.

[kanjiology]

When I had it internally it was something close to 3.3v, but it makes sense with the PhantomX causing issues now. My PicoPSU is only 80W, maybe I'll upgrade it to 160W.

[spectreman]

When I had it internally it was something close to 3.3v, but it makes sense with the PhantomX causing issues now. My PicoPSU is only 80W, maybe I'll upgrade it to 160W.

Please note that the X68000 is not designed to support these modifications, and over time you may experience instability issues.

[hlide]

Maybe the PhantomX is consuming too much juice?

Using a PhantomX makes the other SCSI emulators useless as it already offers a VDBOOT (that I modified by adding some tools like LHES and drivers like SUSIE) and a 4GB VDISK (well a little less than 4GB) which contains the same contents of a 3GB HDD image that seems to be published somewhere in that forum. But, yeah, I didn't check all the games are running fine though.
 

[amazin]

Using a PhantomX makes the other SCSI emulators useless as it already offers a VDBOOT (that I modified by adding some tools like LHES and drivers like SUSIE) and a 4GB VDISK (well a little less than 4GB) which contains the same contents of a 3GB HDD image that seems to be published somewhere in that forum. But, yeah, I didn't check all the games are running fine though.
 
[/quote]

Care to share it somewhere?

Cheers

[TinaTurner]

New firmware for BlueSCSI supports X68000-SCSI and X68000-SASI

see: firmware v2024.10.26 https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2024.10.26
commit: https://github.com/BlueSCSI/BlueSCSI-v2/commit/fd296c9512f5ce3e9936920ca7548965f05a1fa2

For SASI users, add this to the bluescsi.ini text file on the root of the SD card


[SCSI]
System="X68000-SASI"

Set the termination jumper on the bluescsi PCB to "off"
Format SD card to FAT32 and name your image file: HD30_512.HDA


However I tested it and it unfortunately gives the error: "So low SCSI level"
Does the new firmware work for anyone else with SASI? ({If it works for you then it must be my SD card)

[aotta]

New firmware for BlueSCSI supports X68000-SCSI and X68000-SASI

see: firmware v2024.10.26 https://github.com/BlueSCSI/BlueSCSI-v2/releases/tag/v2024.10.26
commit: https://github.com/BlueSCSI/BlueSCSI-v2/commit/fd296c9512f5ce3e9936920ca7548965f05a1fa2

For SASI users, add this to the bluescsi.ini text file on the root of the SD card


[SCSI]
System="X68000-SASI"

Set the termination jumper on the bluescsi PCB to "off"
Format SD card to FAT32 and name your image file: HD30_512.HDA


However I tested it and it unfortunately gives the error: "So low SCSI level"
Does the new firmware work for anyone else with SASI? ({If it works for you then it must be my SD card)

Well, as confirmed by the commit, last version didn't add the X68000 support, it was already added in previous releases with my pull 112 on december 2023.
The difference for SCSI is that in bluescsi.ini the right "parity" parameter needs to be:
EnableParity = 0 ; for SASI
EnableParity = 1 ; (default) for SCSI

With last FW update, you can simply use directly the quirks X68000-SASI or X68000-SCSI without the need of specifiying the parity option.

[TinaTurner]

Yes great work on the mod. It seems the newer firmware is just a shortcut to set EnableParity = 0 and do the rest of the X68000 quirks (selectionDelay = 0; enableSCSI2 = false; maxSyncSpeed = 5;)

I still cant get this "bluescsi centronics" working though on this new firmware.
Error is always:
Check ID X: So low SCSI level 
(Where X is the SCSI ID set on the file name. Usually 3)


-The machine is a X68000 Expert 2 AC
-Has an Etarikashikoshi 8MB + MIDI expansion card installed.
-blueSCSI is a centronics version that plugs directly into the back of the X68000 into the Hard Drive expansion port. Needs external 5v power via the micro USB port on the pi.




If someone wouldn't mind double checking my steps please for where I am going wrong:



1. Set up SASI drivers:

Set switch.x options by booting from master v3 floppy and type these commands:

switch.x

memory: highlight, enter. Use arrow up/down and set the memory you have (in my case 2MB onboard and 8MB with the Etarikashikoshi card so set it to 10MB 10240)
Boot: highlight, enter. Use arrow up/down to select STD. Enter again.
HD_MAX: highlight, enter, Use up/down arrow to selelct 0. Enter again,
Quit: Highlight the very last option (translates to "End"). Press Enter then Y to save.


Now set to boot to SASI. At the command prompt enter these commands:

cd sxsi
bootset.x
ED0100
1



2. BlueSCSI prep

Update firmware:
connect the bluescsi pi to your Windows laptop over USB holding the bootsel button on the pi. When the new drive letter appears in File Explorer, copy the latest uf2 firmware file to the root of the new drive. Wait a minute it will automatically disconnect. Firmware is now updated.

SD Card:
Format the SD card to Fat 32 using the "fat32 formatter" utility.
Create a file on the root of the SD card called bluescsi.txt with the following text:

[SCSI]
System="X68000-SASI"



Copy in a disk image. In my case I used the 2.20 3GB disk image.
Name the file:
HD30_512.hds

This tells bluescsi it's a Hard drive image on scsi ID 3 in 512 bytes

Safely remove SD from Windows then physically remove the card.


-Plug in the SD card to the pi/bluescsi
-Set the Termination jumper to OFF on the bluescsi pcb.
-With the X68000 powered off, plug the bluescsi it into the centronics port at the back of the X68000
-Connect up a micro USB cable from the 5v plug to the pi and confirm a blue light.


3. Boot from bluescsi

Power on the X68000 and start praying.


Welcome Personal Workstation X68000

SxSI Booter version 1.00  IOCS version 1.00

Check ID 0 Not Conn. (should this not say "SASI UNIT"?)
Check ID 1 Not Conn.
Check ID 2 Not Conn.
Check ID 3 Chk.Conn. (for 2 seconds) then: So low SCSI level (NOOOOOOOOOOOOO!!!!!!)
Check ID 4 Not Conn.
Check ID 5 Not Conn.
Check ID 6 Not Conn.
Check ID 7 Not Conn.
Standard boot because no unit can start
Then a message in Japanese about insert bootable disk with icon of a hand inserting a floppy.


It was fun getting this far but not so much fun now after seeing low SCSI level error around 100 times.




Troubleshoot steps:

1. Tried another SD cart formatted to FAT 32,
2. tried different 5v power supply to the BlueSCSI
3. Tried various combinations of resetting/powering up the x68000 and delaying power to the bluescsi.
4. Even tried another bluescsi v2 (my BlueSCSI Desktop v2 edition that I use on a Capcom CPS3 arcade PCB). Same low SCSI level error.


One thing I noticed that could be related: many forum posts say to use SCSI ID3 for the HD image file as ID0 is used by the SASI controller. My X68000 Expert, there is nothing on ID0 at all (it says "Check ID 0 Not Conn." but images online imply this should actually say "Check ID 0 SASI UNIT" When I boot the master floppy disk it says: "Device with ID0 status: Does not operate YSXSIYSCSIHD.SYS could not register".


Open to any suggestions!

[incrediblehark]

Try setting a longer delay for the SxSI boot loader (I use 4 personally). I'll see if I can upload my .ini - I'm on a fw before the SASI - SCSI flags were added for X68000 so I'm using the standard SCSI config for x68k with parity off and hdd image named HD10_512.hda

My 3.00 set to release soon will have an archive specific for BlueSCSI so it should (hopefully) be a quick drag and drop onto your sd card to get up and running.

[amazin]

By the way, we should put this "you must use ID3" to rest, this is not true.

What happens is that in a SASI machine, you have that option HD_MAX by default set to 1.

This "HD_MAX" according to the manual is the "max number of physical SASI HDDs", so if you don't have a physical SASI HDD connected to your X68000, this should be set to 0. Then you get SCSI ID0 available on SxSI. That might be one of the reasons people recommend setting the SCSI device to ID3.

The other reason is that there was an early version of SCSI2SD that was hardcoded to use SCSI ID3, but all devices available will let you assign any SCSI ID you want to the emulated SCSI device.

There's absolutely NO REASON for any one to use SCSI ID3 today.

[amazin]

What I firmly believe it's the issue with BlueSCSI V2 on SASI machines is because SASI machines cannot power the BlueSCSI as there is no equivalent to the SCSI "TermPWR".

The "So Low SCSI device" is a SCSI Termination error.
The "Check IDx Not Conn" is an issue with BlueSCSI V2 "freezing" and not getting reset. If you remove the power, reconnect the power and press reset on the X68000, this will go away.

@aotta has devised a quick and simple solution to power it by grabbing 5V from somewhere and adding to a specific pin.

I believe that this might fix the issues related to powering BlueSCSI V2 **AND** fixing the Termination Power.

Here's a photo of what he did:


Although he done this on a Shodai (CZ-600) I'll try to apply this to an Ace probably tomorrow, just need to find 5V there somewhere. I know a way of doing this by getting 5V from the back joystick connector on the I/O (bottom) board, but it's not practical.

Cheers

@incrediblehark I saw your PM, haven't got time to test it yet, life is a nightmare right now :-D

[incrediblehark]

@amazin no worries!

Attached is my .ini which is very bare bones but works well for me, I tend to agree with amazin's comments about the power cycling / so low errors.

[aotta]

about the 5v grabbed from pcb for external SASI, i confirmed i did it also in my ACE HD but the input point is different of course... i didn't take any photo of that mod but i got power from the solder side of the 20pin floppy connector

[TinaTurner]

@incrediblehark Thanks I tried your ini file but it's the same issue.
your one:
[SCSI]
System=X68000
EnableParity=0 ; Off

my one was:
[SCSI]
System="X68000-SASI"

my one is really the same as yours just using the new firmware includes the EnableParity=0 by default.

I also tried adding a 4 second delay as suggested but sadly no change:

cd sxsi
bootset.x
ED0100
4


@amazin Is that soldering wire picture the same for an Expert model?
The docs say to set the bluescsi SCSI termination jumper to "off" but I tried the "on" position too and same error.
The log.txt file in the sd card has no errors about power and I used 2x separate 5v 1amp psu's with micro usb cables. Is the 5v tapping from the X68000 only for convenience or does it help with the "termination power"?

I also tried setting the hard drive image scsi ID to 0 (and 1) by renaming the image on the sd card but it just moved the "So low SCSI level" error to the new ID.

Could this termination power issue be addressed in a firmware update?

[aotta]

@TinaTurner I think the real question is: does anyone besides me have a bluescsi2 "centronics"?
My internal version (both mounted internal and external with adapter cable) works like a charme, so i'm afraid of an hardware incompatibility for the centronics version with our X68000. I suggest you to check with other flavour of BlueScsi2!

[TinaTurner]

I've tried all 3x types of bluescsi I have here and sadly all are the same:

1. BlueSCSI v2 Centronics
2. BlueSCSI v2 DB25
3. BlueSCSI v2 Desktop


So either
a) I've made a mistake in the steps (see post #64 above)


b) The new bluescsi firmware v2024.10.26 has a bug (has anyone else tried it?)


c) My X68000 has faulty hardware.

[spectreman]

@TinaTurner

This is the model you have, right?

https://shop.onegeekarmy.eu/index.php/product/bluescsi-v2-centronics-2/

https://jcm-1.com/product/bluescsi-v2-centronics-50/

These two apparently similar models have different hardware revisions.

The first one is: 2023_10a ( Belgium )

The second one is: 2024_03a ( USA/Canada )

Did you assemble it yourself or did you order it already assembled?

Model with WIFi or without?

Meanwhile try to set on switch.x:

BOOT: ROM $ED0100
HD_MAX: 0

Regarding the external power supply, use a 5V 2A (tablet charger)

Turn on X68000, and then connect the USB cable (remember that USB cables are NOT all the same), and reboot.

Try this.

[aotta]

@TinaTurner i think your cables are too long, i had errors similar to yours before shorting my 50 pin cables to about 10-15cm!
And, i named my two .hda files from 00, not from 03, i agree with amazin in this!

[TinaTurner]

Hi all,

Thanks for the guidance!

1. BlueSCSI v2 Centronics
This is 2023_10a, preassembled, no wifi (from one geek army)
No cable, directly connected in to x68000.


2. BlueSCSI v2 DB25
Preassembled, wifi, (from flamelily). This one 100% works as it's used on a capcom CPS3 arcade pcb to load up new games.
Using a 1m scsi cable.

3. BlueSCSI v2 Desktop
Preassembled, wifi, (from flamelily). This one 100% works as it's used on a capcom CPS3 arcade pcb to load up new games.
Using a 1m scsi cable.


BOOT: ROM $ED0100
HD_MAX: 0
Tried that and same issue.


Regarding the external power supply, use a 5V 2A (tablet charger)
Will try that! Can't find one around the house. Inly have 5v 1a.


shorting my 50 pin cables to about 10-15cm!
Thanks, will order one. Note that the Centronics one has no cable and also has the issue.


named my two .hda files from 00, not from 03

Is this my problem? I only have 1x image: incrediblehark's image and I've tried naming it
HD00_512.hds
HD10_512.hds
HD30_512.hds
HD00_512.hda
HD10_512.hda
HD30_512.hda

[aotta]

shorting my 50 pin cables to about 10-15cm!
Thanks, will order one. Note that the Centronics one has no cable and also has the issue.

I know Centronics has direct connection, but noone has successfully tested that version.
Keep in mind that i built myself cables using a 50 pin idc cable, cutting it and cramping a centronics connector. I had issue "low voltage detected" with 25cm lenght (not always indeed, but most time) and good result with 10-15 cm.
But, did you try connecting it internally? i built an adaptor if you're interested: https://nfggames.com/forum2/index.php?topic=7445.0