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

Onkyo UP-A1
Goto page 1, 2  Next
 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> JP1 - General Forum
View previous topic :: View next topic  
Author Message
jetstar52



Joined: 16 Oct 2003
Posts: 177
Location: Sacramento, CA

                    
PostPosted: Sat Mar 17, 2012 2:00 am    Post subject: Onkyo UP-A1 Reply with quote

I've uploaded an .ict file with learns from an Onkyo UP-A1 iPod dock. I'm trying to make an upgrade for a 15-100 and a 10820n. IRscope recognizes the signals as NEC1-f16 and NEC2-f16, but I can't seem to get either KM or RM to make a working upgrade file. I see that user pjigar tried to make an upgrade a few years back, and eferz posted an RM file, but that file didn't work.

Thanks in advance for any help. The .ict file is:

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=10826
_________________
I used to have 5 remotes that controlled one thing each. Now I have 6 remotes that each control everything!
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3367

                    
PostPosted: Sat Mar 17, 2012 3:11 am    Post subject: Reply with quote

Here's a RMDU file for the UP-A1. You'll need to assign some of the buttons.

The protocol executor I used is NEC1-f16 3Fixed, because all of the signals are device 210.30 with the first OBC = 72. You can see that in IRScope. Only OBC2 varies. Note that this executor has 210.30 as the default, because it is primarily useful with the Onkyo receivers.

If you really need the NEC2 signals (which would repeat while just holding rather than tapping the buttons), we'll need to make a custom executor. That's not too hard.
Back to top
View user's profile Send private message
jetstar52



Joined: 16 Oct 2003
Posts: 177
Location: Sacramento, CA

                    
PostPosted: Sat Mar 17, 2012 4:55 am    Post subject: Reply with quote

Thanks, but uploading the protocol and device upgrade causes my remote to reset with any keypress. Here's the IR file:

http://www.hifi-remote.com/forums/dload.php?action=file&file_id=10828
_________________
I used to have 5 remotes that controlled one thing each. Now I have 6 remotes that each control everything!
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3367

                    
PostPosted: Sat Mar 17, 2012 10:57 am    Post subject: Reply with quote

It works fine with an unextended remote, and the protocol executor has no custom code in it (it just changes the number of fixed bytes). So I doubt that the upgrade is causing the resets.

When I try loading your diag.ir file into either IR or RMIR, both tell me that the upgrade region of memory has overflowed, and asks if I want to relocate some of the upgrades elsewhere. I don't know how either program deals with extenders, but it seem to me that moving the upgrades may overwrite some extender code. I don't know. But it prompted me to look to see if there are any non-used upgrades in the IR file.

Possibly Misc Audio 1011, 1111 and VCR 1533, 2002 are unused? If they are, removing them will save around 200 bytes. Might help.
Back to top
View user's profile Send private message
eferz
Expert


Joined: 03 Jun 2010
Posts: 1078
Location: Austin, Texas

                    
PostPosted: Sat Mar 17, 2012 1:19 pm    Post subject: Reply with quote

jetstar52 wrote:
I see that user pjigar tried to make an upgrade a few years back, and eferz posted an RM file, but that file didn't work.

Thank you for pointing out the issue with one of my upgrades. Though, I didn't know which one you were referring to because my recollections fail of ever creating one for the Onkyo UP-A1. So, I assumed that you were referring to the Onkyo TX-NR807 (2 of 2). After further inspection, I realized an issue was caused after shifting from the NEC1-f16 Official protocol to the NEC1-f16 3Fixed. Remote Master did not retain the OBCs as expected, so I inadvertently uploaded an invalid upgrade and for that I apologize.

The file has been restored in v1.2 with NEC1-f16 Official protocol and the appropriate OBCs if you'd like to test it. However, as 3FG indicated you'll need to address your remote's memory issues first.

3FG wrote:
Here's a RMDU file for the UP-A1. You'll need to assign some of the buttons.

The protocol executor I used is NEC1-f16 3Fixed, because all of the signals are device 210.30 with the first OBC = 72. You can see that in IRScope. Only OBC2 varies. Note that this executor has 210.30 as the default, because it is primarily useful with the Onkyo receivers.

I tried fixing my upgrade to use the NEC1-f16 3Fixed protocol but it ends up shooting <unknown> signals according to IR Scope & Widget. I even tried using your upgrade as well and it does the same thing. For some odd reason, only the NEC1-f16 Official protocol shoots out the expected results. That's why I restored my version of the upgrade to the official instead of 3fixed.

I've uploaded my file here for analysis.
_________________
Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)
Back to top
View user's profile Send private message
jetstar52



Joined: 16 Oct 2003
Posts: 177
Location: Sacramento, CA

                    
PostPosted: Sat Mar 17, 2012 1:31 pm    Post subject: Reply with quote

3FG:
I think you're right. I loaded your upgrade into an unextended 15-133, and everything worked. Thanks very much for your help. I'll try to see what's going on with the 15-100.

How did you come up with the EFC values? They're different from the IRscope readings.

eferz:
Yes, the Onkyo TX-NR807 (2 of 2) is the one I tried. I'll test the modified version in a 15-133 to see if it works.
_________________
I used to have 5 remotes that controlled one thing each. Now I have 6 remotes that each control everything!
Back to top
View user's profile Send private message
eferz
Expert


Joined: 03 Jun 2010
Posts: 1078
Location: Austin, Texas

                    
PostPosted: Sat Mar 17, 2012 1:49 pm    Post subject: Reply with quote

jetstar52 wrote:
How did you come up with the EFC values? They're different from the IRscope readings.

In most cases the OBC > EFC, especially when using custom protocols. This is because the EFC values are dependent on the protocol and its fixed data. So, if you're creating an upgrade with different specifications then EFCs are useless. It is better to stick with the OBC values when creating upgrades and EFCs when manually programming your remote.

I believe he propagated the OBC column in Functions tab of RM with the OBC2 values from IR Scope's Notes column instead. The 3Fixed version has three protocol arguments; device 1, 2, and 3. Therefore, they respectively address device, sub-device, and OBC1. This leaves the OBC column in the function tab open for OBC2's.

jetstar52 wrote:
Yes, the Onkyo TX-NR807 (2 of 2) is the one I tried. I'll test the modified version in a 15-133 to see if it works.

Thanks. I'll be glad to hear the feedback.
_________________
Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3367

                    
PostPosted: Sat Mar 17, 2012 2:55 pm    Post subject: Reply with quote

eferz,
I think you're the first person to try the f16 3 Fixed using a HCS08. There is an error in protocols.ini, which leads to all three fixed data bytes being sent with zero bits per byte. Please change:
Code.HCS08=20 15 23 46 31 C7 45 00 08 01 21 01 11 01 21 03 44 D2 DC 11 94 08 CA CC FF 5F
to
Code.HCS08=20 15 23 46 31 C7 45 08 08 01 21 01 11 01 21 03 44 D2 DC 11 94 08 CA CC FF 5F

If we can get 3 Fixed to work, it will save a lot of space (roughly 3 bytes per function used in the remote.)
Back to top
View user's profile Send private message
eferz
Expert


Joined: 03 Jun 2010
Posts: 1078
Location: Austin, Texas

                    
PostPosted: Sat Mar 17, 2012 5:14 pm    Post subject: Reply with quote

3FG wrote:
eferz,
I think you're the first person to try the f16 3 Fixed using a HCS08. There is an error in protocols.ini, which leads to all three fixed data bytes being sent with zero bits per byte. Please change:
Code.HCS08=20 15 23 46 31 C7 45 00 08 01 21 01 11 01 21 03 44 D2 DC 11 94 08 CA CC FF 5F
to
Code.HCS08=20 15 23 46 31 C7 45 08 08 01 21 01 11 01 21 03 44 D2 DC 11 94 08 CA CC FF 5F

If we can get 3 Fixed to work, it will save a lot of space (roughly 3 bytes per function used in the remote.)

I implemented the changes as you instructed and the OBCs are now equivalent to to its official counterpart. However, now the protocol of the new IR signals are being decoded as NEC2-f16 instead of NEC1-f16.
_________________
Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3367

                    
PostPosted: Sat Mar 17, 2012 5:48 pm    Post subject: Reply with quote

Well, now that you point it out, the executor I've called NEC1-f16 3Fixed does in fact shoot NEC2. We actually need a more complicated executor to send the dittos used by NEC1.

I think it is probably OK to just rename the executor. It seems like most equipment these days is happy with either format. We could also consider a combo executor which could shoot either NEC1 or NEC2, but of course that will need two command bytes.

jetstar52, does the 3Fixed executor work for all your buttons?
Back to top
View user's profile Send private message
jetstar52



Joined: 16 Oct 2003
Posts: 177
Location: Sacramento, CA

                    
PostPosted: Sun Mar 18, 2012 12:40 am    Post subject: Reply with quote

Quote:
jetstar52, does the 3Fixed executor work for all your buttons?

Yes! The upgrade works fine in an unextended 15-133. Thank you again so much!
Quote:
I implemented the changes as you instructed and the OBCs are now equivalent to to its official counterpart.

What do I need to replace to get the correct HCSO8 protocol?
Quote:
I believe he propagated the OBC column in Functions tab of RM with the OBC2 values from IR Scope's Notes column instead. The 3Fixed version has three protocol arguments; device 1, 2, and 3. Therefore, they respectively address device, sub-device, and OBC1. This leaves the OBC column in the function tab open for OBC2's.

I'm still not grasping it Embarassed . For example, IRscope reads the display key as: device 210.30, OBC 72 and hex 12, with D2.1E.48.48 in the Misc. column. But the OBC in the upgrade is hex ED.
_________________
I used to have 5 remotes that controlled one thing each. Now I have 6 remotes that each control everything!
Back to top
View user's profile Send private message
eferz
Expert


Joined: 03 Jun 2010
Posts: 1078
Location: Austin, Texas

                    
PostPosted: Sun Mar 18, 2012 1:07 am    Post subject: Reply with quote

jetstar52 wrote:
What do I need to replace to get the correct HCSO8 protocol?

You're actually setting the correct assembly code of the "NEC1-f16 3Fixed" protocol for the HCS08 processor. Well, technically the "NEC2-f16 3Fixed" protocol but that's for 3FG to follow up on. Anyways, go into your Remote Master directory, inside of it will be the protocol.ini file which defines the different protocol initializations. Open the file in an editor, like Notepad, then navigate to the [NEC1-f16 3Fixed] section where you will see the following line below:
bad line in protocol.ini wrote:
Code.HCS08=20 15 23 46 31 C7 45 00 08 01 21 01 11 01 21 03 44 D2 DC 11 94 08 CA CC FF 5F

and it should be changed to

good line in protocol.ini wrote:
Code.HCS08=20 15 23 46 31 C7 45 08 08 01 21 01 11 01 21 03 44 D2 DC 11 94 08 CA CC FF 5F

Btw, this will not affect your RS 15-100 remote since it uses a S3F8 processor.


jetstar52 wrote:
I'm still not grasping it Embarassed . For example, IRscope reads the display key as: device 210.30, OBC 72 and hex 12, with D2.1E.48.48 in the Misc. column. But the OBC in the upgrade is hex ED.

Perhaps you need to update IR Scope? Here's a screenshot of what I see.

_________________
Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3367

                    
PostPosted: Sun Mar 18, 2012 1:49 am    Post subject: Reply with quote

I think the display of the Misc column is set in this case by DecodeIR.dll. jetstar52, make sure you have version 2.43 in your IRScope directory.
Back to top
View user's profile Send private message
jetstar52



Joined: 16 Oct 2003
Posts: 177
Location: Sacramento, CA

                    
PostPosted: Sun Mar 18, 2012 3:10 am    Post subject: Reply with quote

Okay, updated my DecodeIR, and now IRscope gives me the OBC2 values. Edited the HCS08 protocol, and now I have an upgrade for the 10820n.

You guys are geniuses, and incredibly generous. Thanks once again.
_________________
I used to have 5 remotes that controlled one thing each. Now I have 6 remotes that each control everything!
Back to top
View user's profile Send private message
3FG
Expert


Joined: 19 May 2009
Posts: 3367

                    
PostPosted: Sun Mar 18, 2012 12:58 pm    Post subject: Reply with quote

Earl,
I was wrong; the IR engine can send dittos without any special executor code. So the below protocols.ini entry can send either NEC1 or NEC2, selectable by the user. If you have time, please check the HCS08 functionality.
Code:

[NEC-f16 3Fixed]
PID=00 0F
CmdParms=OBC
CmdTranslator=Translator(comp,lsb,0)
DefaultCmd=00
DevParms=Device1:8=210, Device2:8=30, Device3:8=80, Style=0:NEC1|NEC2
DeviceTranslator=Translator(comp,lsb,0,8,0) Translator(comp,lsb,1,8,8) Translator(comp,lsb,2,8,16)
FixedData=B4 87 F5
CodeTranslator.S3C80=Translator(comp,3,1,52)
CodeTranslator.HCS08=Translator(comp,3,1,52)
Notes= Useful if the device.subdevice and the first command byte (Device 3) remain constant for the entire upgrade.  Use NEC1-f16 Official if more flexibility is needed.
Code.S3C80=43 8B 31 8B 12 C7 4D 08 08 01 21 00 FD 01 21 03 30 D2 DC 11 94 08 B6 8D 01 46
Code.HCS08=20 15 23 46 31 C7 4D 08 08 01 21 01 11 01 21 03 44 D2 DC 11 94 08 CA CC FF 5F


Note that RMIR apparently won't allow one to use two instances of these executors with one set up for NEC1 and the other set up for NEC2, because the PIDs would need to be different, and I don't see a way to change the PID for the second instance.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic       JP1 Remotes Forum Index -> JP1 - General Forum All times are GMT - 5 Hours
Goto page 1, 2  Next
Page 1 of 2

 
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
Top 7 Advantages of Playing Online Slots The Evolution of Remote Control