Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user IcePic ! (Registered 2024-12-03) You are not logged in - nap
CSDb User Forums


Forums > C64 Coding > Accurately Measuring Drive RPM
2020-08-03 16:07
chatGPZ

Registered: Dec 2001
Posts: 11378
Accurately Measuring Drive RPM

To bring the discussion from 1541 Speed Test into the forum....

first lets recapitulate:

The general idea is: have a "marker" on a track, then measure the time for one revolution using timers. Generally there are different ways to achieve this:

- wait for the marker and toggle a IEC line. the C64 measures the time using CIA timer. this is what eg the well known "Kwik Load" copy does, the problem is that it is PAL/NTSC specific, and it can never be 100% exact due to the timing drift between drive and C64.

- wait for the marker and measure the time using VIA timers on the drive. the problem with this is that VIA timers are only 16bit and can not be cascaded, so you either have to measure smaller portions at a time, or rely on the wraparound and the value being in certain bounds at the time you read it.

now, to make either way slightly more accurate, a special kind of reference track can be used. typically this track will contain nothing except one marker - which makes the code a bit simpler and straightforward. this is what 1541 Speed Test does. the DOS also does something similar when formatting, to calculate the gaps. This obviosly has the problem that we are overwriting said track.

Now - the question isn't how to do all this, that's a solved problem. The question is, given a specific implementation, how *accurate* is it actually, and why?

The basic math to calculate the RPM is this:

expected ideal:
300 rounds per minute
= 5 rounds per second
= 200 milliseconds per round
at 1MHz (0,001 milliseconds per clock)
= 200000 cycles per round

to calculate RPM from cycles per round:
RPM = (200000 * 300) / cycles

two little test programs are here: https://sourceforge.net/p/vice-emu/code/HEAD/tree/testprogs/dri.. ... the first reads timer values between each sector header and then the total time for a revolution is accumulated from the delta times. the second leaves the timer running for one revolution and then indirectly gets the time for a revolution from that. to my own surprise, both appear to be accurate down to 3 cycles (in theory the second one should be more accurate, at least thats what i thought. i also expected some more jitter than just 3 cycles)

1541 Speed Test writes a track that contains one long sync, and then 5 regular bytes which serve as the marker. it then reads 6 bytes and measures the time that takes, which equals one revolution. somehow this produces a stable value without any jitter, which was a bit surprising to me too (i expected at least one cycle jitter, due to the sync waiting loops) (i am waiting for the source release and will put a derived test into the vice repo too)

So, again, the question is... how accurate are those and why? (a stable value alone does not tell its accurate). Some details are not quite clear to me, eg if we are writing a reference track, how much will that affect the accuracy of the following measurement? how will the result change when the reference track was written at a different speed than when doing the measuring? Will using a certain speedzone make it more or less accurate?

Bonus question: can we use https://en.wikipedia.org/wiki/Chinese_remainder_theorem with two VIA timers to make this more accurate? or is it a pointless exercise?
 
... 263 posts hidden. Click here to view all posts....
 
2020-08-06 18:03
chatGPZ

Registered: Dec 2001
Posts: 11378
Quote:
that's totally out of scope of the discussion. of course we are assuming a standard DOS formatted disk.

the thread is about comparing how accurate the two methods are, not how you can make them fail using non standard disks. please stick to the topic. you still havent explained some of your claims regarding accuracy.

tlr: eg you could put two sector 0 headers after each other, and only one of them is followed by a data block - that will work fine (for reading at least). copy protections used this, as a simple copier will not recreate this.
2020-08-06 19:46
Zibri
Account closed

Registered: May 2020
Posts: 304
Quoting Groepaz

the thread is about comparing how accurate the two methods are, not how you can make them fail using non standard disks. please stick to the topic. you still havent explained some of your claims regarding accuracy


Mine are not "claims".
The proof is my program itself and no progranm before that could accomplish the same results including yours.
Even after the modifications.

I even tested your programs since you clearly didn't even take the time to test them before committing them.
The screenshots are more than eloquent.

I repeat: I have nothing to prove nor to explain to you nor anybody else. If you wanted to learn something you use the worst attitude to do so.
Sorry, but I really am not in the mood to be teaching anything to you.
2020-08-06 20:02
chatGPZ

Registered: Dec 2001
Posts: 11378
So i take it that you can not explain why one method is supposed to be more accurate than the other, nor explain why the explanation in post #30 is false. Repeating the same claims over and over does not help, nor prove anything. Forget my program, my program (or anyone elses) is irrelevant for explaining how accurate yours is.
2020-08-06 20:12
Zibri
Account closed

Registered: May 2020
Posts: 304
Quote: So i take it that you can not explain why one method is supposed to be more accurate than the other, nor explain why the explanation in post #30 is false. Repeating the same claims over and over does not help, nor prove anything. Forget my program, my program (or anyone elses) is irrelevant for explaining how accurate yours is.

Bite me.
Live with it.
2020-08-06 20:17
Zibri
Account closed

Registered: May 2020
Posts: 304
If anyone is interested some made even a video tutorial (in italian, but automatic sbutitles seem to work about fine).

https://www.youtube.com/watch?v=p87sw33byYY
2020-08-06 20:27
Compyx

Registered: Jan 2005
Posts: 631
"Some"
2020-08-06 20:33
chatGPZ

Registered: Dec 2001
Posts: 11378
Pretty cool, he even let you work on his drive!
2020-08-06 20:43
Rebok

Registered: Apr 2017
Posts: 10
Zibri, what about the station 1541-II. Is there a similar way to adjust?
2020-08-06 20:51
chatGPZ

Registered: Dec 2001
Posts: 11378
Take off the top cover, the pot is on the small motor control board
2020-08-06 20:54
Hoogo

Registered: Jun 2002
Posts: 105
I know how to double the accuracy....
Previous - 1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | ... | 28 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Impetigo/Crescent
Twilight/Excess/Arcade
WVL/Xenon
Matt
cobbpg
aNdy/AL/Cosine
Guests online: 128
Top Demos
1 Next Level  (9.7)
2 What Is The Matrix 2  (9.7)
3 13:37  (9.7)
4 Coma Light 13  (9.7)
5 Edge of Disgrace  (9.7)
6 Mojo  (9.6)
7 The Demo Coder  (9.6)
8 Uncensored  (9.6)
9 Wonderland XIV  (9.6)
10 Comaland 100%  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Party Elk 2  (9.6)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.6)
5 Libertongo  (9.5)
6 Rainbow Connection  (9.5)
7 Onscreen 5k  (9.5)
8 Morph  (9.5)
9 Dawnfall V1.1  (9.5)
10 It's More Fun to Com..  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Nostalgia  (9.3)
5 Triad  (9.3)
Top Logo Graphicians
1 t0m3000  (10)
2 Sander  (9.8)
3 Mermaid  (9.5)
4 Facet  (9.4)
5 Shine  (9.4)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.062 sec.