4 ms·

Oh yes, totally agree. We have a rough duty cycle spreadsheet now and we will be careful to obey the rules ;-)

myself248 7y ago
That's the nice thing about 915 in the US, it's basically do-whatever. Not the case with 315/433, though! I'm a huge fan of 900MHz meshes, and have a basement full of Ricochet hardware. Starmode chat was the coolest thing in the world, but GPS's were expensive back then, so mobile nodes didn't know where they were. Stationary routers were programmed with their lat/lon when they were installed, and the MCDN mesh did geographic (distance-bearing) routing within them. On the Meshtastic site, it says the TTgo board is recommended "for most users", without saying why. It looks like this is because the GPS is built into the TTgo board but not the Heltec, but this isn't clearly explained. I picked up a few of the Heltec boards recently, because they were much more commonly available. I assume I can tack on a GPS to some random UART pins and tweak some pin assignments in a header file somewhere? If I have stable power and a high point somewhere, I'd be interested in running a repeater node that helps _everyone_'s traffic, not just my own friends who have the same encryption key loaded or whatever. Is there a way to do that, or can that be added as a feature request? Is there support for arbitrary data transport over the Lora layer; could I ssh from my phone, across the meshtstic lora, to my desktop at home sitting near another node?
- ourlordcaffeine 7y ago
  >Is there support for arbitrary data transport over the Lora layer Seconding this, I am thinking about making ultra-remote seismometers that send back (highly compressed and carefully selected) readings via something like LoRa. I could use this as the transport layer and only have to worry about the sampling and processing. (Yes - I know about the raspberry shake. It has a lot of flaws with the design which is why I'm going for the redesign)

That's the nice thing about 915 in the US, it's basically do-whatever. Not the case with 315/433, though! I'm a huge fan of 900MHz meshes, and have a basement full of Ricochet hardware. Starmode chat was the coolest thing in the world, but GPS's were expensive back then, so mobile nodes didn't know where they were. Stationary routers were programmed with their lat/lon when they were installed, and the MCDN mesh did geographic (distance-bearing) routing within them. On the Meshtastic site, it says the TTgo board is recommended "for most users", without saying why. It looks like this is because the GPS is built into the TTgo board but not the Heltec, but this isn't clearly explained. I picked up a few of the Heltec boards recently, because they were much more commonly available. I assume I can tack on a GPS to some random UART pins and tweak some pin assignments in a header file somewhere? If I have stable power and a high point somewhere, I'd be interested in running a repeater node that helps _everyone_'s traffic, not just my own friends who have the same encryption key loaded or whatever. Is there a way to do that, or can that be added as a feature request? Is there support for arbitrary data transport over the Lora layer; could I ssh from my phone, across the meshtstic lora, to my desktop at home sitting near another node?

ourlordcaffeine 7y ago
>Is there support for arbitrary data transport over the Lora layer Seconding this, I am thinking about making ultra-remote seismometers that send back (highly compressed and carefully selected) readings via something like LoRa. I could use this as the transport layer and only have to worry about the sampling and processing. (Yes - I know about the raspberry shake. It has a lot of flaws with the design which is why I'm going for the redesign)