Mastodawn

The Broken Mesh: Why the Fight Between Meshtastic and MeshCore Matters

2,734 words, 14 minutes read time.

The fracture between the Meshtastic and MeshCore projects is a warning that you cannot ignore. For years, people thought a simple, off-grid data net was the answer for when the main lines go down. But now, the community is divided. This is not just a small fight over code. It is a total disagreement on how to handle communication when things get ugly. If you think you are ready just because you bought a cheap radio board and did not bother to learn how the software actually works, you are just a hobbyist playing with toys. The rift between Meshtastic and MeshCore shows how fragile these systems are and why you need to know your gear inside and out. A mesh net is only as good as its weakest link. If you do not master the tech, you are just a dead node in a silent town. We are seeing the growing pains of a decentralized technology that is outstripping the discipline of its users. You must choose your tools based on the reality of the physics, not the popularity of the app. Demand that your firmware be an efficient tool for data transmission, not a bloated social media platform for the 915 MHz band. If you do not take the time to understand the modulation, the packet structure, and the routing logic of the software you flash onto your hardware, you are just a child playing with a walkie-talkie while the grown-ups are trying to build a grid. Mastery of the radio spectrum is not an option; it is a requirement for anyone who claims to be prepared. This split is the first real test of whether civilian mesh can survive the chaos of its own success. You either learn to navigate the airwaves or you signal your own failure. Every packet you send without understanding the cost is a round wasted in a firefight. Stop treating your emergency comms like a smartphone app and start treating it like the life-support system it is. This technical mastery is the difference between a working link and a radio that does nothing but drain your battery in the dark.

Troubleshooting LoRa Mesh Protocol Inefficiency and Network Congestion

The fight between Meshtastic and MeshCore comes down to how they use the radio waves and the small chips that run them. Meshtastic has been the big name for a long time. It uses a flooding method where every radio repeats every message it hears. In the woods, that is fine. In a city with a hundred users, it is a train wreck. The air gets crowded, messages hit each other, and the whole system jams itself. MeshCore did not start because people wanted a new app. It started because the old way is inefficient. The core of the split is about the overhead—the extra data that hitches a ride on every message. Meshtastic adds a lot of features, but those features take up space. MeshCore wants to strip everything down to the bone so the network stays stable. When you have very little room to send data, every extra bit is a mistake. This is a battle between lots of features and it just has to work. If your software is fighting your hardware, you lose. The divergence between Meshtastic and MeshCore is rooted in the physics of the 900 MHz ISM band and the limitations of the ESP32 and nRF52 chipsets. As the node count grows, the airwaves become a chaotic mess of collisions and retransmissions, effectively jamming the very frequency the operators are trying to utilize. While Meshtastic has focused on a feature-rich user experience with a heavy reliance on a specific structure, MeshCore proponents argue for a leaner, more modular approach that prioritizes the stability of the underlying mesh over the bells and whistles of the interface. When you are operating on a low-bandwidth, high-latency medium like LoRa, every byte of overhead is a liability. You either master the protocol or you become a dead node. The math does not lie even if the marketing does. If your network protocol consumes more than ten percent of your bandwidth for heartbeats, your network is dying. Every extra feature in the code is another potential point of failure when the signal gets weak. You have to decide if you want a chat app or a survival tool. The flooding algorithm used by Meshtastic is a blunt instrument that was never meant for high-density urban deployment. It works by simply re-broadcasting every unique packet received until a hop limit is reached. In a sparse environment, this ensures the message gets through by any means necessary. But as the number of nodes increases, the probability of two nodes transmitting at the same time goes up. This leads to packet collisions where neither message is readable. MeshCore attempts to solve this by moving toward a more structured routing system. This means the software tries to figure out the best path for a message instead of just yelling it to everyone. This shift requires a level of technical discipline that many casual users find frustrating. It means the network is less plug-and-play and more of a precision tool. If you want a network that survives a real crisis, you have to move away from the chaos of flooding. You have to understand how the Media Access Control layer handles traffic. You have to know how to set your timing parameters so you are not stepping on your own neighbors. The split is a clear line in the sand between those who want ease of use and those who want engineering reliability. You cannot hide from the physics of the airwaves. Either your packets move or they die in the dirt. Stop assuming the software will fix your bad placement. Fix the engineering or get off the air.

Physics of LoRa Packet Collisions and Signal to Noise Ratio Analysis

To understand this split, you have to look at how these radios actually talk. They use a low-power system called LoRa. It is built for long range, but it is slow. There are strict rules on how long you can broadcast before you have to shut up and let others speak. Because Meshtastic repeats everything, adding more people makes the problem worse fast. This is not a glitch. It is physics. MeshCore was built to change how messages find their path through the net. Instead of everyone yelling at once, it wants a smarter way to move data that does not waste airtime. The split happened because one group likes the safety of repeating everything, while the other wants a clean, quiet network. If your radio is spending eighty percent of its power just saying I am here, you are not communicating—you are just making noise. The split proves that the current path is heading for a crash where no one can get a message through. LoRa is designed for long-range, low-power communication, but it is inherently limited by the Duty Cycle regulations of the FCC Part 15 and similar international bodies. Meshtastic’s current implementation of the flooding protocol means that as you add more users, the probability of packet storms increases exponentially. MeshCore was conceptualized to address the need for a more rigid, perhaps even more disciplined, routing logic that could potentially mitigate the hidden node problem and reduce the airtime usage per packet. The technical fallout between the two development paths stems from a disagreement on how to manage the limited airtime of the ISM band. One camp believes in the resilience of redundant flooding, while the other seeks a more surgical, routed approach to data delivery. This is a matter of Spectral Efficiency. If your mesh is using the majority of its available airtime just to say it exists, you have failed as an operator and an engineer. You are polluting the spectrum with digital noise. This noise prevents emergency traffic from getting through. It creates a false sense of security where people think they have a working link when they actually have a jammed one. You must look at the duty cycle of your own node. If you are transmitting more than one percent of the time in the 900 MHz band, you are likely part of the problem. MeshCore is an attempt to force the network into a more responsible state. It prioritizes the survival of the link over the convenience of the user. This is a hard truth that many do not want to hear. Physics does not care about your feelings or your user interface. It only cares about the signal-to-noise ratio. If your signal is lost in the noise of your own network, you have built nothing but a very expensive paperweight. Every packet sent is a risk. In a real-world scenario, a long transmission can be used to find your location. Flooding makes this risk much higher because your message is repeated over and over by every node in the area. A routed system like what MeshCore aims for reduces this risk by limiting the number of times a message is sent. This is not just about efficiency; it is about security. You have to understand that the airwaves are a shared resource. If you treat them like your own personal garbage dump, you will find yourself alone and unheard when the time comes to actually send a call for help. The split between Meshtastic and MeshCore is a debate over the very future of private, off-grid data. One side wants to make it accessible to everyone, while the other wants to make it work when nothing else does. You have to decide which side of that line you stand on. If you are not monitoring your packet loss and your noise floor, you are not an operator. You are just a passenger in a system that is bound to fail. Stop looking at the colorful screens and start looking at the spectrum. The truth is in the waterfall, not the icons. The physics of 915 MHz demand respect that a plug and play mindset cannot provide.

Off-Grid Communication Solutions and Technical Radio Discipline

The result of this fight is a mess where gear running one software will not talk to gear running the other. For you, that means your radio is a brick if your neighbor is on the other side of the fence. This is how a mesh net dies. A mesh needs everyone to speak the same language. When the builders split, the network breaks. This should wake up anyone who thinks they can just download a file and be safe. The hard truth is that we are seeing a new tech grow too fast for the people using it. You have to pick your tools based on facts, not what looks cool. Demand software that moves data fast and clean. If you do not know how your radio sends a packet or why some settings work better than others, you have no business relying on this in a pinch. The split between Meshtastic and MeshCore is a reminder that in the world of radio, there are no shortcuts. For the operator in the field, this means your gear might be useless if the person three blocks away is running a different branch of the protocol. This is the death of a mesh. A mesh requires a common language, a shared set of timing parameters, and a unified understanding of frequency hopping and spreading factors. When the developers split, the network breaks. This should serve as a wake-up call to anyone who thinks they can outsource their emergency communications to a GitHub repository they do not understand. The split between Meshtastic and MeshCore is a reminder that in the world of RF, there are no shortcuts. If you cannot explain the difference between a Spreading Factor of seven and twelve, or why a 125kHz bandwidth is preferable over 250kHz in a high-noise environment, you have no business relying on these tools. The hard truth is that we are witnessing the growing pains of a decentralized technology that is outstripping the discipline of its users. You must take personal responsibility for your station. This means testing your range with real-world obstacles. It means understanding how your antenna height and gain affect your local mesh. It means being able to re-flash your firmware in the dark while the rain is pouring down. If you cannot do these things, you are not prepared. You are just a collector of electronic gadgets. The discipline of the amateur radio spirit must be applied to these new digital modes. We are losing the technical edge that made the license worth having in the first place. The split is a chance to reset. It is a chance to move away from the appliance operator mindset and back toward the engineering mindset. You should be auditing your own mesh. Look at the traffic logs. See how many packets are being dropped. See how many of your traffic is just node discovery overhead. If you find that your network is inefficient, do not wait for a developer to fix it. Change your settings. Educate your neighbors. If the split leads to a better, more efficient protocol, then it was worth the friction. But if it just leads to two broken networks instead of one, then we have all lost. The practical application of this knowledge is simple: test everything. Do not assume your mesh will work because the light on the board is green. Prove it. Send data over the longest possible path. Monitor the battery drain. Watch the spectrum on an analyzer if you have one. If you do not have the tools to verify your network, you do not have a network. You have a hope. And hope is not a plan for communication. Secure your nodes, harden your protocol, and stop relying on software you have never bothered to read. The day is coming when the only thing between you and the void is the connection you built yourself. Don’t let it be a connection built on laziness. Clean up your messy node or accept that you will be silent when it matters.

Conclusion: The Future of Decentralized Mesh Networks and User Mastery

The discipline of the old-school radio operator has to be applied here or the whole thing will fail. The split between Meshtastic and MeshCore is a call to stop being a lazy user and start being a real operator. We do not have time for good enough when the grid is down. Check your gear, learn the rules of the airwaves, and be ready for a future where the channels are full and the software is broken. Build your setup expecting things to break. There is no room for being soft. Learn the math, understand your range, and make sure every message you send is worth the airtime. The grid is weak, the airwaves are crowded, and your own lack of knowledge is the only thing truly blocking your signal. Fix your gear, learn the system, and stop waiting for someone else to save you. The grid is fragile, the spectrum is finite, and your ignorance is the only thing standing between you and a total blackout. Fix your station, fix your protocol, and stop waiting for someone else to secure your link. The time for playing games with digital toys is over. Mastery is the only way forward. Master the code, master the RF, or stay off the air. This hobby demands engineers, not appliance operators. Be the asset the network needs, not the QRM that kills it. Finalize your build, test the link, and maintain the discipline required to keep the airwaves open for those who truly need them.

Call to Action

Join the Network and Master Your Comms Before the Grid Goes Dark. The split between Meshtastic and MeshCore is a wake-up call for every operator. You cannot afford to be a passive user when the lines of communication are at stake. Whether you choose the feature-rich path or the lean efficiency of the core, the responsibility for a working link lies with you. Don’t wait for a crisis to realize your nodes are misconfigured or your protocol is inefficient. Start auditing your setup today by getting out in the field to find your real-world limits, diving into the spreading factors to clear the noise, and educating your local mesh to ensure your neighborhood stays connected. The airwaves belong to those who master them. Secure your hardware, flash your firmware, and become a reliable node in the decentralized future. Join the conversation, build the grid, and stay off the silent list.

SUPPORTSUBSCRIBECONTACT ME

D. Bryan King

Sources

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Bryan King Apr 29

The Cloud-Burner: How to Master NVIS for Reliable Local Comms

1,593 words, 8 minutes read time.

If you have just earned your Technician or General class license, you have probably already realized that the radio world is full of “dead zones.” You might be able to talk to a guy in Italy using a massive tower, or a guy across town using a local repeater, but what about the people two counties over? Often, that sixty to two-hundred-mile range is a “skip zone” where your signal just flies right over their heads. This is where Near-Vertical Incidence Skywave, or NVIS, comes in. Think of it as taking your radio signal and pointing it straight up at the sky, using the atmosphere like a giant mirror to bounce that energy right back down into your local region. It is the ultimate tool for keeping your community connected when the internet goes out or the repeaters fail. It doesn’t require a hundred-foot tower or a thousand-dollar antenna; it requires a little bit of wire, a low branch, and the willingness to learn how the air above your head actually works.

Understanding the Ionospheric Mirror

To get a handle on NVIS, you have to understand that the ionosphere isn’t just empty space; it’s a layer of the atmosphere filled with particles that have been “charged up” by the sun. We call this ionization. During the day, the sun is hitting these layers hard, making them thick and reflective. At night, they thin out. For NVIS to work, we need to pick a frequency that is low enough to be reflected back down rather than passing through into space. This is governed by something called the Critical Frequency, or $f_c$. If you try to send a signal straight up at a frequency higher than $f_c$, it’s gone forever. For new hams, the rule of thumb is simple: use the 40-meter band (7 MHz) during the bright part of the day, and move down to the 80-meter band (3.5 MHz) or 160-meter band (1.8 MHz) as the sun goes down.

The goal here is to keep your “angle of incidence” near ninety degrees. Imagine standing in a room with a flashlight and a mirror on the ceiling. If you shine the light at a sharp angle toward the wall, the light bounces off and hits the far corner of the room—that is your standard long-distance “DX” skip. But if you shine that flashlight straight up at the ceiling, the light bounces right back down onto your head. That is NVIS. By “burning the clouds” with your signal, you create a solid umbrella of coverage that fills in all those local gaps. The math behind this is surprisingly straightforward. The Maximum Usable Frequency (MUF) for your local area is roughly equal to that Critical Frequency because the “Secant” of your ninety-degree angle is essentially one:

$$MUF = f_c \cdot \sec(0^\circ) = f_c \cdot 1$$

When you stay below that $f_c$ limit, you ensure your signal doesn’t punch through the atmosphere and disappear. Instead, you get a reliable, high-strength signal that blankets your entire region, regardless of hills, buildings, or trees that might block a standard line-of-sight signal.

The Low-Hanging Wire: Your NVIS Antenna

The most common mistake new hams make with NVIS is trying to get their antenna too high. We are taught that height is king, but in the NVIS world, the ground is actually your friend. To push your signal straight up, you want a horizontal dipole antenna mounted very low—usually only 10 to 15 feet off the ground. When the antenna is this low, the radio waves that hit the ground reflect back up and join with the waves going toward the sky. This creates a massive “lobe” of energy pointing at the zenith. If you put that same antenna 50 feet in the air, the energy starts to focus toward the horizon, which is great for talking to Japan, but terrible for talking to the next town over.

When you build a low antenna, the “impedance” of the wire changes. Impedance, represented by the letter $Z$, is basically how much the antenna resists the flow of electricity from your radio. A standard dipole in free space is about 72 ohms, but when you bring it close to the dirt, that number drops. You might see your SWR (Standing Wave Ratio) jump around because the ground is “soaking up” some of that energy or reflecting it back into the wire. The formula for this total resistance looks like this:

$$Z = R_{rad} + R_{loss}$$

Your goal is to keep $R_{rad}$ (the energy actually leaving the antenna) high and $R_{loss}$ (the energy turning into heat in the dirt) low. You can help this by laying a “reflector wire” on the ground directly underneath your antenna. This acts like a mirror on the floor, bouncing even more energy up toward the sky and away from the dirt. It is a simple, cheap way to make a basic wire antenna perform like a professional military setup. It is about working smarter with the space you have, using the foundation of the earth to amplify your reach.

Operating with Discipline and Purpose

NVIS isn’t just about the gear; it’s about the man behind the mic. Because you are using lower frequencies like 40 and 80 meters, you are going to encounter a lot of noise. These bands are where lightning crashes and electronic interference from house appliances live. To be successful, you have to develop a “radio ear.” You learn to listen through the static for your brothers. You also have to be ready to change bands. If you’re talking on 40 meters and the signals start to fade as the sun sets, don’t just keep cranking the power. That is a waste of electricity and hard on your gear. Instead, understand that the ionosphere is changing. Be the leader who says, “The sun is going down, the critical frequency is dropping—let’s move the net to 80 meters.”

This kind of communication is a responsibility. In an emergency, NVIS is often the only thing that works when the cell towers are down and the repeaters have no power. As a new ham, mastering this technique means you are becoming a valuable asset to your family and your community. You aren’t just playing with a hobby; you are learning the physics of the atmosphere so you can provide a lifeline when it matters most. It takes patience to learn the cycles of the sun and the quirks of your local soil, but that discipline is what separates a true operator from someone who just bought a radio.

Take pride in the “bench time.” Build your own dipoles, experiment with different heights, and don’t be afraid to fail. Every time you tune an antenna or successfully make a contact two towns over during a storm, you are gaining technical mastery. You are learning to provide for those around you by using your mind and your hands. Keep your station clean, keep your character grounded, and remember that the strength of the airwaves comes from the discipline of the men who use them. Whether you are a Technician just starting out or a General looking to expand your skills, NVIS is the gateway to a whole new level of radio capability.

Looking Ahead: The Power of Local Links

The future of radio isn’t just in satellites or high-speed digital networks; it’s in the resilient, local links that we build ourselves. As you grow in this craft, you’ll find that NVIS is a bridge. It connects people across distances that are too far to see but too close for standard skip. It is a testament to the order of the world—that even the very air above us is designed in a way that allows us to reach out to one another. By mastering the “Cloud-Burner” technique, you are stepping into a long tradition of operators who value self-reliance and technical skill.

Continue to study the $SFI$ (Solar Flux Index) and watch how the bands open and close. Treat your fellow hams with respect and kindness, and always be willing to help the next new guy who is trying to figure out why his signal isn’t getting out. We are a community built on shared knowledge and a commitment to the craft. Stand tall, keep your wires taught, and we will see you on the air.

Call to Action

If this story caught your attention, don’t just scroll past. Join the community—men sharing skills, stories, and experiences. Subscribe for more posts like this, drop a comment about your projects or lessons learned, or reach out and tell me what you’re building or experimenting with. Let’s grow together.

SUPPORTSUBSCRIBECONTACT ME

D. Bryan King

Sources