I’m receiving randomly an UNKNOWN from 49km and 28km away. Meshtastic software knows the distance of the transmitter and the direction, but not its location or name? Also, these receptions do not show up when meshtastic --node is used, but is in the debug table and still no location or name info.
Signal 100% looks odd with so long distance. What is the frequency in use ?
USA 915Mhz. If that is the default frequency at firmware installation.
oddly, on Monday, Memorial Day, between 7pm and 8:30 pm I received these stations:
Rolling Hills Gateway 28Km in Rolling Hills Estate
La Canchas Park node 28km in Rolling Hills Estate
tJAZ 38c4 in Huntington Park
meshDigital 49Km in Siera Madre (I think - I lost my logs)
Odder, the TTGO was on a box, 2 feet from the ground, beneath my bench. I just updated it to the latest firmware. The La Canches Parks did confirm on Facebook it was an active station. Being a Ham Radio Operator since the 1980s, I am finding this quite interesting, because my experience with lora, is not distances over 5 miles. At 5 miles, I was using a high gain antenna at both end with a Line of Site between the stations. My theory, at this time, it’s an odd propagation to do local environment.
Most likely an older device on the default channel so the packet did not decode properly.
1 Like
Yes the good old Rolling Hills Road…, but hey I am here in Germany one or two “Steinwurf” away 
But the TTGO-Lora has WiFi to the Router…
1 Like
I have been monitoring DEBUG PANEL.
There is address being received, but not showing up in the main display. Like 33.9814646 -118.2656099 at 52 feet height. Battery 99. SNR 10.25
There another address being received, but not showing up in the main display. Like 33.7851907 -118.3410644 . Battery 98. SNR -20.75
How many packets does it take to get a complete ID?
These locations are on the other side of down town Los Angeles and the other is in Rolling Hill Estate. Over 30 miles away.
How?
Why am I receiving these station after the fog rolls in? Inversion layer? Ducting?
Is there a way to log heard station? Even if they are only one packet?
Why am I receiving, multiple entries in the Debug Panel, of only one type of information packet? For instance, methDigital I only receive its name packet. The other two, I only receive the Geo location address packet.
Have you thought of using Maden Head Location format? Its shorter in size. The math is easy. For instance my address is DM13xxxx…
TNX
unknown names happen when you receive packets before a nodeinfo packet (with the name). those nodes are on the public MQTT server, where signal is calculated different.
2 Likes
Can these Satellites z.B. Norsat affect the meshtastic network?
The Tiny GS Project is only for receiving these LORA Packets.
Might increase channel utilization if your devices are on the same frequency, but is unlikely to be sending Meshtastic nodeinfoapp packets.
most Lora cubesats are in the 430 MHz range, some even outside shy of 400 MHz. I’d say most of Meshtastic runs on 800+ MHz, so no real chance of interference there.
1 Like
Interestingly enough I have been able to attain a connection from around 32 miles with some hills in the path. It was a particular sunny day and no overcast. This was extremely reliable and consistent. Granted the antennas were external but not a huge gain around ~4.5 dB.
1 Like
That is a great success! What was the signal report like?
Sometimes microwave propagation can be baffling, LORA just really helps 
On a separate note, can anyone clarify how often nodeInfo packets are sent out? I understand the default is every “heartbeat” but I was never able to pin down exactly how often that was.
Every time my devices turn on with power they send a heartbeat and everytime they confirm a message they send a heartbeat. The location settings for broadcasting the location seem to send out at that interval even if gps location is disabled. This was software locked at 375 seconds to avoid too much channel noise on settings like long/slow.
