I am cruizin' along with my programming, thanks to the intellectually gifted folk hereabouts. I am left with only one last hurdle(for now). My HTPC is operable via an airboard keyboard. It runs on WMCE2005. I now have my 8110 configured well for it(combination of WMCE remote and Airboard), excpt for this one glitch. When I start MCE, many times the arrows on the remote will not have any effect after the interface starts. Previously, my workaround was to "learn" the left mouse click from the Airboard, after which, all was well. I have found it necessary to upgrade to extender version 3.1, which worked beautifully, except I cannot learn or use learned functions anymore. So after reading on here about "make" and "break" commands, I created a macro that consisted of left click make and left click break. It seems to respond the way it is supposed to, but not with the same effect as the learned left click. 
The info displayed when the left click is learned is as follows:
#      Protocol                Device       OBC
#1  AirB2-BC44               23            4
#2  AirB4-3C.C4.5D.A5     7             4
The Macro used 171 for the make and 179 for the break.(Airboard protocol)
Ok....done rambling. Any help?
			
			
									
						
										
						Help with 8810w, Airboard, and WMCE2005
Moderator: Moderators
- 
				jon_armstrong
 - Expert
 - Posts: 1238
 - Joined: Sun Aug 03, 2003 9:14 pm
 - Location: R.I.P. 3/25/2005
 - Contact:
 
- 
				jon_armstrong
 - Expert
 - Posts: 1238
 - Joined: Sun Aug 03, 2003 9:14 pm
 - Location: R.I.P. 3/25/2005
 - Contact:
 
SHEESH!!! This is frustrating! Ok, so to recap, when I start WMCE2005 the arrows usually do not have any effect, basicall rendering the remote useless. If I left click on the Airboard, the arrows magically come back to life. Try as I might, I could not get this to work programatically. If I learn the left click, it works fine. But if I program the left click, it gives the appearance of working, i.e. the cursor shows up, a mouse click occurs, choosing "My TV" etc, but it does not re-enable the arrows. So...I went over to the green button forum, and found that others have an issue just pressed numlock twice, and all was well. So...I learned numlock, decoded the information, used those values. SIGH. While numlock did cycle on and off, it still did not re-enable the arrows. I know numlocks is cycling because the little light on the receiver said so, but no arrows. So it MUST be something elses in the send, as when I learn it, it works great. Can anyone help? what else is there? Here is what the Numlocks info is...
AirB2-89.71
Airb2-09.F1.5D.A5
Deciphering hex, I used OBC 137 for make and 009 for break.
Is there anything in the 5D.A5 part? Reaaly annoyed here...lol
			
			
									
						
										
						AirB2-89.71
Airb2-09.F1.5D.A5
Deciphering hex, I used OBC 137 for make and 009 for break.
Is there anything in the 5D.A5 part? Reaaly annoyed here...lol