Re: [concordance-devel] Harmony 300

2013-03-25 Thread Bart Cerneels
I see good progress has been made on supporting the 300. I've build the branch and patch attached in http://sourceforge.net/tracker/?func=detailaid=3559622 I can identify the remote with -i, but what I would really like to do is dump the configuration. concordance -wb

Re: [concordance-devel] Harmony 300

2013-03-25 Thread Bart Cerneels
On Mon, Mar 25, 2013 at 2:58 PM, Scott Talbert s...@techie.net wrote: On Mon, 25 Mar 2013, Bart Cerneels wrote: I can identify the remote with -i, but what I would really like to do is dump the configuration. concordance -wb --dump-config=remoteconfig.bin failed with error 3: Requesting

Re: [concordance-devel] Harmony 300

2013-03-25 Thread Scott Talbert
On Mon, 25 Mar 2013, Bart Cerneels wrote: I see the LC_ERROR_UNSUPP in CRemoteMH::ReadFlash() but I guess implementing this is a little much to jump into? While I'm familiar with HID at a high level, I have not worked directly with it in userspace and the harmony remote's protocol is

Re: [concordance-devel] Harmony 300

2013-03-25 Thread Bart Cerneels
On Mon, Mar 25, 2013 at 3:34 PM, Scott Talbert s...@techie.net wrote: On Mon, 25 Mar 2013, Bart Cerneels wrote: I see the LC_ERROR_UNSUPP in CRemoteMH::ReadFlash() but I guess implementing this is a little much to jump into? While I'm familiar with HID at a high level, I have not worked

Re: [concordance-devel] Harmony 300

2013-03-25 Thread Scott Talbert
On Mon, 25 Mar 2013, Bart Cerneels wrote: Did a quick hack to test, certainly not as easy as it sounds. Is the 300's config max 1KiB? USB HID response package is 64 bytes right? But it's actually the internal API that is the trickiest bit, certainly without the documentation. In