• AVR Freaks

Hot!RN4678 Poorly Documented Command Interface and other problems ...

Author
WM
Junior Member
  • Total Posts : 12
  • Reward points : 0
  • Joined: 2018/05/22 06:15:04
  • Location: 0
  • Status: offline
2018/06/01 00:15:16 (permalink)
4 (1)

RN4678 Poorly Documented Command Interface and other problems ...

This forum seems utterly broken, I am trying to post a new thread but get internal server errors constantly.  I attach what I am trying to post, please, mods, do something to help!
#1

12 Replies Related Threads

    WM
    Junior Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2018/05/22 06:15:04
    • Location: 0
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/04 00:30:18 (permalink)
    4 (2)
    I have given up on this module: the documentation is so poor you have to guess what the response to all commands are, it has an incompatability with Garmin GLO that support are not interested in helping with as we are not buying millions pa, the underlying configuration memory map is not published, the auto reconnect feature does not work, there is no command to get a name when the inquiry does not return one yet such a feature is needed as not all devices provide names to inquiries.
     
    If it works for you I am pleased for you.
     
    It does not work for me.  Neither does Microchip support.  Niether does this forum (I am sure the contributors are excellent, the platform sucks so hard it is untrue, the fact I could not post this thread without attaching what I was trying to post is proof of that). 
     
    Anybody know of a nice dual mode Bluetooth module that is documented, does work and has support?
    post edited by WM - 2018/07/04 00:35:05
    #2
    DarioG
    Allmächtig.
    • Total Posts : 54081
    • Reward points : 0
    • Joined: 2006/02/25 08:58:22
    • Location: Oesterreich
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/04 02:50:58 (permalink)
    0
    I only used Bluegiga in the past - more expensive than these (I remember) but they were ok...

    GENOVA :D :D ! GODO
    #3
    WM
    Junior Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2018/05/22 06:15:04
    • Location: 0
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/04 02:58:30 (permalink)
    4 (1)
    DarioGI only used Bluegiga in the past - more expensive than these (I remember) but they were ok...

     
    Thanks, much more expensive, but perhaps that is what we have to pay ... an experienced project manager once told me "the quality is remembered long after the cost has been forgotten" ... plays both ways.
    #4
    DarioG
    Allmächtig.
    • Total Posts : 54081
    • Reward points : 0
    • Joined: 2006/02/25 08:58:22
    • Location: Oesterreich
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/04 03:35:33 (permalink)
    0
    wink
    I have not used bluetooth since 2015 then... I hoped to test these RN or BM Microchip things as I have a new request but... oh well :)

    GENOVA :D :D ! GODO
    #5
    WM
    Junior Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2018/05/22 06:15:04
    • Location: 0
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/04 04:22:41 (permalink)
    3 (1)
    The documentation is poor, but not so poor you can't work out what it is up to, just makes it hard to feel comfortable working with it, if it is not documented, is it more or less likely to change at the next firmware release??? I know what I think.
     
    I had it working with a Android to RN4678 classic SPP connection and a iOS to RN4678 BLE transparent UART connection.  So it will clearly meet some needs as a device to be connected to.
     
    It is in the area of working as a device that you connect to other classic devices I feel it all falls down.  Not all devices respond with a Bluetooth friendly name to an inquiry, you need to be able to make a request to get a name from a Bluetooth address.  It may be such devices that don't give their name are not entirely compliant with whichever Bluetooth standard but many devices don't, and other Bluetooth modules do provide this facility to query a name from an address.  The Holux M-1200E GPS device is one such device that does not give a name to an inquiry.  The OBS 421 I have used previously is a dual mode Bluetooth module that does provide the facility to query a name from an address.  The RN4678 is, IMHO, difficient in theis area.  Users don't want to see a Bluetooth address in a list of devices to connect to, they want the Bluetooth friendly name, it is literally impossible to do this with the RN4678 at the moment as far as I know - if it is possible let me know!  Support haven'e been able to tell me after many weeks ...
     
    I got a classic SPP connetion to the Holux working but ... could not get the same with a Garmin GLO.  So there is an incompatability here Microchip are unwilling to address.  Who knows how many more devices it will not work with.  The OBS 421 works happily with both the Holux and the Garmin.
     
    Then there is the auto reconnect mode on the RN4678 that just does not seem to work at all for me.  The equivalent mode on the OBS 421 works a treat.
     
    Sigh...
     
     
    #6
    RISC
    Super Member
    • Total Posts : 5379
    • Reward points : 0
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/04 05:16:48 (permalink)
    3 (1)
    Hi,
     
    Did you use firmware v1.11 on the RN4678 ?
    Are you referring to the Command User's guide ?
    I used the RN-4678-PICTAIL and its manual "RN4678 PICtail/PICtail Plus Daughter Board User's Guide" to get started and did not face specific compatibility issue with the few iOS and Android smartphones I tested it against :
     
    RN4678 is even already BT 5.0 certified : Search for "Microchip Technology" in below page :
    https://launchstudio.bluetooth.com/Listings/Search?_ga=2.63777961.700765753.1525998363-316978260.1514482525
     
    Are you sure that the isue is not on GARMIN GLO side....
    Is it BT 5.0 ???
     
    Regards
    #7
    WM
    Junior Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2018/05/22 06:15:04
    • Location: 0
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/04 05:44:16 (permalink)
    0
    Yes firmware version 1.11 in a RN4678 PICTAIL.
     
    Yes I am referring to the 50002506B RN4678 Command Reference.pdf.  It does not document responses to commands.  It does not document all responses it provides.  It does not document the configuration memory map.  I could go on.
     
    As we all know, certification is one thing, interoperability is another.  I can't find the GLO specifically on the Bluetooth listings, but there are a heap of Garmin devices listed, and a lot of listings that don't search properly - not sure quite what to make of that.  All specifications are full of holes, two devices can meet the same specification and not work together.  Making a certified device is all good and well, making one that is interoperable with as many devices that also meet the specification as possible is another.
     
    No the Garmin GLO is not BT 5.0, it is BT 4.0 I believe, and operates as a classic device.  No I am not sure it is not a Garmin GLO issue.  I can say it works fine with the OBS 421 and BX3015 dual mode Bluetooth modules I have also tried and presumably a host of other devices that consumers use to connect to it.  Is the problem with it?  Maybe.  Is it with the RN4678?  Maybe.  It is an interoperability issue and not, I suggest, a BT certification issue.  It could be a problem with both GLO and RN4678 of course.
     
    My problem is this: I buy a module so I don't have to worry about these things.  I buy a module to not have to own an expensive Bluetooth sniffer and wade through Bluetooth specifications.  I buy a module an expect it to work and be well documented and well supported, so that if I find a "funny" I can have help working through it.
     
     
     
    post edited by WM - 2018/07/05 08:35:30
    #8
    mwtucker
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2007/06/12 20:15:17
    • Location: 0
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2018/07/24 19:22:39 (permalink)
    0
    Just getting started with the RN4678.  I am starting to agree that the documentation is poor.  I have been able to get the RN4678 PIC-TAIL to communicate with my Andriod phone.  I used a terminal emulator app on the phone (Serial Bluetooth Terminal, kai-morich) and Tera-Term on the PC.
    #9
    WM
    Junior Member
    • Total Posts : 12
    • Reward points : 0
    • Joined: 2018/05/22 06:15:04
    • Location: 0
    • Status: offline
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2019/09/09 00:07:19 (permalink)
    4.5 (2)
    I have moved on, Microchip support for the genunine issues with the RN4678 is non-existant.  They talk, but do nothing.  This is a device they bought up and don't properly support.
     
    Try a u-blox NINA-B2 for a dual mode Bluetooth module.  As cheap, well documented, complete support.  I had simuilar compatability issues, they aknowledged them, fixed them, provided development firmware to confirm the fix, then released the fix.  Fantastic. 
     
    I had some issues with the Sierra Wireless part, they aknowledged them, did nothing about it.
     
    Microchip will not even aknowledge the problem.  They don't really support RN parts.
     
    Just my experience and my 2p.
     
    #10
    NKurzman
    A Guy on the Net
    • Total Posts : 17934
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: RN4678 Poorly Documented Command Interface and other problems ... 2019/09/09 11:49:53 (permalink)
    0
    My RN4678 Works fine in BLE Mode.  And is shipping  But Yes the Support in limited at best.
    #11
    Jump to:
    © 2019 APG vNext Commercial Version 4.5