Perfect FDS 2C33 audio when not using actual FDS disks?

[Hubz]

I traced the connector with a multimeter and soldered the wires. It's ghetto but works. I'll take a pic and post it later.

[Hubz]

Here's a couple pics.

https://www.dropbox.com/s/mwpu9ogjnpdno ... 0.jpg?dl=0
https://www.dropbox.com/s/tm2e0cvtd49lk ... 2.jpg?dl=0

[Tomy]

Wow, you directly connected it. When I back home, I will try it. Thank you.

[DrDementia]

let us know the results.

my problem is still unresolved, I suspect my drive. I checked my cable it seems to be good, continuity through the cable and connector, I checked from the pins to stick. I don't want to solder wires to it either

so I changed the src code to print out the values returned from the function calls but they didn't mean much to me. maybe someone can add some more logic as to why "read failed" so we can debug our problems a little easier.

fdsstick works great other than that though.

[Tomy]

Hi DrDementia,

Sorry for the late. I can't get it work. My case is same as yours.

The error is from fdsstick as I understand. So, it is no easy to know what is the problem from the source I think.

I've 4 PCs, only one have better result. All others will fail when the magnet head return to the beginning of disk.

It will show error immediately. I saw Chris post, said his good PC have USB 3.0 powered. I try my PC which have USB 3.0, it can read

FDSSTICK, but not fds drive.

Then I try to add some buffer between fds drive and fdsstick. The problem still the same. No idea what is the problem at the moment.

I already rquest loopy to try more PC, I waiting for his test now. If some PC not compatible with fdsstick. I think loopy can update

firmware to fix it.

I doing Twin Famicom to fdsstick cable at the moment. It should be working well I think.

[jaek_3]

Can someone tell me how to physically write to disks with this?

[loopy]

On read errors - I've found that a series resistor (10k or so) on the READ DATA pin ("pin 9" in my pinout diagrams) helps.
http://3dscapture.com/fdsstick/fds_res.jpg

I built a GUI, it's not quite finished but you can try it out. http://3dscapture.com/fdsstick/FDSStick.exe
I made a small change to the firmware to make using the button easier. Instead of slot numbers, you push the game number (1, 2, 3, etc..). After the game loads, the button changes disk sides (1=A, 2=B, ...)

[DrDementia]

I tried the 10k resistor, didn't seem to work, not one successful read yet. I tried two PCs, different ports. I don't have a usb3.0(blue) port so I can't test that. Most of the time reading fails at the beginning of the disc (right before or after click?). I reinserted the stick each time.
I'll try to test and debug some more when I have some time.

I've 4 PCs, only one have better result. All others will fail when the magnet head return to the beginning of disk.

It will show error immediately. I saw Chris post, said his good PC have USB 3.0 powered. I try my PC which have USB 3.0, it can read FDSSTICK, but not fds drive.

So does that rule out the fds drive? does the pc that works(have better results) always work?

I attached my modified fds.exe. it prints out more info, maybe loopy can get some debug info from this. maybe someone can show me what a successful read looks like. I should have probably gave some more meaningful labels.

here's one of my better reads. (we need a spoiler to hide this text)

fds -r read1.fds
FDSStick console app (Aug 31 2015)
Opened FDSStick (xxxx.xxxx)
dev-readstart
readbuf
result D3118E
bytesin 0
readbuf 9F0020
dev rd result 100
buff
result FE
bytesin FE
readbuf 9F0020
dev rd result 100
buff
result FE
bytesin 1FC
readbuf 9F0020
dev rd result 100
buff
result FE
bytesin 2FA
readbuf 9F0020
dev rd result 100
buff

result FFFFFFFF
Read error.
Failed.

[Tomy]

Hi DrDementia,

My problem solved. I can read FDS disk now. Not yet for write.

What I do is :

1) Add 10k resistor on pin 9.
2) Update fdsstick firmware to v1.03
3) FDS Drive don't mod, let it original
4) Modded Power Board v5

I've 4 PC here. Now, two PC very stable. One PC sometimes error, re-insert fdsstick, it is ok again. Only 1 PC with AMD CPU not work (never work)

The cable I make is very long (2 feet). So, "long" is not the problem.

Because I don't have 7201 drive here, I can't test write. I'm finding a way now, if I can write, I'll tell you.

I tried your fds.exe, it is not work for me. It error everytime, never success. I use loopy fds.exe v2 at the moment.

[Tomy]

Hi DrDementia,

I can write FDS disk now.

What I do is :

1) Add 10k resistor on cable pin 9.
2) Update fdsstick firmware to v1.03
3) FDS Drive with 7201 chip (no need to mod)
4) Modded Power Board v5

All my 3 PCs ok, only the one with AMD CPU not ok.
I can Read and Write FDS disk.

[jpx72]

Where can I download the firmware with edited button function? Thanks

[Tomy]

Download this : http://3dscapture.com/fdsstick/FDSStick.exe
Plug in fdsstick to your PC and run FDSStick.exe
It will auto update your fdsstick firmware.
(It will show updating on screen, don't remove your fdsstick at that time. If not, I afraid it may die.)

[loopy]

I updated the windows GUI (fdsstick.exe) to allow disk reading/writing.

[DrDementia]

The cable I make is very long (2 feet). So, "long" is not the problem.

I tried your fds.exe, it is not work for me. It error everytime, never success. I use loopy fds.exe v2 at the moment.

thanks for clarifying the cable length, mine is a little too short.
Thanks for testing. does loopy' fds.exe v3 work for you? why use v2?

My further testing. I tried the new gui (fdsstick.exe) I could only get it to read the first 0x33 bytes or so of the disks- sometimes less. I tried most of my discs around 20, some multiple times. I got part of the header the "NINTENDO HVC". I could never get a whole block. I always get - crc failure and 508 bytes lost.

My setup was similar to Tomy's. I tried with and without the resistor, same results.
1) 10k resistor on pin 9.
2) 3206 FDS Drive unmodded
3) Modded Power Board v5

I got another FDS with a 7201. I tried reading with it and get the same thing only part of the header. Any clue to what I'm missing?

[loopy]

Is it an old computer?