Keyboard Shortcuts
Likes
- Crestron
- Messages
Search
|
Re: Yamaha 3080 multiple connections
Thanks everyone, Seems like you are right about this, probably something wrong in the keep alive /reconnect logic that cant be easily fixed. Em sex., 1 de abr. de 2022 ¨¤s 03:31, Thorsten K?hler <thorsten.koehler@...> escreveu:
|
|
Re: Yamaha 3080 multiple connections
¿ªÔÆÌåÓýI agree with Steve, IR is pretty stable in general (especially via cable) and often totally sufficient, with RS232 next to the list. However, for Yamaha, i?m using the YNCA protocol and found that to be very reliable and stable even over firmware updates. It?s just a dead simple ASCII protocol. To the OP: which control protocol are you using? ? Cheers, Thorsten ? Von: [email protected] <[email protected]> Im Auftrag von Steve Kuehn ? I know this doesn't answer your question. But since no one appears to have an answer for your question, thought I share a little insight base on my personal past experience.? In general, I avoid doing IP control for any consumer product, at least for anything mission critical, because of reliability issues.? Virtually ever job I have done using IP control on TVs and receivers, I have had to eventually go back on convert it to some other method because IP control was intermittent or a firmware update broke it.? A commercial product is a different story -- IP control is generally robust.? |
|
Re: Loading VT files to CP4
Yep, I seen this happen with several older projects.? System had been working fine for years.? I make an update to the system using newer Crestron software and all of a sudden all the iPhone/iPad interfaces stop working.? Remove the spaces from the VTP project, recompile, and download and everything starts working again.
|
|
Re: Yamaha 3080 multiple connections
I know this doesn't answer your question. But since no one appears to have an answer for your question, thought I share a little insight base on my personal past experience.? In general, I avoid doing IP control for any consumer product, at least for anything mission critical, because of reliability issues.? Virtually ever job I have done using IP control on TVs and receivers, I have had to eventually go back on convert it to some other method because IP control was intermittent or a firmware update broke it.? A commercial product is a different story -- IP control is generally robust.?
I just did a Yamaha RX-A3080 and what I did was control it will IR.? There is a 3.5mm jack on the back of the RX-A3080 so you don't have to put a flasher on the front of the unit.? IR will always work because the manufacturer is very careful not to break that interface during firmware updates.? If I need feedback, such as volume level in my case, I do an RS232 connection to the receiver.? The RX-A3080 has RS232 port on the back of it.? I only use RS232 for feedback as if that breaks, and I have seen that happen after a firmware update, at least the receiver will turn on, switch inputs, and the volume control will still work.? The only thing that happens is the volume level may not display on any two-way interfaces.? But at least the system is still usable. If you want to use IP control, you will probably have to write your own module. At least that is what I have had to do in the past. If the issue is with the firmware in the receiver, even that won't work. |
|
Re: NVX vs. SVSI
¿ªÔÆÌåÓýThanks for the insight, Ed ¨C very interesting. I also did some additional reading about the concept. I guess I just have too much of an Corporate/Enterprise IT background to imagine such a technique being approved by any IT department. ? ? Cheers, Thorsten ? Von: [email protected] <[email protected]> Im Auftrag von eoqualls ? Jeff,? In 2010 we were focused on VLAN switching, as it was much faster (instant seamless switching vs slow multi-second switching on other products).? We produced control system drivers to make implementing VLAN switching very simple.? Thorsten, I know you find this hard to imagine, but many of our dealers continue to use VLAN switching for its unmatched performance.? We have VLAN based installations over 10 years old that continue to perform perfectly. ? In 2016 we decided to add standard network routing via Multicast to our products.? The commercial installers made it clear they had customers that needed this.? Our current firmware supports both VLAN and Multicast switching.? This firmware update is backwards compatible with our devices in the field.? An installation that started as VLAN, can easily be converted to Multicast if standard network routing is desired. ? One other thing that you might be interested in knowing is that we have plenty of inventory available.? We have always purchased our silicon far in advance, as our circuit board designs are very stable and don¡¯t change frequently.? Our commitment to a stable, long term architecture allows us to confidently purchase our chips far in advance.? It¡¯s the companies that do Just In Time manufacturing that are suffering from the chip problems. ? Thank you for your consideration.? If anyone here is interested, please let me know if you want to get a demo kit for testing and evaluation.? We also offer online and classroom training for installers. ? Ed Qualls Chief Executive Officer +1-727-475-7033 |
|
Yamaha 3080 multiple connections
Hello, I'm working on a residence with 3 yamaha receivers, RX V85, RX A2080 and RX 3080. They are all using Yamaha 3010 IP v1.2 to connect and they all work fine with the xpanel app. The problem is that all of them area trying to force a reconnection even if the module is already connected, leading to dozens of processes running showing up in toolbox. As you can see below, the module has an IP connection via socket but tries again to reconnect.? Maybe because the residence has 3 of them? Anyone has this issue? Any tips on fixing this? Thanks, Daniel Arola Heres my toolbox output: 00:00:02.719 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_Gourmet 00:00:02.719 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_Gourmet 00:00:02.719 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_Mainroom 00:00:02.719 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_Mainroom 00:00:02.719 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_Mainroom 00:00:02.734 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_SuiteMaster 00:00:02.734 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_SuiteMaster 00:00:02.734 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_Gourmet 00:00:02.734 ? ?Connected ? ?//{{Connection_Status_Text}}_Gourmet 00:00:02.734 ? ?1 ? ?{{TCP/IP_Client_>>_Connect-F}}_Gourmet 00:00:02.750 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_SuiteMaster 00:00:02.750 ? ?Connected ? ?//{{Connection_Status_Text}}_SuiteMaster 00:00:02.766 ? ?1 ? ?{{TCP/IP_Client_>>_Connect-F}}_SuiteMaster 00:00:02.766 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_Mainroom 00:00:02.766 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_Mainroom 00:00:02.781 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_Mainroom 00:00:02.781 ? ?Connected ? ?//{{Connection_Status_Text}}_Mainroom 00:00:02.781 ? ?1 ? ?{{TCP/IP_Client_>>_Connect-F}}_Mainroom 00:00:02.891 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_SuiteMaster 00:00:02.891 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_SuiteMaster 00:00:02.891 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_Gourmet 00:00:02.891 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_Gourmet 00:00:02.891 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_Gourmet 00:00:02.906 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_SuiteMaster 00:00:02.906 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_Mainroom 00:00:02.906 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_Mainroom 00:00:02.906 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_Mainroom 00:00:02.922 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_Gourmet 00:00:02.922 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_Gourmet 00:00:02.937 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_Gourmet 00:00:02.937 ? ?Connected ? ?//{{Connection_Status_Text}}_Gourmet |
|
Re: NVX vs. SVSI
Hi Ed, Great information. Some followup questions:
Thanks, Jeff ------------------------------------- Jeff Klein, DMC-E Head Volunteer AV Geek Faith Baptist Church Glen Burnie, Maryland (Website / Twitter) ?/ @FBC_TechTeam / @mixingforjesus "Clothe yourselves, all of you, with humility toward one another, for God opposes the proud but gives grace to the humble." 1 Peter 5:5 On Thu, Mar 31, 2022 at 11:10 AM eoqualls <ed@...> wrote:
|
|
Re: NVX vs. SVSI
¿ªÔÆÌåÓýJeff,? In 2010 we were focused on VLAN switching, as it was much faster (instant seamless switching vs slow multi-second switching on other products).? We produced control system drivers to make implementing VLAN switching very simple.? Thorsten, I know you find this hard to imagine, but many of our dealers continue to use VLAN switching for its unmatched performance.? We have VLAN based installations over 10 years old that continue to perform perfectly. ? In 2016 we decided to add standard network routing via Multicast to our products.? The commercial installers made it clear they had customers that needed this.? Our current firmware supports both VLAN and Multicast switching.? This firmware update is backwards compatible with our devices in the field.? An installation that started as VLAN, can easily be converted to Multicast if standard network routing is desired. ? One other thing that you might be interested in knowing is that we have plenty of inventory available.? We have always purchased our silicon far in advance, as our circuit board designs are very stable and don¡¯t change frequently.? Our commitment to a stable, long term architecture allows us to confidently purchase our chips far in advance.? It¡¯s the companies that do Just In Time manufacturing that are suffering from the chip problems. ? Thank you for your consideration.? If anyone here is interested, please let me know if you want to get a demo kit for testing and evaluation.? We also offer online and classroom training for installers. ? Ed Qualls Chief Executive Officer +1-727-475-7033 ed@... |
|
Re: Managing/Processing volume
The issue for me is all about Feedback display.
Sending discrete volume levels work fine. our system uses the actual feedback of the unit to determine what the next value level will be i.e. if I send 'x' and then receive 'x' my next increment is to send 'y', BUT if I still receive 'x' as feedback, or the unit is sluggish in returning 'y', I just send 'y' again, thinking that the unit is still at 'x' instead of 'y' This problem results from one of two conditions a. the unit is sluggish in returning its feedback - slower than my Inc/Dec ramping - I've seen this with a number of AVRs using RS232 and the Sony ZA series with IP control b. The conversion from the serial text coming from the Yamaha (-80 to 16) to the Analog values are not always correct leading to weird display of the volume status In Case A, the solution is to use a pair of analog buffers one fed with my direct ramping analog and the other with the parsed Analog from the AVR. the output of both are the FB signal going to the UI Then I enable the first whenever I'm ramping so that the FB is just my ramping value - this provides very smooth display for the client After 1 second of not ramping I disable Abuf 1 and enable Abuf 2, passing the ACTUAL volume level from the AVR to the UI display This method has worked great for years with Sony ZA, Denon, Marantz, etc. With the Yamaha units, the seeded value does not convert correctly part of the time. The solution (So far): It seems that the Yamaha IP control delivers the volume level values fast enough that I can just use it directly as the FB without the switching, eliminating the need to have a change-over Assuming that it continues to keep up, this will be my 'solution'... Thanks All! |
|
Re: Managing/Processing volume
¿ªÔÆÌåÓýI just prefer to use the volume control modules available in the crestron database rather than AINC.? They already have memory for 4 volume presets built in. ? The point was that raise and lower on the AVR modules kind of sucks and they do not have an analog volume level input, so I found a way to send the direct level to the AVR precisely because it allows the AVR to be controlled like a crestron device. ? From: <[email protected]> on behalf of BruteForceIsUnderRated <crestronpro@...> ? The outputs of the analog step could be connected to an EQU to and SIO to send the discrete steps. As an analog you can store it like any other signal. ? On Wed, Mar 30, 2022 at 9:50 AM MSTC <kol.mstc@...> wrote:
|
|
Re: NVX vs. SVSI
¿ªÔÆÌåÓýHi, ? the VLAN ?rewriting¡° method you describe below sounds insane to me and i?d never even think about using that in a production environment. I can?t imagine that this is how it?s supposed to work¡ ? Cheers, Thorsten ? Von: [email protected] <[email protected]> Im Auftrag von FBC Tech Team ? On Wed, Mar 30, 2022 at 2:14 PM eoqualls <ed@...> wrote:
? Hi Ed,? I appreciate the reply. As I said, "they are (were?)". Can you clarify if the routing method has changed? Our issue in 2010(?) was that the routing of the units we purchased for testing onsite was accomplished by rewriting switch port VLANs rather than traditional multicast network routing/IGMP Snooping. I.e. to route a JAP unit on port 1 of a switch to port 20, 25, 33 and 46 you would use the JAP software to command the network switch to change the ports to be on the same VLAN via network switch commands and the receiving JAP units would display whatever streaming video came over that VLAN. If you wanted to route across switches in larger systems, we also would have to add those VLANs to the uplink ports and command the other switches to change the target port VLANs as well. If memory serves, you could only command one switch with the JAP control software, which could be a "real" or "virtual" switch. A "real" switch system would be limited to what you could physically stack together (1U switches with stacking cables) or how many cards you could fit in, say, a Cisco 6800 chassis or similar. All of our network cables would have to be home run to that physical switch, which would have been very problematic for us. A "virtual?switch" was also possible, and would allow you to have multiple switch groups to avoid having to home run everything, i.e. the Cisco Nexus line where the core and FEC expanders can all over a site but be seen as one single switch. We'd considered that idea, but found the FEC expanders to be way too loud to be located in conference and training rooms (think Cisco 3850 fans when it first starts up...but ALL the time...yuck). ? SVSi, Electrosonic/Extron, Evertz, Crestron NVX (which actually wasn't available at the time of our install) and other network protocol streaming products are routed like any other network traffic. I can have all my control devices on VLAN10, streaming devices on VLAN11 and VTC camera/touch panel control on VLAN12, and those assignments never change. Rather than communicating with switches to route things around, we command the decoders directly from the Crestron control system to pull in this or that encoder stream .? ? If JAP products are now using standard network routing like the SVSi and NVX systems are, rather than changing switch?VLANs, that's great as that would give us another product to consider. If it's still routed via commanding network switches to change VLANs for routing, that's not something that works well for our large systems (and our network departments weren't too keen on that either). ? Interested in your thoughts, ? ? ------------------------------------- Jeff Klein, DMC-E (Website / Twitter) ?/ @FBC_TechTeam ?/ @mixingforjesus ? "Clothe yourselves, all of you, with humility toward one another, for God opposes the proud but gives grace to the humble." 1 Peter 5:5 |
|
Re: NVX vs. SVSI
On Wed, Mar 30, 2022 at 2:14 PM eoqualls <ed@...> wrote:
Hi Ed,? I appreciate the reply. As I said, "they are (were?)". Can you clarify if the routing method has changed? Our issue in 2010(?) was that the routing of the units we purchased for testing onsite was accomplished by rewriting switch port VLANs rather than traditional multicast network routing/IGMP Snooping. I.e. to route a JAP unit on port 1 of a switch to port 20, 25, 33 and 46 you would use the JAP software to command the network switch to change the ports to be on the same VLAN via network switch commands and the receiving JAP units would display whatever streaming video came over that VLAN. If you wanted to route across switches in larger systems, we also would have to add those VLANs to the uplink ports and command the other switches to change the target port VLANs as well. If memory serves, you could only command one switch with the JAP control software, which could be a "real" or "virtual" switch. A "real" switch system would be limited to what you could physically stack together (1U switches with stacking cables) or how many cards you could fit in, say, a Cisco 6800 chassis or similar. All of our network cables would have to be home run to that physical switch, which would have been very problematic for us. A "virtual?switch" was also possible, and would allow you to have multiple switch groups to avoid having to home run everything, i.e. the Cisco Nexus line where the core and FEC expanders can all over a site but be seen as one single switch. We'd considered that idea, but found the FEC expanders to be way too loud to be located in conference and training rooms (think Cisco 3850 fans when it first starts up...but ALL the time...yuck). SVSi, Electrosonic/Extron, Evertz, Crestron NVX (which actually wasn't available at the time of our install) and other network protocol streaming products are routed like any other network traffic. I can have all my control devices on VLAN10, streaming devices on VLAN11 and VTC camera/touch panel control on VLAN12, and those assignments never change. Rather than communicating with switches to route things around, we command the decoders directly from the Crestron control system to pull in this or that encoder stream .? If JAP products are now using standard network routing like the SVSi and NVX systems are, rather than changing switch?VLANs, that's great as that would give us another product to consider. If it's still routed via commanding network switches to change VLANs for routing, that's not something that works well for our large systems (and our network departments weren't too keen on that either). Interested in your thoughts, Jeff ------------------------------------- Jeff Klein, DMC-E Head Volunteer AV Geek Faith Baptist Church Glen Burnie, Maryland (Website / Twitter) ?/ @FBC_TechTeam ?/ @mixingforjesus "Clothe yourselves, all of you, with humility toward one another, for God opposes the proud but gives grace to the humble." 1 Peter 5:5 |
|
Loading VT files to CP4
I just ran into an issue when I can load Some VT files into the web/mobility section of a CP4, BUT not others????
Both are iPad/Crestron App files One loads, the other doesn't - both say project successfully loaded but only one shows up in the tool I can load the 'problem' file into a CP3 no problem Anyone else see this issue??? I'm running the latest FW -?v2.7000.00052 TIA! |
|
QSYS with Mat Klucznyk Github
Hello.
I was forced to use the Github QSYS modules. I reached out to Mat Klucznyk on FB but thought I might ask here as I have seen some previous posts. First. I could not get the QSYS 2.21 Modules to work. The Fader MUTE ON worked. but the Toggle and OFF did not work. And when trying to fade up/down it would only move one step and no further.? I rolled back to version 2.0.0 and that seemed to resolve. so not sure if that is a known issue or not.? Second. the CP4 is getting slammed with the following RX Message {"jsonrpc":"2.0","method":"ChangeGroup.Poll","params":{"Id":"1","Changes":[]}}\x00 Is that normal? should I be worried I am going to bog down the processor? Thank you -Scott?? |