Except the TV Connector is most definitely NOT Bluetooth. It’s “AirStream”. But maybe you were using “Bluetooth” as a generic term for wireless.
The old version TV connector didn’t have an on-off switch. The newer version has one on the top, along with other buttons. I happen to have the old one.
It most definitely is. It’s bluetooth LE housed under a phonak marketing term of “Airstream”
I’m a doubting Thomas. All I can find is that it’s 2.4 ghz. Tha’s also the same as Roger FM. Can you point me to a source? Thanks. I also wonder why so many technologies use 2.4 ghz. It’s a vary crowded spectrum!
I’m way out of my league in this stuff, but found this post from Gr8tdane
Based on it and my limited understanding, if I had to bet I’d say it’s not Bluetooth because it can stream to multiple devices without pairing, but again, way out of my league.
Yes yes your are correct.
Generic terms can sure get a person In trouble.
May I have a coke?
Did a quick look at this TV Connector with “Airstream Technology “.
It uses proprietary 2.4 GHz streaming protocol.
Looks like everyone was a little bit right.
It’s proprietery bluetooth low energy and they are calling it “airstream”. You can tell this by looking at the FCC certification.
OK. I found the FCC site that I could search if I had the FCC id number. I’ve searched for a FCC id number for the TV connector without success. Read through the online manual several times looking for it. I also saw a post on the forum that said you’d looked it up for Oticon, but not Phonak. Can you provide any further direction?
I based my conclusion on what Phonak says about AirStream:
“The TV Connector can simultaneously stream audio signals up to 15 meters to an unlimited amount of connected hearing aids.”
First of all, the 15 meters is weird. I’ve seen BT radios that work at 10 meters, and BT radios rated for something much bigger, like 40 meters, but never 15 meters.
Secondly, I’ve done quite a bit of work with BLE and data transfers. Even with a proprietary profile, you cannot stream “…top rated sound quality streaming…”. We needed to transmit 300sps of a single channel of 8 or 16-bit data and even with a custom protocol we could barely do that. Dual channels of 8Ksps (even if we downgrade the high end to hearing aid frequencies) is TWO ORDERS OF MAGNITUDE more data.
Here’s a custom BLE (GATT) profile that can transfer 1KByte/sec with handshaking. You CAN go to higher throughputs, but they become very lossy because you can’t afford timeslicing to retransmit bad packets.
Plus, even with custom GATT profiles, BLE must still be paired.
Plus, BLE maxes out at pairing 7 devices, even with custom GATT profiles.
Now, in the past, one of my startups made true one-to-many time-division protocols using WiFi radio chips (same as BT radio chips). But it’s not BT or BLE in any way, shape, or form.
As far as I know, all equipment sold in the USA is required by law have an FCC ID. I can’t recall which specific document I found it in for the Opn, but it was either the user manual or a data sheet. You should be able to find it somewhere.
Here’s another clue that might be helpful. One need only pair the TV connector once. After that, if the aids are set to auto-connect (which is the default I think), then the aids connect very quickly anytime you’re in range if there’s sound and power coming into the TV connector.
I would be very surprised if they are not using BLE. There isn’t a lot of room inside an HA for two separate receivers. AFAIK, HAs are usually built based on BT SOC. Again, these devices will support BTC and BLE, but not some random unrelated protocol. The FCC ID should prove one way or the other.
I have the TV Connector. On the back it says:
FCC ID: KWC-TVCONNECTV2
Thanks! Very helpful. Here’s what I found: Sonova USA . Wireless audio transmitter TVCONNECTV2 FCC ID KWC-TVCONNECTV2
No mention of Bluettooth. Just Digital Transmission System. There’s also mention of confidentiality so I’m guessing there was more info on application than is reported to public. I still consider the question open.
That’s pretty interesting. Lots of information but not a straight answer. Proprietary comes to mind. Looks like the license allows a frequency and wattage.
It uses bluetooth.
BLE is generally proprietary, because there aren’t as many profiles for it as there are for BTC. Consider BLE as a toolkit that you must customize to use, rather than a finished product. Maybe some day that will change.