• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 511 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Manufacturer ID vs Default Network ID?

MikeH
Guru 15580 points


I am confused about the definition and relevance of the Manufacturer ID vs the Default Network ID.

I am trying to configure slave units that automatically pair with a master which contains a specific (unique) Manuacturer ID and Product ID. I have found (using the debugger) that one of my cc85xx devices has the unique hardware ID of 0x2000ABCD. I manually set the Product ID of this master to 0x00000001. So I use 0x2000ABCD as the manufacturer ID, and 0x00000001 as the product ID for the pairing filter for all of my slaves. However, if I configure a second network with a different master (with a different unique hardware ID, say 0x2000ABCX) the original slave will not pair with this second master. I must configure the Default Network ID in the slave to match the new master's unique ID before pairing will occur. 

My question is......what is the relevance of a unique Manufacturer ID if you must always program slaves to search for a Default Network ID for each new master? It appears that each new master creates a new Manufacturer ID, which is it's unique hardware ID.

Can someone shed some light on this?

  • 0
    TI__Mastermind 21125 points

    Let me try to clarify this. 

    You are correct that the your manufacturing ID should be set to one of your devices unique hardware ID. This will ensure that (at least if everyone do this) you also get a unique manufacturing ID. Texas Instruments do not keep a register or take any part in the manufacturing ID selection.

    Product ID is set freely by the end user as it is always used in combination with the 'unique' manufacturing ID. It is also possible to set a filter on only part of the product ID to filter on a range of different products. 

    For the pairing process you have a few different options:
    1. You have no pairing trigger (button) on the slave and want to pre-pair to a given master. Then you will need to know the unique network to that specific master. The filter function will not work in this case as this is a fixed slave to master pairing.
    2. You have a pairing button on slave and can then choose three different modes.
    2a. Proximity. Choose this if there is no button on the master. A button push on the slaves will pair to the first master within range that pass the pairing filter criteria set. 
    2b. Protocol master pairing signal. This is only valid if there is a pairing button also on the master. A button push on the slaves will pair to the first master that has it's pairing button pushed and also fits the pairing filter criteria set.
    2c. Protocol master pairing signal + proximity. Combination of the above.  Please note that proximity is a configurable threshold. 

    Now for the problem you describe it seems that you do not want a button push and have a predefined state where it can connect to more than one master and I'm afraid this is not possible with the current FW1.3.0.

    Hopefully the above shed some light to what can and can't be done with regards of PurePath Wireless Audio pairing.

    Best regards, 
    Kjetil

  • 0 in reply to Kjetil
    Guru 15580 points

    Very clear response. Thanks. However, I look forward to having a slave that is able to pair with multiple masters based on Manufacturer ID and proximity with no button.