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

PID $016C: XMP Protocol
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10
 
Post new topic   Reply to topic    JP1 Remotes Forum Index -> JP1 - Software
View previous topic :: View next topic  
Author Message
The Robman
Site Owner


Joined: 01 Aug 2003
Posts: 21237
Location: Chicago, IL

                    
PostPosted: Sun Jul 04, 2010 6:30 pm    Post subject: Reply with quote

I'll take a look, but be aware that there is the potential for cases when the user will need to use the UEI version even if they don't have it resident, and that's if we ever see a device that uses both OBC bytes at the same time.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Back to top
View user's profile Send private message Visit poster's website
alanrichey
Expert


Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA

                    
PostPosted: Sun Jul 25, 2010 3:56 pm    Post subject: Reply with quote

Just a passing comment, but having said that all my XMP created BIN files are working I have found one anomaly.

When we originally built a working Slingbox Custom Remote for the Dreambox DM Series we used PID: 01 6C and fixed data of 0E 0F 44 1A (provided by Rob I think)

Now, when I install any of the Dreambox DM boxes onto my Harmony and learn the codes, IRScope gives me 'XMP-1' with device 26. Now when I enter those values into Remotemaster I obviously get the right Protocol ID of 01 6C, but the fixed data shows up as 1D 0F 44 1A 1F 00 40. And the remote does NOT work in real life, sending the wrong signals.

Please don't waste any time on this, as we already have a working system, but maybe it might be of academic interest to someone, as there does seem to be an error somewhere Laughing

Al
Back to top
View user's profile Send private message
The Robman
Site Owner


Joined: 01 Aug 2003
Posts: 21237
Location: Chicago, IL

                    
PostPosted: Sun Jul 25, 2010 8:42 pm    Post subject: Reply with quote

You're missing the sub-device, which is zero, if you enter that you'll get the correct hex code. So the question is, did IRScope give you a sub-device and you just missed it (the device code should have been shown to you as 26.0), or did it not give you the sub-device at all? If it's the latter, we'll need to get Graham to take a look at it.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Back to top
View user's profile Send private message Visit poster's website
alanrichey
Expert


Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA

                    
PostPosted: Sun Jul 25, 2010 9:08 pm    Post subject: Reply with quote

My fault, as usual Smile IRScope does give 26.0.

I keep learning, I have to admit I always assumed that a zero sub-device could be left as blank. Don't recall it ever causing a problem before.

I still get a slightly different fixed data, with 3 extra bytes at the end but I assume they aren't essential ?

Thanks for setting me straight

Al
Back to top
View user's profile Send private message
The Robman
Site Owner


Joined: 01 Aug 2003
Posts: 21237
Location: Chicago, IL

                    
PostPosted: Mon Jul 26, 2010 7:51 am    Post subject: Reply with quote

The problem is that the default sub-device isn't 0, so if you leave it blank, you'll get a different value. The extra 3 bytes are for the JP1 version of the protocol (ie, the version that we wrote specifically so that it would fit in the Slingbox). If you switch to the UEI version, you'll just see 4 bytes (but it won't work in the Slingbox).
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Back to top
View user's profile Send private message Visit poster's website
alanrichey
Expert


Joined: 24 Mar 2008
Posts: 3529
Location: UK/USA

                    
PostPosted: Mon Jul 26, 2010 8:30 am    Post subject: Reply with quote

OK, I remember we had to apply that 'fiddle factor' to device numbers before you got the proper implementation. Makes sense now.
Back to top
View user's profile Send private message
ElizabethD
Advanced Member


Joined: 09 Feb 2004
Posts: 2348

                    
PostPosted: Sun Aug 22, 2010 11:02 pm    Post subject: Reply with quote

I just posted about what I think is a problem with this protocol - it does not see 2 signals when the same code is sent in a macro (e.g. channel 22)
http://www.hifi-remote.com/forums/viewtopic.php?p=90167#90167
and also that thread mentions that the signal doesn't repeat in a macro.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride Smile
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 - Software All times are GMT - 5 Hours
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Page 10 of 10

 
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