Differences between revisions 12 and 13
Revision 12 as of 2021-02-21 11:13:15
Size: 3141
Editor: asbesto
Revision 13 as of 2021-02-21 12:28:45
Size: 3254
Editor: asbesto
Deletions are marked like this. Additions are marked like this.
Line 73: Line 73:


for i in $(seq 1 20) ; do

fluxengine seek -t 77
fluxengine seek -t 0



Fluxengine scratchpad

Hardware connections

  • Flat cable pin 1 to the micro-USB side.
  • Non-inverted floppy connection to the drive! Red wire to the dent side. This is the same for 5"1/4 and 8" disks.

Turn on the FD FIRST, and connect the fluxengine usb cable AFTER. Drive must turn LED on for about 2 seconds, eventually parking the head.

If LED is fixed ON, this means some cable are upside down!

./fluxengine rpm must read the rpm speed. WITH A DISK INSIDE

Test cases

  • IBM PC 360K disk on 360KB drive: ./fluxengine read ibm -s:t=0-40 -o petacci.img
  • ???IBM PC 1.2MB on 1.2MB drive: ./fluxengine read ibm -o petacci.img (to be tested)
  • IBM PC 360K Floppy disk on a 1.2MB DRIVE: ./fluxengine read ibm -s:t=0-79x2 -o petacci12.img
  • Read data and flux, IBM PC 360KB Disk on 360K drive: fluxengine read ibm -s:t=0-40 --retries=0 --revolutions=10 --overwrite --write-flux=testdisk.flux
  • M20: con drive da 1.2MB: fluxengine read ibm --retries=10 --revolutions=10 --write-flux=testdisk.flux

8 inches

  • fluxengine read ibm -s:t=0-76 --retries=1 --revolutions=3 --overwrite --write-flux=prova.flux -o prova.img


  • nome="prova"; fluxengine read ibm --retries=1 --revolutions=3 --overwrite --write-flux=^Come.flux --visualiser-period=167 --write-svg=$nome.svg -o $nome.img

svg test:

  • seq 1 380 | while read i; do fluxengine read ibm -s prova.flux --visualiser-period=$i --write-svg=$i.svg ; done

echo usage: leggi name

# normale 0.2, --bit-error-threshold=0.4 da provare in caso di errori anali
# :s=0 single side read

fluxengine read ibm -s:t=0-77 --retries=100 --revolutions=5 --bit-error-threshold=0.4 --overwrite --write-flux=$nome.flux -o $nome.img 1>$nome.log 2>&1 &
#fluxengine read ibm -s:t=0-77 --retries=10 --revolutions=5 --bit-error-threshold=0.4 --overwrite --write-flux=$nome.flux -o $nome.img 1>$nome.log 2>&1 &
#fluxengine read ibm -s:t=0-77 --retries=5 --revolutions=5 --bit-error-threshold=0.5 --overwrite --write-flux=$nome.flux -o $nome.img 1>$nome.log 2>&1 &
tail -f $nome.log

# --revolutions=X: when reading, spin the disk X times.  X can be a floating
# point number.  The default is usually 1.25.  Some formats default to 1.
# Increasing the number will sample more data, and can be useful on dubious
# disks to try and get a better read.
# --pulse-debounce-threshold controls whether FluxEngine ignores pairs of
# pulses in rapid succession.  This is common on some disks (I've
# observed them on Brother word processor disks).
# --clock-interval-bias adds a constant bias to the intervals between pulses
# before doing decodes.  This is very occasionally necessary to get clean
# reads - for example, if the machine which wrote the disk always
# writes pulses late.  If you try this, use very small numbers (e.g.  0.02).
# Negative values are allowed.
# Both these parameters take a fraction of a clock as a parameter, and
# you'll probably never need to touch them.

for i in $(seq 1 20) ; do

fluxengine seek -t 77
fluxengine seek -t 0


FluxengineAppunti (last edited 2021-02-21 17:18:13 by asbesto)