Communication port information

Excellent excellent. :D The exact info I needed to test the 5v line with my custom connector. Best news is it actually works :D

I'm trying make my DaVinci 2.0 Duo print like it had a 0.18mm nozzle when in reality it has a 0.4mm one which is pretty standard for printers. I'm going to continue to try to tweak my design so it can be printed on cheap printers,


Hopefully this will make the communication port more accessible for people who want to use it for modding.


y3mCrr2Eh3YIxbrXWX2WXmqEy-C6qs1Tcu8TQRnNXygZwKAvryFsL6aNIRLyFdDVs1XBbGmaxDUkneDCjRJjBQttB-4MPMR45j1I_LQW14QWlUaRAnPIy0QE2EEcF_zHH4AJRnrDH2nuX8Gjpzv8-bft-OGKpTeda2WrdRhSz7C2A8
 
Last edited:
The 5V line is a signal line and should not be used as a power source. In my design, I'm using that signal to indicate when the Saturn system is on or has been power cycled. The communication protocol for the FDD isn't very robust, so detecting a system reset is unfortunately rather important.

zone66x, would you be willing to send me a copy of your connector design files? I've been planning on creating a connector with a 3D printer, but the past year has been very hectic with work. The connector, combined with a couple of hardware improvements that I've been able to make over the past year, may finally make refining my design into a sell-able device feasible.

miyasan, You are correct about the 28 bytes in the change partition command, but that is indicated in the protocol document. That portion of the transfer is sent as a full block and thus follows the full block protocol (which includes a 4 bytes header and a 4 byte CRC).
 
Last edited:
Hey BrokenLizard,

Glad to see your still alive and kicking :):top:

The 5V line is a signal line and should not be used as a power source. In my design, I'm using that signal to indicate when the Saturn system is on or has been power cycled. The communication protocol for the FDD isn't very robust, so detecting a system reset is unfortunately rather important.

Yeah read your PDF document describing as much. :) It's not the end of the world if one must rely on an external power source. I was planning to do some test with an ArduinoNano which can get it's power from the USB or an adapter. The SH-2 is wonderfully flexible in how it can communicate via serial so I if a cheap device like an ArduinoNano is used it will open many possibilities via it's many modules like sd card slot, wifi and bluetooth.

zone66x, would you be willing to send me a copy of your connector design files? I've been planning on creating a connector with a 3D printer, but the past year has been very hectic with work. The connector, combined with a couple of hardware improvements that I've been able to make over the past year, may finally make refining my design into a sell-able device feasible.

I started working on creating a communication port connector because your work and dilemma in producing a connector inspired me. :D I'm planning to put the connector design on my thingiverse account at some point so anyone can make the connector and hopefully make devices to work with it. :) I tend to only put up designs that I've actually be able to successfully print consistently I still need to sort things out before I upload though.

I use a "cheap" DaVinci 2.0 Duo which uses the more widespread, accessible and cheaper FDM technology. What printer do you have or are planning to use? If your planning to use an SLA printer then the tolerances of my design will need to be adjusted due to the increased precision of those printers.

Here's some pictures of some of the design and test print process for anyone who's interested in 3d printing ;)

My current design is using Molex spring type connector used for connectors like the one used to power floppy drives. It seems to work but they are wider and thicker than what is actually needed. The main problem with this is that the walls between the pins and outer walls of the connector are very thin (~0.2mm and ~0.4mm respectively). If anyone knows of readily available alternative let me know ;) I still think that a design using male DuPont pins should be possible, but I'm a bit worried that the it's inflexibility of the DuPont pins may possibly wear out the Saturn's communication port pin prematurely.

The male DuPont pins would be great to make a printable controller port connector though! :D Another project in the near future maybe ....:whistling:

Anyhow it's almost time for bed and I still want to get some SH-2 assembly working on my Saturn so I guess I'll leave it at that. Again, Glad to see you're still around and working on your backup thing for the Saturn :)

Regards,


Alex
 
I guess putting my personal projects on hold for a while really shows. I can't even remember what I included in my own document! Anyway, I'm planning on getting back into the mix once I can finally finish rebuilding my server.

As for the connector pins, I actually found a couple potential contacts back when work first got their 3D printer. I'll go back through my notes and try to find the part numbers. Mounting these contacts might be more challenging than the contacts you mentioned, but at least from the pictures and datasheets that I've found, appear to have a greater resemblance to the original contacts.
 
I just discovered that I never uploaded the latest version of my FDD protocol document to my server, so for the past 5 years it has been slightly out of date. I'll need at least a couple of days to review it, but then I'll upload the latest version.
 
I guess putting my personal projects on hold for a while really shows. I can't even remember what I included in my own document! Anyway, I'm planning on getting back into the mix once I can finally finish rebuilding my server.

As for the connector pins, I actually found a couple potential contacts back when work first got their 3D printer. I'll go back through my notes and try to find the part numbers. Mounting these contacts might be more challenging than the contacts you mentioned, but at least from the pictures and datasheets that I've found, appear to have a greater resemblance to the original contacts.

*Imagines some mad scientist lab with wires, electronics and papers everywhere* :D

Amazing that it's been over 20 years since the Sega Saturn was born. Look like some of us still haven't forgotten it and are still trying to make that next awesome mod. :)
 
I just discovered that I never uploaded the latest version of my FDD protocol document to my server, so for the past 5 years it has been slightly out of date. I'll need at least a couple of days to review it, but then I'll upload the latest version.

I WANT IT NOW! :cwm23:

jk jk :D

After 5 years, I think 2 days of review won't disappoint anyone. There's so little documentation regarding the communication port that even your outdated pdf is still very much appreciated. :)
 
My work has a MakerBot Replicator 5th Gen with the specifications listed below. There are a few local companies that rent out time on higher quality printers as well. Given that the only quote I could get for professionally made molded connectors was $9,000 (for the first batch of 100 12" single ended cables), rental costs should be far more reasonable.

Print Technology: Fused deposition modeling
Build Volume: 25.2 L x 19.9 W x 15.0 H cm [9.9 L x 7.8 W x 5.9 H in]
Layer Resolution: 100 microns
Filament: 1.75 mm [0.069 in] MakerBot PLA Filament
Nozzle Diameter: 0.4 mm [0.015 in]

As for the contacts, I still have not found my notes with part numbers yet, but I was originally envisioning using contacts of the type general type found in SIM card readers (see the linked picture). I know there are companies that sell the contacts individually, but it will take a little bit of searching. I also have access to friends who are fluent in Chinese so that might help in the search.
$(KGrHqFHJE4FG)n-SiwiBRupTpfM1g~~60_35.JPG
 
I got ss-fdd. it is very expensive...

I monitored SPI between Saturn and FDD.
I wrote a little about it.

<<command: change partition>>
(1) send command token(4byte + CRC4byte)
{0x80, 0x11, (uint16)partition number, CRC}

(2) get ACK(4byte + CRC 4byte)
{0x20, 0x00, 0x00 0x00, CRC...}

(3) get device information(24byte + CRC 4byte)
[0]0x10: start token
[1]0xff:
[2]-[3]0x0014: total of data
[4]0x00: device ID.
[5]0x02: total of partition.
[6]0x05: SPI clock.
[7]0x0c: unknown
[8]-[11]0x000b4000: total bytes.
2HD fdd capacity are 1474560bytes, so half are 737280bytes = 0x0b4000.
[12]-[15]0x000000b4: total clusters.
1cluster is 4096bytes = 0x1000
[16],[17]0x1000: unknown, maybe read max?
[18],[19]0x1000: unknown , maybe write max?
[20]-[23]0x00005000: unknown
[24]-[27]0x0000fae2: CRC

(4) get Floppy state(4byte + CRC 4byte)
{0x20, 0x00, 0xff, 0x00, CRC 4byte}
 
Hey all,

I just posted the 3d files to print the male communication port connector I made. :D It's still a work in progress but it's usable in it's current state. Better having something than nothing at all.

3D printer files


Enjoys,

Alex
 
I just updated my Sega Saturn Floppy Disk Drive Communication Protocol document to version 1.4.

Alex, thanks for the 3D models! I'm still looking into finding smaller, gold plated contacts but so far everything I've found would require disassembling an existing connector.

Currently, I'm in the process of updating my design to use a faster microcontroller and potentially connect to the SD card using SQI. Additionally, I'm exploring a new protection circuit design for protecting the Sega Saturn's communication port incase contention occurs. This new design might enable faster data transfers, but I will need to test its response dynamics first.

Especially since my work bought a 3D digitizer, this recent progress may enable the selling of realistic looking SD card-based floppy drive replicas within a few months.
 
Here is a data sheet with potential contacts. While this week is rather hectic for me, I'll try and go over the dimensions within a few days and see if any of these might work.
 

Attachments

  • ENG_DS_6-1773460-8_Spring_Fingers_0814.pdf
    3.7 MB · Views: 264
1447360-9, 1447360-8, 1871059-1 look like the most likely candidates. These all meant to be surface mounted to a PCB though. To use them properly you would need two separate very thin PCBs and solder the pins to them. I guess it's not the end of the world but it would complicate things a bit. Another option would be to maybe use wire and conductive epoxy.
 
We could use PCBs, but I was sort of hoping we could solder wire to the contacts and then pot them. This might require a multi-part connector though.
 
We could use PCBs, but I was sort of hoping we could solder wire to the contacts and then pot them. This might require a multi-part connector though.

Yeah true could try that. I was actually looking for the contacts on aliexpress but didn't have any luck finding them. Found them on digikey though.
 
Just wanted to let everyone know I'm still aound and I'm planning on working on the connector soon. I've had very little free time lately and I've been using the time that I do have to finish up a translation project. It's too difficult to simultaneously work on multiple projects, so I'm trying to complete the short ones first.
 
Excuse me while I resurrect this thread. I can't get the documents about the port communication, and this thread died out .wassup.
 
Last edited:

Attachments

  • Sega Saturn Floppy Disk Drive Communication Protocol.pdf
    1.3 MB · Views: 308
  • SegaSaturn FDD FAQ.pdf
    285.6 KB · Views: 372
I've attached the BrokenLizard's file my answer
pseudo saturn kai by cafe-alpha supports the floppy disk, you can have a look at the source code here : PPCenter :: Pseudo Saturn Kai
FDD Operator is here : http://segaxtreme.net/content/satdev/Tools/sega/FDD.rar
BrokenLizard's newest page : Sanford T. Freedman | Projects | FloppyFake (thanks SteveKwok)
Awesome, thank you. I'm Godkingofcanada btw, from the yaba freenode. I 3d printed 6 of the comm port adapters and just wired one.
 
Back
Top