connection to mDot

[mahshad.parsa@gmail.com]

Hello,

I upgraded the mLinux firmware of our Multitech mconduit from the version 3.1.0 to the 4.0.1 following the steps defined in the page “Flashing mLinux Firmware”
I edit lora-network-server.conf as follow:

“udp”: {“appPortUp”: 1784, “appPortDown”: 1786, “downstreamPort”: 1700, “upstreamPort”: 1700}, “log”: {“syslog”: true, “path”: “/var/log/”, “console”: true, “level”:30}, “whitelist”: {“enabled”: true, “devices”: []}, “addressRange”: {“start”: “00:00:00:01”, “end”: “FF:FF:FF:FE”}, “db”: “/var/run/lora/lora-net-server.db”, “mqtt”:{“host”: “127.0.0.1”, “enabled”: true, “port”: 1883}, “__v”: 3, “test”: {“disableRxWindow2”: false, “disableDutyCycle”: false, “disableRxWindow1″: false,”disableRxJoin1”: false, “disableRxJoin2”: false}, “lora”: {“channelPlan”: “EU868”, “frequencyBand”: 868, “rx2Datarate”: 0, “antennaGain”: 3, “frequencyKR”: 922900000,”frequencySubBand”: 1, “dwelltimeUp”: 0, “frequencyEU”: 869500000, “netID”: “000000”, “dutyCyclePeriod”: 60, “packetForwarderConfig”: “”, “frequencyAS”: 922600000,”packetForwarderMode”: false, “lbtEnabled”: false, “rx1Delay”: 1, “minDatarate”: 0, “nodeQueueSize”: 16, “maxEIRP”: 20, “maxTxPower”: 26, “rx1DatarateOffset”: 0,”joinDelay”: 5, “dwelltimeDown”: 0, “enabled”: true, “ADRStep”: 30, “maxDatarate”: 4}, “network”: {“key”: “2b-7e-15-16-28-ae-d2-a6-ab-f7-15-88-09-cf-4f-3c”, “leasetime”:0, “name”: “multitech123”, “baseKey”: “”, “passphrase”: “multitech123″,”eui”: “01-01-01-01-01-01-01-01”, “salt”: “”, “public”: “1”}}

I try to connect to the Multictech mconduit via the mDot. So I enter following AT command in mDot:
AT+NI=0,01:01:01:01:01:01:01:01
AT+NK=0,2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C
AT+PN=1
AT&W
ATZ
AT+JOIN

But it can’t joint to conduit!

Thanks in advance for your help

Best regards
Serge

[Jason Reiss]

Change public to an integer.
public: 1

Use either name/passphrase or eui/key values not both.
Repoase name/passphrase with “”

name/key or eui/passphrase would work too.

Troubleshooting LoRa Communication

[mahshad.parsa@gmail.com]

Dear Json thanks a lot
I apply your reforms, but mDot can not connect to conduit yet.
I check all things in http://www.multitech.net/developer/software/lora/troubleshooting-lora-communication/.
Is it important that conduit be in packet forwarder mode or network server mode?
I applied following commands for changing mode of conduit.

update-rc.d lora-packet-forwarder defaults 80 30
sudo /etc/init.d/lora-network-server stop
sudo nano /etc/default/lora-network-server => ENABLED=”no”
sudo nano /etc/default/lora-packet-forwarder => ENABLED=”yes”
sudo /etc/init.d/lora-packet-forwarder start

[Jason Reiss]

If you want to join the Conduit and have packets available on the Conduit then network server is needed.

Getting Started with LoRa Conduit mLinux (LoRa Configuration)

Go back to the network server configuration. Enable logging, “syslog”: false, path: “/var/log/lora-network-server.log”, “level”: 100

View the log while joining.

If you want forward packets off the Conduit to a cloud network server use the packet forwarder.

[mahshad.parsa@gmail.com]

I back to network server mode. I changed lora-network-server.conf as follow:

{“udp”: {“appPortUp”: 1784, “appPortDown”: 1786, “downstreamPort”: 1700, “upstreamPort”: 1700}, “log”: {“syslog”:false, “path”: “/var/log/lora-network-server.log”,”console”: true, “level”: 100}, “whitelist”: {“enabled”: true, “devices”: []}, “addressRange”: {“start”: “00:00:00:01”, “end”:”FF:FF:FF:FE”}, “db”: “/var/run/lora/lora-net-server.db”,”mqtt”: {“host”: “127.0.0.1”, “enabled”: true, “port”: 1883}, “__v”: 3, “test”: {“disableRxWindow2”: false, “disableDutyCycle”: false, “disableRxWindow1″: false,”disableRxJoin1”: false, “disableRxJoin2”: false}, “lora”: {“channelPlan”: “EU868”, “frequencyBand”: 868, “rx2Datarate”: 0, “antennaGain”: 3, “frequencyKR”: 922900000,”frequencySubBand”: 1, “dwelltimeUp”: 0, “frequencyEU”: 869500000, “netID”: “000000”, “dutyCyclePeriod”: 60, “packetForwarderConfig”: “”, “frequencyAS”: 922600000,”packetForwarderMode”: false, “lbtEnabled”: false, “rx1Delay”: 1, “minDatarate”: 0, “nodeQueueSize”: 16, “maxEIRP”: 20, “maxTxPower”: 26, “rx1DatarateOffset”: 0,”joinDelay”: 5, “dwelltimeDown”: 0, “enabled”: true, “ADRStep”: 30, “maxDatarate”: 4}, “network”: {“key”: “2b-7e-15-16-28-ae-d2-a6-ab-f7-15-88-09-cf-4f-3c”, “leasetime”:0, “name”: “”, “baseKey”: “”, “passphrase”: “”,”eui”: “01-01-01-01-01-01-01-01”, “salt”: “”, “public”:1}}

then I restart it by follow command:
/etc/init.d/lora-network-server restart

then I try to join mDot to conduit:
OK
AT+NI=0,01:01:01:01:01:01:01:01
Set Network ID: 01-01-01-01-01-01-01-01

OK
AT+NK=0,2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C
Set Network Key: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c

OK
AT+PN=1

OK
AT&W

OK
ATZ

OK
AT+JOIN
Failed to join network

ERROR

But it can’t joint to conduit.
I check lora-network-server.log, But I can’t found useful information!
Please help me.

Logger Level Changed to 30
7:59:31:426|INFO| Lora Network Server started, Version: 2.0.19 GwSerial: 19111614
7:59:31:433|INFO| Loaded default global_conf.json from /var/config/lora/
7:59:31:433|INFO| Setup for global_conf.json for EU868
7:59:31:435|INFO| Write global_conf.json card 1
7:59:31:443|WARNING| Setting for beacon interval not found. Beacon is disabled.
7:59:31:444|INFO| Lora Card AP 1: MTAC-LORA-868 MTAC-LORA-1.0
7:59:31:445|INFO| Lora Card AP 2:
7:59:31:448|INFO| Network Server Config ———————
{
“__v” : 3,
“addressRange” : {
“end” : “FF:FF:FF:FE”,
“start” : “00:00:00:01”
},
“db” : “/var/run/lora/lora-net-server.db”,
“license” : {
“hasFile” : false,
“isValid” : false,
“maxDevices” : 2000,
“maxGateways” : 10,
“maxKeys” : 2000,
“type” : 0
},
“log” : {
“console” : false,
“level” : 100,
“path” : “/var/log/lora-network-server.log”,
“syslog” : false
},
“lora” : {
“ADRStep” : 30,
“antennaGain” : 3,
“beaconDelay” : 0,
“beaconInterval” : 0,
“beaconPower” : 27,
“channelPlan” : “EU868”,
“dutyCyclePeriod” : 60,
“dwelltimeDown” : 0,
“dwelltimeUp” : 0,
“enabled” : true,
“eui_1” : “00:80:00:00:A0:00:05:ED”,
“frequencyAS” : 922600000,
“frequencyBand” : “EU868”,
“frequencyEU” : 869500000,
“frequencyKR” : 922900000,
“frequencySubBand” : 1,
“joinByteOrder” : “LSB”,
“joinDelay” : 5,
“lbtEnabled” : false,
“lbtScanTime” : 5000,
“lbtSxOffset” : -24,
“maxDatarate” : 4,
“maxDatarateEU” : 5,
“maxDatarateUS” : 4,
“maxEIRP” : 20,
“maxTxPower” : 26,
“minDatarate” : 0,
“minDatarateEU” : 0,
“minDatarateUS” : 0,
“netID” : “000000”,
“nodeQueueSize” : 16,
“packetForwarderConfig” : “”,
“packetForwarderMode” : false,
“rx1DatarateOffset” : 0,
“rx1Delay” : 1,
“rx2Datarate” : 0,
“rx2Frequency” : 869525000,
“sxOffset” : -162
},
“mqtt” : {
“enabled” : true,
“host” : “127.0.0.1”,
“port” : 1883
},
“mtsLic” : “”,
“network” : {
“baseKey” : “”,
“eui” : “0101010101010101”,
“key” : “2b7e151628aed2a6abf7158809cf4f3c”,
“leasetime” : 0,
“name” : “”,
“passphrase” : “”,
“public” : 1,
“salt” : “”,
“vendorId” : “008000”
},
“packetForwarders” : [
{
“channels” : [
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 868100000
},
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 868300000
},
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 868500000
},
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 868800000
},
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 869000000
},
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 869525000
},
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 869800000
},
{
“bandwidth” : 125000,
“enabled” : false,
“frequency” : 869800000
},
{
“bandwidth” : 250000,
“enabled” : true,
“frequency” : 868300000,
“spread_factor” : 7
},
{
“bandwidth” : 125000,
“enabled” : true,
“frequency” : 868800000,
“spread_factor” : “FSK”
}
]
}
],
“test” : {
“disableDutyCycle” : false,
“disableRxJoin1” : false,
“disableRxJoin2” : false,
“disableRxWindow1” : false,
“disableRxWindow2” : false
},
“udp” : {
“appPortDown” : 1786,
“appPortUp” : 1784,
“downstreamPort” : 1700,
“lensPort” : 1790,
“upstreamPort” : 1700
},
“whitelist” : {
“devices” : [],
“enabled” : true,
“maxSize” : 2000
}
}

7:59:31:448|INFO| ——————————————-
7:59:31:448|INFO| Devices leases will not expire.
7:59:31:449|TRACE| Connect to db
7:59:31:450|DEBUG| Open db in /var/run/lora/lora-network-server.db
7:59:31:453|DEBUG| Load db /var/run/lora/lora-net-server.db into /var/run/lora/lora-network-server.db
7:59:31:456|INFO| DB loading…
7:59:31:507|INFO| Database version: 17
7:59:31:507|INFO| Latest version: 17
7:59:31:511|DEBUG| {
“join_response_10” : 0,
“join_response_30” : 0,
“join_response_70” : 0,
“join_response_90” : 0,
“join_response_avg” : 0,
“pkts_1st_wnd” : 2,
“pkts_2nd_wnd” : 0,
“pkts_dropped” : 0,
“pkts_missed” : 0,
“rx_crc_errors” : 1,
“rx_dups” : 0,
“rx_join_dups” : 0,
“rx_joins” : 2,
“rx_joins_nok” : 0,
“rx_joins_nok_gw” : 0,
“rx_joins_nok_mic” : 0,
“rx_joins_nok_nonce” : 0,
“rx_joins_nok_unk” : 0,
“rx_joins_ok” : 2,
“rx_joins_too_late” : 0,
“rx_mic_fails” : 0,
“rx_pkts” : 2,
“tx_1st_wnd” : 2,
“tx_2nd_wnd” : 0,
“tx_ack_dups” : 0,
“tx_ack_missed” : 0,
“tx_ack_pkts” : 0,
“tx_joins_1st_wnd” : 2,
“tx_joins_2nd_wnd” : 0,
“tx_joins_dropped” : 0,
“tx_pkts” : 2
}

7:59:31:512|TRACE| Connect to MQTT
7:59:31:574|TRACE| Start Command Thread
7:59:31:575|TRACE| Initialize Lists
7:59:31:579|TRACE| MQTT – connected with server
7:59:31:581|TRACE| MQTT – subscribed id: 1 qos_count: 1 granted_qos: 2
7:59:31:592|TRACE| Testing Upstream UDP Port
7:59:31:593|TRACE| Start Command Receive thread
7:59:31:594|TRACE| Start Time thread
7:59:31:594|TRACE| Start Db Backup thread
7:59:31:595|TRACE| Start Mqtt thread
7:59:31:595|TRACE| Start Beacon thread
7:59:31:596|TRACE| Start appData thread
7:59:31:597|TRACE| Start GatewayDownstreamReceive thread
7:59:31:597|TRACE| Start GatewayReceive thread
7:59:31:599|INFO| Database backup interval every 3600000 ms
7:59:31:600|DEBUG| AppData thread started
7:59:31:601|INFO| Beacon is disabled
7:59:38:307|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 0167c604
7:59:38:312|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
7:59:48:513|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01697304
7:59:48:515|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
7:59:57:384|TRACE| TX-ACK|127.0.0.1:46038 4 bytes 0151ff01
7:59:57:385|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PUSH-DATA|127.0.0.1:46038
7:59:57:387|INFO| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|Parsing 1 packets
7:59:57:388|DEBUG| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|DATA: 0001010101010101012ce0000000008000e11053aded7d
7:59:57:389|DEBUG| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|FREQ: 868.100000 MHz DR0 RSSI: -47 dB SNR: 92 cB
7:59:57:389|DEBUG| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|TYPE: Join Request
7:59:57:391|DEBUG| GW:00-80-00-00-a0-00-05-ed|JOINREQ-RX|0001010101010101012ce0000000008000e110
7:59:57:391|DEBUG| GW:00-80-00-00-a0-00-05-ed|DEV-EUI|00-80-00-00-00-00-e0-2c
7:59:57:392|DEBUG| GW:00-80-00-00-a0-00-05-ed|JOIN-EUI|01-01-01-01-01-01-01-01
7:59:57:392|DEBUG| GW:00-80-00-00-a0-00-05-ed|DEV-NONCE|10e1
7:59:57:393|DEBUG| ED:00-80-00-00-00-00-e0-2c|CHECK-KEY|MIC Valid
7:59:57:393|DEBUG| ED:00-80-00-00-00-00-e0-2c|APP-NONCE|6f5053
7:59:57:396|INFO| ED:00-80-00-00-00-00-e0-2c|DEV-ADDR|Found End Device in DB 8e1a83
7:59:57:412|DEBUG| Freq 0: 8688000
7:59:57:412|DEBUG| Freq 1: 8690000
7:59:57:412|DEBUG| Freq 2: 8695250
7:59:57:413|DEBUG| Freq 3: 8698000
7:59:57:413|DEBUG| Freq 4: 8681000
7:59:57:414|INFO| ED:00-80-00-00-00-00-e0-2c|QUEUE-TX|JOIN SIZE: 33
7:59:57:414|INFO| ED:00-80-00-00-00-00-e0-2c|JOINREQ-OK|JOINS: 3 UP: 3
7:59:57:424|DEBUG| ED:00-80-00-00-00-00-e0-2c|PACKET-RX|GW:00-80-00-00-a0-00-05-ed Time_us:23217628
7:59:57:424|DEBUG| ED:00-80-00-00-00-00-e0-2c|PACKET-RX|Downlink Packets Queued: 1
7:59:57:425|DEBUG| ReceivedFrame ID: 0
7:59:57:441|DEBUG| getTimeOnAirMs SF: 12 BW: 125 PL: 8 SZ: 32 TOA: 1646
7:59:57:441|INFO| ED:00-80-00-00-00-00-e0-2c|JOIN-ACCEPT|DevAddr: 008E1A83
7:59:57:442|TRACE| Schedule DC band: 1 available: 240 duration: 1696 freq: 868100000
7:59:57:442|DEBUG| Duty cycle limit met – Band: 1 time-on-air available: 240 ms
7:59:57:442|DEBUG| getTimeOnAirMs SF: 12 BW: 125 PL: 8 SZ: 32 TOA: 1646
7:59:57:443|TRACE| Schedule DC band: 2 available: 2472 duration: 1696 freq: 869525000
7:59:57:443|INFO| ED:00-80-00-00-00-00-e0-2c|SCHED-TX|Use RX2 TOA:1696 ms
7:59:57:448|DEBUG| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|JSON: {“tmst”:23217628,”time”:”2018-10-24T07:59:57.382260Z”,”chan”:0,”rfch”:0,”freq”:868.1,”stat”:1,”modu”:”LORA”,”datr”:$
7:59:58:713|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 014aec04
7:59:58:716|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:0:3:154|INFO| GW:00-80-00-00-a0-00-05-ed|FRAME-TX|IP: 127.0.0.1:43232 CH: LC1 DEV: 00-8e-1a-83 FCNT: 00000000 REPEAT: 0
8:0:3:154|INFO| ED:00-80-00-00-00-00-e0-2c|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 51
8:0:3:155|DEBUG| GW:00-80-00-00-a0-00-05-ed|FRAME-TX|DATA: 206c3ecd10d5376b760774900c3e73c26de834b69cfd1fc3fd5845633c97131f35
8:0:3:155|DEBUG| GW:00-80-00-00-a0-00-05-ed|PACKET-TX|RX2 OFFSET: 6000000
8:0:3:170|DEBUG| GW:00-80-00-00-a0-00-05-ed|FRAME-TX|JSON: {“txpk”:{“appeui”:”01-01-01-01-01-01-01-01″,”codr”:”4/5″,”data”:”IGw+zRDVN2t2B3SQDD5zwm3oNLac/R/D/VhFYzyXEx81″,”datr”$
8:0:3:170|DEBUG| GW:00-80-00-00-a0-00-05-ed|DUTY-CYCLE|BAND: 2 DUTY: 3098
8:0:3:171|DEBUG| getTimeOnAirMs SF: 12 BW: 0 PL: 8 SZ: 33 TOA: 1810
8:0:3:171|INFO| Update DC Band: 2 Duration: 1810 time-on-air available: 1288 ms
8:0:3:172|INFO| GW:00-80-00-00-a0-00-05-ed|UDP-TX|JSON-SIZE:319
8:0:3:172|TRACE| TX-MSG|127.0.0.1:43232 323 bytes
8:0:3:174|DEBUG| DeviceTransmitController::TransmitFrame ID: 0
8:0:8:913|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 0129cd04
8:0:8:916|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:0:19:111|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01baab04
8:0:19:112|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:0:29:312|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01f2fb04
8:0:29:313|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:0:39:514|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01e34604
8:0:39:515|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:0:49:711|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 017cc204
8:0:49:712|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:0:59:912|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 0154f804
8:0:59:914|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:1:10:111|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 011be804
8:1:10:112|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:1:20:312|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01e78d04
8:1:20:314|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:1:30:511|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01765a04
8:1:30:512|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:1:40:712|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 012e6304
8:1:40:714|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:1:50:911|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01339f04
8:1:50:916|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:2:1:112|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01c99a04
8:2:1:114|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:2:11:314|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01663204
8:2:11:315|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:2:21:512|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 010db704
8:2:21:513|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:2:31:711|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01315804
8:2:31:712|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:2:41:764|TRACE| TX-ACK|127.0.0.1:46038 4 bytes 01a35a01
8:2:41:765|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PUSH-DATA|127.0.0.1:46038
8:2:41:765|INFO| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|Parsing 1 packets
8:2:41:766|WARNING| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|CRC-ERROR
8:2:41:912|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01255d04
8:2:41:913|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:2:52:115|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01051704
8:2:52:116|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:3:2:311|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 0158e904
8:3:2:312|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:3:12:513|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 015ed404
8:3:12:516|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:3:22:711|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01abb204
8:3:22:712|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:3:32:911|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01cdc604
8:3:32:912|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:3:43:112|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 019bb404
8:3:43:114|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:3:53:311|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01541104
8:3:53:312|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:4:3:511|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 010e8204
8:4:3:512|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:4:13:710|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01744104
8:4:13:712|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:4:23:911|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01213d04
8:4:23:912|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:4:34:113|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01dc8704
8:4:34:114|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:4:44:312|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 0170e904
8:4:44:314|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:4:54:511|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 013ea104
8:4:54:512|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:5:4:712|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 0141e104
8:5:4:713|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:5:14:911|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01fc6704
8:5:14:912|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:5:20:689|TRACE| TX-ACK|127.0.0.1:46038 4 bytes 013e0101
8:5:20:690|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PUSH-DATA|127.0.0.1:46038
8:5:20:690|INFO| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|Parsing 1 packets
8:5:20:691|WARNING| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|CRC-ERROR
8:5:24:685|TRACE| TX-ACK|127.0.0.1:46038 4 bytes 017e9701
8:5:24:686|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PUSH-DATA|127.0.0.1:46038
8:5:24:687|INFO| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|Parsing 1 packets
8:5:24:687|WARNING| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|CRC-ERROR
8:5:25:112|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01eadc04
8:5:25:113|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:5:35:314|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 016b9604
8:5:35:315|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:5:45:511|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 018f3804
8:5:45:512|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:5:55:711|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 015c2a04
8:5:55:712|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:6:5:911|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01ecb004
8:6:5:912|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:6:16:111|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 013bfb04
8:6:16:112|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:6:22:934|TRACE| TX-ACK|127.0.0.1:46038 4 bytes 0132af01
8:6:22:936|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PUSH-DATA|127.0.0.1:46038
8:6:22:936|INFO| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|Parsing 1 packets
8:6:22:937|WARNING| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|CRC-ERROR
8:6:26:312|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 013c5404
8:6:26:313|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:6:36:511|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01ec1804
8:6:36:512|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232
8:6:41:749|TRACE| TX-ACK|127.0.0.1:46038 4 bytes 01db5c01
8:6:41:750|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PUSH-DATA|127.0.0.1:46038
8:6:41:751|INFO| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|Parsing 1 packets
8:6:41:751|WARNING| GW:00-80-00-00-a0-00-05-ed|FRAME-RX|CRC-ERROR
8:6:46:711|TRACE| TX-ACK|127.0.0.1:43232 4 bytes 01021a04
8:6:46:712|TRACE| GW:00-80-00-00-a0-00-05-ed|SEEN|PULL-DATA|127.0.0.1:43232

[Jason Reiss]

Request was accepted and response was sent.

Check at+njs after the join failed.
There may be an issue with DR0 and Rx2 where a timeout fires before the packet is done being recieved.

Try join a few times. You may need to wait for duty cycle.

Otherwise try to join ABP. At+njm=0

[mahshad.parsa@gmail.com]

Thanks a lot.
I will check it

[mahshad.parsa@gmail.com]

I increased received delay and join delay by following commands:
AT+RXD=15
AT+JD=15
I try to change DR, but it only accept DR0 (AT+TXDR=7).
Please help me about join ABP configuration, in front of conduit and mDot.

[Jason Reiss]

Troubleshooting LoRa Communication

http://www.multitech.net/developer/wp-content/plugins/download-monitor/download.php?id=44

[mahshad.parsa@gmail.com]

According to the following link
http://www.multitech.net/developer/wp-content/plugins/download-monitor/download.php?id=44

I set DevAddr, Network Session Key and Application Session Keys according to the following commands:
AT+NJM=0
AT+NA=01:fa:b0:1c
AT+NSK=00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF
AT+DSK=FF:EE:DD:CC:BB:AA:99:88:77:66:55:44:33:22:11:00
I can send data to conduit and see received uplink packet.
when we use ABP mode?
My application is sensitive and it may disconnect by any reasons. In this situation we need join to conduit between operation again. I think, OTAA mode is better for my application from ABP mode.
How I solve my problem about receive joinaccept from conduit?
I checked output log of mDot during AT+JOIN, It is as follow:
ن$ے[INFO] Send join request RxDelay: 0 Rx1Offset: 0 Rx2Freq: 869525000 Rx2Dr: 0
[INFO] Configure radio for TX
[INFO] Configure radio for TX
[INFO] Configure radio for TX
[INFO] Configure radio for TX
[INFO] Rx Window 1
[INFO] RxDone 17 bytes RSSI: -36 dB SNR: 75 cB
[ERROR] MIC failed
[INFO] Packet RSSI: -36 dB SNR: 75 cB
[ERROR] Failed to join network

in side of network server, I set Network key and Application key same as each other and equal with AT+NK=2b7e151628aed2a6abf7158809cf4f3c.

• This reply was modified 6 years, 5 months ago by mahshad.parsa@gmail.com.
• This reply was modified 6 years, 5 months ago by mahshad.parsa@gmail.com.
• This reply was modified 6 years, 5 months ago by mahshad.parsa@gmail.com.

[Author]

Posts