fluxengine

PSOC5 floppy disk imaging interface

Explore on GitHub Read Hacker News discussions

3Distinct people

4Mentions

0Explicit recommenders

447GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

PSOC5 floppy disk imaging interface

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2021-01-07 07:20:47 UTC to 2026-07-08 18:02:53 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	1	1
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	2	2
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	1	1

What Hacker News says

4 sources

986aignan·Jul 8, 2026

There's an issue on the FluxEngine git repo that may be related to this: https://github.com/davidgiven/fluxengine/issues/75 At the end of the thread, David Given reports that some PC floppy drives drop pulses when trying to read 800k Mac disks: https://github.com/davidgiven/fluxengine/issues/75#issuecomm... So the Cambridge page might be saying "use an Applesauce controller" as a sort of shorthand for "use a drive from an actual Apple computer".

In Copy That Floppy – Cambridge guide for preserving data from fragile floppy disks

rasz·Oct 16, 2025

https://github.com/davidgiven/fluxengine and my little contribution if you have a $5 logic analyzer board (FX2LP) and want to play in Sigrok/PulseView/DSView https://github.com/raszpl/sigrok-mfm

In The people rescuing forgotten knowledge trapped on old floppy disks

rasz·Oct 16, 2025

https://github.com/davidgiven/fluxengine

In The people rescuing forgotten knowledge trapped on old floppy disks

mjg59·Jan 7, 2021

Context, since it's not spelled out with a lot of background in the article: most floppy drives spin at a fixed RPM, which is referred to as a Constant Angular Velocity (CAV: ie, no matter how far out on the disk you are, the disk rotates by a constant angle per second). This means that towards the outer edge of the disk more magnetic media is passing under the head per second than towards the inner edge of the disk (with a larger circumference, a constant angle will represent a longer chunk of media). If you're writing the same number of bits per second, this means each bit takes up a larger amount of magnetic media at the outer edge compared to the inner edge. If, instead, the drive spins at a Constant Linear Velocity (CLV: ie, the same amount of magnetic media passes under the head per second no matter where on the disk you're accessin

Read the rest

g[1]), each bit can take up the same amount of magnetic media, which means you can store more bits per track towards the outer edge of the disk. Macs did this in order to increase the amount of data you could store, at the cost of additional complexity in the drive to support spinning at different rates. It also means that 800K Mac disks (the largest format which used variable rates) can't be read on normal PCs, which lack support for variable rates. FluxEngine works at a lower level than the standard PC floppy interface - it allows the OS to look at the actual magnetic flux data on the disk, whereas the standard PC floppy interface will only pass back the interpreted bits. Even if the disk is spinning at a constant RPM, knowing where the head is located allows that magnetic flux data to be turned back into the appropriate bitstream (or vice versa for writing) and allows handling CLV disks even though they're in a CAV drive. [1] Except it doesn't actually do that - there's only 4 different speeds, as you can see in https://github.com/davidgiven/fluxengine/blob/7eaf3de5723436... .

In Writing 800kB Mac disks with FluxEngine