Image; GIF 3K

Determining clock speeds

 

 

  There are three stand-alone Econet clocks:

There are three parts of the clock signal that you need to be aware of:

Data is transmitted on the falling edge of the mark. Therefore, within a certain period, you ideally want the mark as short as possible and the space as long as possible. The faster your clock goes, the faster you can transfer data across the network. However this is modified by three factors:

 

 

  The duration required for each type of machine to recognise the clock is shown below, along with experimental times taken from my network.

   BBC micro or Master . . . .  4µS  ; minimum 4µS         (250kHz)
   FileStore . . . . . . . . .  4µS  ; only likes its own clock!?
   SJ research MDFS  . . . . .  3µS  ; works down to 2µS   (500kHz)
   SJ Econet bridge  . . . . .  3µS  ; works down to 2µS   (500kHz)
   RiscOS computers  . . . . .  2µS  ; works down to 1.5µS (~660kHz)

   Maximum period duration . . 13µS  ; ( 70kHz)
   Acorn default clock setting  5µS  ; (200kHz)
It is not possible to exactly calculate the duration of the MARK; but it is possible to calculate the SPACE, as shown below:
       2 × d
   S = -----
       v × c

   Where:

     d = distance of the longest side of the network (in metres)
     v = velocity factor - assume 0.5 for most cables
     c = the speed of light - 300,000,000 (3×108)

   For example, a 600m network with the clock 200m from one
   end and 400m from the other.

           2 × 400
   S = ---------------  =  5.33333333E-6, rounded up to be 6µS
       0.5 × 300000000

   Therefore, your SPACE is 6µS, try your MARK to 1µS,
   which gives you a PERIOD of 7µS - a frequency of 143kHz.

The best thing to do is to set the above recommended clock speed, and then increase it in small steps until you the network becomes unstable; then slow it down a step.
You should, on average, be able to shave at least a µS off of the recommended speeds, except for 6502 based equipment such as BBC micros and FileStores.
The MDFS cannot quite keep up with RiscOS machines, but it isn't far behind - and you will find your network is quite comfortable operating a tiny bit slower in order to allow the MDFS to be used.

 

 

  Please be aware, however, that the MDFS may require a slower speed than it seems. My MDFS is quite happy serving using a 0.5µS mark in a 2µS period. When I come to use the FAST terminal to talk directly to the MDFS firmware, it fails on anything faster than a 1µS mark in a 4µS period... Remember to check for things such as this.

 

 

  If you have hooked in the MDFS on a seperate network using the SJ bridge, it is a trivial matter to set the bridge to Admin mode and alter the speed as applicable - it is almost fun!
Those of you using a clockbox, who are handy with a soldering iron, might like to rig up some kind of flip switch on the clockbox so you can instantly select a fast or slow clock.
I did this to my FileStore in the days before I had a clockbox. Switch to the left, lethargic mode for the FileStore. Switch to the right, a little quicker for the A3000.

If you consider this, I have a few suggestions:

For details of which links to change in your particular clock, please refer to the hardware specification for it.


Return to econet index


Copyright © 1999 Richard Murray