JP1 Remotes Forum Index JP1 Remotes


FAQFAQ SearchSearch 7 days of topics7 Days MemberlistMemberlist UsergroupsUsergroups RegisterRegister
ProfileProfile Log in to check your private messagesLog in to check your private messages Log inLog in

Emotiva UMC-200 or Emotiva Fusion 8100

 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> Code Search
View previous topic :: View next topic  
Author Message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Wed Dec 03, 2014 1:58 pm    Post subject: Emotiva UMC-200 or Emotiva Fusion 8100 Reply with quote

Subject: Emotiva Fusion 8100

1. Device: Emotiva UMC-200, Emotiva Fusion 8100 should also work
2. Type of device: A/V Receiver
3. Year: 2013
4. JP1/UEI Remote model: RCRP05BR
5. Do you have a JP1 cable? Yes
6. Still have original remote? Yes
7. Checked the file section? Yes (Only an older Emotiva receiver exists)
8. Checked Pronto file section (at R/C)? Yes (no Emotiva devices listed)
9. Partially working setup code? No
10. Learning remote question? n/a
11. Have you tried the JP1 Lookup Tool? Yes, but only found older Emotiva receiver.

I tought the RCRP05BR all the commands I need from the original Emotiva Fusion 1 remote, clicked "Convert to Device Upgrade". Seemed like it worked but when I deleted all my learned functions the upgrade didn't work. I must be missing something or doing something wrong.

Any help much appreciated, thanks.


RMDU

Code:
Description=UMC-200 - Emotiva Fusion 8100
Remote.name=RCA RCRP05B black
Remote.signature=31793179
Notes=Device Upgrade automatically created by RemoteMaster from 28 Learned Signals all with protocol NEC1, device 174, subdevice 134.
DeviceType=Tuner
DeviceIndex=3
SetupCode=2002
Protocol=00 5A
Protocol.name=NEC1
ProtocolParms=174 134 0
FixedData=00 8A 9E
Notes=Device Upgrade automatically created by RemoteMaster from 28 Learned Signals all with protocol NEC1, device 174, subdevice 134.
Function.0.name=Mute
Function.0.hex=AD
Function.1.name=Ok
Function.1.hex=E7
Function.2.name=Left
Function.2.hex=17
Function.3.name=Right
Function.3.hex=CF
Function.4.name=Up
Function.4.hex=97
Function.5.name=Down
Function.5.hex=B7
Function.6.name=Menu
Function.6.hex=57
Function.7.name=Info
Function.7.hex=6D
Function.8.name=Guide
Function.8.hex=F5
Function.9.name=Exit
Function.9.hex=4D
Function.10.name=Vol+
Function.10.hex=2D
Function.11.name=Vol-
Function.11.hex=0D
Function.12.name=Ch+
Function.12.hex=7F
Function.13.name=Ch-
Function.13.hex=87
Function.14.name=Power
Function.14.hex=F7
Function.15.name=Live
Function.15.hex=BF
Function.16.name=Page+
Function.16.hex=5D
Function.17.name=Page-
Function.17.hex=ED
Function.18.name=Day+
Function.18.hex=A5
Function.19.name=Day-
Function.19.hex=FD
Function.20.name=PIP_Ch+
Function.20.hex=67
Function.21.name=PIP_Ch-
Function.21.hex=77
Function.22.name=1
Function.22.hex=3F
Function.23.name=2
Function.23.hex=DF
Function.24.name=3
Function.24.hex=5F
Function.25.name=4
Function.25.hex=C7
Function.26.name=5
Function.26.hex=07
Function.27.name=AUD
Function.27.hex=C7
Button.15=1|null|null
Button.16=2|null|null
Button.17=3|null|null
Button.19=4|null|null
Button.1a=5|null|null
Button.4=Vol+|null|null
Button.5=Vol-|null|null
Button.33=Mute|null|null
Button.6=Ch+|null|null
Button.7=Ch-|null|null
Button.3=Power|null|null
Button.2e=Menu|null|null
Button.2d=Ok|null|null
Button.29=Up|null|null
Button.2a=Down|null|null
Button.2b=Left|null|null
Button.2c=Right|null|null
Button.14=Exit|null|null
Button.13=Info|null|null
Button.21=Guide|null|null
Button.23=Page+|null|null
Button.24=Page-|null|null
Button.2f=Live|null|null
Button.31=Day+|null|null
Button.32=Day-|null|null
Button.3b=PIP_Ch+|null|null
Button.3c=PIP_Ch-|null|null
Button.11=AUD|null|null


The HEX from Emotiva:
http://emotiva.com/resources/media/umc200/remote_codes.pdf

[/code]
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3219

PostPosted: Wed Dec 03, 2014 3:37 pm    Post subject: Reply with quote

The decodes of the Pronto Hex given for the Emotiva UMC-200 are NEC1 device 32, subdevice 95. Try replacing 174.134 with 32.95 in your upgrade.
Back to top
View user's profile Send private message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Wed Dec 03, 2014 7:21 pm    Post subject: Reply with quote

3FG wrote:
The decodes of the Pronto Hex given for the Emotiva UMC-200 are NEC1 device 32, subdevice 95. Try replacing 174.134 with 32.95 in your upgrade.

Not working
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3219

PostPosted: Wed Dec 03, 2014 7:59 pm    Post subject: Reply with quote

If you have a OEM remote that does control your Emotiva, learn the signals, verify that the learns work, and then upload the RMIR file which contains the learns. That way we can exclude the conversion to an upgrade.
Also, do you have a UMC-200 or a Fusion 8100?
Back to top
View user's profile Send private message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Wed Dec 03, 2014 9:40 pm    Post subject: Reply with quote

I have the Fusion 8100 with the OEM remote and learning works. Tomorrow I'll create a fresh RMIR with all the learns.

And my mistake, I thought the UMC-200 and Fusion used the same remote... programmed both on a Harmony 600 and the UMC-200 does not work for the Fusion.

Thanks for all your help.

Jim
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3219

PostPosted: Wed Dec 03, 2014 11:42 pm    Post subject: Reply with quote

I checked the GlobalCache Control Tower database and it appears that indeed the Fusion Series uses NEC1 174.134. I quickly checked Mute and Vol+, and these functions agreed with the Hex in the OP.

So we are likely looking for something that went wrong with the upgrade, rather than the learned signals.
Back to top
View user's profile Send private message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Thu Dec 04, 2014 12:30 am    Post subject: Reply with quote

Maybe I'm doing something wrong.

I'm using:
Remote Master v2.03 Alpha 25e
31793179 (RCA RCRP05B black).rdf
RCRP05B.map

Under Learned Signals I select all of the Fusion commands (AUD) and click the "Convert to Device Upgrade". Then I edit the Device, changed "Description", changed "Device Type" to Tuner, changed "Setup Code" to 2002, then Save as EmotivaFusion8100.rmdu
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3219

PostPosted: Thu Dec 04, 2014 1:53 am    Post subject: Reply with quote

That all seems correct. I own a RCRP05B, and also a IR Widget. If you post your RMIR file, I'll load it into my remote and see what IR signal it is sending.
Back to top
View user's profile Send private message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Thu Dec 04, 2014 5:19 am    Post subject: Reply with quote

http://www.eplanetdesign.com/EmoFusion.zip

This includes an RMIR with the learned commands, the Fusion is all AUD, it also includes the Fusion RMDU, that way I think you should be able to compare the learned signals against the upgrade signals.



Thanks
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3219

PostPosted: Thu Dec 04, 2014 11:21 am    Post subject: Reply with quote

Jim,
Here's what I'd like to see: A RMIR file without learns which does have your Fusion upgrade. I believe that's the configuration which doesn't work, and so that's the RMIR file which we can diagnose.
Back to top
View user's profile Send private message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Thu Dec 04, 2014 12:55 pm    Post subject: Reply with quote

No learns.

http://www.eplanetdesign.com/0022.zip
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3219

PostPosted: Fri Dec 05, 2014 2:02 am    Post subject: Reply with quote

The 0022 RMIR file actually has the incorrect device.subdevice numbers, but that isn't the real problem. The 0020 RMIR file would work even after deleting the learns except that RMIR has a bug related to NEC IR protocols. This bug is causing your remote to shoot NEC1 device 174 (shorthand for 174.81) instead of the desired and indicated 174.134.

It's easy to work around. Open the 2002 device upgrade, and on the Setup tab delete the 0 entered in the Parm field, leaving a blank field. When you do that the Fixed data will change from 00 8A 9E to 20 8A 9E. Save this RMDU file, delete the learns and upload to the remote.
Back to top
View user's profile Send private message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Fri Dec 05, 2014 9:49 am    Post subject: Reply with quote

Works perfect!

Thank you, thank you!
Back to top
View user's profile Send private message
Jim-W



Joined: 15 Nov 2014
Posts: 50
Location: Dallas, TX

PostPosted: Mon Dec 08, 2014 6:34 am    Post subject: Reply with quote

Created a complete organized upgrade and posted.

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=12980

Thanks again
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> Code Search All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

Powered by phpBB © 2001, 2005 phpBB Group
Get Smart! the band's official homepage Rockabilly Central