Hot!Paring problem with RN4871 Rev 1.30

Author
PIC4C code
Junior Member
  • Total Posts : 100
  • Reward points : 0
  • Joined: 2011/02/21 10:32:55
  • Location: 0
  • Status: offline
2019/04/04 09:00:58 (permalink)
0

Paring problem with RN4871 Rev 1.30

I upgraded RN4871 to 1.30. The unit rev was 1.18 out of the box.
Response to D command:
BTA=21436587A9CB, Name=NUM2, Connected=no, Authen=2, Features=0000, Services=C0
Pairing response from my Android smart phone
“Couldn’t pair with NUM2. Check your NUM2 settings and try again.”  First time I ever saw this type of response.
Factory reset SF,2 . Reset to new MAC and name. Same problem.
Tried SA 1,2 and 4.  Pin #123456.  Same response of pairing.  I'm missing something but don't know what.  Wondering if someone else had this problem.
Pairing works fine on my RN42.
 
#1

11 Replies Related Threads

    myZigbee
    Super Member
    • Total Posts : 244
    • Reward points : 0
    • Joined: 2006/11/17 08:34:52
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/08 09:49:36 (permalink)
    0
    You may want to remove the old bonding information from your android phone first before try pairing again.
    #2
    PIC4C code
    Junior Member
    • Total Posts : 100
    • Reward points : 0
    • Joined: 2011/02/21 10:32:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/08 16:25:13 (permalink)
    0
    I removed all my former pairing and made sure their is no other pairing.  I ran my app with debug to make sure that no pairing was found therefore no connection.  The app has been using RN42 that pair nicely.  As mentioned I want to replace the RN42 with RN4871.
    #3
    petrenn
    New Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2019/04/04 08:37:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/09 10:28:38 (permalink)
    0
    I’m having the exact same problem see my post below. Try iOS smartdata app and if it works then according to a message I’ve received from Microchip this morning you need to recompile the Android app source available for RN4020 and include the custom service UUID for RN4871 as it is not currently included. I will try this tonight. It does work with IOS smartdata app though
    #4
    rogermorrell
    New Member
    • Total Posts : 7
    • Reward points : 0
    • Joined: 2012/09/18 14:37:12
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/09 10:45:45 (permalink)
    0
    I also found the Android code not nearly as good as the iOS
    Where is the Android source ?
    Roger
    #5
    petrenn
    New Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2019/04/04 08:37:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/09 11:21:51 (permalink)
    0
    Go to Microchip and search for RN4020 then look in supporting docs and software section for MLDP Demo Android.
    #6
    petrenn
    New Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2019/04/04 08:37:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/09 11:21:51 (permalink)
    0
    I agree with the IOS code being better than the android. Do you have one compiled with the latest Swift4? The one I have is old and needs migrated and I’ve no idea how to.
    post edited by petrenn - 2019/04/09 11:24:17
    #7
    PIC4C code
    Junior Member
    • Total Posts : 100
    • Reward points : 0
    • Joined: 2011/02/21 10:32:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/09 13:50:21 (permalink)
    0
    Roger,
    I have an Android phone Galaxy 7.  It pairs with my RN42s and ear phones.  Does not pair with my RN4871s.  Also has a pairing response I've I haven't seen before:
    “Couldn’t pair with NUM2. Check your NUM2 settings and try again.” NUM2 is the device name.
    No delay, responds immediately.  My existing android app, with RN42, looks for the pairing then connects.  I was hoping the RN4871 would do the same.
    Roger 
    #8
    petrenn
    New Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2019/04/04 08:37:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/09 17:14:04 (permalink)
    0
    So someone will have to test this in Android... One will have to recompile the source code and add the following service ID UUID. I can confirm they exist in Microchip SmartData code and this is why the IOS app works:
    //RN4020 Module:
    private let mchpServiceUUID = CBUUID(string: "00035B03-58E6-07DD-021A-08123A000300")
    private let mchpTxUUID = CBUUID(string: "00035B03-58E6-07DD-021A-08123A000301")
    private let mchpRxUUID = CBUUID(string: "00035B03-58E6-07DD-021A-08123A000301")
    //end RN4020
    private let mchpRemoteTxUUID = CBUUID(string: "00035B03-58E6-07DD-021A-08123A0003FF")
    private let mchpRemoteRxUUID = CBUUID(string: "00035B03-58E6-07DD-021A-08123A0003FF")
    //RN4871 Module
    private let isscServiceUUID = CBUUID(string: "49535343-FE7D-4AE5-8FA9-9FAFD205E455")
    private let isscTxUUID = CBUUID(string: "49535343-8841-43F4-A8D4-ECBE34729BB3")
    private let isscRxUUID = CBUUID(string: "49535343-1E4D-4BD9-BA61-23C647249616")
    //end RN4871
    private var customServiceUUID = CBUUID(string: "00000000-0000-0000-0000-000000000000")
    private var customTxUUID = CBUUID(string: "00000000-0000-0000-0000-000000000000")
    private var customRxUUID = CBUUID(string: "00000000-0000-0000-0000-000000000000")
     
    The syntax may be different in Android though..
    #9
    petrenn
    New Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2019/04/04 08:37:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/09 17:25:06 (permalink)
    0
    Update: guys- if you check the dates on the source code and on the two apk files on Microchip website you will notice that the source code is newer than the actual apps and the actual changes I'm suggesting below are already there. So one will just have to download it and run the apk file within. geez...I just tested it and it works fine
     
    #10
    PIC4C code
    Junior Member
    • Total Posts : 100
    • Reward points : 0
    • Joined: 2011/02/21 10:32:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/10 08:41:59 (permalink)
    0
    Hi;
    I think my original post has got lost in the shuffle.  I have an Android phone Samsung galaxy 7.  On that phone I have an app that uses the list of paired devices.  I use that list and choose which device I want to connect.  My RN42s, head phones, etc pair with no problems.  I have two RN4871s that will not pair.  When I try, I get a readily response message:   
    “Couldn’t pair with NUM2. Check your NUM2 settings and try again.”  NUM2 is the device name.  I never seen this message before.  My D response on the device is: BTA=21436587A9CB, Name=NUM2, Connected=no, Authen=2, Features=0000, Services=C0
    Therefore I'm trying to figure it out and wondering if anybody else has ran into the same problem.  I also have a ticket with Microchip.
    Roger
    #11
    PIC4C code
    Junior Member
    • Total Posts : 100
    • Reward points : 0
    • Joined: 2011/02/21 10:32:55
    • Location: 0
    • Status: offline
    Re: Paring problem with RN4871 Rev 1.30 2019/04/16 11:54:33 (permalink)
    0
    PROBLEM SOLVED:  I have a RN4870 I used year or so before that paired OK.  Tried it this time and didn't pair.  I cleared the phone cache and data then reboot.  I've done the this procedure several times without success.  Tried it again with the RN4870 and it paired.  So I connected the RN4871s and they paired.  WOW  Good example of a paradigm that engineers run into.  Works with RN42, therefore should work with the RN4871. Lesson learned.
    Thanks for all your help.
    Roger
    #12
    Jump to:
    © 2019 APG vNext Commercial Version 4.5