2.8" QD Disk Emulation

General discussion forum - for all that doesn't fit in any other category.
Post Reply
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

AMSynths wrote: Sun Sep 01, 2019 6:32 pmyep perfect
Very Interesting ! We are close ! I have just added some blank bytes (0x00) before the track beginning on your DSKA0004.QD.

So can you try write to this images ?

EDIT : DSKA0004.zip removed.
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

Ignore the previous test/post and try this instead :

Update the firmware with 3.4.1.13 (attached)

And try to write to this image !
HxCUSBFE.UPD
(61.5 KiB) Downloaded 303 times
DSKA0004.zip
(418 Bytes) Downloaded 309 times
AMSynths
Posts: 85
Joined: Fri Aug 09, 2019 10:43 am

Re: 2.8" QD Disk Emulation

Post by AMSynths »

Load fails with Illegal QD and write fails with verify error.
I can no longer do a F! Load to read the bank name.
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

AMSynths wrote: Mon Sep 02, 2019 11:34 am Load fails with Illegal QD and write fails with verify error.
I can no longer do a F! Load to read the bank name.
Load fail is normal : The image is blank.

Please share the image after the write fail !
AMSynths
Posts: 85
Joined: Fri Aug 09, 2019 10:43 am

Re: 2.8" QD Disk Emulation

Post by AMSynths »

See attached. I tried reading after writing, last time it found the bank name.
Another write after a save does recognise that its a QD that has been written to.
Attachments
DSKA0004.zip
(717 Bytes) Downloaded 289 times
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

Retry to write on the last DSKA0000.QD image (the one from this post : viewtopic.php?f=2&t=773&start=225#p21206 )
with this firmware :
HxCUSBFE.UPD
(61 KiB) Downloaded 294 times
And share the image.

Also can you try to read these images and tell me what you get :
to_read2.zip
(1.43 KiB) Downloaded 299 times
AMSynths
Posts: 85
Joined: Fri Aug 09, 2019 10:43 am

Re: 2.8" QD Disk Emulation

Post by AMSynths »

Latest fw loaded
to_read2 gives Illegal QD
Last DSKA0000.QD gives I/O error 2 - from Sun Sep 01, 2019 2:25 pm

I can still write to 0004 with a verify error, and then successfully read the file back in
Attachments
DSKA0001.zip
(79.92 KiB) Downloaded 333 times
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

AMSynths wrote: Mon Sep 02, 2019 2:39 pm I can still write to 0004 with a verify error, and then successfully read the file back in
Interesting. Which DSKA0004 from this thread exactly ?
Is the full read working ? (i mean with the sample ?)
This is maybe related to this ? :
AMSynths wrote: Sun Sep 01, 2019 4:52 pm 0004 loads reliably time after time, and ok without pull up resistor.

I have noticed one change needed:
The full QD read after a F1 Load needs to be delayed until after the check read has gone to the end of the QD and stopped. At the moment I can hit Load during the check read and it stops with Illegal QD, because the Gotek has allowed a read during a read

Sequence should be:
F1 Load
Sampler reads the QD bank name AND continues to the end of the bank/disk - takes another 3 seconds or so
Any pressing of Load during this time is delayed to start reading until this first QD read has stopped
Once the check read has fully completed to the end of the Bank, a full Load can take place, and the sampler reads the QD bank into memory

Hope that helps!
I am not sure what do you mean by "because the Gotek has allowed a read during a read" but i suspect that the ready window is a bit too long then the ready signal still asserted too much time after the write and the verify start immediately. This is similar to what you describe.


attached a new firmware with a end of write splice support.

EDIT : HxCUSBFE.UPD removed.
AMSynths
Posts: 85
Joined: Fri Aug 09, 2019 10:43 am

Re: 2.8" QD Disk Emulation

Post by AMSynths »

Hi.
There are 3 types of Load QD:

1. Normal Load - reads the bank on the QD
2. F1 Load - reads the name of the bank and the structure only but keeps reading to the end of the bank, as the QD cant stop mid track. The sample data is not loaded.
3. F2 Load - reads the bank on the QD but does not load performance parameters, same use case as 1 in terms of disk handling

Because an F1 Load frees up the display and sampler controls early (within 1 second), it is possible to hit Load again.
Its important that this second command is actioned after the disk has reached the end of the read.
So the Gotek needs to complete a read before starting another one

Hope that helps
AMSynths
Posts: 85
Joined: Fri Aug 09, 2019 10:43 am

Re: 2.8" QD Disk Emulation

Post by AMSynths »

Latest fw loaded

0000 I/O Error 2
0001 Illegal QD
0002 Illegal QD
0003 Illegal QD
0004 Loads ok
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

Can you try to write to each of these images ?. (They are currently all blanks with an increasing ready window size from 4.67s to 4.77s)
please post them back here.

EDIT : to_write_and_read.zip removed.
AMSynths
Posts: 85
Joined: Fri Aug 09, 2019 10:43 am

Re: 2.8" QD Disk Emulation

Post by AMSynths »

All fail verify

EDIT : archive removed!
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

AMSynths wrote: Mon Sep 02, 2019 5:53 pm All fail verify
Some are fully readable when you try to read them ?
AMSynths
Posts: 85
Joined: Fri Aug 09, 2019 10:43 am

Re: 2.8" QD Disk Emulation

Post by AMSynths »

Only 0005 is readable, the rest fail with Illegal QD
Jeff
Site Admin
Posts: 8247
Joined: Fri Oct 20, 2006 12:12 am
Location: Paris
Contact:

Re: 2.8" QD Disk Emulation

Post by Jeff »

New firmware. Changes :

- Timing : Fix the track position after a write.
- Data line is masked outside the ready zone.

EDIT : HxCFEUSB.UPD removed.

EDIT : to_write_and_read2.zip removed.

The images are blank, try to write to each images and post them back.

And thanks for all the tests and your patience... This take longer than i expected...
(I think there is a last thing to fix if this fw still doesn't work properly with the Roland)
Post Reply