Real Noah's Flood?
This blog looks at an article that proposes a scientific theory for a Noah flood event that matches our own scriptural timeline dating, perhaps the first I have ever seen. Before that, more notes on Solomon's introduction of a divine name. Then shop work notes and a headline review.
Divine Name
Over the past couple weeks Ryan and I have been looking at the problems of Solomon, and what Solomon did to the text. He was the first of eventually 6 editors.
Unlike the other future editors, Solomon cracked open the scribal layer of handling the manuscript, so creating what we know now as the Hebrew manuscript tradition. One of his changes was to change the divine name, creating the Yahweh term we currently see in Hebrew.
Now, imagine you are an inspired writer who is tasked with writing up this event. Your text has Joshua as the divine name for everything up through David. How will Solomon's actions be described in the inspired text?
Let me plot spoil this question by saying we get to a situation where there are more than 1 divine names running in the inspired text. The first name, Joshua, is going to be the name of the true god, who was there in the Garden of Eden, visited Abraham, called Moses and eventually shows up in New Testament times as a man who walked around with us.
The second name, Yahweh, is going to be used in the inspired text to describe Solomon's false god. We will also find there are a few other false gods referenced too, like Baal, but usually the other gods are without references to a specific name.
Then there are places like Jeremiah 23:27 which call out the change in divine name directly. False prophets are the people who caused the community to forget Joshua's actual name.
This problem of false god names continues on, all the way into the New Testament. The "Messiah" term, or in Greek "Christ," belongs in this same class of problems. These words also function like another false divine name.
This insight implies a technical problem that we have never noticed before. There are different divine names, but only 1 true divine name. The writers of the text actually do use several different divine names. They use both the 1 true name, and then the others as well. That Jeremiah 23:57 is a good example.
This is no longer a simple problem of word substitution. What the original terms might be in any given passage depend on what is being said in that passage. Is it speaking against Baal? That can be inspired. Is it asking Joshua if he is the Messiah? That, too, can be an inspired question.
This understanding will impact audit work here soon enough. But it has immediate impact on the TT and related apps. For those apps, at this point in our recovery work, Ryan must determine from context what the likely inspired divine name might be. He has begun that work, and it is showing up in our apps as of this week.
Changes
We have always ever assumed there was only 1 divine name. So the Yahweh term in the Hebrew, with generic parallels in the Aramaic and Greek, needs to be corrected back to Joshua. From the perspective of the audit work, we would want to know how to correctly spell the divine name, and then audit everywhere it is used to see if surrounding words pass sentence level audit.
But, the inspired writers were not actually limited to only 1 divine name. There is both the name of the true god, and then there are the names for the others. In Solomon's case he had a false god with a divine name and Solomon then replaced the true god's name as part of his editing pass. Solomon could do this because he was an editor operating at the level of a scribe.
Recall in the Sermon on the Mount we find Joshua giving commentary on Solomon by saying holy, or special, is the name of god. This was to indicate Solomon did not respect nor use the true divine name.
So recovery work, audit work, is more complex than we've ever considered. The audit has more than one case to check for, and Ryan's current TT work has the problem that we should be reading about how Yahweh took control as the publicly known divine name starting with Solomon. The religious system at Jerusalem, even to our day, is following a false god, and doing so under the name of a false god.
With the release of the scripture apps this week Ryan has put in the tooling to be able to handle more than 1 divine name in the TT and related apps like the 400 and Sabbath Reads.
He has carefully touched a few of these places to make sure the tooling is working. He has also done a quick general pass to fix other places, like Ananias replacing the name Joshua with false names like Messiah. This work is complex, and there will be more tuning of these names in weeks to come.
What I want to do here in this blog is show you some first examples of what this looks like so you can get a feel for what this does in the corrected text.
TT
I try and write these blogs so the links are resilient against changes to our apps. The TT and related apps are not fixed in terms of books and locations of stories, so giving direct links here in the blog is something I normally do not want to do.
Instead, the link here is to the TT app itself. The normal link to this app is found off of paleo.in. In order to follow along with this blog, use the Search function, found in the upper right menu. Then search for the term "Yahweh." (Without punctuation.)
Expect this list of Yahweh references to grow across the weeks to come. In the TT, though, the first references to Yahweh will be in Solomon's day because Solomon is introducing that false god into the family of Jacob.
As of this week, the 2nd paragraph that shows up in the search is the story of the letter that Solomon wrote to Hiram in order to arrange for the logs that Solomon used to build Solomon's temple. This is a passage originally from 1 Kings 5:3-6. The quote is "I purpose to build a house to the name of Yahweh, my god."
From the perspective of a normal reader of the TT, this passage now makes perfect sense. Joshua has been the divine name since the Garden of Eden.
Solomon is now telling Hiram that Solomon is building that temple to the false god Yahweh. In this letter, Solomon is now found outside of the tradition of his father David. Solomon is now following the Jebusite, or general Canaanite, god Yahweh.
Hiram responds in the next paragraph, and is pleased to help Solomon with logs because Solomon has now apparently accepted the Canaanite god Yahweh, which Hiram apparently shares.
Remember also that the 6 editors are identified in the text through the use of copies of letters. This is the letter for Solomon. The temple, for sacrifice, to the false god Yahweh, is Solomon's main villainous act.
480th Year, Solomon's Temple
To see how this functions across Solomon's day you can scan down through the other references to Yahweh that show up in the search results. The meaning of most of those references is now abundantly clear. Solomon has done something evil, and he has fundamentally left the religion that was firmly established by Moses after leaving Egypt.
You can see a quote originally from 1 Kings 6:1 where the Temple to Yahweh was started in the 480th year after leaving Egypt.
This is no longer a simple timeline reference to orient us in the history from Moses. It is now something like a tombstone marking the public death of the religion that Moses had established. That passage now indicates they had returned to Egypt. Presumably Egypt shared the same false god.
Note the math. The heirs of Jacob were in Egypt about the same amount of time as they were outside of Egypt in the promised land. They had been 430 years in Egypt as slaves. Then 40 years in the wilderness, free but not fully in the promised land. Then they had been 440 years in the land of Canaan not as slaves. Then they finally returned to slavery when Solomon started his temple. Those 430 years in Egypt is nearly the same as the 440 years in Canaan.
Queen of Sheba
If you keep scanning down the search results you will find the name Yahweh used in the account of when the Queen of Sheba comes to visit Solomon. This is originally from 1 Kings 10:1-13. She can now be seen as visiting the place that is dedicated to the religion of Yahweh. She may already share that same religion, having come to see what Solomon had built. She is of course overcome by what she sees. She was probably not changing religions as we normally understand.
The tone of this story is now very different than what we are used to. We as readers of the inspired story, are no longer a part of the wonder of the Queen of Sheba. Readers are now outsiders to the religious interactions between Solomon and the Queen of Sheba. Why? This building was not Joshua's temple. The Queen of Sheba's seduction is now a story about how this false system is so attractive to those who do not know Joshua. It is why we are not to build such grandiose buildings.
Jeroboam's Calf Idols
This change in divine name to Yahweh also makes clear the problems that Jeroboam faced after the death of Solomon. If you keep scanning down the search results you will see a reference to Yahweh that also includes Jeroboam. This passage is originally from 1 Kings 12:25-31.
The kingdom had split after the death of Solomon. Jeroboam had rebuilt Shechem as his capital. But the people were still going to Jerusalem to offer sacrifice to Yahweh at Solomon's temple.
Jeroboam was having trouble competing with Solomon's temple to Yahweh. A lot of money had been spent, it was a grand tourist destination.
This problem was Jeroboam's chance to recover public worship of Joshua. For whatever reason he did not do that. Instead, Jeroboam set up 2 calf idols, one in Beth El and the other in Dan. He calls these "your gods, who brought you out of Egypt." See 1 Kings 12:28-30.
Jeroboam could have returned to Joshua, but instead he creates these idols, calls them gods, and then explains how these were the gods who brought them out of Egypt. The slim chance of returning to Joshua was now lost, even in the northern kingdom.
In this Jeroboam story we also are seeing an example of yet more false gods. We are also setting up for future stories where each side of the now split kingdom is ruled by kings where neither side knows the true god Joshua.
Ezra's Letter
The link here is to Ezra's commissioning letter in the BRB. The cite is Ezra 7:11. This is the letter that identifies Ezra as yet another of the villainous editors. This letter has an introduction which explains that Ezra was a "...learned scribe in the commandments of Master..."
This passage in the BRB uses "Master" as the Divine Name in keeping with the Aramaic conventions of the BRB. Aramaic presumably went through an editing pass where all references to the divine name were abstracted to a generic, "master" in this case.
So what is the divine name that we would eventually expect to find instead of the Aramaic term for "master" as currently found in this passage?
You can think about this yourself. I would guess at this point that the inspired writer who brings us this passage would be telling us that Ezra was a learned scribe in the commandments of Yahweh. Ezra was a follower of Solomon's editing tradition. So Ezra's god is Yahweh, and the inspired writer would use that name.
So now Ezra can more easily be understood as against the things of the true god Joshua. Ezra really was a villain.
If you read through the entire commissioning letter you will see that the king himself, in well known Persian practice, followed the "god of the skies." This is yet another false god. But, and curiously, the king is allowing Ezra to set up and get running the house of Yahweh in Jerusalem.
As readers of the inspired text, neither of these gods is particularly important to us. We are watching the affairs of nations and their false gods at work in this passage. Everything Ezra would later do to set up the synagogue system will thus also be false. This transmits out to Acts 15 where the Synagogue system is lamented because it is where Solomon's version of Moses is read every Sabbath.
Acts 15
As a final link for this study, consider Act 15 in the BRB as linked here. Within that chapter is an important quote of Amos which discusses David's fallen tent. Amos and that Acts 15 passage also reference "Master" as the divine name.
What is the likely inspired name there?
I would think Joshua is the original Amos inspired divine name, and it should eventually pass audit as Joshua, both in Amos and in Acts 15.
Future Work
Ryan is starting to look ahead at this problem. Many of the stories involving the Jerusalem kings are going to involve a battle between gods. When a green voice prophet shows up, he is going to be representing Joshua. The kings of Jerusalem are going to be creating plot complications because they usually do not follow Joshua.
This split in the divine name is going to be providing literary purpose to otherwise obscure material from the time of the Kings. The story of the Jerusalem kings is not simply marking time across the better part of 500 years, but instead going to be showing the folly of following other gods, who are ultimately not gods at all.
Day at the Beach
Ryan and I took Wednesday this week and drove over to Ocean Shores. That resort town is on the Pacific Ocean with easy beach access. We parked and spent a day away from the normal routine. It generated a long lot set with many more insights into the problem of false gods. There was also a long discussion about the project. There is still months of work ahead, but so far Joshua seems happy with what is going on and is hinting at what comes after recovery.
When we were back to normal work on Thursday, there were headlines dealing with Trump's sudden decision to try and force a stop to the war in Ukraine. He is giving everyone, in Ukraine and across Europe, a week to agree.
The Europeans need time to rearm, which is why everything so far has been calls to a cease fire. This time, it looks like Trump is looking to lie to the Russians and call this an end to the war.
I have long thought this war should time more coincident with Noah related events in 2029, basically just after Trump leaves office early that year. If Trump pulls off this immediate Ukraine peace deal, he will effectively have set in motion the more likely prophetic timing for nuclear war.
I had already written what follows, but by Thursday, it was making more sense as to why these Noah related dates are going to become interesting a few years out. The Europeans, really the Zionist bankers that rule the west, will break the peace and begin another war with Russia. I would expect them to do so along the timing discussed below.
Sermon on the Mount
Last week's blog dealt with the Sermon on the Mount. There is an epilogue starting at Matthew 7:24 that uses the illustration of someone who builds his house on the rock. This rock would be the inspired text, carved in stone, at Shechem. Building a house this way means that when the rains come, and rivers overflow, and the winds blow, that house will still stand. The way the rains come and the river overflows are the marker that may match some other timeline story.
This is an illustration, but it may have a specific historical reference as to when the work of the editors is eventually overthrown. Overthrowing the work of the editors looks to happen coincident with historic rains and floods.
There are also many public evidences that the world is generally rejecting Israel in ways never seen before. Their brand damage over the genocide in Gaza is going to be hard to repair. They appear to even be doubling down rather than backing off that genocide. Israel, of course, are the modern heirs to the editors, so they are another possible marker for the end of the Sermon on the Mount. But, Israel is relatively dry. The Jordan river can flood, but normally does not. Most of the water of the Jordan is used domestically, which is why the dead sea is drying up.
There is also a timeline match to Noah that we are also watching on the charts. An actual, or at least symbolic, replay of Noah's flood may be what Joshua is referencing there at the end of the Sermon of the Mount. If so, Joshua may be dating specifically in history when the work of the editors is removed, without much detail as to the actual mechanism.
When I understood that reference to Noah in the Sermon on the Mount I wanted to follow up and review my current understanding of Noah. Let me do that here. There are several important topics I need to cover.
Noah's Flood Dating
Buried within the story of Noah's flood is a 7 day warning, given in divine voice. See Genesis 7:4. That warning is an actual historical reference, of 7 calendar days, but it is also a divine reference so flows through the rules of 2 Peter 3:8, where 1 day is as 1000 years.
To take Noah's flood as a prophetic warning, we can take the dates for Noah's flood as charted and then offset them by 7000 years. Let me hit the highlights here.
The math for this involves charting Noah. His flood was in his own 600th year, which was 6020 AA. So we can take the Noah's flood dates and run them forward from the charted dates by 7000 years to see when this might be in our day.
Genesis 7:4 puts the start of the flood at 600-02-17 of Noah, so 6020-02-17 AA when charted, but in our day 13020-02-17 AA (2029-02-22).
Genesis 7:4 says 40 days of rain wiped every creature from the earth, so the last day of those 40 was 6020-03-27 AA, but in our day would be 13020-03-27 AA (2029-04-03)
Genesis 8:3-4 indicates the ark rested 150 days later, so in our day 13020-07-17 AA (2029-07-17).
Genesis 8:5 indicates the mountains became visible on day 1 of month 10. So 6020-10-01 AA, but in our day 13020-10-01 AA (2029-10-04). At this point the raven and dove are sent out with various additional offsets.
Genesis 8:13 indicates the earth was becoming dry in Noah's 601st year at day 1 of month 1, so 6021-01-01. In our day 13021-01-01 AA (2030-01-02).
Genesis 8:14 indicates that Noah came out of the ark on the 2nd month, 27th day of that second year, so 6021-02-27 AA, or in our day 13021-02-27 AA (2030-02-27). Note curiously at this date the Gregorian Calendar is aligning with the same month and day numbers as on the AA calendar.
This marks the end of the flood series of dates and is slightly more than 1 year in total for the flood.
Noah's Flood Verification
There is a certain structure to the prophetic dates that I just laid out above. Note how we are using an ancient date and then leaping out into the far distant future.
This is very much unlike the normal date series we follow here in the blog. The dates from the 2000th anniversaries of Joshua's life have been running since 1998. We can verify them by looking at what has already happened. The early dates in the sequence did not expect serious headlines. But we can track down that they happened and that they followed the text. Confidence comes in the prophetic set of dates as they run out across time.
Unlike those Joshua anniversary dates, we generally don't like dates that start at some ancient date and then reach into our immediate future without a series of intermediate dates running ahead. Why?
Because that ancient date may be wrong. Then, even if it is correct, with a long distance, leaping, date structure we cannot know for sure if we are in those Noah dates until they actually start happening in the news. They are not helpful in any way in terms of preparing.
What if there is a math error? Or what if we are looking at an edited story that is otherwise not inspired? Or worse, an editor changed the timing?
Predictive dates with this leaping structure have been regularly proposed by various people across history. These are almost always wrong.
Every 2 years, since the late 1700s, on average, with written documentation, someone in the USA has predicted the end of the world within the next 5 or so years. This history is why we hate such dates.
The Noah dates given above are useful only after "it" starts because they indicate that "it" will take just over a year to finish, AND it will finish on Gregorian dates that match the historical text. So the tail end of this story is still useful for purposes of holding on until that storm is over. But the storm must begin on the expected date for this to hold.
But, we cannot place much confidence in these dates BEFORE they start flowing in headline news.
Until then, we can only look around for suggestive or predictive headlines that might agree with these 2029 and 2030 series of Noah dates as being at least interesting to keep following.
The current war in Ukraine is perhaps the best venue for building up to a Noah Flood like story. So we could generally say we have storm clouds brewing in Ukraine heading towards a 2029/2030 storm.
Should Trump get the Ukraine war to stop now, then we are setting up for a restart just after Trump leaves office in early 2029. Peace in Ukraine may hold only by the force of Trump's personality. Should a weak, or female president follow Trump in 2029, then it may be a war that cannot be stopped. A female president after Trump, say Harris, then we also would match the Branham prophetic words from about 100 years before.
Other Noah's Flood Replays
Noah's flood is not unknown to the timeline. Noah's Flood replays in headline news every time we rerun the main timeline.
Noah's flood was seen in replay form during the first Persian Gulf War. The USA lead a group of nations who pushed Iraq out of Kuwait. It was a fight over oil fields and oil rights.
Noah's flood was seen as the US Civil war, on a series I don't normally discuss publicly, but in any case the US Civil War was also a Noah's Flood replay.
On the series we are following now, with the 2000th anniversary of Joshua's life, Noah's flood replayed with the Saudi lead war against Yemen. Curiously Yemen has become famous for sinking ships aligned with Israel. A very nice Noah like touch.
So Noah's Flood prophetic replays always show up as wars. These are not natural events. This is why I have strong conviction that the original Noah's Flood was not a natural event either. It was the result of war of some type. Noah himself may not have been on either side of that war. In any case he was told how to escape the flood.
In the past few weeks, Russia has tested a few new weapons systems that strangely match features of Noah. Let me review some of that here.
Daniel Davis Deep Dive
The link here is to a Youtube video where Daniel Davis interviews Ted Postol. Postol is a retired professor who is an expert in nuclear weapons. They discuss 2 new nuclear weapons that Russia has recently revealed to the public.
The first is a nuclear powered cruise missile that also carries a nuclear weapon. It can loiter in the sky for a mostly unlimited amount of time. There is no defense against it. It uses the heat of a small nuclear reactor to heat air. That heating causes expansion and expanding air pushes through the blades of a rotating jet turbine providing propulsion.
In watching Noah related headlines from the first Persian Gulf War, Noah's sending out of the raven and dove seemed to replay with the raven being war planes carrying weapons and the dove being passenger planes carrying peace missions.
This new Russian weapon looks like a raven by that definition. It may have some raven like use. Think about the dates I've given above if you want to think about when this might get used.
The other new Russian weapon is a nuclear powered torpedo carrying a large nuclear bomb. This weapon is discussed in the latter half of the video linked above. Postal shows the expected blast zone if that torpedo is used against various American harbors, including Pearl Harbor in Hawaii and others along the US east coast. The warhead is so large it will ignite the entire land mass of the large island of Hawaii, even with an underwater detonation.
This weapon is another possible cause for the flooding component of Noah's flood once we reach 2029 and 2030. It is a doomsday weapon.
John Helmer with Nima
The link here is to an interview this week where John Helmer was on with Nima Alkhorshid. Helmer is based in Moscow and one of the best in terms of tracking the war. They range in topics, but eventually discuss how Europe needs to suspend the war in Ukraine in order to return in a few years. This so Europe can be better armed. The west cannot defeat Russia now, and will try again in the future.
After this video was recorded, Trump started talking about his new peace plan for Ukraine. Watch for it to become a cease fire to give the west, really the Zionist bankers, time to rearm. Any sort of partial peace pushes the war with Russia into that 2029/2030 prophetic window for the replay of Noah.
Dating Historical Noah
Part of building confidence in the 2029 dates given above comes from watching for when and how Noah has replayed in other times. I gave some of those above.
The other way to build confidence in understanding Noah is to understand the historical event of Noah's Flood itself. A big anniversary of Noah is special in that it is NOT part of a longer rerun of the entire timeline. So an anniversary related replay, say the 7000th anniversary in this case, may more closely match the original Noah's Flood event.
There is very little historical evidence as to what happened in the original Noah's Flood event. All we have to go by is the story in Genesis. But, when this replays the headlines are always way more complex.
A few weeks ago there was a link from a post on X that went to a long and interesting article that lays out a scientific theory for the historical Noah's Flood event.
I chased it down and read it. This new theory for Noah is impressive enough, and detailed enough, that it may also bear on our understanding events of 2029 and 2030. As you read what follows, ask yourself, could widespread use of very large nuclear weapons trigger an actual replay of the original, historical, Noah's Flood?
ECDO Hypothesis
The link here is to an article on The Ethical Skeptic website. The article is dated in May of 2024. It is a very long and very technical scientific article that explores a theory about a possible, historical, Noah's flood event.
Using the same calendar as I used above to date Noah's flood, this article dates a theoretical Noah's flood sometime between ~5000 AA and ~6600 AA. Stated slightly differently, that article is dating the flood at 5800 AA +/- 800 years. That article is only off by ~200 years from the real value given in scripture. (Of course they don't know how to read scripture to get the scriptural date.)
I have never seen a theoretical model for a Noah event that was so precisely on the actual date for Noah. Let me summarize the key points because it is rather remarkable the extensive evidence used to support that dating for Noah.
Not Ice Age Ending Floods
This is NOT the major ice age ending melt events of around 13,000 years ago. Yes, there were great floods at that time too. They happened at the end of the mile thick ice shelf over Canada. This article is exploring a very different event. This ECDO hypothesis is not changing the known dates for the Missoula floods. This is providing new dates for a new event that happened in history that was the likely cause for Noah's Flood.
The ECDO Hypothesis is ultimately providing a precise dating for what is normally called a pole shift. They use the notation Np to mark the current location of the North Pole. They use Np' to mark the other location of the North Pole. During this Noah event the pole moved between 2 different locations, upsetting the earth's oceans.
That Np' location is estimated at 104 degrees south along the 31st meridian. Think 14 degrees south of the current equator. That Meridian is a line from the current North Pole down through the geographic center of the earth in northern Turkey and also through the Giza Plateau in Egypt. The location of Np' is down in southern Africa.
Informally, when someone starts discussing a possible pole shift there is a usual assumption that this is a mostly magnetic event where the current north and south poles simply exchange places. This is wrong.
New Core Data
The article goes deep into new research into the inner core of the earth. Parts of the core cause rotation and magnetic north where we see it now. Other parts of the core want the north pole at that other location in Africa.
These 2 locations are discovered and understood through recent mapping of the interior of the earth's core. There are various illustrations in the article that show off the structure of the core itself. The surprise from these radar survey's of earth's core is that it is irregular. It is not even layers of material. Different materials want the pole to be at different places.
(Note, these pole shifts are also likely caused by mantle shifts within the core that are beyond what I am reporting here in the blog. Read that article for more.)
The shift between those 2 locations happens suddenly, and violently, triggering sloshing in the oceans. The pole shift itself moves in a straight line between these locations. This is what caused the event known in the text as Noah's Flood.
Human Evidence
The article then goes on to look for evidence from ancient human buildings that would support the idea of Np' being in Africa. There are hundreds of examples around the world that have ancient buildings that were set with a presumed Np' in Africa.
Just like we do now, ancient buildings were set with sides parallel to the equator, which was not at the current location before Noah.
Rotation Points
It then goes on and explains that during a shift, there are 2 points of rotation which essentially do not change. One is in the Amazon river valley, the other is in Indonesia. During the pole shift the earth is rotating around another axis that comes out at these locations.
These locations would not see serious inundations because the oceans are sloshing around these 2 points. Biodiversity studies are cited which suggest these 2 locations were not wiped out by flooding during the pole shift. More damage from flooding would be seen across the rest of the earth during such a shift.
Giza
There is a section in the article dealing with the great pyramid in Giza. The 104 degree angle between Np and Np' is seen in the design of that building, which itself is on that meridian line between Np and Np'. Note that Np and Np' are calculated from surveys of the earth's core, not by studying Giza.
The article speculates that the biggest pyramid structure was built there, with certain features, to mark or memorialize Noah's Flood. It may have also contained tooling for tracking planetary stability.
Final Thoughts
The article linked above does not go into the cause of the flood, at least not to the level of human agency as the cause.
Replays of Noah's Flood always involve wars. They are events caused by human agency. So the original Noah's Flood event is also likely to be ultimately caused by human agency. Perhaps it was as bad as a major war, or even a war between Earth and Mars which caused the original flood.
The earth is like a spinning top, suspended in space with little to hold it in place. Could the use of weapons like what Putin has recently shown, cause the North Pole of earth to jump between Np and Np'?
The damage would be far worse than just the localized damage from the bombs themselves. The maps given in that article suggest the generally safer places to be located should such a pole shift happen again. Pray it not be that bad.
Shop Work
This week the 3rd Voron was debugged and moved off the bench to its normal position in the shop, still pending calibration.
I am way behind in 3d design work, and only have a few parts that are ready to print. Those printer ready parts have been waiting for the new Elegoo printer to get setup. So with the Voron done, I turned my attention to getting that new printer running.
Once the bench was clear the new Elegoo printer was unboxed and assembled. This printer was added to the farm to allow single prints for large format letters used on the lid of the Table exhibit. It will also be used for single prints for many parts of the full sized Sower, Reaper, Silo and Well exhibits.
This printer is cheap in price, with generally poor reviews. But the bed size was just big enough to warrant trying to get this thing working. It is a physically big printer, as would be expected for a 420x420 mm bed.
Because bench space is limited in the shop I needed to get this printer setup so it could sit on top of one of the Vorons already setup in the shop. This meant designing and printing various feet to allow an Ikea Lack table top to set firmly on the Voron and then more feet to replace the regular Elegoo feet. These specially designed feet sit off the corners of the Lack table top and lock the entire stack of printers together. All of that special design work went well with various parts 3d printed on the existing Prusas.
Then there was printer setup and first print. Ryan helped me with this since it is a big and heavy printer. We were able to get it running without trouble. A small pre-sliced sample print that came with the printer ran successfully. Next step was to get some of the real exhibit parts running on this new printer.
Printables.com had the configuration files needed for Prusa Slicer, and setting up the slicer was easy. The printer also connected easily to the cat5 network in the shop. It runs Klipper software like the Vorons, but uses the "Fluidd" web interface rather than "Mainsail" as on the Voron. So that interface was new in terms of details, but no great surprise. It also just worked.
Watch for pics on Telegram, the punctuation and Wa letter came through with only a few problems. Each type of 3d printer tends to have a personality, about like pet cats. It takes a few sample prints to learn the what the issues might be.
The bed size of 420mm is something of a tease. The heated part of the bed is more like 400mm and the difference means the plastic does not stick well to the bed around the edges. It is now winter heating and the shop is cooler than summer, so this problem is exaggerated by the season. The parts planned for this printer will usually be pushing right up to the edge, so this is an important issue to understand and work around.
The fix appears to be "heat soaking" the bed, without actually running parts, for maybe an hour before first print. The controller on the printer lets this happen. Neither the Prusa printers, nor the Vorons, have this cold edge problem. The Prusas, if they were run with the heat on yet not printing, would trigger a safety timeout. The Vorons normally do a 5 minute heat soak at the start of every print. The Vorons have much more powerful AC bed heaters that fit the whole bed and do not have cold edges either.
The next problem was seen when I moved on to the second full sized letter, the Sa. During this print there was a bed shift. This is where the Y belt skips and the print head misaligns with the part, ruining the print.
I'd seen this problem on a Youtube review, so this wasn't unexpected. The Y belt was suddenly very loose and it was trying to print off the top of the bed. This seems to be a shakedown problem which can be fixed through retightening of the Y belt. There is a handy knob on the front for that. The Youtuber seemed to suggest it was a one time, shake down, problem. We'll see.
But, more importantly, this means this printer cannot be left alone when running in the shop. Somebody needs to be in ear shot to listen for trouble. Like a new pet cat exploring the house getting caught behind furniture. This printer needs someone listening for strange noises. It will take awhile before it can be trusted to run around alone.
In any case, so far, this printer still looks promising. It does produce nice big flat parts when everything is running OK.
Headline Review
Hebrew Hate Speech
The link here is to a post on X dealing with how X has had to stop automatic translation of Hebrew into English because of the amount of hate speech found in typical Hebrew language posts. Strange world. Not sure if we should be mad at X for covering truth, or mad at Hebrew speakers for being so barbaric.
MD-11 Crash Update
The link here is to a Blancolirio video on Youtube dealing with the preliminary NTSB report on the recent MD-11 crash. That crash was on a prophetic echo of 911, so is interesting for our timeline studies.
The prophetic stories would want this to be caused by human agency, not by simple or natural accident.
In that video you can see still photos from airport security cameras that captured the moment when the left engine mount failed. The engine itself ripped lose, and flew up and over the top of the plane where it was eventually found in the right side of the runway.
Not mentioned in the report, this path of the engine may have let debris into the center engine, causing a stall there.
This was an identical failure to an earlier DC-10 crash. In the earlier crash it was mechanics in Tulsa who figured out a way to save time, but which cracked a key part in the wing attach point. This time, the same part failed again. Probably this time it was metal fatigue not caught during regular inspection.
So this was probably not malicious, but still should not have happened. Strange how history repeats.
Peace Deal?
The link here is to a Zero Hedge article dealing with Trump's proposed peace deal over Ukraine. Probably another week before we know for sure how this will work out. Just talk? Most in Ukraine and Europe have rejected it. We'll see.
Yen Carry Trade
No link. Hal Turner carried an article dealing with possible unwinding of the Yen Carry trade. His articles go behind a paywall. Related articles on Zero Hedge are also behind a paywall.
For perhaps decades, traders have borrowed money in Japan at zero percent interest and used that borrowed money to buy assets in the USA, often stocks. Any asset earning more than 0 interest can be purchased this way. This is Japan as the vassal of the USA being used to prop up assets within the USA itself.
Recent interest rate changes in Japan appear to be ending that trade. The risk is that traders unwind those trades to pay back rising interest loans in Japan. Should that happen, many assets in the USA would be expected to drop in value. This may already be happening in the USA, with Hal offering a $2T drop in value on the S/P 500 on Thursday as an example.
More Later,
Phil