AT-Firmware: mDot not receiving data when in class C
- This topic has 2 replies, 2 voices, and was last updated 7 years, 7 months ago by
Alexander.
-
AuthorPosts
-
August 30, 2017 at 8:19 am #20818
Alexander
ParticipantHello all!
I want to use the class C mode to receive data with the mDot, using the AT-firmware. I have a conduit gateway (MTCDT-H5-210A, the AEP version) with the Lora-gateway card (MTAC-LORA-868) installed and an mDot (MTDOT-868-X1P-SMA-1) that is connected via RS232 to my computer. I created my personal Lora network and have no problem sending and receiving data in Class A configuration. However, when i switch to class C configuration, i can not receive data on the mDot. I was expecting the data to immediately show up on the serial console, as soon das i send it from the gateway. But it is not even received when i send an empty message:
AT+SEND
Of course, i configured class C on the mDot, as well as on the gateway:
at+dc C OK
admin@mtcdt:~# lora-query -n Net Addr Dev EUI Class Joined Seq Num Up Down 1st 2nd Dropped RSSI min max avg SNR min max avg 00:00:00:01 00-80-00-00-00-00-a6-83 C 2017-08-30T09:39:56Z 48 3 5 3 2 0 -3 7 2 6 10 8.1
I am using firmware version 1.4.3 on the gateway and firmware version 3.0.0 on the mDot. Find the configuration of the mDot at the bottom of this post. I can also post the conduit gateway settings, if needed.
Is the AT version even capable of continous receiving? Do i have to use a command or will it just show up in the console?Looking forward to hear from you!
Regards, Alex.at&v Device ID: 00:80:00:00:00:00:a6:83 Default Frequency Band: EU868 Current Frequency Band: EU868 Frequency Sub Band: 0 Public Network: off Start Up Mode: COMMAND Network Address: 00000001 Network ID: 8a:xx:xx:xx:xx:xx:xx:67 Network ID Passphrase: xxxxxxxxxx Network Key: 52.xx.xx.xx.xx.xx.xx.x.xx.xx.xx.xx.xx.xx.xx.db Network Key Passphrase: xxxxxxxxxx Network Session Key: fb.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.xx.b3.07.30 Data Session Key: eb.0c.62.da.xx.xx.xx.xx.xx.xx.xx.9f.dd.90.58.45 Network Join Mode: OTA Network Join Retries: 2 Preserve Session: off Join Byte Order: LSB Join Delay: 1 Join Rx1 DR Offset: 0 Join Rx2 Datarate: DR0 - SF12BW125 Join Rx2 Frequency: 869525000 App Port: 1 Listen Before Talk: off Link Check Threshold: off Link Check Count: off Error Correction: 1 bytes ACK Retries: 1 Packet Repeat: 1 Encryption: on CRC: on Adaptive Data Rate: off Command Echo: on Verbose Response: off Tx Frequency: 0 Tx Data Rate: DR0 - SF12BW125 Min/Max Tx Data Rate: Min: DR0 - SF12BW125 Max: DR7 - FSK Tx Power: 27 Min/Max Tx Power: Min: 0 Max: 27 Tx Antenna Gain: 3 Tx Wait: on Tx Inverted Signal: off Rx Delay: 1 s Rx Inverted Signal: on Rx Output Style: BINARY Debug Baud Rate: 115200 Serial Baud Rate: 115200 Serial Flow Control: off Serial Clear On Error: on Wake Mode: INTERVAL Wake Interval: 10 s Wake Delay: 100 ms Wake Timeout: 20 ms Wake Pin: DI8 Log Level: 0 OK
August 30, 2017 at 8:27 am #20821Jason Reiss
KeymasterReceived packets will not appear on command port unless in serial data mode.
A custom application on mDot may be needed to handle Class C received packets depending on your use-case.The following are commands to be used to see that Class C packets are received.
Enable logging to see packet being received in debug output
AT+LOG=6To show last packet received
AT+RECVTo show counter of last packet received
AT+DLCTo enter serial data mode
AT+SDTo exit issue +++
August 30, 2017 at 9:57 am #20826Alexander
ParticipantWow, that was fast!
I was not aware of the serial data mode. Problem solved, thank you very much 🙂Regards,
Alexander -
AuthorPosts
- You must be logged in to reply to this topic.