KeithL
Administrator 
Posts: 10,247
|
Post by KeithL on Mar 6, 2022 20:18:41 GMT -5
The maximum output current available from the Trigger Outputs is a hardware limitation. Therefore it should not have changed due to a firmware update.
70 mA is a pretty heavy current demand for a trigger input on modern gear...
Inductive loads like relay coils, and inputs with large smoothing capacitors, can both be difficult to drive...
And either can also sometimes trip the overcurrent protection on our trigger outputs even if their steady state current requirement is within our capabilities...
(Most modern gear draws somewhere around 20 mA - noninductive) But, again, that shouldn't have changed due to a firmware update.
This is the response I got from Buckeye in regards to my trigger issue: "I did some quick searching and found in the RMC-1 owners thread on Emotiva that there is a known "short coming" that it seems the RMC-1 triggers do not have either enough juice or are very sensitive to inductive loads generated by traditional mechanical relays (like the ones my amps use). Seems to be a problem especially for people trying to trigger sub amps." "I would suggest getting their 12v trigger module that takes a trigger signal and beefs it up before sending it on to the amps." Part of the response above was removed due to their personal interaction with Emotiva. I did order the Emo ET-3 Trigger Expansion Module as suggested. Hope that does the trick because I really like the Buckey amps I got. I do seem to recall now some discussion about the Emo triggers but do not remember myself what the complete discussion or outcome was. Take care. Per my previous query to Emotiva tech support, the XMC-2 triggers are rated for 80 mA each. So that’s 80mA x 4. My 2 Buckeye amps are rated at 70 mA each and worked flawlessly with a separate trigger out from the XMC-2 for each amp under firmware 2.3. When I moved away from the XMC-2 I bought the Emo ET-3, which also works fine with the Buckeyes. |
|
|
|
Post by Thunderduck on Mar 6, 2022 20:27:24 GMT -5
The maximum output current available from the Trigger Outputs is a hardware limitation. Therefore it should not have changed due to a firmware update.
70 mA is a pretty heavy current demand for a trigger input on modern gear...
Inductive loads like relay coils, and inputs with large smoothing capacitors, can both be difficult to drive...
And either can also sometimes trip the overcurrent protection on our trigger outputs even if their steady state current requirement is within our capabilities...
(Most modern gear draws somewhere around 20 mA - noninductive) But, again, that shouldn't have changed due to a firmware update.
Per my previous query to Emotiva tech support, the XMC-2 triggers are rated for 80 mA each. So that’s 80mA x 4. My 2 Buckeye amps are rated at 70 mA each and worked flawlessly with a separate trigger out from the XMC-2 for each amp under firmware 2.3. When I moved away from the XMC-2 I bought the Emo ET-3, which also works fine with the Buckeyes. Keith, will the ET-3 fix my issue with the trigger outputs on my RMC-1 not apparently being able to power on my amps? Thank you. |
|
|
|
Post by 5channels on Mar 6, 2022 20:32:06 GMT -5
Do the triggers get disabled if you do a Factory Reset as part of the FW upgrade?
|
|
|
|
Post by jbrunwa on Mar 6, 2022 20:58:58 GMT -5
The maximum output current available from the Trigger Outputs is a hardware limitation. Therefore it should not have changed due to a firmware update.
70 mA is a pretty heavy current demand for a trigger input on modern gear...
Inductive loads like relay coils, and inputs with large smoothing capacitors, can both be difficult to drive...
And either can also sometimes trip the overcurrent protection on our trigger outputs even if their steady state current requirement is within our capabilities...
(Most modern gear draws somewhere around 20 mA - noninductive) But, again, that shouldn't have changed due to a firmware update.
Per my previous query to Emotiva tech support, the XMC-2 triggers are rated for 80 mA each. So that’s 80mA x 4. My 2 Buckeye amps are rated at 70 mA each and worked flawlessly with a separate trigger out from the XMC-2 for each amp under firmware 2.3. When I moved away from the XMC-2 I bought the Emo ET-3, which also works fine with the Buckeyes. Is the trigger circuitry in the RMC-1 the same as the XMC-2? If so, It should handle the Buckeye amps as long as you don’t try to drive more than one amp per trigger output. |
|
|
|
Post by Thunderduck on Mar 6, 2022 21:05:37 GMT -5
Just FYI, I was using Trigger 1 for the amp driving the 3 front speakers and Trigger 2 to power on sides, back surrounds as well as my 4 ceiling speakers.
|
|
|
|
Post by trevorlj on Mar 7, 2022 11:49:19 GMT -5
Just as a datapoint...I have a RMC-1L triggering 2x 8-Channel Buckeye amps. No issues here kicking em' on with individual triggers.
|
|
|
|
Post by Thunderduck on Mar 7, 2022 11:55:27 GMT -5
Just as a datapoint...I have a RMC-1L triggering 2x 8-Channel Buckeye amps. No issues here kicking em' on with individual triggers. Don't understand why others are having no issue triggering their Buckeye amps on when I can't get mine to work. I do have the trigger rocker switches on the back of the amps in the "O" position as instructed. Will keep trying. |
|
cawgijoe
Emo VIPs 
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,032
|
Post by cawgijoe on Mar 7, 2022 12:06:56 GMT -5
Just as a datapoint...I have a RMC-1L triggering 2x 8-Channel Buckeye amps. No issues here kicking em' on with individual triggers. Don't understand why others are having no issue triggering their Buckeye amps on when I can't get mine to work. I do have the trigger rocker switches on the back of the amps in the "O" position as instructed. Will keep trying. Maybe you guys can compare notes on how everything is hooked up and operated to figure out what is causing the triggering issue? Just an idea...hopefully it's something simple. |
|
|
|
Post by cwmcobra on Mar 7, 2022 12:22:12 GMT -5
The system has been working fine with a single video source, my Sony disc player configured on HDMI 1 of the XMC-2. The XMC-2 is connected to the JVC RS2100 projector with a certified 8K fiber optic HDMI cable. Today I added a Dish receiver to the system and can't get it to work reliably. Audio works fine, but video hardly works at all. Flashes on and off a few times and then seems to stay off. If I connect the Dish receiver directly to the projector, it works fine. So it seems something in the XMC is not playing nice with the Dish receiver. I've played with settings for the HDMI 2 input on the XMC and changed the HDMI EDID setting int the projector to "B". Nothing has solved the problem yet. Do I need an HDMI switch between the XMC and projector? Something to straighten out the HDMI interface? I've seen the HDFury thread; is this something I need to consider? Are others having problems with Dish receivers? Thanks, Chuck I played with this a lot yesterday and concluded that there is something about the Dish receiver HDMI signal that the XMC-2 doesn't like. So I have run the HDMI output from the Dish receiver directly to HDMI 2 input on the projector. And get digital audio through the XMC-2 using the Optical connection. Watched a couple hours of TV last night without any hiccups. Looks like this will be a permanent workaround. |
|
|
|
Post by hsamwel on Mar 7, 2022 15:10:43 GMT -5
Just as a datapoint...I have a RMC-1L triggering 2x 8-Channel Buckeye amps. No issues here kicking em' on with individual triggers. Don't understand why others are having no issue triggering their Buckeye amps on when I can't get mine to work. I do have the trigger rocker switches on the back of the amps in the "O" position as instructed. Will keep trying. How is your triggers setup in the prepro? As I wrote before there seem to be a bug which if you don’t set either (or both) fronts or subwoofer in the trigger/speakers it won’t trigger at all. |
|
|
|
Post by Thunderduck on Mar 7, 2022 16:33:49 GMT -5
Don't understand why others are having no issue triggering their Buckeye amps on when I can't get mine to work. I do have the trigger rocker switches on the back of the amps in the "O" position as instructed. Will keep trying. How is your triggers setup in the prepro? As I wrote before there seem to be a bug which if you don’t set either (or both) fronts or subwoofer in the trigger/speakers it won’t trigger at all. Trigger 1 and 2 are setup in the RMC as follows: Power: Main Zone only Input: All Inputs selected Speakers: Heights, Center, Fronts, Subwoofer, Rears, Surrounds all selected Headphone: Override selected In the Input section of the Main Menu, all of the Inputs have Speaker Preset set as Preset 1 Can't think of any other area to check. I am currently on firmware 2.5. I am going to refert to version 2.3/3. See what that does if anything. Was original on 2.3 when this issue started with my installing the RMC into the system. |
|
|
|
Post by doc1963 on Mar 7, 2022 16:53:33 GMT -5
How is your triggers setup in the prepro? As I wrote before there seem to be a bug which if you don’t set either (or both) fronts or subwoofer in the trigger/speakers it won’t trigger at all. Trigger 1 and 2 are setup in the RMC as follows: Power: Main Zone only Input: All Inputs selected Speakers: Heights, Center, Fronts, Subwoofer, Rears, Surrounds all selected Headphone: Override selected In the Input section of the Main Menu, all of the Inputs have Speaker Preset set as Preset 1 Can't think of any other area to check. I am currently on firmware 2.5. I am going to refert to version 2.3/3. See what that does if anything. Was original on 2.3 when this issue started with my installing the RMC into the system. Those settings seem valid and should work. My triggers work fine (and always have) and I'm currently on firmware v2.5. So reverting back might be fruitless. It might seem obvious, but I'm going to ask anyway... are your trigger cables "mono"...? If so, have you tried different cables that might seat better...? |
|
|
|
Post by Thunderduck on Mar 7, 2022 17:09:27 GMT -5
Trigger 1 and 2 are setup in the RMC as follows: Power: Main Zone only Input: All Inputs selected Speakers: Heights, Center, Fronts, Subwoofer, Rears, Surrounds all selected Headphone: Override selected In the Input section of the Main Menu, all of the Inputs have Speaker Preset set as Preset 1 Can't think of any other area to check. I am currently on firmware 2.5. I am going to refert to version 2.3/3. See what that does if anything. Was original on 2.3 when this issue started with my installing the RMC into the system. Those settings seem valid and should work. My triggers work fine (and always have) and I'm currently on firmware v2.5. So reverting back might be fruitless. It might seem obvious, but I'm going to ask anyway... are your trigger cables "mono"...? If so, have you tried different cables that might seat better...? Yes, the cables are mono. I have some different cables I can try. Just have to dig them out. Just want to point out that when I power the amps on manually everything works fine. Just getting those darn things to turn on is the trick. Will try different cables and let you know the results. Really appreciate everyones help. |
|
|
|
Post by ElectricKoolAid on Mar 7, 2022 17:23:04 GMT -5
It would be a major bummer if Buckeye amps didn't work with the Emo triggers as those are the amps I'm planning to upgrade to in the future!
|
|
|
|
Post by Thunderduck on Mar 7, 2022 17:34:14 GMT -5
It would be a major bummer if Buckeye amps didn't work with the Emo triggers as those are the amps I'm planning to upgrade to in the future! As noted by trevorlj in a post above, his RMC1L and 2 Buckeye amps are working fine. I do not believe you have anything to worry about. Just something about my units that do not like each other. Will keep trying and thanks once more for alls help. |
|
|
|
Post by Thunderduck on Mar 7, 2022 17:38:04 GMT -5
Trigger 1 and 2 are setup in the RMC as follows: Power: Main Zone only Input: All Inputs selected Speakers: Heights, Center, Fronts, Subwoofer, Rears, Surrounds all selected Headphone: Override selected In the Input section of the Main Menu, all of the Inputs have Speaker Preset set as Preset 1 Can't think of any other area to check. I am currently on firmware 2.5. I am going to refert to version 2.3/3. See what that does if anything. Was original on 2.3 when this issue started with my installing the RMC into the system. Those settings seem valid and should work. My triggers work fine (and always have) and I'm currently on firmware v2.5. So reverting back might be fruitless. It might seem obvious, but I'm going to ask anyway... are your trigger cables "mono"...? If so, have you tried different cables that might seat better...? Just a thought. Since the Trigger 1 amp is only powering the fronts and center, should I just Trigger 1 to power on only those speakers and Trigger 2 the rest? Almost seems like there should be some way to select both triggers at the same time. May be way off base with this so will not take it wrong if you tell me what an idiotic idea. :-) |
|
|
|
Post by doc1963 on Mar 7, 2022 17:40:09 GMT -5
It would be a major bummer if Buckeye amps didn't work with the Emo triggers as those are the amps I'm planning to upgrade to in the future! I’ve been looking at them too and, from what I’ve read, Dylan will be using a newly designed input board that requires much less current to trigger them on (30 mA versus 70 mA). But as also been mentioned above, there are others using Buckeye amps with their Emo G3 processors without issue. This might just be an odd case… |
|
|
|
Post by doc1963 on Mar 7, 2022 17:51:08 GMT -5
Those settings seem valid and should work. My triggers work fine (and always have) and I'm currently on firmware v2.5. So reverting back might be fruitless. It might seem obvious, but I'm going to ask anyway... are your trigger cables "mono"...? If so, have you tried different cables that might seat better...? Just a thought. Since the Trigger 1 amp is only powering the fronts and center, should I just Trigger 1 to power on only those speakers and Trigger 2 the rest? Almost seems like there should be some way to select both triggers at the same time. May be way off base with this so will not take it wrong if you tell me what an idiotic idea. :-) Those settings use the incoming signal as a reference to determine whether that particular trigger is deployed or not. If you want both amplifiers to turn on regardless of what “speakers” are used based upon the type of signal, then leave them all selected. Since I have separate two channel and 9 channel amps, I configure my triggers based upon the inputs. 2-channel inputs only use trigger 1 (where my 2 channel amp is connected) and all multichannel inputs use both triggers. Since my subwoofers are always used, one is connected to the trigger output of my XPA-DR2 and then daisy chained between the two subwoofers. |
|
|
|
Post by Thunderduck on Mar 7, 2022 18:02:28 GMT -5
Just a thought. Since the Trigger 1 amp is only powering the fronts and center, should I just Trigger 1 to power on only those speakers and Trigger 2 the rest? Almost seems like there should be some way to select both triggers at the same time. May be way off base with this so will not take it wrong if you tell me what an idiotic idea. :-) Those settings use the incoming signal as a reference to determine whether that particular trigger is deployed or not. If you want both amplifiers to turn on regardless of what “speakers” are used based upon the type of signal, then leave them all selected. Since I have separate two channel and 9 channel amps, I configure my triggers based upon the inputs. 2-channel inputs only use trigger 1 (where my 2 channel amp is connected) and all multichannel inputs use both triggers. Since my subwoofers are always used, one is connected to the trigger output of my XPA-DR2 and then daisy chained between the two subwoofers. Just was grasping at straws. Will leave settings as is. If there is some issue with the current it takes to trigger the amps, will the ET-3 that I ordered help in that regard or is it just a waste? |
|
|
|
Post by Thunderduck on Mar 7, 2022 18:30:45 GMT -5
Those settings seem valid and should work. My triggers work fine (and always have) and I'm currently on firmware v2.5. So reverting back might be fruitless. It might seem obvious, but I'm going to ask anyway... are your trigger cables "mono"...? If so, have you tried different cables that might seat better...? Yes, the cables are mono. I have some different cables I can try. Just have to dig them out. Just want to point out that when I power the amps on manually everything works fine. Just getting those darn things to turn on is the trick. Will try different cables and let you know the results. Really appreciate everyones help. Tried different cables with no luck. However, there is another issue I have been having since putting the RMC back into the system that I did not include before because I did not think it could apply. I still be it doesn't but will describe what it is. The unit had firmware ver 2.3/3 when I started using it again. I normally have Video Remains On selected as I did at this time. The issue is that when the RMC is off for any length of time, when I turn the tv on there is no video. I need to reselect the tv HDMI input in order to get the video to come. After this is done, things will be ok as long as I don't turn the RMC and tv off for several hours. If I do, especially overnight, I will not get any video when I first turn on the tv. I updated to ver 2.5 firmware to see if that would help put still have the issue. With this video issue and the trigger issue I am thinking that there is something else going on with my RMC. It may take a trip back "home" to have it looked at there. Really think that is about it for solving this here. I hate to take up to much space and time with these issues. Thanks for the help/suggestions from you all. Take care. |
|
