Peer to peer mode: Connect command not found
- This topic has 2 replies, 2 voices, and was last updated 7 years, 3 months ago by
Simon Morrison.
-
AuthorPosts
-
November 23, 2017 at 10:03 am #21884
Simon Morrison
ParticipantI have two mDots, one connected to the UDK and the other to a USB/Serial Convertor. I updated their firmware to V3 but when I could not get peer to peer to work I loaded 2.0.16-1. I followed the example in the AT command manual (same sequence is shown on the web site) except the example is for a US unit. Instead I used AT+TXDR=6 at which point it started to work. I then just exchanged a little bit of data a few characters at a time using RealTerm at both ends.
They stayed connected for two days and just now I found that unit 1 still received data from unit 2, but unit 2 did not receive from unit 1. It also started echoing data I entered back to the screen.
I typed +++ at both ends which disconnected them. Now they both won’t recognise the CONNECT command and say “Command Not Found!”. I tried power cycling and using ATZ but that made no difference.
Any ideas?
Device ID: 00:80:00:00:00:00:a1:c3 Frequency Band: EU868 Frequency Sub Band: 0 Public Network: off Start Up Mode: COMMAND Network Address: 00112233 Network ID: 2b:7e:15:16:28:ae:d2:a5 Network ID Passphrase: Network Key: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.45 Network Key Passphrase: Network Session Key: 00.11.22.33.00.11.22.33.00.11.22.33.00.11.22.33 Data Session Key: 33.22.11.00.33.22.11.00.33.22.11.00.33.22.11.00 Network Join Mode: PEER_TO_PEER 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 Link Check Threshold: off Link Check Count: off Error Correction: 1 bytes ACK Retries: off Packet Repeat: 1 Encryption: on CRC: on Adaptive Data Rate: off Command Echo: on Verbose Response: off Tx Frequency: 0 Tx Data Rate: DR6 - SF7BW250 Tx Power: 11 Tx Antenna Gain: 3 Tx Wait: on Tx Inverted Signal: off Rx Delay: 1 s Rx Inverted Signal: on Rx Output Style: HEXADECIMAL 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
November 23, 2017 at 12:48 pm #21885Martin Pelletier
ParticipantHi Simon,
Tx frequency is 0!! ->AT+TXF=your frequency. I believe if you dont have the right frequency for your mdot, it will not support it!! Check the model description just to be sure.Other thing the mdot library has to follow the mbed-os
ie lib mdot 3.0 for mbed-os 5.4.7 (otherwise you could get some weird behavior)regards,
MartinNovember 24, 2017 at 2:25 am #21887Simon Morrison
ParticipantThanks, it is working again 🙂
-
AuthorPosts
- You must be logged in to reply to this topic.