开云体育

So I've been trying to get things working with the Comcast Voice and a TSR...

I'm trying to use the *Demo* program, though I'm increasingly thinking that it is perhaps worst than the non-existent ones we've been missing in the last few years...

?

- I have IP control of the comcast box (Xi6)

- I have set up the TSR with CS auth, etc.

- The CCD shows connected and I can control the CBx via the button commands into the module...

?

However:

1. On the TSR VTP project, the MODE button often turns itself on by itself! This raises the 'Enable_fb' output on the Apple TV Controls Reserved joins slot. When this happens I don't get any Voice data into the program. The demo program has a '1' on the enable input so whenever the TSR updates the Mode state turns back on...Why is the AppleTV Controls slot even enabled on this demo program?? Is it necessary for the Comcast Voice to work?

2. The demo program has the CCD Module serial VoiceData input coming from the Apple TV Control Reserved joins slot, but when I? get the TSR to deliver Voice serial text into the program (MODE has to be disabled) it comes thru on the TSR Voice Control slot via the 'Voice Capture Result fb' output Not the Apple TV 'Data_fb' output - This never gives me any serial data, even when the AppleTV Mode/Enable_fb is High...

Any ideas??? TIA

So no one has done any work on this???

I have done this about half a dozen times. I had problems with the demo program and just did it my way. IMO the hardest part is trying to advice the tech how to get into the secret menu of the cable box to enable IP control.

It's like a nintendo cheat code lol. My first go at one was on a CP3 and IP control had some issues like run away channels that would never stop. Not sure if this happens on a 4-series processor. On every project I'm using IR for control and IP for voice control and it's been solid with no issues. When I get back in town I can send you a example program from one of my projects as a reference if you haven't figured it out by then. Just let me know.

?

Thanks EJ, that would be wonderful...

FTR, I have IP control working (I have seen a few glitches). My problem is that I can't get the VoiceReady_F output from the CCD module to go high, and this no voice control...

I reviewed my setup with TS and they said that it looked like all the settings, Auth, etc. looked correct...

I thought that maybe there was some other special setting in the Xi6 was needed but haven't found any info on that...

And yes, the comcast remote does do voice control so it is activated in the box....

Hi ckangis,

?

What's your email address?

Thanks EJ,

Its:

chris at eicustom dot com

?

And Tony, I'm pretty sure that you can just use your 'XP' routing to connect the TSR to the specific CCD file for each box...? EJ, confirm?

OK, so I have things working now. And it actually seems to work really well!!

Unfortunately for me, it wasn't a real problem but red herrings that I would say are at the feet of Crestron (I should be used to this...)

?

Part of the issue is the Generic CCD file that by nature has universal I/Os that may/may not be used with specific hardware, and thus the help file does not offer specific help notes about how said specific hardware works, or what signals are used/not used or how they behave....? ?Have I said how much I hate these CCD files...?

If they would just publish help notes and idiosyncrasies in dedicated documents instead of some 'creepy' output into the console (which probably doesn't have all that we need anyway), we would be miles ahead of the game, IMHO!!!

?

Here's the take-aways for those who haven't tried it yet:

- The CCD help file (Typical PDF doc with the demo program) has not been updated for notes about the Voice I/Os. Thus, your only hope is trying to look at the demo program and divine the secret knowledge of the application which creates red herring #1.

- The 'VoiceReady_F' output NEVER goes HIGH.? My suspicion is that the cable box doesn't tell us this so thus, red herring #2, as the Demo program has a signal that tells the user ready/not ready.??

- Maybe this one is obvious to others but not me. When you press the MIC button, you literally start getting PAGES and PAGES of unreadable hex data coming thru the RawVoiceData. Even without speaking. This was particularly confusing because in trouble-shooting this (because no VoiceReady_F) my tests with just the basic Voice extender, I received beautiful, readable text coming into the program. The Hex blather seemed very not right, especially since it wasn't based on my speaking...Red herring #3

?

At the base, It seems to work well. I would love to not have the pages of hex vs actual readable text (which perhaps this is security stuff), and would love to see Crestron actually help us deploy these kinds of things efficiently, unless of course they would like to write fat checks for us as a community T/S'ing and fixing stuff...? Fat chance, not fat checks!...:(

?

?