[alejandro ballesta]

thanks

[alejandro ballesta]

Hi Jason,
re-reading your answer I suppose there is no ‘command way’ to change this setting to lora::ON, right?
Do you think maybe we can lower the power output for the first join? The problem we want to avoid is concurrents “join requests” due to all nodes powering up at the same time.
We are also applying some random delay to the first join to prevent interferences.
Thanks!

[alejandro ballesta]

Example of a successful join. Same result.

at+txch
Index	Frequency  DR Max Min  On
  0	868100000      5   0    1
  1	868300000      6   0    1
  2	868500000      5   0    1
  3	    0          0   0    0
  4	    0          0   0    0
  5	    0          0   0    0
  6	    0          0   0    0
  7	    0          0   0    0
  8	    0          0   0    0
  9	    0          0   0    0
  10	    0          0   0    0
  11	    0          0   0    0
  12	    0          0   0    0
  13	    0          0   0    0
  14	    0          0   0    0
  15	    0          0   0    0
  R2	869525000      0   0

OK
at+join
Successfully joined network
OK
at+txch
Index	Frequency  DR Max Min  On
  0	868100000      5   0    1
  1	868300000      6   0    1
  2	868500000      5   0    1
  3	868800000      5   0    1
  4	869000000      5   0    1
  5	869525000      5   0    1
  6	869800000      5   0    1
  7	868100000      5   0    1
  8	    0          0   0    0
  9	    0          0   0    0
  10	    0          0   0    0
  11	    0          0   0    0
  12	    0          0   0    0
  13	    0          0   0    0
  14	    0          0   0    0
  15	    0          0   0    0
  R2	923300000      0   0
OK

[alejandro ballesta]

thanks Jason
I suppose that if both rx windows are available you can receive up to 2 downlink frames after the uplink one.

Regards

[alejandro ballesta]

Hi Silva,

don’t know if you’ve solved your problem yet.
I found the same issue when migrating from ubuntu 12 to 16.
The problem is ubuntu 16 (i think 14 also) does not associate the usb:pidvid (the exar one) to the cdc_acm driver automatically.
You can try to modify the udev rules (hard and i cannot make it work correctly), or you can do it manually.
As sudo (maybe sudo su) execute the next line. Sudo doesnot behave well with echo

echo “04e2 1410” >/sys/bus/usb/drivers/cdc_acm/new_id

check your “vid pid” in with lsusb. Write down “bus XXX device YYY”
check driver loaded with lsusb -t, found “bus XXX” and the leaf “device YYY”.

Hope it helps

[alejandro ballesta]

Hi Jason,

I read the packet-fwd code (thread_up code) and realize there is no protocol check inside. Also saw there was a lot of debugging messages that I wasnt seen because the conduit was running this process as a daemon.
I started the packet forwarder in foreground and lots of info appeared on the screen!
Messages received by a node configured as NJM=3 are received by the packet-fwd and sent to a udp server in my pc.

����. ('10.200.6.203', 34890)

|���. ('10.200.6.203', 34890)

����.{"rxpk":[{"tmst":749697916,"time":"2018-01-25T11:15:36.123466Z","chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":7.0,"rssi":-65,"size":22,"data":"YDMiEQAASAABfXp+QUNQvX3j4lO+SQ=="}]} ('10.200.6.203', 46320)

3���. ('10.200.6.203', 34890)

Also receives keep-alive like messages.

Thanks for the info!

[alejandro ballesta]

Hi Jason,

thanks for your fast reply
I suppose something like that was happening

12:21:47:677|INFO| GW:00:80:00:00:a0:00:16:2e|FRAME-RX|Parsing 1 packets
12:21:47:678|WARNING| GW:00:80:00:00:a0:00:16:2e|FRAME-RX|REJECTED|REASON: Unexpected message type VALUE: 58

I will take a closer look at what you sent.

Regards.

[alejandro ballesta]

Hi Jason,

thanks for your reply.
I assume you’re telling me that no AT command support for multicasting is available at this time, right?

[alejandro ballesta]

Maybe I am replying myself…
Datasheet says set to 7dBm to allow 100% duty-cycle.
Is power output calculated adding TXP+ANT?

I have tested again using TXP=4 and I can send whatever I like without even checking TXN. It always reads 0. I believe power output is 4dBm plus 3dB gain of the antenna (by default), this will make the 7dBm number of the regulation free.

Am I right?

[alejandro ballesta]

Hi Jason,

You’re right, it was the modulation. After copying the lora-network-server.conf.sample to /var/config/lora, some params were changed to setup for EU band but some not. Rx2Datarate old value was 8.

I’ve changed to values from 0 to 7 and the results now are really good.

Thank you very much!

[alejandro ballesta]

yes you’re right. this time dlc was incremented just 1, maybe rx error.
I have just tried another one, same result. One received one not.

at+rssi
-61, -87, 0, -81
OK

As you said, I noticed data from the xdot is modu:LORA but frames from the Conduit are modu:FSK.

How can I change downlink modulation in the Conduit?

[alejandro ballesta]

Hi Jason,

thanks for your reply

/opt/lora/lora-network-server –version
MTS Network Server – Version 1.0.18

MultiTech xDot
Firmware: 2.0.14-(detached from 3699e9b)
Library : 2.0.14-(detached from 7f6b74e)

Here is an example of two consecutive messages sent

/var/log/`
8:50:27:64|INFO| Queue app data 2 bytes
8:50:27:65|INFO| Scheduled 5 bytes payload
8:50:27:325|INFO| Frame transmitted to 00:00:00:06 via GW (00:80:00:00:a0:00:0d:b5 Chan FC1 127.0.0.1:56959) Seq# 6
8:50:27:329|INFO| Check response size: 00000006 sf: 7 bw: 0 dur: 10 < tm: 51 wnd: 2
8:50:27:330|INFO| TransmitQueue canIncreaseDuration tmst: 412279129 us dur: 51 ms 0
8:50:27:336|INFO| Update DC Band: 2 Duration: 0 time-on-air available: 360000 ms
8:50:27:336|INFO| Transmit UDP message to Gateway 242 bytes

8:51:14:231|INFO| Queue app data 2 bytes
8:51:14:231|INFO| Scheduled 5 bytes payload
8:51:14:492|INFO| Frame transmitted to 00:00:00:06 via GW (00:80:00:00:a0:00:0d:b5 Chan FC1 127.0.0.1:56959) Seq# 7
8:51:14:495|INFO| Check response size: 00000006 sf: 7 bw: 0 dur: 10 < tm: 51 wnd: 2
8:51:14:496|INFO| TransmitQueue canIncreaseDuration tmst: 412326297 us dur: 51 ms 0
8:51:14:498|INFO| Update DC Band: 2 Duration: 0 time-on-air available: 360000 ms
8:51:14:498|INFO| Transmit UDP message to Gateway 242 bytes`

I believe the data is really being sent. Here you can find the output of the mqtt subscriptions

lora/00-80-00-00-04-00-1e-e7/down { “data”:”CgE=
“}
lora/00-80-00-00-04-00-1e-e7/packet_sent {“appeui”:”2b-7e-15-16-28-ae-d2-a5″,”data”:”YAYAAAAABQABxux+goOk”,”datr”:50000,”deveui”:”00-80-00-00-04-00-1e-e7″,”fdev”:25000,”freq”:869.52499999999998,”imme”:true,”ipol”:true,”modu”:”FSK”,”ncrc”:false,”powe”:14,”rfch”:0,”size”:15}

lora/00-80-00-00-04-00-1e-e7/down { “data”:”CgE=
“}
lora/00-80-00-00-04-00-1e-e7/packet_sent {“appeui”:”2b-7e-15-16-28-ae-d2-a5″,”data”:”YAYAAAAABgABkOeYgwq4″,”datr”:50000,”deveui”:”00-80-00-00-04-00-1e-e7″,”fdev”:25000,”freq”:869.52499999999998,”imme”:true,”ipol”:true,”modu”:”FSK”,”ncrc”:false,”powe”:14,”rfch”:0,”size”:15}

output in xdot`

AT+DLC?
4

OK
AT+DLC?
5
OK

new data available
AT+RECV
0a01
OK

`

Thanks!

• This reply was modified 6 years, 7 months ago by alejandro ballesta.
• This reply was modified 6 years, 7 months ago by alejandro ballesta.

[Author]

Posts