F-22 Next-Generation micro–Data Transfer Cartridge (mDTC)
sam.govCool coincidence. In a past job, I specifically made replacement PCMCIA cards for these (and other) planes. Instead of making cards with a controller and onboard storage, we made cards with an FPGA/microcontroller and a microSD card soldered to the PCB. We did this specifically because these aircraft use (at least partially) broken implementations of the PCMCIA protocol, and we'd update the bus protocol per aircraft to work around the limitations. None of these planes can just go buy stuff off the street because some large portion just doesn't work because their protocol isn't fully implemented and isn't flexible to deal with variance in timing/speed/etc.
A fun story: Our cards had whatever industrial-spec microSD card we could find (16GB, 32GB, etc.), and we'd internally limit the disk size to whatever the platform needed. Almost every aircraft had some specific number of MB they wanted because all of their CONOPS listed it, and they didn't want to update documentation or software to put a different number there. We had a plane that could only use EXACTLY 128MB, but they were currently using 256MB cards and partitioning them to 128MB. We updated the disk size to present as 128MB so they could skip this step, and they specifically told us to put it back to 256MB because they didn't want to update the commissioning process to remove the partitioning step.
It was rewarding work, and the card we designed was cheap (~$500 each, which is literally nothing for major platforms like this) and 100% US-designed and made (with the exception of ICs manufactured in the usual places). Still, the procedural and cultural practices of these program offices made it a real struggle to get traction and deploy them widely. Government acquisition is just generally designed around funding primes for current development and then paying through the nose for sustainment later. It was hard to design something for widespread sustainment use because by the time you were done and ready for production, a bunch of parts would be obsolete. Then you'd have to rev the design over and over. We were never allowed to stockpile anything, even if it was trivially cheap, to facilitate production later.
Why weren't you allowed to stockpile anything? Last-Time-Buys would be important for decades long supply chain support right?
Another story:
PO came to me and asked if our card would work on their plane. We ship them a prototype and it doesn't work. They ship it back and send along a card that does work in the plane. We test it, and the card is just faster. We get the designer of the data box (works at the prime) on the phone and talk to him. Explain that our card works within timing specs but isn't working in the plane reader. He says something along these lines: "Oh, our reader implements the communication specification just fine, but only for fast cards. When we designed the box we wanted to hit a certain read/write speed, so we went out and bought a bunch and found the fastest cards and wrote our VHDL to talk to those cards." After we collected our jaws from the floor we updated our card to run a little faster and it started working. They had a lot of trouble finding commercial cards that worked.
And another:
One of the hardest parts to find for a PCMCIA card is stamped sheet metal cases. When we made prototypes, we bought case kits where the PCB just dropped in if you followed the PCB outline and used the right 68 pin connector. Around 2020 the companies that made them started to discontinue them, sent out a notice to offer final production batch ordering to do final lifetime buys. I BEGGED a bunch of groups to go order a few thousand, or tens of thousands and just put them in a closet somewhere (they were like $9/each). No one could make the decision in time, they went obsolete. We ended up designing a new machined aluminum case with super tight tolerances and features and it was like 80% of the total $500 cost.
I would have killed to be able to use the machined aluminum case.
The number one reason we had to retire PCMCIA cards on the flight line was the stamped steel case getting caught on something and bending one too many times. We could fix it a few times, but they wouldn't fit in the aircraft after a while (tighter tolerances than the laptops).
When we designed the prototypes with stainless steel cases we potted the internals (and case) with thermal epoxy to make them more rugged. It made them super strong and durable. We had a lot of issues with machined aluminum cases not fitting well in a bunch of readers because of the tight tolerances.
Yeah, the aircraft had insanely tight tolerances. Generally due to shifting during g-loading causing wear on the connector if the cards had ANY wiggle at all.
P5 pucks?
That's funny that they couldn't make the decision in time because those notices often give minimum 9 months advance warning and sometimes 2 years.
Cool coincidence, since I'm writing a storage driver for an airplane at the moment! Software reuse is very difficult in aerospace since the hardware and software were both qualified in a very specific combination, in the context of an aircraft program, and any change or adaptation is a huge effort.
That means lots of 'clean sheet' driver rewrites from a spec document for your specific environment and hardware, and lots of hand rolled drivers that work well enough, but not great, because the burden of certification is too much to justify incorporating fancy features, like driver interrupts or multiple speeds. Just hard-code exactly the settings you need for your project, you'll save weeks of extra V&V effort.
I worked on submarines in the 2000s and there was a whole cottage industry of old men who maintained the weapons control systems. The Navy wasn't allowed to upgrade the weapons control computers, as far as I understood, in part because of nuclear weapons limitation treaties, so they had to keep the dinosaurs running. 14in HDDs and analog circuitry and all the rest. And all of the companies that built them, all of the manufacturing lines and tooling and processes, were long gone.
Cool. I was in the game during the period when DTMs were still being used, and ended up doing sw mods to support the PCMCIA replacements, which was a real hair puller because of lack of documentation and difficulty in getting Windows to work with the cards (a lot of work was more on the pc side - planners/loaders).
for others - the DTM was a solid black "brick" that weighed a few pounds and was maybe 128MB of solid state memory. About the size of a brick, but half as thick. Very expensive (I think we were paying ~6K at the time), with long lead times. The SCSI devices we used to read/write from the PC were even harder to acquire; you had to get a spot on the manufacturing schedule, and we were a small defense contractor, so no real way to get moved up the list. Made for difficult contract deliveries, and of course absurdly expensive bids due to all of this.
Everyone was really excited to the change to PCMCIA, except the ones of us implementing it!
edit: i may be conflating a few memories, I do remember fighting with microSDs as well, I think. Trying to remember; I think the DTM 'bricks' had a version that accepted a PCMCIA or micro card as the memory, so the interface hardware/sw didn't need to change. I have no idea if the DTMs are in use anymore.
Stupid question, why a microSD instead of an eMMC? They are supposed to be more reliable for industrial and military uses.
Anyway, thank you for your very interesting comment. I work at a particle accelerator, and we also have to deal with lots of obsolete hardware and "interesting" procurement arrangements for totally bespoke designs sold by a single company in the world. We are now trying to procure a CNC, a reflowing station, and several other tools so we can build the boards ourselves, in the long term is much cheaper.
I don't remember why we chose microSD. If I had to guess, at the time, it was easier to find microSD cards with industrial temp operating range.
What happens if the microSD fails while in flight?
It could just be from personal experience but I found full size SD to be much more reliable than Micro. Always imagined it was likely because of heat dissapation.
Using a larger card could actually be a good reliability idea assuming your microcontroller could take account specific sectors going bad and whatnot (like modern SSD)
Depends on the aircraft.
Some only read from data cartridges at system load and login, such as ones used for mission systems (GPS keys, sensors, weapons, etc.). Some read infrequently (Nav maps from mission data load). Some have prognostic data frequently written.
From my extensive experience flying A10-Cs in DCS World...there's a data loading step where the cartridge is read and its contents loaded into the flight management computer. I'm guessing that from that point on, the card isn't accessed, especially during flight.
YOu have people here that wrote the sw; no need to guess.
They were read all the time. Example: The rockwell collins CNDU-800 had 2 databases of points, the primary and reversionary (something like that). The latter being max 200 super important 'get home' waypoints and such, and they were loaded on boot. The Primary was just a collection of waypoints/navaids/airports, and those were dynamically seeked for if, for example, you modify your plan in flight. Because what computer could store 128MB of memory?
I forget the airframe, but for one project I modified the code on the 800 to function as a 'black box' of sorts. We'd record GPS data and the like, to be used for mission debriefs and such in SW that I also wrote. This ended up used in all kinds of places I can't talk about.
Great anecdotes, any idea of what would happen if the card failed in flight?
> "Cool coincidence. In a past job, I specifically made replacement PCMCIA cards for these (and other) planes."
It sounds like you'd be in a good position to bid on this contract. With your experience in navigating procurement bureaucracy, you could make millions!
> We were never allowed to stockpile anything
Now allowed by whom? Was it a business decision or a regulation?
Without going into a ton of detail, I was working as a federal employee for a federal laboratory. Per regulation we couldn't purchase anything not directly tied to an agreement, and we weren't allowed to complete with industry.
Typical work would look like this:
A group would come to us and say, "We use these cards, but they wear out and we need like 200 more to keep running for 15 more years, we talked to primes about fixing this problem for us but they said the only thing they're willing to do is redesign the entire data handling infrastructure in the plane for $500M." So we'd get some tiny amount of money (like $200k) and redesign the card and make them ~20 prototypes. It'd work great, then they'd spend 3 years working on production contracts to try to get 200 built for $100k. In 3 years, some part would go obsolete, they'd come back and give us $50k to update the design and test, then start the 3 years cycle to buy 200 again. Rinse and repeat.
If they would have just given us like $30k, we already knew which parts were high risk of going obsolete, we could have just bought everything necessary to build 1000 units and dropped them in storage, but federal regulation limited what was possible. SUPER frustrating to have something that solves a problem and watch it fall apart over crappy policy.
It's sad to see this request, knowing that I was part of the team that designed a solution specifically to solve it, knowing it worked and tested it on the platform, but some part probably went obsolete and they never got enough manufactured to solve the problem permanently.
Sounds like an opportunity. Form "Jotux Electronic Supply, LLC" (JES) and stockpile the stuff that's cheap now but you believe is gong to be unavailable in the future. When they come back in a few years, the parts are available from JES, they are just much more expensive now.
This was a regular and consistent joke we made, and we saw contractors do specifically this as well. All of our work was intended to be advertised and eventually produced by multiple manufacturing contractors. One contractor would see that a specific part was going obsolete and go buy all of them, and basically starve out the competition. After they were the only contractor that could actually build it the price they would quote would go up 10x.
You could earn good money as a consultant
Believe it or not, there are companies buying up almost every (to-be-)discontinued electronics component imagineable. They shrink-wrap the parts under nitrogen to prevent oxidation and put them away in huge warehouses.
And you don't even want to think about which kindsbof products rely on this supply chain.
This is a microcosm of much of what's wrong with government. Interesting story, thanks for sharing.
Ironically, I would bet the rules hamstringing OP in the story were downstream of some earlier, misguided attempt to "fix" a previous perceived problem in government (open ended contracts/procurement leading to "waste"). So now all employees in federal labs have their hands tied.
Highlighting isolated examples of government waste (or outright lying about it) is eternal red meat for politicians/private sector special interests: the "Golden Fleece awards" [1] started by Sen. William Proxmire and taken up by Sen. Rand Paul are a notorious example.
Then to "fix" the issue we pile on even more counterproductive rules like OP's example or DOGE's weekly TPS reports which add even more wasteful bureaucracy, to somehow reduce government inefficiency.
>build 1000 units and dropped them in storage, but federal regulation limited what was possible.
Is this because they are worried about custody/security? Or a requirement that they actually be new?
It's a complicated morass of regulations in the FAR.
Color of money: We typically had RDT&E funds that were specifically for research and development. We couldn't use those funds to buy components for procurement or operations and maintenance items.
Speculative stockpiling: It's just explicitly banned in the FAR.
Another big problem was the FAR is a gigantic mess of regulation that no one fully understands and it's interpreted differently by every agency. Sometimes the agency is casual with interpretations and will let you do certain things, sometimes they're terrified of getting anything wrong and ultra conservative. Because it's so large you can generally find regulations and clauses to support acceptance AND denial for a lot of actions. More often than not the only thing procurement people cared about was CYA, and they could always find something in the FAR that justified denial.
Heard a rather long conversation on some podcast about how govt used to have this capability of building really amazing things like the Hoover Dam and the Empire State Building and said with all the government regulation, we are just hamstrung from having that ability to build something amazing within budget and on time any more. They repeatedly cited the CA High Speed rail line, the Honolulu Rail Transit and even the VA Electronic Health Record Modernization project.
I can see their point, but comparing projects in the 1930's to those in 2026 seems a bit dishonest. The lack of work safety equipment and rules back then allowed these projects to move fast, ignore safety and build both the Hoover Dam and Empire State building in record time. They were not without casualties because of this. Even OSHA wasn't founded until the 1970's.
I wonder if there will ever be a good balance; or if the amount of regulation has permanently hamstrung large scale software and engineering projects from getting done on time and on budget.
> "govt used to have this capability of building really amazing things like the Hoover Dam and the Empire State Building"
Government didn't build the Empire State Building. It was financed by a private company called Empire State, Inc. that was backed by a bunch of Wall Street bankers and industrial titans. It was designed by Shreve, Lamb & Harmon, and the main contractor was Starrett Brothers and Eken. All private companies.
Historically, regulation only come in if it helps some unique entity lobbying for it make money. Who benefits from this?
That’s ahistorical. Funny how supposedly regulation only benefits big business and incumbents, and yet those same big businesses simultaneously demand deregulation.
I think large businesses are pretty universal in advocating that regulation change (increase or reduction) in their favor.
In a previous (but different job from discussed here) I worked at a large company that had had a stringent regulatory body with a "Industry-Wide Standards Board." The board had representatives from companies, including the one I worked for. They would regularly create internal efforts to capture regulation.
Example: They internally added requirements to all of their products that all communications on all data busses must be encrypted with a best-practices encryption standard. It took about a year of development to complete, and as soon as they were done they went to the board and demanded this critical security infrastructure be a requirement for all devices seeking certification. It was approved, and every other company had to start work to comply with it. It basically created a technical floor that small companies could never hope to reach.
Agreed that almost all businesses try to co-opt regulations to their advantage. The person I was replying to said _all_ regulation only came into existence due to someone abusing the system to make money. That’s flat out bullshit. Good luck even trying to prove it’s a majority.
Other countries are still capable of building things much faster and cheaper than the US is.
It is quite insane that you are not allowed to compete with industry. That sounds like a good thing to campaign on these days "PREVENT INDUSTRY GOUGING"
It's one of the ways the US economy effectively “owns itself” and if you hold USD then it's unfortunately a good thing: https://www.archives.gov/milestone-documents/president-dwigh...
If Congress didn't write spares into the contract twenty years ago, then you don't have spares
Yep, and in most cases spares were part of the original contract but these systems have far exceed their original expected lifetime.
Aircraft: Deployed -> Orig. Retirement -> Current Retirement F-15: 1975 -> Early 2000s -> 2030s (C/D) / 2040s+ (E/EX) F/A-18: 1983 -> Early 2000s -> 2030 (Legacy) / 2040s (Super) F-22: 2005 -> 2030 -> Late 2030s-2040s C-5: 1970 -> Late 90s-Early 2000s -> 2045-2050 (C-5M) C-130: 1956 -> 1980s-90s -> 2030s (H) / 2050s+ (J) A-10: 1977 -> 1990s-2010s -> 2030+ (2033-37 proposed)
This sounds so wasteful.
That's because it is. The FAR is trash and should be thrown out and re-written, but congress isn't operational enough to do it and primes have plowed too many regulations into it to ever let them give it up.
In my experience, trying to get the government to adopt innovation feels cumbersome and "paperwork-first." I've brought disruptive tech to some FedCiv orgs and they would say things like "we don't have a line item for that in our budget." Luckily, things like OTAs signal an attempt on their part to make the process better. (I'd recommend the book Unit X by Raj M. Shah for a history behind the push to improve the acquisition process).
The real absolute killer is that when something that "works" should be upgraded, someone in the government needs to be the one to approve it.
Nobody, absolutely nobody, wants to be that person. Because if it doesn't go great, it's your dumbass that thought it would be a good idea to fuck up the thing that "worked fine".
And if it does work, good job, now get back to work.
are you referring to the the Federal Aeronautics Regulations aka 14 CFR?
Federal Acquisition Regulation: https://www.acquisition.gov/browse/index/far
When you're dealing with smaller quantities and high engineering costs, the math changes drastically.
Wasteful here is relative. Wasteful relative to what? Certainly not wasteful relative to upgrading all the existing hardware to take microsd cards
You mean F-22s aren’t iPods?
they didn't want to update the commissioning process to remove the partitioning step
Depending on regulations, updating the processes and associated documentation might have been more wasteful with regards to time to update, review and update the processes, time to get everyone retrained, risks of being out of compliance due to confusion, materials to print everything out, etc.
Yes, 100% agree. Another common problem we saw was that most major systems were owned by one specific contractor. Lockheed owns f-22, Boeing owns f-15, etc. Oftentimes there was some requirement to use the process as defined and delivered from the contractor. Want to update a document to remove step 7 from the data loading process? Welp, you'll need to get them on contract to update the document, verify it, regenerated documentation, train users to stop doing step 7, and reissue to the PO. That will only be $1.5M.
I'm not saying it's bad that these processes are in place, they make sense for systems this large, expensive, complicated and important. But there once was a time where government employees owned a bunch of this and when there was a problem they could just go fix it. That has been eroded, and prime contractor dependency has been enshrined in the way we purchase and maintain these systems with the sole intent of giving more money to those contractors.
Pure regulatory capture: https://en.wikipedia.org/wiki/Regulatory_capture
Airworthiness-adjacent regulations are deliberately hard and bureaucratic to change, specifically to prevent techbros from "moving fast and breaking things" with safety-critical stuff they know nothing about. This is considered a feature, not a bug. The powers that be would rather waste millions of dollars than let a cavalier change slip through and cause a fatal accident.
As a casualty of this, changing parts in any material way often requires a full design review of the change, and for large defence programs like the F-22 this process can be prohibitive.
surprised you haven't put 2 for redundancy
Some servers have devices like that, just 2 microSD cards in raid 1 used to boot hypervisor and do little else, so all hard drives can be used for storage without hosting OS
It's worth pointing out that there are actually two main types of PCMCIA memory cards. The most common by far are the ATA cards mentioned here, which are basically CF cards in a different form factor (equivalent to a CF card in a CF-to-PCMCIA adapter) and work by emulating either an IDE hard drive or an ISA IDE controller depending on wiring. While uncommon at this point, CF controller chips are still available and some specialized suppliers do manufacture these cards brand new using modern NAND flash.
The much more problematic ones to find a replacement for in 2026 are the so-called "linear" memory-mapped cards, consisting of one or more banks of raw parallel NOR flash with no controller IC. Linear cards were never standardized and the protocol used to interface to parallel flash can vary greatly across chip families, so the vast majority of devices that use them are hardcoded to only accept cards with a specific manufacturer and device ID. Many NOR flash manufacturers from the turn of the century have long discontinued their products and emulating parallel flash using modern FPGAs and microcontrollers is also non-trivial due to their memory-mapped nature, so owners of legacy telecom equipment and original Dance Dance Revolution arcade cabinets [1] are left with pretty much no viable replacement option once the stock cards fail.
[1] https://psx-spx.consoledev.net/konamisystem573/#flash-chips-...
Oh! I have one of these. Except it’s only 2MB and my Newton is currently using it.
When you get a chance, you should throw it in an F35 and see if it works!
I see no PCMCIA port in my F-35. And I’m fresh out of F-22s.
So your saying that Dance Dance Revolution and Fighter Jets might be competing for the same stock of legacy hardware?
For anyone wondering what these are used for:
All current US military aircraft (at least up through the F-35) use CF cards to take mission planning from the laptops in the SCIF (or whatever unclass space they are using) to the aircraft.
As an aside, LCACs (among other platforms) also use these systems and cards. So this is a pretty widespread use case.
I heard recently The F-16 updates are known as "tapes". So like "M6 tape brought this and that feature but there was a serious issue so had make a M6.2 tape". The source did not clarify if the fighters literally load software from tapes and I was too afraid to ask...
The F-16 also uses PCMCIA cards.
It's the right size for the job. It's small enough to be easily carried around, and big enough that it can be handled while wearing heavy gloves. They're big enough to have labels on them. The drive encloses and supports a PCMCIA card on five sides, and locks it into place, so it stays seated while fighter planes do fighter plane things.
PCMCIA cards were an excellent choice for military purposes. MicroSD cards are too tiny to handle with gloves or outdoors. In this application, you want a visible label on the device, since the card contains mission specific data and there are other similar cards around. USB drives supported only by their own connector are not well supported against G loads and vibration.
So they had a great solution. It just became obsolete because everybody wanted tiny laptops and phones.
I concur with this, and it's the same reason I've standardized around the Samsung external SSDs. Come to think of it, they're kind of a similar volume to PCMCIA cards, albeit not as long, and I have each of mine labeled. I also know, positively, where they all are, which I can't say about any of my microSD cards.
Make Data Big Again
F-16 OFP was, as I understand it, originally loaded from an actual magnetic tape. Not any more though.
A lot of computational models today still use "tapes" and "cards" terminology; they started from (or still are in) Fortran. Cards are files containing the parameters, and tapes are the bulk I/O.
You get errors like "Entry in Card 2A column 4 cannot be zero" and hopefully your front end GUI translates that into the field name.
Do you ever think if something under the hood is still using a tape when you issue a `tar` command? Same idea.
i wonder how many young nerd minds you just blew with that statement lol
"128MB of mission targets ought to be enough for anybody"
Bought a few CF cards from Dogfish SSD (https://dogfishssd.com/) sometime ago. They are readily available on Amazon and can be bought with relatively no fuss. The company are NOT based out of the US though.
The company that I do recommend for any industrial flash is Delkin Devices (https://www.delkindevices.com/). They are based out of San Diego, CA and I bought USB 3.0 high endurance drives from them and so far the performance of those have been solid, and it's lasted me many cycles. These are whom you'd be in contact with, for bids like these.
It's worth expanding the supply chain options locally. If anyone needs this they'd have to get Micron or Sandisk to make and assemble them into other form factors. This part is what is harder than it looks, and would need to be done.
Dogfish ? Will maybe sell to the USAF if they made them in a Dogfight fashion
It's got the shark, dog and fish marketing on it. Could work!
delkin?
are they typo-squatting belkin?
i'm of the mindset that i might sue.
As a bit of a fun aside, Industrial CF cards are a popular stand-in for hard disks in vintage computers (since in IDE mode they can be adapted passively to IDE - they're both parallel ATA but with different pinouts). Too bad they don't make hard drive noises, though.
>Too bad they don't make hard drive noises, though.
Funny thing, there were CF cards which were basically mini hard drives
Coincidentally, Microdrive was also the name for removable disks that were basically cassette tapes for Sinclair ZX Spectrum computers.
These seemed super niche, right up until they wound up in the iPod Mini en masse.
These seemed super niche, right up until they wound up in the iPod Mini en masse.
They were very popular with professional photographers before that.
As I recall, there was a period of time where pro photographers would purchase MP3 players that used the microdrives and strip the drive out because it was significantly cheaper than buying the photog marketed microdrive alone.
The 2004 iPod Photo (classic iPod with an upgraded color display) also had a "camera connector" designed to let you dump photos from a camera to its more spacious hard drive.
The 2004 iPod Photo (classic iPod with an upgraded color display) also had a "camera connector" designed to let you dump photos from a camera to its more spacious hard drive.
This still exists: https://www.apple.com/shop/product/mw653am/a/usb-c-to-sd-car...
I use it to back up the photos I shoot on my big camera to my iPhone while I'm traveling.
They have an adapter now that generates the hdd noise based on seek, I/O, etc. https://serdashop.com/products/hddclicker
I forgot how much an indicator hard drive noises were until just now, in those days where programs took 2 mins to either open or crash. Frozen ui but plenty of hdd noise indicating read write, probably a good sign it hasn’t actually crashed and you just need to sit tight.
True, but a frozen system with high disk activity could also indicate that the app had a memory leak and was simply dumping glitchy data into a growing scratch file/partition after it exhausted available ram.
I thought the lack of a whining motor was great. My ARM2 (Acorn Archimedes) computer is silent with a CompactFlash card.
Yeah, I assembled a retro PC with a CF card and I very much prefer the silent operation.
OTOH I love the loud "thwong" when the CRT powers up and degausses itself xD
You can make fake clicky noises with a speaker. https://serdashop.com/products/hddclicker
I remember using the flashing light on the tower as an indicator that something is still happening, even though the application looked hung up.
"[...] The PC or CF card must have a storage capacity of 256 megabytes (MB) or greater [...]" I'm guessing they have some system that bootstraps off of PC cards, or stores some small amount of low-bandwidth essential things. It's interesting that it's cheaper to req. a bunch of cards & adapters than it is to retrofit & modernize. Well, I suppose that's not that surprising, if I stop to think about it; from a systems integration point it's certainly way more reliable and less risky to replace a like part for a like part, rather than redesigning the hardware to use a more modern flash storage device.
You'd be _amazed_ at the red tape and expense required to modernize any part of a military aircraft maintenance system. You have to understand, when the US military orders a new plane, they don't buy only the plane. They buy the blueprints, parts manifest, pilot training curriculum, maintenance manuals, maintenance equipment, etc... literally just about everything except the manufacturing facility where they are built. Each aircraft is its own big program with tens of thousands of people employed by it at any given time. Changing even one small piece of it is a monumental undertaking.
Circa 2000, I worked in an avionics shop that serviced (among others) MH-53J helicopter navigation and autopilot systems. The test bench for this system was about 20-feet long end-to-end and was driven by a rack-mount IBM PC with an 8086 running MS-DOS. Storage was a 5MB (or so) pre-IDE hard drive with its own controller. These were... not reliable. And since we were a training base, getting new ones was just about impossible. When the drive died, much of the test bench was useless. I wanted so bad to swap out that drive with some kind of ISA->CompactFlash adapter, but _any_ unauthorized modifications to a test bench or procedure were strictly illegal, even if you knew what you're doing.
The AIR FORCE MATERIEL COMMAND seemed weird at first look. Material and Materiel are different words and not a misspelling. TIL.
Oh my Singaporean friend Alice told me I should contact them, she has a supplier but if she does the deal through my US company it'll be a lot easier!
Tell Alice I said hi!
Plaion[0] is manufacturing new PCMCIA storage cards, though the storage might be too small for their application. It would be hilarious to see Air Force equipment running on Neo•Geo memory cards.
0 - https://www.play-asia.com/el/neogeo-aes-memory-card-white/13...
China again is the gate to the bridge from 20th to 21st century. We don't have them because we never even tried to secure the supply chain beyond the bare minimum.
SanDisk makes them, I bought some a few years back.
I have a few in my retro junk pile. Except they say SunDisk, not SanDisk.
Why not use SD to CF converter adapters?
One extra layer, but the chips are commodity.
With glue, should be able to meet environmentals, shock and vibe etc
Hmmm, I have a drawer full of old PCMCIA CF adapters, I wonder if they can use them.
Aliexpress should be happy to sort them
"Old" I think you mean new...
I hear the FAA will have some spare floppies soon.
HN headline is wrong/misleading.
This is more of a survey to identify _potential_ suppliers of NEW CF/PC memory cards. It's not a request for bids, nor asking civilians to root around their junk drawers for cards to send off to the military.
Reading between the lines, they are likely evaluating multiple options for modernizing whatever F-22 system this is, and need to find out if going this route is even feasible.
Good catch. This is typically "market research" by the agencies and departments performing it. Many outcomes possible, such as a BPA, an IDIQ, a sole source supplier, etc.
I'd be looking at CF to SATA adapters and more modern SATA SSD discs (assuming form factor not an issue).
that is literally in the rfp
The capability of the plane is to fly and blow stuff up. Modernizing some internal component adds nothing to its capabilities and introduces more risk that something will go wrong, possibly even in flight. Therefore, they should stay with the standards that work.
Sorry, I am Not very good with headlines but Open to recommendations
In almost all cases, use the HN guidelines.
"Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize."
Are you sure? Don't want them to hesitate and miss blackfriday sales. You can bag 16GB CF for £20.
They'll probably want SanDisk extreme for a super sonic jet fighter though and that's pricier.
Try it, but if there is a single Chinese chip in there, and trust me they do check (they have partnerships with major US electronics companies that do the authentication), you will get your door kicked down, and you will do prison time. It doesn't even matter if you honestly didn't know.
Trust me part of my company works in this field of legacy government stuff, and the gov is well aware of the overwhelming temptation to pass off cheap Chinese clones. You absolutely will be nailed to the cross for it. I have seen it happen a few times.
Sourcing parts like this is enormously difficult, because you also need to know the supply chain. Sometimes you can even spin up runs of legacy chips to meet order criteria. We have a catalog and fab that will make us new old chips that are 20-30 years out of production, but the MOQ is pretty high.
All that being said, the gov will pay $12,500 for a 256MB card from 2002.
SanDisk is not a U.S. manufacturer. You would not put Chinese storage media into a F22.
> Sandisk Corporation (formerly SunDisk Corporation and SanDisk Corporation) is an American multinational computer semiconductor company based in Milpitas, California.
Or, you could halt the data center plague, causing the storage prices to plummet, and then buy normal modern storage at normal prices again. Because you have that power. You're literally part of the US government.
These are legacy systems using legacy storage that almost no one produces or sells anymore. It's completely unrelated to current memory/storage pricing or shortages.
choosing to believe that claude runs on a system that's heavily dependent on tens of trillions of 5.25" floppy disks and some poor tech that has to swap them when prompted.