*Thanks Tschak for the correction delivered with all the subtlety and finesse of a Texan*
OK, sorry, that does make sense- so the message in the log
35;1mSet Screen Type^[[0m, retry none, parameters: <0x773f9b70>
08 01/22/13 21:55:19.657 Parameter 48(Value): 66 <0x773f9b70>
is noting the screen type
being set as opposed to the actual screen ID. Which is what it says, of course!
Right, so the screen type at the point when I press chdown on the remote is 'B'. Remote layout is ignored, so, by Remote Mapping
looking at ScreenType 'B', a chdown on the remote should fire one of these:
chdown;ChanDown;|0 -203 1 28 26 7
Which should be a message to the Onscreen Orbiter (-203) of type command (1) which is a simuated keypress (28) for which parameter 26 has the value 7. The button table
would give 7 as "Scroll Down".
So all the setup looks good. Except that when I press the button on the remote, I get a
08 01/22/13 7:10:09.129 Received Message from 121 (USB UIRT 0038 / TV
Room) to 10 (Media Plug-in / Server Closet), type 1 id 65 Command:Jump Position In
Playlist, retry none, parameters: <0x6e69eb70>
Why, Mr Anderson, why?
I guess the first test I can do is hit the "play" button when I'm on the same grid because in the remote mapping, that is mapped to
Play;|0 -203 1 37
for screentype 'B' but is not mapped to that for any other screentype. So if the system is using that record in remotemapping, I would expect to get the associated command 37 which is "play media" send to the onscreen orbiter (device -203).