#General Connect
35 messages · Page 1 of 1 (latest)
Oh less of a question of inappropriate, more just redundancy lol
I'm still able to see it, but I can't link to it for whatever reason
#connect Was retired in favor of #1196916552725958706.
#connect message
The idea: #contributor-lounge message
Ah gotcha, didn't see that message! In that case, would it be worth archiving the channel?
Above my paygrade.
Are we using this one now?
Can we make a US- South Dakota channel?
ahhhh --- The "Post" button wasn't populating for some reason. It worked now.
I'm sure it's going to be a full room 🤣 - The whole 3 of us in the state that have one 🙂
Made a good haul of contacts yesterday across #arkansas #missouri #illinois #kentucky while flying.
@real plover got your message from in flight this morning (I assume in Iowa). You successfully bridged locations about 2 hours away from one another which was great.
Cool!!
This is just a portion of nodes received from my flight today AR-> NJ->PA. Couple messages did come through in air and thanks to those that reached out on IG!
saw you Rusty
Rad!
Flying “low” level this morning across, PA, NY, CT and RI. (12,000’ and 23,000’) 😎
I really enjoy making contact with y’all!
POI: I seem to have better contacts and more time to tx/rx messages when below the mid 20k’ altitudes. I’m using this 1/4 wave dipole with a Rak starter kit + Rak 12500 GPS.
https://www.mouser.com/datasheet/2/418/9/ENG_DS_ANT_916_CW_HW_A-3238424.pdf
I’ve not been happy with the GPS updating. I’ve got is set at 15 mins max, smart interval 20 meters, 1 minute minimum report and 1 minute between GPS fixes. Turning off the DLOP (position dilution) seems to help. I have long fast as a secondary channel and precise position reporting for that channel set. The only way to get myself to show up on the app’s map is to send a position report over LF and even then sometimes it doesn’t. Node is stuck in a window.
This also drains the 1100MAh battery FAST!
Your temporary bridging of different pockets of nodes is pretty awesome, as well as how long of a distance you seem to be reaching. Is your flight path public? Would be interesting to map the height/distance reached between nodes next time you're in the area flying. Ya, I didn't receive your location, but did receive the message. We need to get more pilots doing this!
Ya. I wish there was a way I could verify some distances!
Timestamp and info from ADSB + meshtastic rx timestamp (as long as location enabled at Rx) should work for that? Could probably use range test feature somehow also to get specific signal levels?
I’ll be flying down East coast today. Providence to Salisbury area
Maryland coast back to PA at 2 today. I’m gonna turn on range test. I think both devices need it on if anyone wants to.
Well, no meshing the rest of today. Some issue with the Wisblock I don’t have time to troubleshoot yet. 😝
is anyone in the Pittsburgh area? I'm going to be traveling there soon and was curious if I should bother bringing my node along
Always bring your node, no matter where
Fun times flying yesterday!
I’m about to fly to ATL and PIT from SAN and I’m gonna spam like crazy
Probably the best way to get an idea of actual network coverage these days. Many were on MQTT at first but think many moved to just local. Fun discovering different 'pockets' of meshes in different metros
Absolutely!
Flying back from PIT to ATL then SAN. Will try spamming again.
Switzerland, murren?