Melbourne Meshtastic Users, Australia #7
Replies: 21 comments 127 replies
-
|
Nice 😄 To answer your q from the discourse board, hood's antenna is this one: https://www.aliexpress.com/item/1005004104155940.html |
Beta Was this translation helpful? Give feedback.
-
|
RippleGuy here. :-) |
Beta Was this translation helpful? Give feedback.
-
|
Anyone have mast recommendations? |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone from USB. After a quick WTF moment on the discourse group until I worked out what was going on. |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, I am interested in the best setup for a rooftop mesh node. Currently I have a 9dbi Omni on a rak 4631 on a 3m mast on the roof of a 2 story house. From the trace routes I have been doing, I have much better receive capability than I have transmit capability. I am interested in whether it is worth trying to dial down the receive sensitivity on the node to match better the transmit range so that the node doesn’t act as a one way repeater. I feel like this isn’t an isolated issue, I see people all over the mesh transmitting and getting no response even though the mesh definitely receives the packets, as proved by MQTT. |
Beta Was this translation helpful? Give feedback.
-
|
Scoja |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys! I brought a node to Melbourne with me for the first time yesterday, and was blown away to be picking up the Mt Dandenong node in Laverton - incredible! I'm wondering if a node placed on Mt Warrenheip might be able to contact Dandenong... A dream of mine is linking Ballarat area with Melbourne... Waiting on 3x Rak Wireless boards to come, meanwhile playing with a T Beam and Heltec v3. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Melbourne. I'm one of the Meshtastic developers and I'm going to be in town this month. Does anyone want to meet up in-person to chat Meshtastic? Maybe in the city? |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, I'm in Werribee and have been experiencing some pretty unusual rf behaviour in the past 2-3 days. Within our frequency space, there is a new signal source that is absolutely blowing the 1watt limit out of the water and around 60%of all packets i receive are bad and about 35% are just dupes from my mast mounted node. I have observed this signal on the spectrum and can only assume its local as everyone else seemed to still be working normally. Prior to this i had a full node list and excellent direct trace to MDR, Ceres rooftop and Dromana. Now i can only get nodes in my home. I have 8 nodes in total (not all in use) and have tested with each and shut down every rf related device to ensure I'm not the one creating the problem with a faulty module. Nope. I have invested heavily in the past few months into hardware to link the city and Geelong as well as create another mesh just for werribee. (City to Geelong not yet deployed) at this point in putting everything on hold, the last thing I want to do is repeat this signal mess and make it everyone else's problem too. Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
I did it @ScoJa71 ! I connected Melbourne to Ballarat / Creswick / Clunes / Talbot / Meredith! I had to use a node on my roof (Heltec V3, hardwired to power) a Wisblock solar node VERY high up in a tree https://meshnode.store/home/27-solar-meshtastic-node-rak-wisblock-inside.html (this exact unit) and another Wisblock solar node with an 8dbi antenna magnetically attached to Mt Buninyong! Mount B reached Mount Dandenong Router - and like that we have a link!
So cool sitting in my living room in Creswick seeing nodes in Geelong and Eastern subburbs of Melbourne - amazing.
|
Beta Was this translation helpful? Give feedback.
-
|
Does anyone here know who owns Jolly nodes? Specifically the 20 Jolly Leopold Router/Client nodes that have recently appeared. If you do, or you know who does, could you please direct them to one of the many resources to provide support on choosing the nodes role? (https://meshtastic.org/blog/choosing-the-right-device-role/ or https://youtu.be/htjwtnjQkkE?si=RvVxD1cphoHDvo72)? 20 routers (or even just 2) will create collisions and lead to an increased hop count per message not just for you, but anyone else (like me) who is unfortunate enough to be in your immediate (0 hop) vicinity. Just as a reminder to everyone, Client mode is what you want for 99% of deployments. Client mode will still repeat other users packets, it just does so in a more intelligent way (with delays based on received signal strength). Router should only be used in very specific, highly advantageous locations (Mount Dandenong Repeater is the perfect example of this) Apologies for rant. |
Beta Was this translation helpful? Give feedback.
-
|
For anyone who saw my hello world an hour or so ago, thanks :) lovely to see a reply almost instantly. Just got my T-Echo, even with the stock antenna I was seeing all of melbourne! (had to climb on the top of the roof though, so that was fun Now I'm very excited to set up the full sized fiberglass antenna and do some range tests |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hey Guys, does anyone want to make a router for Mt Dandenong for Meshtastic? I'm thinking of changing MDR over to the Meshcore system..... Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Can you tell me more about your decision to switch? I’m tempted to come too and bring Buninyong over, I lost interest when I realized I’m 1 hop from my Buninyong node, which means MDR is 2 hops, meaning I can’t meaningfully chat to anyone in melbourne, even though the infra is there. 2 hop limit is great for CBD folks or a festival, but for us in the sticks who’d like to connect ourselves to the CBD mesh, its useless.
If Meshcore works better in this regard, then I’ll bring my nodes over to it
… On 31 Jan 2025, at 22:53, ScoJa ***@***.***> wrote:
Hey Guys, does anyone want to make a router for Mt Dandenong for Meshtastic? I'm thinking of changing MDR over to the Meshcore system.....
It would be cool to have both. 🙂
Cheers!
—
Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIMJMPRTO6HE2PUSC4BR3VL2NNP4FAVCNFSM6AAAAABQYOY3CWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4YDMOA>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, I've got a bit of disappointing news, but a potential solution too. Please spread the word of this post and get it out there, everyone needs to know. As most of you know, I have been logging the spectrum and trying to figure out why our mesh is so unreliable one day and then pretty damn good the next. I've found the cause. Firstly, channel 20 is the default channel and where every new user lands, experiments, misconfigures and eventually learns. In the mean time the efficiency of the mesh suffers. That's a big issue. But it's not the main issue. Many of you will have noticed random nodes with incredible signal strength, no hops, and when you can get a traceroute, it's only one way. Mystery solved. That massive and hugely over amplified section is ONE SIGNAL. The owner(s) of these nodes have decided to take over 0.5mhz as one channel and the very edge overlaps 919.875mhz perfectly. This is no accident. I have seen this channel extend all the way out to a full mhz and it transmits at least twice per second. Wondering where your bad packets are coming from? Can't figure out why traceroutes take the weirdest routes and only sometimes work? Sick of not getting message acks and feling like you're missing half the conversation? Now you know why. I have setup private meshes away from this mess, and every one of these issues vanish. From what I can see, there are about 5-6 of us who are not only heavily financially invested, but have taken the time to learn how a mesh should be constructed and maintained. Scoja (MDR), VKTWO, possibly GW-R and HHRO, myself and my team mate Kouk. So, my solution... We leave just enough infrastructure on ch20 to keep it at least partially working. We use this to build our circle as people mature into the system. But we stop investing in ch20. Instead, we choose a dead section of the frequency allocation (i have already identified several good candidates) and build a massive private/invite only mesh. We have a ton of equipment waiting to be deployed on the mountain and elsewhere too. We create simple rules. If you break them, you get added to the ignore list on every router. No second chances, game over. We can also use custom modem settings that will not only work better, but also prevent our routers from listening to anything without the custom settings. It might start off slow, but it will demonstrate the true potential of LoRa and bring the reliability back. I'm definitely moving forward with this myself, I refuse to deal with this mess anymore. Anyone else in? Ideas? Obviously, this ongoing conversation is going to have to go private asap too... Bangers |
Beta Was this translation helpful? Give feedback.
-
|
I reckon do both Scoja, Meshtastic still has plenty of people finding it a buying a board, and MDR is truly the backbone, losing it would be a real shame. I’m happy to donate a solar panel / battery if you have a rak / t114 to whacking it?That being said, I’m thinking it might be cool to try mesh core.How would it’s routing algo help those of use in regional vic with a link? (But realistically needing 5-6 hops)Sent from my iPhoneOn 2 Feb 2025, at 16:35, ScoJa ***@***.***> wrote:
LOL, now I don't know what to do :)
Maybe I switch MDR over to Meshcore for a while so we can all test it out. (It seems to really help linking us all together and it would give us a good feel for it. We can always build another repeater and put it up there and run both. I'm very tempted......
I've been playing with it on a RAK board here at home and it's looking good.
It's just a real bitch to get to MDR and set it up. (ladders and shit. I put Hi-vis on to look official :) LOL
Thoughts??
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah I'm not a Facebook lover either, but the Mesh Vic group has quite a
few members and it would be a good discussion place to get them to switch
too.. alternatively I just created subreddit r/VicMeshas a neutral mesh
protocols related discussions space
https://www.reddit.com/r/VicMesh/s/ppuFrLkiQg
…On Sun, 2 Feb 2025, 20:18 Stephen Hallett, ***@***.***> wrote:
I dont use facebook, literally anywhere else please 🙏
—
Reply to this email directly, view it on GitHub
<#7 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPOQQEKPICSYRLDVAB37R32NXPHVAVCNFSM6AAAAABQYOY3CWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBTGA4DAMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Not to step on any toes, but if you (like me) hate Discord / Facebook / Reddit (to a lesser extent) for hiding information behind a closed door - you’re welcome to come make an account on the BBS I just spun up for us!
(Literally minutes old, bear with me as I configure it and fire up SSL - but feel free to make an account and start some topics.)
http://vicmesh.dingus.com.au <http://vicmesh.dingus.com.au/>
Taylor
… On 3 Feb 2025, at 09:22, Rohan King ***@***.***> wrote:
Same, however I'm not sure a thread about Melbourne, Australia is the best place for it?
—
Reply to this email directly, view it on GitHub <#7 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIMJMPSSBKUZXTGSIEM6UJL2N2LBPAVCNFSM6AAAAABQYOY3CWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBTGQ4DSNI>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
Just a quick update.... Cheers |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone know who owns !3368dbc4? I suspect Geelong/Leopold based from traceroutes. The node is currently sending out environmental data every 30 seconds, which equates to 18% airtime. Hopefully this is an accidental configuration, and not an inconsiderate choice. |
Beta Was this translation helpful? Give feedback.

















Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
1st 😉
Beta Was this translation helpful? Give feedback.
All reactions