开云体育

Hi All,
I have successfully controlled the Yamaha A1080 series AVR's with RS232 (my preferred method) for a few years now, using the Yamaha RX-A3010 RS232 v1.2 module.
I have a project coming up that will be using either the RX-A8A or the RX-A6A, which apparently only can be control via IP, no RS232...
I know that there is an IP version of the above module...

What are others' experience with Yamaha IP control, in particular if you've controlled the A8A or A6A??
Can you use the above module's IP version for these models?
Any issues of idiosyncrasies??

TIA!!

IMO the Yamaha IP control works perfectly well.

Thanks RickWookie! Good to know...
Do you think that the module set I've been using will work with the new receivers?? I'm assuming that the protocol hasn't changed....

It’s the same [it’s fun to stay at the] YNCA protocol over both 232 and IP. I use module for the RX-A810 (or 820 or whatever it is, it’s from the marketplace) because it has more inputs, including the HDMI inputs you’ll need for those new AVRs. Tbh though if you ever find a command is missing you can simply edit the module and just add a signal to the Serial IO symbol (and the argument defs respectively). That’s why I like YNCA, you can pretty much guess the command string needed just by looking at the other commands.

Great Info!, Thanks Rick W!

Signed,
A former Village Person...

I'm just about to deploy a program to control a Yamaha AVR with IP control, planning to use the 'Yamaha RX-A3010 IP v1.2' module.
It has a built-in Socket connect and optional standard TCP Client connection points.

I'm wanting to use the TCP client instead of the Socket connection as I need to send so specific commands from the program.
In looking into the module, the TCP connections only go to a 'Virtual Connection' module and not to the internal logic and S+!!!

First, am I wrong in thinking that this is very bad behavior on the part of the programmer??

Second, if I set up a parallel TCP connection for my purposes...
A. will that work??
B. Can I use the same port #, or will I need a different one (this assumes that the unit support multiple port connections...)

TIA!!

Not sure if the AVR will accept multiple connections to its control port, but expect it will because I can certainly still use the iOS app while Crestron is also connected.

Why do that though? Just add whatever custom string you need to the giant SIO within the module and add its driving signal to the args so you can fire it. That’s what I do. You don’t need to touch the S+ code at all.

Yeah, I see that now inside the module...Updating now!!
TY, RW!!

Ive used the YNCA protocol on both RS232 and IP. Both worked exceptionally well.

I am doing a job at the moment where I am controlling 10 WXA-50's. These are using the new YXC protocol. I haven't found any modules for them yet so writing my own unless someone else has one out there!

YXC is just a HTTP API and by my understanding is similar if not the same as MusicCast API. When I was testing the CCD for my RX-A780 I was able to confirm with network captures that the device was being controlled over HTTP via GET/POST and not older TCP/50000 YNCA spec. You could likely get away with basic functions using on of the newer Yamaha CCDs if you dont want to write your own module. Best thing about YNX is that your not limited to a single connection as you are with YNCA on port 50000.

Yamaha Extended Control API Specification:

Just a follow-up regarding the RX-AxA series of AVRs...
The 'Yamaha RX-A3010 IP v1.2' module seems to work fine...
BUT
It does not have the commands for the HDMI inputs. The previous generation of the AVRs used the 'AV1 thru AV7' input commands for the HDMI, but now the HDMI inputs are dedicated with the AVx inputs relegated for Component/Composite inputs (when/if available)
You can alter the strings by changing the 'AVx' to 'HDMIx' and that seems to work fine...

Thanks Jsells,
I have all the protocols, what I don't have is the "Desire". This job is a domestic and a very rarely do domestic so I know I will never use it again. That's why I am spending too much time looking to see if any one else has done one.

Yes, that’s what I was trying to convey here:?/g/crestron/message/243850

That module already has the correct input names as used by the new RX-AnA units I think. Rather than changing/replacing the existing input commands, I find it better to just add the new ones, thus expanding the module and making it more universal. That way I don’t have to worry about having the correct version for a particular Yamaha AVR. Another such command example that’s not consistent across models is the “all channel stereo” mode. Rather than naming it “All channel stereo” which would have been universal, it’s called 5, 7 or 9 channel stereo, depending on the model! I therefore now have all three commands in my customised module, even though only one of the three will ever work for any one AVR.