it needs a lot of GUI polishing and simplifications, but the project looks nice! I'm not sure what is different at protocol level in contrast of meshtastic, but if it is so much better as you explained in last video, I really looking forward for the future of this
Super promising project! Great to be a part of it, and I can confirm, even in these beginning stages it does work! Exciting times ahead! I am test 1 test 2! It is snappy too from what i've experience For example, Meshtastic is reporting 25% chnutil at the moment, but MeshCore is still sending and receiving messages no problem! Lower overhead is exactly what we need! Static repeaters is a brilliant idea. You wouldn't want your mobile phone towers going for a week holiday in Spain whilst you're in the rainy UK leaving you without coverage, so good static repeaters are fantastic! Still early days here but so far so good! Subnet
Hi Andy. I used to be a games coder in the early days (C/C++ even assembly) - now training myself to be an embedded systems engineer. Your videos have helped give me some inspiration, very interesting. A career that is in demand which is good news.
Can canned messages be created and sent in a similar way on meshcore? I just set up a rook pro on meshtastic and i can see it working better with meshcore for emergency message system.
I can see the appeal for this in congested ares but can't the same (or close to) be achieved with Meshtastic? Repeaters placed evenly to cover the desired area and the rest of the mesh nodes on client mute. I think the biggest hurdle would be actually getting people to use client mute ;) Also Meshtastics does have a bbs if people want to use it, though it's not built in to the software. Both have their use cases, Meshcore is ideal for places like UK where it seems theres a node in every other house. In a sparsely populated mesh the meshtastic approach would possibly work better.
Love what you're doing here. Is there any plan for a KISS TNC/Direwolf/VARA interface? I'm in a heavily wooded rural area and UHF just doesn't work. We've been using reticulum on the HF ISM bands (6.78mhz,13.56mhz, sub100mw in USA) into an NVIS antenna to get connectivity to each other. Would love to see something like this in Meshcore.
Meshcore a client is not connected to a repeater but if that client is in range of a another client with it route the message using the client connection?
Some of the things you're describing remind me of ARP and other OSI model tricks. Stuff I always wondered why MT wasn't using it! I was messing around with a T-Deck OS in circuit py but it's taken a back seat to 12 months of 3d print troubleshooting.
It sounds like the things you wanna be careful with on this system will also help with Meshtastic - ensuring good signal between long range repeating nodes. The only novel thing here that stood out to me was the chat group behaviour which is stateful about the conversation history. Question on that: how often does a node check for the latest chat state (missing messages)?
With the group's feature on this device someone should add a /username packet feature when you post a message so whoever you send a message to knows who sent the message.
it needs a lot of GUI polishing and simplifications, but the project looks nice! I'm not sure what is different at protocol level in contrast of meshtastic, but if it is so much better as you explained in last video, I really looking forward for the future of this
Super promising project!
Great to be a part of it, and I can confirm, even in these beginning stages it does work! Exciting times ahead!
I am test 1 test 2!
It is snappy too from what i've experience
For example, Meshtastic is reporting 25% chnutil at the moment, but MeshCore is still sending and receiving messages no problem!
Lower overhead is exactly what we need!
Static repeaters is a brilliant idea.
You wouldn't want your mobile phone towers going for a week holiday in Spain whilst you're in the rainy UK leaving you without coverage, so good static repeaters are fantastic!
Still early days here but so far so good!
Subnet
publishing the source code as promised; good on ya Andy. really nice work.
This is looking great! Can't wait to test it out over here in the US. Keep up the awesome work!!
Very interesting, and informative.
Thanks, Andy.
Hi Andy. I used to be a games coder in the early days (C/C++ even assembly) - now training myself to be an embedded systems engineer. Your videos have helped give me some inspiration, very interesting. A career that is in demand which is good news.
Can canned messages be created and sent in a similar way on meshcore? I just set up a rook pro on meshtastic and i can see it working better with meshcore for emergency message system.
I can see the appeal for this in congested ares but can't the same (or close to) be achieved with Meshtastic? Repeaters placed evenly to cover the desired area and the rest of the mesh nodes on client mute. I think the biggest hurdle would be actually getting people to use client mute ;) Also Meshtastics does have a bbs if people want to use it, though it's not built in to the software.
Both have their use cases, Meshcore is ideal for places like UK where it seems theres a node in every other house.
In a sparsely populated mesh the meshtastic approach would possibly work better.
Does mesh core communicate with meshtastic devices or only mesh core devices ?
Great video!
Love what you're doing here. Is there any plan for a KISS TNC/Direwolf/VARA interface? I'm in a heavily wooded rural area and UHF just doesn't work. We've been using reticulum on the HF ISM bands (6.78mhz,13.56mhz, sub100mw in USA) into an NVIS antenna to get connectivity to each other. Would love to see something like this in Meshcore.
That is so cool I didnt know there was HF ISM bands. what radio are you using?
Meshcore a client is not connected to a repeater but if that client is in range of a another client with it route the message using the client connection?
Yes p2p.
where do buy the TDeck
There's a link in the video description
@@Mjenneau Thanks see you in the chat on TDeck.
Hey Andy 👍
Does it work OK on the T-Decks with the poor touchscreen? Can it be flashed with Launcher?
Yeah doesn't rely much on touch, M5 launcher works and settings are stored persistently
Some of the things you're describing remind me of ARP and other OSI model tricks. Stuff I always wondered why MT wasn't using it! I was messing around with a T-Deck OS in circuit py but it's taken a back seat to 12 months of 3d print troubleshooting.
Is it a true mesh? Self healing and all?
It sounds like the things you wanna be careful with on this system will also help with Meshtastic - ensuring good signal between long range repeating nodes.
The only novel thing here that stood out to me was the chat group behaviour which is stateful about the conversation history. Question on that: how often does a node check for the latest chat state (missing messages)?
It only checks for messages when you login to the room.
With the group's feature on this device someone should add a /username packet feature when you post a message so whoever you send a message to knows who sent the message.
Never downloaded code from discord before....
You don't, code is on github 😁
@@andykirby The github has some *very* basic examples.
Um....... that's a blackberry😂
Can someone explain to me wtf this is all i hear is nerd talk but never on what it does in lamensterm or what it for ?
Off grid texting, line of sight. Each client needs its own node / radio.
@RazorBucks ahhh.. ty now I get it
👍👍👍👍👍👍🫶👍👍👍👍👍👍
Meshcore will never be popular because it's closed source.
It's open source and on github ???