Hacker Newsnew | past | comments | ask | show | jobs | submit | generuso's commentslogin

Indeed. Here is another page about the same thing: https://cwandt.com/products/pocket-fiche

"This project is a collaboration with Miles Segal (Gotham Silicon), whose mission is to make microchip fabrication more broadly accessible. Creating ultra high resolution micron-scale imagery is the very first step in this process."

"Those are clips of Miles in the Columbia University Nano-fabrication Facility where he is developing a workflow to make the technology required to build microchips more accessible."

Another mention of the same: https://x.com/JoinEdgeCity/status/1966180823129878656

"Miles Segal is building an ASIC foundry by repurposing vintage nano-fab gear to deliver custom chips in 24–48 hours."

"During the week he was at @EdgeEsmeralda, he focused on making new connections – leaving with new energy, confidence, and momentum from countless serendipitous convos."

So it seems to be one very young dude passionate about revolutionizing semiconductor processing. Whether there is an actual market for a super fast turnaround at 1 um node, and whether he has the experience and the support to pull this off, is somewhat dubious.

But of course wonderful things do sometimes happen. While he was a student, Sam Zeloof became a legend by building a chip fabrication lab in his garage, using surplus and home-made equipment. Now he has a serious team, working on developing mini-fabs: https://fab2.com/ That looks pretty serious.


>See the “3.1515…”? Each pixel in this 3×5 font is 750 nanometers x 750 nanometers. At the limits of visible light wavelengths.

No, I don't see 3.1515 ;)


Sounds great as a slogan, but there are no details. For comparison, Intel's 1 um process (Fab 3, 80386-era) required about 4 weeks of processing time, and if pushed, the samples could be processed in as little as two weeks. For a long time they were getting about one working die per 4" wafer.

Yes, only one day of processing is impossible for any kind of integrated circuit.

One day of processing would be possible only for semi-custom integrated circuits, like gate arrays, which have already been fabricated until a last step that only adds one or two custom metal layers to interconnect the existing components and then separates and packages the devices.

Even with that, one day of processing would be possible only for making a small number of chips, where the metal layers would be patterned without masks, by direct exposure of the photoresist with a laser projector. Making photolithography masks would take more than one day.


They could employ something similar to https://minimalfab.eu https://minimalfab.com https://www.yokogawa.com/industries/semiconductor/minimal-fa...

These are available since about a decade, and would enable such short turnaround times for single chips.


Short turnaround times does not mean a single day.

Even an ancient 1 micron CMOS process requires something like one hundred process steps, many of which may need up to a few hours in an oven. If completely automatized, it could be done in a week for small batches, but not in a day.

One day could be achieved only for semi-custom integrated circuits, where the customer only specifies the interconnection of the components existing on the pre-processed chip.

Decades ago, when unlike today, there were a very great number of integrated circuit producers, there were many who offered a set of IC dies from which to choose one, where each variant could have different sizes, while including various mixtures of digital gates and analog components like amplifiers, comparators, voltage references etc., and after choosing one of the available base dies the customer would specify only how to interconnect the components and how to bond the die to the package pads.

With such semi-custom integrated circuits, it would be possible to complete their fabrication process in a day, by using direct exposure, instead of masks, for the final metal layers.

At the 1 micron level, the photoresist can be patterned directly with a laser projector. There is no need for an electron-beam machine, like for nanometer-resolution lithography.


Yes, Yes. I know. Because of that I said 'something similar'. Yokogawa/Minimal.fab themselves say different things for different chips, up to one week, but also one day.

That depends on the used substrate, they don't only have the ones which are in common use. They also don't need masks for anything, and their wafers are small. It's all a little hard to get, and the most current information is their Japanese site, with translation.

Have you looked deeper at theirs, or 'similar' stuff? I think it's misleading trying to extrapolate from an ancient process to this, 'or similar', because the roads taken by the mainstream(machinery and processing) do not necessarily apply to other roads, which others may have taken. And I don't mean by circumventing physics. Just applying them differently. For different volumes and scales.


> They also don't need masks for anything

To skip the use of masks, there exists only 2 possibilities.

For low resolutions, down to around the 1 micrometer claimed in the linked site, it is possible to use a small and low cost laser projector, which is also quite fast.

For higher resolutions, an electron-beam machine is needed, which works in a vacuum chamber, and which is big, expensive and slow (the slowness is not actually due to the electron beam, but to the fact that a chip that must be made with high resolution lithography would have many more components in the same area than a chip that can be made with low resolution lithography).

An electron-machine would be bigger by itself than what Yokogawa shows as being a "Minimal Fab", so I assume that Yokogawa uses a laser projector.

I could not find any statement about which is their best achievable resolution, but they give an example of a circuit made with 4 micrometer gate length, so I assume that their best resolution might be around 1 micrometer, which is compatible with a laser projector.

Yokogawa gives their processing time at one week, for a fabrication process with 98 steps, which is very close to what I have estimated in another posting here.

Actually, I think that the company whose site is linked in this thread might have just bought some equipment from Yokogawa, as that could match their claims.

Nonetheless, a one-day processing remains compatible only with semi-custom chips, where the customer just interconnects the pre-existing components, not with a fully custom chip.

Moreover, the Yokogawa equipment uses tiny wafers, where the maximum die size is limited to about 8 by 8 millimeters, and at that size you would get 1 die per wafer, with great chances that it may be a bad one, or if you make small 2 by 2 mm dies, you get just 16 per wafer, from which a dozen might be good, and so on.

So you must need only a small number of dies, otherwise the fabrication could take forever. Nonetheless, even such a small number of dies could be good enough for prototypes or for the needs of small businesses or individuals.

I certainly would like to order such integrated circuits, but for this the vendor would have first to publish the technical documentation with the characterization of the semiconductor devices that can be made with their fabrication process, to enable the customer to do simulations of their designs, before submitting one for fabrication.

A one-micron resolution is intermediate between that used for the Intel 80386 processors and Intel 80486 processors, but closer to the latter.

So it would certainly be good enough to make various custom circuits, which could substitute the standard microcontrollers or FPGAs together with any needed auxiliary ICs, where MCUs and FPGAs typically must include at least an order of magnitude more internal resources than are used in any single project, in order to enable their use in any of those projects, so a dedicated chip can be made much simpler and more energy-efficient.


I would argue that the primary use for this type of prototyping is to test analog chip designs, because analog components don't scale down that well. Digital information only needs to distinguish between 0 and 1 but with analog electronics the maximum current or voltage you support grows as you use a bigger area or thicker layers.

I personally don't believe that even a $100 service delivering you 1 micron chips could compete against a $10 FPGA unless you are intentionally doing something the FPGA was not designed for like analog electronics or low static power.


I don't have the impression that a $10 FPGA can implement the equivalent of an 80386. I can believe it of a $1000 FPGA. I don't know what the right intermediate point would be. But big FPGA's are very expensive, mostly because the customers for such things are well funded.

I partially agree with you, in the sense that any useful custom integrated circuit must include some analog part, otherwise it would not be competitive with standard programmable logic.

Nonetheless, having actually worked as an analog IC designer, I can assure you that today, and especially when using a CMOS IC process, where the analog devices that are available, like MOSFETs, are inferior to the bipolar junction transistors and junction FETs, which were available in the fabrication processes traditionally used for analog ICs, it is completely impossible to make a competitive analog circuit that is purely analog.

Any CMOS analog circuit needs a digital part, even if it is something as simple as an amplifier, and more so for things like a power supply or a motor controller, or something that acquires data from analog sensors.

At the minimum, a digital automaton together with a lot of configuration switches is needed to perform the auto-calibration of the analog parts when the IC is powered on. Otherwise, things like differential amplifiers would be unbalanced, bias current sources and amplifier gains would have values very different from those needed for the circuits to work as designed, etc.

Digital parts may also implement in a simpler or more reliable way various kinds of control feedback loops and various protections to undesirable conditions, e.g. overcurrents, overvoltages etc.

So any useful custom CMOS circuit must be a mixed digital-analog design, i.e. it must include both a digital part, with flip-flops, digital gates and switches, and an analog part, with amplifiers, comparators, analog multiplexers, oscillators, voltage references, etc.

An one-micron CMOS process would be especially useful if its component list would include some NMOS transistors with a higher breakdown voltage, of at least 12 V, but preferably even of 20 V, or ideally of 25 V (to have a safety factor if using an 18 V power supply, as required by the gate drivers of some power MOSFETs).

An one-micron CMOS IC would likely use 3.3 V for the main power supply, and it should be able to use 5 V at least for I/O buffers. But if some transistors with a higher breakdown voltage would also be available, they could be used for open-drain output buffers that would be tied to an external higher voltage and they could be used to command directly some external power MOSFETs, without an intermediate gate driver. A standard 5 V I/O buffer could command directly an external GaN HEMT (gallium nitride switching transistor), but presumably the output current of the buffer would be low, so the switching of the external transistor would be slow in comparison with using an additional gate driver IC.


If Isar will get a large scale commitment from the government(s) to launch the OneWeb 2.0 constellation, as the European alternative to US, Chinese and Russian systems, they may well become a major launch provider. And of course they are already working on a much larger reusable rocket.

Although the original OneWeb satellites were assembled in the USA, they were developed in Europe and the components were always sourced predominantly from Europe, Canada, and Africa, with only some parts produced by the European companies in the USA, and even fewer parts sourced from the US companies. It is a very European satellite.


Incidentally, the early investment for Isar came from Bülent Altan, the Turkish ex-SpaceX guy who was in charge of the guidance system for Falcon-1, Falcon-9 and Dragon.

Very interesting, thanks.

It looks like he was an angel investor in Isar, and then co-founded a VC firm that continued to invest in Isar: https://alpinespace.vc/


Most of the US space launch startups have failed. And in Europe it is harder to even try.

There was a confluence of several factors which helped SpaceX to succeed, and not the least of these was the employee number one. For many years, Tom Mueller has been working in his free time on rather large liquid fuel amateur rockets, which he was building in his garage and which he was launching from some amateur rocketry facilities in the desert. In terms of regulation it was a relatively accessible hobby in the US. At the time Musk found him, he was working on the original "BFR" -- a very large liquid fuel amateur rocket. So the deal was to invest serious money into the project and scale the same no nonsense approach to a small orbital launch vehicle. They were in LA, the center of US aerospace manufacturing, so through Tom's professional connections and knowledge of who was who in the industry, they were able to source the necessary materials, components, and to find the key personnel for their company. Significantly, NASA has already spent probably a decade or more trying to get somebody to produce a cheap small launch vehicle. This did not directly affect SpaceX, but it did fund the R&D for example at Barber-Nichols, which enabled them to offer a turbopump for SpaceX engine at a much lower cost than it would have been possible otherwise.

At first, Musk and Co thought that they would be able to develop the rocket for a few million dollars. But even in the US regulatory environment it turned out that doing everything in compliance with regulations raised the costs to well over a hundred million dollars.

So, Tom's hobby + Musk's activism + industrial ecosystem in the area + NASA's prior support of component vendors + being at the right time to snag the International Space Station delivery contract were all important for SpaceX thriving where so many others have failed.


USA got the cream of the crop of the managers of the German missile program, while the USSR got the workers, who actually did the work with their hands and built the parts for the rockets. (One exception was Helmut Gröttrup, the head of the V-2’s guidance and telemetry systems.)

In fact, after the war the USSR has briefly reconstituted the manufacturing of V-2 in Germany, employing thousands of people, before transplanting this entire industry to the USSR. This dramatically lifted the level of Soviet manufacturing and relevant metallurgy.

von Braun's dissertation was on engine design and testing. But when he built the Redstone missile in the USA, he ordered the engine from a US company -- the engine which was already a generation ahead, compared to the imported German engines which the US engineers studied after the war.

Meanwhile, the Soviets have developed even better engines, completely on their own, though with the important parts built using the materials and the equipment brought from Germany.

So it is debatable whether having the German higher-ups and having a greater continuity with German design philosophy was a good thing or a liability.

It is less well known, but France have also imported a significant number of ex-Peenemunde engineers for their program. And their engines developed in a way different from both the American ones and the Soviet ones -- which definitively shows that although internalizing the German know-how was the starting point for everyone, it did not define the path of subsequent development.

Of course, the engines were not the whole story. The Germans took to the USA the advanced prototypes of the inertial guidance systems which were developed for the missiles that were supposed to come after the V-2. And the Soviets got Helmut Gröttrup. This did have its effects in both cases.


great comment, just wanted to add a little: all three countries were pioneering rocketry in the 20-30s, more or less in equal measure.

I don't know why this WW2 rocket discussion happened to begin with, but people here don't seem to understand that there is no magical inherent technical skill which is unique and irreplaceable. Experience helps to speed things up, sure, but it can be acquired by any program given time and resources, with no talent blockers.


> USA got the cream of the crop of the managers of the German missile program, while the USSR got the workers

That's a bit oversimplified. The Russians got quite a few important scientists and engineers in other areas (aircraft design, nuclear physics, electronics, radar, optics), they just didn't make as good use of them as the US (e.g. the 'American Germans' essentially won the space race for the US).


Talking about the role of V2 in the development of rocketry in various countries is more or less relevant to the discussion of Isar, because it was a major milestone, and it did influence all rocketry worldwide, in many different ways.

Rocketry may be much more talked about, but in terms of headcount is was a tiny thing compared to the number of German experts who were "invited" into all Allied countries after the war. Just France and UK had brought in about 3 thousand persons each. If one had said that this did not happen, that would have been an error. But simply not bringing this up at all because it is not very relevant to the discussion of Isar is fine, I think.

Debating who "won" the space race, and who "used" Germans "better" is not something that I want to do.


They do not like to talk about it too much in public these days, but Rocket Lab had somewhat shady beginnings. Once they moved past the semi-amateur phase, their first real project was weapons development on a DARPA contract. They were working on a paste-like semi-solid fuel for throttleable engines for munitions, and other similar things.

That pushed their main NZ investor away, and they somehow hooked up with the US intelligence community, which facilitated a rather unique series of inter-government arrangements for launching US reconnaissance satellites from NZ. That was probably always the appeal -- to launch over China with very little warning. A cheap, rapidly launchable vehicle was always a dream of the US agencies -- in 2003 this was FALCON program (Force Application and Launch from CONUS) run by DARPA and the Air Force, and today it is the Space Force's "Victus".

So, although the bulk of work was done in NZ, Rocket Lab functioned rather intimately with the US spooks from the very early on, including getting some funding from In-Q-Tel. Then in 2013, for the bulk of investment they just had to become a Delaware Corporation, for all the usual reasons. Very soon they moved engine manufacturing to a facility in California. More recently, with the large rocket (Neutron), their main manufacturing operations are in LA and the launch facility in Wallops. All in all, they are an international outfit.


It is uncontroversial among Dostoyevsky's scholars that his main focus is on Russian mysticism while the stories themselves are merely a setting for presenting author's theology. But that may be flying over the head of a typical Western reader. Even for Russian schoolchildren this requires to be carefully explained.

Dostoyevsky subtly advocates that Western rationalism, materialism, and utopian socialism lead to failure, and only spiritual communion of people bound together by love and Orthodox faith can give hope. This idea of specialness of "messianic Russian soul" and of Orthodoxy is extremely in vogue today in modern Russian ideology. But that is a different subject.


Marc Raibert was a student of Ivan Sutherland. Sutherland had a lot of pull at DARPA. This facilitated the unique prototyping work done at Boston Dynamics to get noticed and supported by DARPA.

But as a flip side of this, Boston Dynamics developed certain idiosyncratic interests in getting the hydraulic valves just right, etc. Their machines required a lot of tender care, (expensive!) and were dangerous to be around.

When Google acquired them, many things were mismatched. Andy Rubin, the VP at Google who advocated for BD, got fired for alleged sexual misconduct. This cast a shadow on the whole plan that he was trying to implement. DARPA finding did not sit well with Google's ethics. They pushed BD to stop getting grants from DARPA.

Expensive and dangerous robots were not an ideal fit for AI experimentation. Google was buying cheap and much safer tabletop robots for that. All in all, there was no good fit, and after spending tons of money on it, Google have gotten rid of them. They did encourage BD to develop a cheaper, safer electric robot, and this became Spot Mini.


It is not clear what "full duration static fire" means, but if the stage was fully fueled, the fuel tank would have contained 1000 tons of methane. The heat of combustion of methane is 55 MJ/kg. TNT equivalent is defined as 4.2 MJ/kg. In terms of heat output (not blast or other effects) this would have been equivalent to 13 kilotons of TNT.

The first atomic bomb had yield of 20 kt TNT, of which about half was in heat, and the rest in the blast and radiation.

Depending on how full the rocket tank actually was, the fireball from the rocket explosion was in the same ballpark, or possibly even larger in the size and duration of afterglow compared to that from the Trinity nuclear test.


> TNT equivalent is defined as 4.2 MJ/kg.

It isn't this simple for liquid oxygen and methane mixtures, and there's a great deal of disagreement between industry and regulators over what the right percentage of TNT equivalence is. Naturally, industry thinks the percentage is low, and regulators are skeptical, so there's a government-run test campaign going on as we speak to collect data for proper modeling.


The TNT is relevant, because the atomic bomb energy output was defined in terms of TNT equivalent. Not the energy of the blast, but the total output. For Trinity this was 20 kt, or 20*4.2 TJ.

This serves as a basis of comparison for this deflagration. If we are considering specifically the appearance of the late fireball, the heat output is the relevant figure of merit.

Assuming about 10-15% of the total bomb energy remained in the heat of the late fireball (with the rest spent on the blast wave, peak thermal radiation and neutron/gamma radiation), the fireball of this rocket deflagration could have exceeded the late fireball from the bomb. But this assumes the tanks were fully filled, which we do not know yet.


A test campaign that’s about to get a large amount of real world data.


The methane is not mixed with oxygen when it's still in the rocket tank, so it can't all explode - most of it will just burn off.

It's still a big boom, but not anywhere close to what world occur with optional mixing.


The side of the rocket failing appears to have allowed a lot of that mixing to occur after the initial fire.


Counting frames on YouTube, I get about 0.3s for the blast front to reach the top of the 600ft towers. That gives an estimate of around 600 tons TNT so definitely nowhere near all the fuel exploding.


how did you compute that?


Sedov-Taylor-Rayleigh blast equation, though this video isn't high enough frame rate to more than ballpark it I think. Tower is ~180m high, so 0.2 sec would be a bit over 1 kiloton instead? But definitely not remotely 13 kt. Still serious of course, when SpaceX suffered launch complex damage during some of its incidents it took a solid 6-12 months to fix.

Everyone can be glad though that no hypergolics are involved at least!


You are talking about the energy of the blast. In my comment I was talking about the heat output. From the followup comments it seems I have not made it sufficiently clear.

The energy of the detonation wave in rocket explosions is typically 1-2% of the energy in the fuel, at least that is the ballpark of what people use for estimating the effects of mishaps.

We also do not know if the tanks were fully filled -- it the past, rocket companies have called 10 second static fire tests a "full duration static fire test." We will probably find out later what it actually was meant to be.


About the couple of times you have said "fully filled", is that a specific industry or engineering slang or term?


Maybe it was a bit too colloquial. I am not sure if this is very important. A formal term would have been "full propellant load." The phrase "fill level" is also used in NASA documents.

The question was whether during this test the stage was loaded with the same amount of fuel as for an actual flight, or only a small fraction of that.


I think we do know that the rocket was fully fueled. This was like a WDR with a static fire.


> Everyone can be glad though that no hypergolics are involved at least!

Well, only a little bit - they do use hypergolic ignition.


The estimate is roughly E = rho*R^5/t^2 with rho the density of air: https://en.wikipedia.org/wiki/Taylor%E2%80%93von_Neumann%E2%...


> not clear what "full duration static fire" means

You fire the rocket as if it’s going to space, but you keep it on the pad. (From the engine’s perspective, it did a full launch.)


I think the point is that that phrasing has been used by rocket companies to mean a whole range of different amounts of fuel load, it's not very precise wording in practice.


From the industry: I would expect to hear "mission duty cycle" in that case. "Full duration" doesn't have a consistent meaning (a fact which is sometimes used to the marketing team's advantage).


Flight computer tells engine to go. Full go, launch sequence. Engine goes. To me, anything but that isn’t a full-duration anything.

If clamped down, it’s a full-duration static fire. If clamps release, it goes to space. Basically, if the engine can’t tell (apart from atmosphere, which is a big apart) it isn’t going to space, it’s a FDSF. It’s a whole-engine show. If you’re running parts through a full duty cycle, that can be done in a lab (or on a stand).


Sorry, no, I've worked on multiple launch vehicles and "full duration" doesn't mean anything consistent to anyone actually working on rockets.


The problem is that there is no standard meaning for the "full duration" in this context.

Some reports say that this means "running all seven BE-4 engines at full thrust for up to 38 seconds".

In flight the engines fire for 190 seconds.

So what the full duration means, and whether they fill the tanks with just enough fuel for the firing, or with a larger amount to help the clamps to hold the stage down, all this we will probably only find out from the investigation, if the results are ever published.


I think it's amazing they can basically hold a rocket down and let it launch like that without things exploding or shearing apart from the forces. Are those the same bolts as the exploding ones they would use for a normal launch?

(on that note it's also amazing that these exploding bolts are so reliable, I can imagine even a single one not releasing would cause... Issues)


Correction: The first stage of New Glenn carries only about 260 tons of methane. The 1150 tons is the full propellent load, liquid oxygen and liquid methane combined.

The heat from combustion of this amount would be about 3.4 kt, which is roughly the same as the heat in the late fireball of the Trinity test.

The mushroom cloud from the New Glenn explosion was also substantial: https://photos.app.goo.gl/a7uPVjsB5n453SJA7


the video is available, it's a large explosion, but nowhere near a trinity mushroom cloud


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: