Mandingo, thx for your effort and reply.
I have not used any pnp script.
I have entered 20_OnkyoReceiver.sh in the #71 template, this seems to be a standard script present in /usr/pluto/bin.
I've tried to run it from cli, but it said not an Onkyo if I remember.
I verified RS232 communication in 2 ways:
KDE -> Cutecom
MessageSend to #37 DSG
When I send a command to #37 like this: /usr/pluto/bin/MessageSend dcerouter 0 37 1 192
the receiver responds correctly. So [color=blue]we know RS232 communication is working[/color].
I've been searching through the wiki, amongst others here:http://wiki.linuxmce.org/index.php/How_to_add_your_own_GSD_device
So what it boils down to:
- 1. AV device was created, and auto-created GSD #37
- 2. GSD #37 is properly linked to /dev/ttyS0
That we know because I can use MessageSend like:/usr/pluto/bin/MessageSend dcerouter 0 37 1 192
- 3.The codes present in LinuxMCE DO work with my receiver (I sent 192, but can send any code)
- 4. It is the link between the Core (DCErouter.log) and GSD that is faulty. (At least I think so, as commands are sent to #1 (core) but aren't routed to #37 (GSD)
Have look at the attached screenshot. I've added some comment & pointer.
I think it must be something 'small & stupid' that I'm overlooking..?
I'll look into your suggestion to create an IR Group, but I know the codes present in device #71 work.