Considering I have no experience with some of these LoRa data modules,
what is this resulting in terms of modulation type, data rate and over
what kind of distance?
--David
KI6ZHD
On 04/01/2016 01:14 PM, folkert wrote:
Ah darn, of course!
Thanks.
Regarding the lora configuration: a friend of mine gave me the
configuration-parameters for best reliability for a long distance:
const RH_RF95::ModemConfig cfg = {
// Register 0x1D:
// BW CR 0=explicit
(8 << 4) | (4 << 1) | (0 << 0),
// Register 0x1E:
// SF CRC enable
(10 << 4) | (1 << 2),
// Register 0x26:
// bit3 = LowDataRateOptimization
(0 << 3)
};
rf95.setModemRegisters(&cfg);
rf95.setFrequency(869.850);
rf95.setPreambleLength(8);
Packet loss is 12-15%.
On Fri, Apr 01, 2016 at 12:41:59PM -0700, David Ranch wrote:
This is because you have your window setting per the /etc/ax25/axports file
set to 1. Change it to say 4 and things should work better.
Btw.. what speed are you running your LoRa network at? A round trip time of
1.6 seconds is quite slow but maybe that's due to the serialization delays
of running your network at say 300bps!
--David
On 04/01/2016 12:07 PM, folkert wrote:
An other strange thing: I can't have 2 packets in that 2 second
interval. E.g. a traceroute only works if I add -N 1 -w 2.
On Fri, Apr 01, 2016 at 08:42:26PM +0200, folkert wrote:
Hi,
This evening I succeeded in doing ICMP over AX.25 over LoRa(!)!
root@savannah:~/data/mkiss_moteino# ping -i 5 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
64 bytes from 192.168.5.1: icmp_seq=4 ttl=64 time=4524 ms
64 bytes from 192.168.5.1: icmp_seq=7 ttl=64 time=1601 ms
64 bytes from 192.168.5.1: icmp_seq=8 ttl=64 time=1601 ms
64 bytes from 192.168.5.1: icmp_seq=9 ttl=64 time=1601 ms
^C
--- 192.168.5.1 ping statistics ---
9 packets transmitted, 4 received, 55% packet loss, time 40005ms
rtt min/avg/max/mdev = 1601.358/2332.248/4524.246/1265.550 ms
Folkert van Heusden
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
