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.

What are the constraints for multiple (that is, maximum), simultaneous audio streams using the CC85XX?

Other Parts Discussed in Thread: CC2590
I've read the CC85XX Family User Guide, the Headset Quickstart Guide, the datasheet, and the Real World Range Testing AN. I've downloaded and installed the Configurator and reviewed its operation. (And, I am awaiting the arrival of the CC85XXDK Headset kit!)
First let me describe my overall goals with respect to the CC85XX devices. And, if the overall goals are not possible with this device, how much can be done? What are the constraints?
Goal: wireless audio for live performances, consisting of (approximately) the following simultaneous links:
(6) Headset mic (mono to PM) with in-ear monitor (mono from PM) (two streams per performer).
(6) Instrument (guitars, keyboards, mono to PM).
(2) Mixed audio to powered speakers (mono from PM).
The Family User Guide indicates (2.2.1) that four audio streams are supported (mapped as 4 of 16) with no restrictions (given the RF is working well). But, the same section says "However, as for the maximum slave count, the number of audio channels streamed and used streaming formats do have a significant impact on audio streaming robustness." This seems to make sense when I read the section 2.4.2 (Anatomy of a timeslot), since the more slots that have to be devoted to more than four slaves would certainly mean that there is less time for re-transmissions, etc. However, section 2.4 (Radio Protocol) says "The protocol supports a star network topology with a single protocol master node and up to seven protocol slave nodes."
For the questions below, please assume:
1. Each node (PM and PS) is programmed with my manufacturer ID (section 1.1.3), and filtering on that ID is done on pairing (though not actually needed currently).
2. My system is the only PurePath system in RF range and use.
3. I can set up multiple PMs (if this makes sense).
4. All nodes are host-controlled.
5. The "optimum" audio encoding is used (whatever this means in this context).
So, here are my questions:
1. Since the 2.4 GHz ISM band is also used by Wifi and Bluetooth, what impact do these have? (In our situation Wifi exists but is not actively used during the live performances. So, does an "idle" Wifi network significantly degrade the Purepath network?)
2. Can I set up multiple CC85XX PMs? (In section 2.4.3, you describe the 18 channel Adaptive Frequency Hopping. Are these 18 channels distributed throughout the full 2.4 Gz to 2.4385 GHz range, or through a subrange of the 438.5 MHz band?)
3. How do I obtain a Manufacturer ID for the CC85XX product line, assuming that I want to ensure that my products can co-exist with products from other manufacturers?
4. What is the number of erase cycles supported by the Flash memory?
Great job on the docs, BTW.
  • Hi David, 

    First of all, compliments to you for a thorough job reading and understand all the documents. It seems that you have gained a good understanding of our offering. 

    The following from the UG is an error we will update in the next revision:  "The protocol supports a star network topology with a single protocol master node and up to seven protocol slave nodes.". It should really read four protocol slave nodes as it does on page 8.

    So to your questions:

    1. Everything that is actively transmitting in the 2.4 GHz band can in effect cause impact on the PurePath Wireless audio link. To what extent and how serious this depends really on the type of interferer. Basically you can divide interferers into two groups, static and frequency hopping. For the static interferers like WiFi and uOwens etc. the built in adaptive frequency hopping algorithm of PurePath works rather well and, depending on the transmit duty-cycle of the static interferer, we can detect these and move away in frequency. For frequency hopping systems (not talking about other PurePath Wireless networks) we have no chance determining the jumping pattern and thus it is little for us to do.

    From your description it seems that you are worried about three interferers. a low-duty / idle cycled WiFi, Bluetooth and other PurePath Wireless networks. 

    • Idle WiFi - if WiFi is idle during PurePath operation it should have little to no impact. With our adaptive frequency hopping we spread our 4 active channels as much as possible in the 2.4 GHz band and the trial channel iterates over the remaining 14 (out of 18 total) channels. Even with some in-frequent WiFi communication between node and access point, the chances of obstructing all 4 active channels is low. Built in re-transmission of our system ensures that we can survive loosing some packets (how many is as you say dependent on the configuration of the network).
    • BT - Bluetooth is operating at 79 channels roughly with roughly 1 MHz occupied bandwidth for ~650us at each channel. PurePath wireless uses 18 channels (more active than the 14 other) with 3.8 MHz occupied bandwidth at ~2-4000us at each channel. Interference (both ways) is then just statistically chances of being at the same frequency at the same time. For a mute event on PurePath Wireless to occur you need multiple timeslots (at varoius frequencies) in a row to crash to mute which is even harder statistically.
    • Other PPW - We are able to detect other PPW networks to some extent and have mechanisms to ensure that two independent networks won't align in time/frequency. 
    In addition to these co-existence issue is also something with the physical parameters of the different radio (saturation, selectivity and blocking performance) and the signal to noise ratio between the wanted signal and interferer at all times.
    2. Yes you can. Depending on the proximity of the different system and configuration you can have multiple networks. You can see 4 networks (master + 1 slave) in very close proximity in use in this video: http://focus.ti.com/general/docs/video/Portal.tsp?entryid=0_nnh06yxq&lang=en
    For the frequency hopping the 18 channels are spaced 4 MHz apart over the entire 2.4 GHz band (channel 1 have center frequency of 2406 MHz while channel 18 has 2474 MHz) . In addition to the different PurePath networks operating at different frequencies they are also diverse in time. Once again; you as a customer have to define what is closed proximity etc and do some testing to make sure this work. It's a huge difference with all the different masters 10 cm apart vs. 10 meters apart. 
    3. Manufacturer ID is selected by you based on the unique chip ID on one of your CC85XX devices (see UG chapter 2.2.1.1). If you want other manufacturers products to be able to connect to your device you either need them to know your manufacturer ID or disable this filtering during the pairing process. Texas Instruments do not ensure compability between different manufacturers.
    4. Erase cycles are limited to 1000. Good catch, something we need to add to our documentation :D
    For your application I assume latency is of the essence and please note that latency is traded directly for range / robustness as the number of re-transmission attempts goes down. Would also have considered antenna diversity on all slaves in your system as they will be moving and not static. This to combat RF multi-path fading effects. 
    Hope some of this helps otherwise let me know and I'll do my best to help you out. 

    Best regards, 

    Kjetil

  • Kjetil:

    Thanks much for the quick response and information.

    Some followup on questions 2 and 3, with #3 first:

    3. On the manufacturer's ID: if I understood your answer (and after a re-read of 2.2.1.1) I simply pick the device ID of any of the devices I purchased (really, TI's ID to mark that specific device), then based on the fact that it is globally unique, I can simply use it as my own manufacturer's ID. Is this correct?

    2. On multiple PMs: the video was useful, though the system in the video was much smaller in scope than what I anticipate (with only a single stream/PM). Since I control the design of my "big" system, I can physically spread out the PMs as needed. But, this raises a couple of questions:

    2a. If the links are designed to use the CC2590 (and this seems to be a good idea, given the fact that it is intended for use within a theaters/stages with a lot of steel in the buildings), how would any distances greater than the wavelength (about 4.1") really make any difference? Ideally, I'd like to have the 3 or 4 PMs in the same console (assume 6" apart), but I can place them, say, 1m apart. The video did not really address the idea of distance between PMs, so any additional info/hints/tips would be appreciated. Also in the video (since I don't have that eval board), what antenna were being used?

    2b. On AFH: from my read of the docs, it appears that the CC85XX chooses from among the 18 channels dynamically. If I know, in any specific system with multiple PMs, that certain frequencies (say, 12 of the 18) work well, is there any way to constrain an individual PM to use a specific subset of the channels? In this way, multiple PMs could coexist without knowledge of (or interference from) each other. I didn't see anything in the command set that would imply that this is possible, but I would offer this as a suggestion for the next firmware revision. I think it could work like this: under the control of an external system, a PM is set into "scan for best channels" mode and paired with a PS. The PS is then moved to the individual locations where the performers would typically be placed, and the PM scans through the channels. (We assume that most performers are not going to move very much, and some - keyboardists and drummers - can really move their position at all.) The quality metric for each channel would be downloaded from the PM for each PS/performer/instrument location. The sound engineer for the theater/stage system would then pick the four best (and, ideally) non-overlapping channels for each PM, based on the physical location of the PSs to which it will be paired. Then, as the last step, those hand-picked channels are uploaded to each PM, and those are the only channels it would use.

    I'll be anxious to hear some feedback on the possibility of this idea (if it already works that way, I've obviously missed it in the docs!) in a future firmware update. (And, this does sound to me like something that is entirely a firmware update.)

    Again, thank much for the information. The design is proceeding.

    Dave

  • David. 

    3. Yes. 

    2a. The concern here is saturation. With the CC2590 the output power increases (to +~11dB) and the chances of saturating another CC85xx master increases. The actual distance depends on the antenna efficiency and radiation pattern, enclosure etc. so it is hard to give a precise answer to what the distance have to be. 6" sounds about right but you will have to test to ensure this - sorry for the vague answer but this is one of the things that can be influenced by to many things to give a good answer and something I usually recommend our customers to do a mock up of based on development kits etc before they make their own board and go all in with our solution. In the video our regular CC85XXDK was used if i remember correctly and this contains a whip antenna. 

    2b. This is a good point and without sharing to many details something we will support in one way or the other in a future FW upgrade. Today it will not limit itself to certain frequencies and jump "freely" around over the 18 channels as defined by our frequency hopping algorithm. 

    Best regards,

    Kjetil

  • Kjetil:

    Thanks very much, this is the information I needed (especially on 2b - will be looking forward to this).

    One last followup and I am probably complete with this thread: I have tested the CC85XX eval boards and am very pleased with their operation. As a digital designer, I'm perfectly comfortable with the design and implementation of the circuit. However, I have no RF experience and as I think about the packaging of these devices for performers (mic, instrument, etc.), is there a preferred mechanical orientation of the master relative to the slave? That is, what it the 3 dimensional "shape" of the signal from the CC85XX eval board? Is it a sphere, disk/donut, cylinder, conical beam, etc? In the case of the disk/donut, cylinder and beam, how is the axis of each oriented relative to the PC board itself? Is it normal to the board, or is the axis parallel to the board? If parallel, which direction? Or, is the signal dispersion broad enough that it really doesn't matter?

    Thanks.

  • David, 

    This totally depends on the antenna and design of the board in general (size of the ground layer etc). 
    If you want to dig into this topic we do have a extensive appnote that covers this:
    http://www.ti.com/general/docs/litabsmultiplefilelist.tsp?literatureNumber=swra328

    More details (including radiation pattern diagram) can be found in the individual document for each antenna.

    For the CC85XXDK the whip antenna supplied is rather omnidirectional (donut) in the X and Y direction with less in the Z axis (along the antenna). We usually achieve best performance placing the boards on a straight surface with the antenna pointing straight upwards.

    Regards, 
    Kjetil