Did MESHTASTIC Die At Hamvention??
Вставка
- Опубліковано 5 лют 2025
- What happened with the MESHTASTIC devices at Hamvention? Let me explain! Don't worry! This is not a bug! We can make this work even better!!
LoRa Chirp explanation video • LoRa CHIRP
📻 Want the best HT antenna? Signal Stuff Signal Stick signalstuff.co... (This is an affliate link)
📻 Looking for the best deal on the Ed Fong J-Pole? www.kbcubed.co...
📻 The Coax I use is ABR Industries (10% off with code: "abr10hrcc"): abrind.com/?sld=6
📻 I use Ham Radio Deluxe: www.hamradiode...
📻 You can find some of my favorite radios and gear at GigaParts: www.gigaparts....
📻 Good Value HTs: HTs: www.buytwowayr...
📻Check out Radioddity ham radio radios and get a discount: Xiegu G90: radioddity.refr...
📻 Support Ham Radio Crash Course Content 📻
Patreon - / hoshnasi (includes monthly newsletter, stickers and Patron perks)
📸UA-cam - / hamradiocrashcourse (includes early access to videos, membership YT badge and custom emojis)
Shop HamTactical: www.hamtactical...
Shop Our Affiliates: hamradiocrashco...
Shop Our Amazon Store: www.amazon.com...
As an Amazon Associate I earn from qualifying purchases.
★ FOLLOW ME HERE ★
🪩 Website………………………► hamradiocrashco...
📸 UA-cam..................► / hamradiocrashcourse
💻 Twitch......................► / hamradiocrashcourse
Podcast………………………► hamradiocrashc...
💻 Discord………………….► / discord
📸 Facebook................► goo.gl/cv5rEQ
📸 Twitter.....................► X.com/Hoshnasi
📸 Instagram................► / hamradiocrashcourse
📨 Physical Mail...........►Josh Nass P.O Box 5101 Cerritos, CA 90703-5101
Music by Sonic D:
Soundcloud.com/sncd
sncd
Facebook.com/djsonicd
#HRCC #hamradio #amateurradio - Наука та технологія
Very honoured to be referenced in one of your videos. Thank you.
We have extremely dense meshes in areas of the UK now and have seen the same issues. Hopefully the techniques in this video will make it to the nerds over here 👍
"Packet" is the right term. The "CHIRP" is still a packet similar to tcp ip. CHIRP's (used in LoRa and other applications) involves transmitting data via chirp waveforms, which are organized into packets. [At least that's my story and I'm sticking to it 😅] Nice video, Thanks!!
Yep. Any protocol with a fixed or variable length data record is sending "packets".
Aww, Chirps
Josh, I always enjoy that when you explain something, you give relevant technical details, go enough into the weeds to satisfy the hard core nerds and yet still break it down to the "green crayon is green" level for people like me.
This happened in the UK a few months back as well. This is great real world testing and will be interesting to see how these tips help prevent it in the future.
Another technique in a busy area especially with lots of small nodes with stubby antennas stuck in a pocket would be for those nodes to be put in client_mute mode. That way they can still send and receive, but wont be repeating traffic. Nodes will ask for a few clients it thinks are far away to repeat its packets. So, if it hears a node weakly, it might ask for that node to echo the information to extend the original nodes range. This is extra traffic and most of the weaker nodes wont really be extending much of anything.
Good video and its good to see Meshtastic starting to take off!
Packet is a correct term; it is used by Semtech in the datasheets for the transceiver chips, such as the SX1276, etc.
Love how you're trying to dumb it down. A broadcast storm is effectively what took the network down. Mesh, is a topology by the way. The packet has framing bits, and the number to which you referred to as CRC is a check sum value and yes it is how Asynchronous transmissions are certain the packet was delivered undamaged as well as responseless protocols like TCP/IP otherwise there'd be netnoise of each node asking and confirming TxRx. Hopefully the developers put a hop map feature into the process. That's how TDRF works to add bandwidth that wasn't there back when Switched 56 and baud rates were thought to be as fast and as much bandwidth as possible. Funny how turning to spectrum over just 2 dimensions opened up the door to huge data rates.
MQTT can be very useful and isn't necessarily a problem to the mesh. The problem arises because it is a fairly complex system and not well understood. New users that try MQTT using the default settings on the default channel will cause congestion, but using MQTT on a private channel with a custom MQTT topic (or through a private MQTT broker) is really not a problem. The thing is, unless you know what this all means and also have a known use case for MQTT, you are certainly better off leaving it alone.
I have found it very useful for remote telemetry over Meshtastic, and it works well with my configuration and does not cause channel congestion.
I'm thinking about this use case to push data into home assistant mqtt would make a great interface for the automation pipelines.
Is there a place to see a list of topics that are used?
Problem is... we're not familiar on how to "properly" set "private" channels up. RTFM is no help.
@@wesleyjones6535 There is an app called MQTT Explorer that (sometimes) works. It's available for Windows. A key point is that the users create the topics. Entering a topic in your MQTT setup will create it on the broker if it isn't already there.
@@dustoff499 Setting up a private channel is pretty basic to Meshtastic. Just create a new channel in an available slot and give it a name that isn't "LongFast." Connect that channel to MQTT (but don't connect the default connect LongFast channel) and you won't cause too much trouble.
This is very much a first world problem. And yes, the Meshtastic developers have done INCREDIBLE work. Josh, TY for reaching-out to them and reporting the proper config and ultimate solution. Is Meshtastic dead? No, we just hit the same speedbumps that partyline phones, Tokenrings and other technologies have hit. Meshtastic's real strength still lies as a backup secure communications when our radios or alternative messaging networks are not available. Great work, TY.
Exactly.
@HamRadioCrashCourse Hey can you do a video series like you did for tech license for the crash course? It really helped.
I put up my first Solar charging Rak 4630 device using Meshtastic OS. I picked up a 283 mile device, Which has since dropped off. I also picked up a 19 mile device. So it is working. not alot of activity local so it is something I will need to monitor for sure! Attempted an install on the garage roof but the light poles were too large... need to get larger hose clamps for it. Had rain and it is still working... charging as well... been on for 20 hrs and still at a 95% charge! So very happy with the performance. Also got a T-Deck and using it to test with as well. Always great to learn about things that are new! Now to connect with Jason here in TX and see if we can expand our influence. ;)
I have done the same thing. The 4630 will never bring my battery higher than 95%. I have the same results. Works perfectly though.
CLIENT (MUTE) is highly underutilized this stops the node from rebroadcasting data, in a dense area leave the retransmission of data to the nodes with the most advantageous positions. I have my elevated nodes as Routers, the nodes on my vehicle roofs as repeaters and my pocket nodes as Client (Mute), my vehicle doesn’t need to show on the node list since I’ll be near enough with my pocket node.
I would leave the vehicle nodes as client role since your car might not always be in an advantageous position, so it can re-transmit on-demand with the same priority as regular clients.
I need to learn more about Mesh. I do a lot of volunteer work where cell phones have no coverage. Some folks are bulky about radios. FRS, enough said and GMRS has cost and licensing issues. Mesh might be great but IP68 or higher is a must. Excellent video and 73, KF0NNQ & WRVR260.
One slight detail, unlike many other mesh protocols Meshtastic does not need to build the mesh up, it does not currently track who is in the mesh or where packets should be flowing.
The mesh is implemented by using very clever CSMA/CA hacking, every-time a node hear a message it tries to rely it, but before doing so it waits the amount it waits is based on how well the message was received, if the reception was good it waits a very long time, if it were bad it waits a short time, and if while waiting it hear someone else relaying the packet is cancel it's own relay attempt, this mean just by waiting and listening you know if someone else farther away is relaying the message already, and if they are you do not yourself, if the wait time expire and you didn't heard anyone then you relay yourself.
The congestion is usually NodeInfo (automated « I am here » messages used to show the list of Nodes in the app, but completely optional and not used in the meshing) and people trying to use the app as designed and send messages.
Haven't gone down the meshtastic rabbit hole yet. That being said, our club is talking about it, so will probably go there soon.
Thank you Josh!(for spending more of my money LOL) 🙂
I was experiencing issues similar that I actually paid for on my cellphone a decade ago and attributed it to system congestion then too. That bumping the head on ceiling quip toward the end was awesome btw.
MQTT doesn't link Meshtastic to the Internet. Its a very lightweight publish/subscribe data passing protocol, typically used in IoT applicarions where your sensors publish their data payloads to an MQTT broker app, and then other apps subscribe to that and get the data.
Using MQTT, you can pass messgages between disparate non-TCP/IP digital networks.
It's recommended MQTT be disabled on cogested Meshtastic networks as it introduces addtional network overhead. meshtastic's bandwith is very low and any additional traffic can affect performance.
CHIRP is the sound of the modulation. Regardless of what anyone calls it, packet is the correct term for the chunk of data transmitted as a unit (using CHIRP modulation).
While not a "bug" in mestastic, the exhibited failure to scale is definitely a design limitation inherent in the choice of flood routing. There are smarter mesh network routing approaches that could be implemented and IIRC meshtastic is working on such. Flood routing is quick and easy to understand and implement, but it always fails this way and has since at least the days of even the limited flooding done by Netware SPX/IPX and NetBEUI in the 1980s and 1990s.
The mesh at hamvention was crazy. Someone definitely had default mqtt server turned on the default channel. I was seeing nodes show up on the map from across the country. I also had mqtt on as well but I was using a club owned mqtt server so people back home could see everything that was happening.
1980's coax based Ethernet had a similar issue. Yes it was a timing issue. they had to back off on how often they talked.
It is a learning curve, It will get better.
The solution with Ethernet was to develop a whole system of switches and routers, so that each device only communicated with the closest other devices. Which by the way meant scrapping EVERYTHING, from the AUIs to the local coaxial network cable. That is, the entire physical layer. That's what it will take to "fix" Meshtastic: replacing it with something akin to a cellular network. So yeah, this will mean that you depend on an infrastructure that will have to be built up from scratch. Which, MAYBE people will plunk down some money to build their own cells, but eventually this will break down into chaos and spotty coverage, and will only work if one or more commercial networks get built.
Also can layer meshes on top of eachother or simply increase the speed at the cost of range for conventions which gives way more throughput by like 300x
@@land_and_air1250 You are right, and that is one thought - routers. Apex nodes or devices that link mesh groups together . Doing it without human intervention is not quite straight forward. We want resiliency in case a router fails or is cut off.
Routers can also introduce loops. A message can take more than one path - without "one way gates" the message can be forwarded back toward the sender and then corrected and routed to the receiver only to loop around back to the sender.
Local comms under a higher "Tree like" router.
@@jimthompson3053 A good system is Reticulum, it is platform agnostic AND can use meshtastic devices. A Meshtastic-Reticulum bridge would be cool. Reticulim is trying to be a low-speed ad-hoc internet.
Josh,
Thank you for your awesome videos on Meshtastic. Due to your videos, I now have my new device sitting here, waiting on me to get off of my behind to print a new case.
I live in seattle north urban part called ballard. The node cluster that i am in crashes my node in about three hours. Take the same rig out in the sticks works for days without a glich, and can throw long balls for miles and miles. not enough nodes and it does little. more nodes past a certain number and your done for. What i have noticed it seems the angle of the nodes to one another might be the posion. thanks for your advise.
This is the same problem we had in the early days of networking
And the early days of Wifi.
This is why they created 100 base-T and 1000 base-T
Because the old 10 base-T really got overwhelmed and we were not getting through from computer to computer on the network.
Back then it worked just like this.
There was no router
It sounds like the system needs network controllers.
So if a control station assigned the priority and who is on the network and when to send.
Like cell phone cells work
Am I interested in getting my license has come from Communications with satellites and wirsing in the Walking something the world require and I haven't not necessarily but the problem is I can't have even a device that transmits whether or not I will ever hit the transmit button or not.... So even if I'm going to use the device only for receive only I'm not permitted to import it.
That one with the screen makes me think I of the Cybiko devices of the early 2000s.
Just remember, if you change to Short/Fast and not everyone else does, you'll be on different frequencies and won't see anything. EVERYONE needs to be on the same primary channel.
This is exactly the opposite; it's an unfortunate thing that the channel name defaults to the modem preset used, but they're _not_ related. You can talk to users in the default channel (named LongFast) using whatever modem preset you want, from ShortFast to MediumSlow.
Sorry, you said 3 tips, including 1 from the community. Did I miss a third one? Turn off MQTT, switch to Short/Medium Range, and what was the third?
lol I took two takes at saying that. Should have been “two tips” I finished editing this at 1:00am 😅
@@HamRadioCrashCourse haha, no worries. I'm only on coffee #2 for the day so I thought maybe I was missing it. Watched the video twice looking for that third tip. :D
Ah damn, sorry about that!
There was 70+ nodes at EDC Las Vegas back in May. The only thing my group of 20 had to do once channel saturation was over 50% was simply change LORA slots from 20 to 60. Left things on Long Fast and things work flawlessly after that. Anyone seeing channel saturation should check one of the other slots. See what the floor looks like. Then coordinate a change with your group and make it. Admin channel works great for this!
MQTT stands for Message Queuing Telemetry Transport, and it's a lightweight messaging protocol that's used to connect devices and applications over the internet.
Someone else said it, but Josh, I think you're messing up your terminology on #2. The channels have to do only with encryption keys. It is the radio mode, and you can use only one radio mode (Lora modem preset) whether Long_fast, Short_fast, etc. And you can only talk to other radios (people) on same mode. But thanks for making the video to help us use it better.
I showed the radio mode on the screen, but yes, set the model to Medium or Short and you should be good. 👍
LONG-FAST is a modem preset, not a per-channel setting.
Unfortunately it's also the default (primary) channel name. Not very well thought out.
I believe my wife is buying me my first heltec v3 for fathers day. Hoping the mesh is somewhat active in Charleston sc
Be the mesh you want to see. 🙂
new firmware fixed this issue. v2.4 or higher and v3.0 is due to have compression
This IS a limitation of Meshtastic, since it has no mechanism for automatically reducing the bandwidth used by each node. Back when "mobile phones", the precursor to cellular phones was a thing, there was a problem: if the prices came down and mobile phones became popular, they would quickly saturate the bands allotted to them. The invention of cellular radio was a response to this, and required that transmissions be limited to short range, and also an infrastructure of "cells", or areas that each fixed station covered. Adjacent cells use different channels, so that a phone talking to its nearest tower does not interfere with other nearby cells. Meshtastic learned nothing from this, and has NO mechanism to keep saturation from happening, and so will be the victim of its own popularity. The more popular it gets, the worse the user experience. And the bigger problem with that is, it will run into the limits WAY before it gets to the point where you can reach anybody you want to communicate with. So it will go from "i can only message 1% of my contacts" straight to "I can't get through to ANYbody."
Please: prove me wrong.
So, I was thinking that the "chirp" was one character or symbol and that a packet was made up of multiple chirps. I am interest to understand that better. What did you read to learn this information?
Why would you ever use the long if you can send the massage with the short? It sounds like someone driving a dump truck to the store when a car will get the same loaf of bread. I'm sure the is a reason. What am I missing?
Fantastic analogy!
Long fast gives more range than short fast so is good for testing and discoverability under normal conditions. Short fast is better for events though
Is that the Lilygo w/ 3D printed case? If so do you have a link to the stl for the case?
My learning adventure continues. If one LoRa-enabled device is connected to the internet, then a hand-picked group of other LoRa-enabled devices could all communicate as a network, by basically using that first device and its internet connection as a hub? And it could be any of them, or multiple, so long as at least one was connected?
Kinda, but the internet is just bridging nodes. It’s not as helpful as you might think. It shares the messages though.
I have a mesh network operating in my community. It works great. We are building a county wide network and hope to have it operating soon. KS4QF
I amateur code lora modules. And built a mesh system for solar sensors. Trying to automatically set the spreading factor(long fast) is difficult. Because all surrounding nodes have to change to the same SF. This takes band width to tell other devices to move to new SF. Or it takes time for a device to listen to each SF until it heats and syncs with another node on the same SF. SF7 takes 2 seconds to complete an 16 byte packet. So even with the best collision avoidance. Only 30 devices could communicate every minute. I am no radio engineer. But lora modules need to be able to switch it's SF automatically based on the preamble of the other device. And the reply packet should automatically drop to a faster SF based on the signal SNR level. Basically an automated power and speed strategy built into the models.
However the regulatory body not being very software to find radios allows the sale of The Analog Devices very capable SDR which is the basis of several strs in a single antenna head that's connected to a another piece of equipment or something designing and building which requires me to have access to some equipment that I can't get.
Turn MQTT off in dense mesh areas. Here in Manchester Uk - it’s a dense area with 100+ active nodes. Just one node can break the bandwidth. If using TinyGS mqtt makes sense! But in a localised comms it’s doesn’t do any favours!
Turn mqtt off and set ignore mqtt. Hops keep to 3 maybe 4 if there are routers in the area…
But the over 1k at burning man had no issue?
The feedback I gave the dev team lead to their being no issue for Burning Man. You’re welcome. 🤣
Meshtastic simple doesn't scale. It's not just airtime, but also the entire MQTT link concept and the fact that your node can "fill up" with node IDs, leading to the dreaded memory full message.
Man I dont know anything about meshtastic or HAM, but just with a borderline understanding of making your own network off grid, these are eventual pitfalls that the pioneers of the internet were trying to figure out some 40 years ago
Fortunately there are a bunch of speed settings and frequencies you can pick between which allow you to layer many different networks on top of eachother without interference just like cellular radios do it
@@land_and_air1250doesn’t Meshtastic work on one specific frequency?
@@JJRfromNYC it works in a frequency band, and has a bunch of usable channels within the band and on top of that each encoding speed and spread factor will be ignored by every other encoding speed and spread factor allowing the same frequency channel to be used 8 times or so if needed without meaningful interference
@@land_and_air1250 thanks. How does one determine the appropriate encoding speed and spread factor? Thinking of investing in Meshtastic. I think it could be great for off the grid Comms.
Hi Josh, noob here, this is regarding an AWESOME older video how to program with CHIRP. My problem is I have quite an older version of win, much older than 10, so could not do it. Tried on my chomeOS laptop as well, would not work. Do you have a program for CHIRP for older than win10 computers? I love your complete easy step by step directions! Thank you!
Is there any way we can connect a Motorola T900 to this for textin?? Please say there is a way
If you're crafty you could swap the internals.
That would be an awesome challenge to re-use the case, screen and keyboard, but swap the internals.
So why is there no talk about a 'self-organizing' node structure where the most powereful meshtastic devices in an area become like a super node hub: They figure out a way to divide spread the load out across multiple super node hubs, so that each smaller device gets a fraction of the traffic. Once the super nodes go down, the meshtastic devices are then re assimulated into the other super nodes. It would have to be automatic based upon signal strength.
Join the Meshtastic Discord and spread your idea around. This is a community driven software package.
Isn't part of the appeal making contacts with others? If you change from long fast although you're utilizing the available bandwidth better, there will be less folks to chat with. I would definitely turn on ignore mqtt on the node so that even if someone mistakenly turns it on your node wont add those to the DB.
Seems like the 2 main problems with Meshtastic are either: Get a node and encounter terrain problems / there's no one I can talk to, OR there's an over-saturation problem. I went from the former to the latter in the span of 3 months. Now I see endless spam on the public channel in my area (mostly new user test messages), and wish I could get back to the few original users back in April 2024.
I believe you can if you change frequency with a small group.
It would be nice if we could just use the widely available Amazon mesh network of Ring devices.
Could someone educate me? I'd like to communicate with people over the Internet (via Meshtastic's MQTT service) so basically I am NOT to use Channel 0 for this purpose because enabling MQTT would cause all of those "Internet nodes" to pile into Channel 0 and annoy all of the people on Channel 0? If so, do I create my own channel with MQTT enabled and all of those "Internet nodes" will only be visible and accessible to me? Or..is there specialized channels that are designed for this purpose that I need to get the shared key/password for? Thank you in advance!
Can you use meshtastic like a cw net? One net controller, anyone that wants in announces themselves one time, and waits for traffic. The net controller polls the net attendees (like Link 11) for traffic. When polled subscribers send what they've got, then are quiet again. The net controller might be the one with the lowest serial number. That way it's more autonomous.
Nothing like that in meshtastic. Simple signal strength dependent flooding of packets. Some lower priority packets get delayed if channel utilisation is too high.
another annoying thing when in a dense meshtastic environment is when someone has range test spamming enabled. this causes those seq 1 seq 2 seq 3 messages to be broadcasted.
the offending device will need range test turned off.
there may be a setting to ignore such messages in later firmware versions or depending on device or os.
Oh yeah, keep that off.
They seem interesting, but I watched "Ham Radio 2.0", live last night, on Meshtastic, and this is the exact complaint I heard from the presenters of the live stream. Thanks for great overview.
Well an added the solution.
Hey Josh, I just a LilyGo T Deck device. I connected it to the app and loaded my encrypted channels. But on the device itself how to do I select one of my encrypted channels instead of the “ Long Fast” one that it is on?
The T-Deck is getting a massive update soon which will add that capability.
@@HamRadioCrashCourse oh awesome. Thank you so much for all you do for the hobby.
I wonder what impact a saturated environment has on battery/power consumption.
Radio is definitely using more power if it's constantly receiving and transmitting packets.
Increased but if it’s nrf based it will still use a trivial amount of power on the order of 100-200 mah per day
this is an artifact of all convenience mesh networking technologies. as networking is made easier, more an more of the bandwidth is taken up by the housekeeping of the mesh.
I have been seeing Meshtastic being discussed more and more. I haven't really looked into it much, but could it be a viable means of communication for let's say a hunting party of 8 to 10 people spread out over a 2 to 5 mile radius from a central location in an area with lots of hills and poor cellular reception? Is it just text based messages that can be sent or can images be sent as well? It is fine if only text can be sent as the main use would probably be to ask someone to bring a quad to help drag a deer or let the rest of the group know that a member of the hunting party is heading back to the cabin earlier than everyone else or staying out later than everyone else.
Text primarily.
Very good for low volume telemetry or text based communications.
I think its capable of doing a binary payload like an image, but its very slow so not practical.
You do need line of site however so having some nodes at higher elevations would be helpful
@@dorvinion thanks for the info. I might have to look into it more then. We might not be able to have our meme war, but at least we can message each other. It might be a viable back up to using GMRS radios.
Wait… didn’t you say there were *three* tips?? Did I miss one? 😮
Is there something in the meshtastic firmware that would allow it to "learn" and stabilize such a dense group of nodes if given some hours or days to figure it out? So after some time that mesh would be functional and not bogged down? Would you be able to simply limit the "background" transmissions to a certain portion of the bandwidth?
Perhaps in the future. But it’s likely best just being user settings. Like hops.
What is the trade off of using short-fast? Does transmitting data more quickly effect range?
Yes it can affect range.
I think of it in terms of saying a callsign:
short: just saying the letters: "KF6EGR"
long: saying each letter with the phonetic alphabet: "Kilo Foxtrot 6 Echo Golf Romeo"
they technically have the same information, but if the signal is bad (due to being far away), the "long" method has a better chance of being understood without error.
Links to videos mentioned please
Added. Thanks for reminder!
Question: does changing from Long Fast to Short fast affect the battery life? I am looking for something to extend battery life on those solar satellite nodes I plan on setting up between Maine and SoCal... (just kidding, though that would be amusing an expensive)
Try and tell us.
Just get a nrf based device (like the RAK) and a decent sized solar panel with decent sized battery and you shouldn't have any issues with battery life.
No the battery usage is the same. Actually short fast uses less because it’s a shorter transmission time. 300x faster than long fast and with far more than 1/300 the range
What is the device with the keyboard? Is that a mini Linux computer running meshtastic?
It’s a RakWireless Meshtastic device. It’s a custom job.
@@HamRadioCrashCourse cool! Do you know if they would be willing to make another one, or who to ask about it?
So much fun! Thx Josh!
Indeed!
Someone explain simply ,what is meshtastic and what is it for , and why would I want it ?
Yeah. I made a video over a year ago that explains it. Simply, these small devices create their own network, disconnected from the internet to exchange text messages. They can send encrypted messages as well over this mesh network they create. Anyone with a desire to text message if standard networks goes down may want Meshtastic devices.
@@HamRadioCrashCourse Thanks I’ll have a look back, I hope it uses 800Mhz band not 70cms as a lot of devices seem to be creeping on to the ham bands
It's 917 MHz.
I have multiple LoRa modules. I have never used them as a LoRaWan purely because I foresaw this system overload. LoRa is phenomenal for sending back data from remote devices. For an internet replacement which is kinda what Meshtastic is trying to be, it's going to be dismal.
I don’t really see the Meshtastic team trying to replace the internet at all. Just light weight messaging. Keep it Short Fast in contested areas.
@@HamRadioCrashCourse But that's something cell phones and messaging apps on tablets do far better.
They only can do that because of the internet data capabilities and high speed wireless. Try doing that on your own and you see what Meshtastic is so special.
@@HamRadioCrashCourse That still doesn't get away from Lorawan being pretty dismal in terms of transmission speed. Sure - you can mesh it with regular internet but then it's not pure Lora. The whole point of LoraWan is to get AWAY from having to route everything through the regular internet.
Sending this to all of my Link 16 datalink operator friends to explain "Time Slot Duty Factor"
Good info, thanks for making this video.
Great info 👍
Just literally described how some stations have ruined APRS in a region
MQTT uplink and downlink are ON in that QR code
Yeah. It was an example. Not something to use.
Sounds like they reinvented a Apple Talk like protocol and filled the band with so much “here I am” traffic that the real messages could not get any time.
I bet MQTT would have been fine if there’d just been a /msh/US/OH/Hamvention topic used.
Default Meshtastic is built for a common environment. MQTT should be off by default. There are special uses for it.
it has the dsd+ issue LOL it isnt smart enough to fence off a gps area for the devices so it doesnt get gridlock
It seems like the Meshtastic network is either completely unheard of or completely saturated depending on the area. The more I watch about it the less enthused I am.
The thing to remember with Meshtastic is you should flesh out your own network. If you can pick up others, great, but it’s supposed to be an off-grid mode for your important communications.
It’s called a broadcast storm. Usually brings down the network.
6:26 “highly contested” 😜
We need to gameify Meshtastic :D
MQTT should stay in my Home Assistant node. Got it.
Think about all the keep alive pings that are broadcast every second on a typical network.
I would also be interested in high frequency contacts and digital contacts again they have no interest in computers or digital and are so old I'm in my 50s and was by far the youngest person there and probably was the only non-native Swiss who didn't attend ZTE which is one of the best engineering schools in Europe and you should check out the HP 9 exam it's absolutely impossible unless you're an engineer HB3 is okay and I can do it in French. Of
If you wana split hairs it would be ”package” but ”packet” works.
I know this is expected. I want what comes after meshtastic. Some one must be working on a new technology that has no node limit. I feel like that would go global (or continental I guess) really quickly.
I think people don’t fully understand the node limit. It isn’t what you think. It’s three hops by default up to seven.
@@HamRadioCrashCourse I guess, maybe I should just try it out and see how it goes :)
Its like a broadcast storm in old networking haha
Life is wonderful; we live and learn every day. Seems like those working on this can easily devise a configurable limit to any mesh network. Don't hard wire it, make it configurable. Problem solved.
The messages in the first screen shot...
I am a lawyer admitted all the way to the Supreme Court so legally speaking I think I'm correct in my legal opinion because for all federal purposes and under federal law my domicile is Kentucky. Therefore this being a completely federal law and Federal Regulation based issue my domicile officially for federal law reasons including the FCC would be Kentucky so I could take legally buy distance with a willing person who will administer the exam my entry level amateur radio license in that manner in English.
If I was there with people I wanted to be able to communicate with - I would just switch to another frequency.
Meshtastic fell flat on its face when 100 nodes were brought within range of each other in one area. That would be the definition of failure.
Yes, but, a simple config change fixed it. It worked great at Huntsville.
Go with “Transmit Storm” or “CHIRP Storm”
Yeah, a throttling algorithm to reduce the traffic in congested environments.
It’s not so much throttling as it is speeding up the transfer so you can have more chirps per minute.
There is an alternative called Ripple.
Skynet finally took over😂
"the burning man" lol
Sounds like you exasperated the issue by posting the QR code.
Yeah I'm in a region where everyone in the radio club is 60 years or older engineers and that's the club and they don't want anyone else in it especially not anyone coming with a computer background or any other new type of technology and being a dual National they were also clearly members of the national party here and I was made clear that I was not welcome. Bern Amateur Radio Club (Aventura cranky old farts who are ultra nationalistic and if you weren't born Swiss you aren't Swiss even if you have the passport and we live in the only direct democracy in the world). It's sad because it has an extremely long history and I assume that it will die out with this group of individuals who are passive-aggressive and extremely cruel. I would guess this would violate one of the international and National regulations but I'm not going to mess with that.. sad because I've been interested since I saw a man using an old Kenwood on the high frequencies in North Carolina as a teenager born in Kentucky and lived in Colorado Montana now abroad for 23 years.
The US federal law states that my last and current voter registration and US domicile is the last domicile which I held before I left which is my mother's home. If that's the case then since this is a federal law we're dealing with my domicile is officially Kentucky for federal purposes so I should be able to take a remote test. I then should be able to take advantage of reciprocity.
I swear, the term "I'll put the link in the description" has to be one of the biggest lies stated by UA-camrs. I have lost count of the number of times that has been said only to find THERE ISN'T SUCH A LINK!!! I see a lot of links for advertising to support your channel but where is the link for Richards video you said would be in the description???
Thanks for the reminder!! ua-cam.com/video/dxYY097QNs0/v-deo.htmlsi=pzCKaaWmzfecwSNK
That’s all the ham community here is talking about. Meshtastic
…. Really that’s it. Lol
@@HamRadioCrashCourse pretty much
👍👍👍