Matthew GreenI’ve been working on a little simulator for MeshCore, written entirely using Claude Code. I was hoping some MeshCore devs might take a look and let me know if there are features they could use. https://github.com/matthewdgreen/meshcore_sim #meshcore
MarSik@matthew_d_green I wonder if it is possible to adapt the #MeshCore core logic to run as a PC app and transmit or receive via a serial KISS TNC. Basically separating the protocol from the radio head. Because I just built one for testing LoRa and FSK ;)
tugaBroadcast abuse isn't well received in software networks.
You can breach the domain with STUN and similar but it would no longer be mesh.
🤔
@tuga @matthew_d_green I think you misunderstood the idea.
I would put a KISS protocol TNC radio module (just a modulator and PA really) out and run the whole #MeshCore logic as a software on a remote computer. Similar to how telcos use eCPRI.
This would still act as a regular MeshCore device.
What you are talking about is a bit unclear to me, but it sounds like the tncattach or 802.15.4 / 6LowPAN use case. Which is also totally valid, but different from what I want here.
fdlamotte 🇩🇴@marsik @tuga @matthew_d_green maybe have a look at pymc core
@fdlamotte @marsik @tuga All of these projects seem to operate on a 1:1 PC/radio model. I think a better design would move the client logic to a PC/smartphone, but each radio device could support many clients — each with their own public key/identity. You’d have to use BLE advertisements to support many clients per radio.
@fdlamotte @marsik @tuga I’m planning to prototype this next week just for fun, to see if it works. But curious if there have been any experiments in this model or if it’s a bad idea for known reasons. (I know iOS background BLE receiving is very very bad.)