Page 1 of 1

Importing learned codes from Sejin SWK-8695WR IR Keyboard

Posted: Tue May 07, 2013 7:20 pm
by abishur
As the subject title says, I've used my URC-10820B00 to learn key presses from a Sejin SWK-8695WR IR Keyboard. The remote itself has no problem learning the signals, but when I try to upload it to ir.exe it gives me an error message and I loose the stored signals.

It specifically says "the learned data BurstSpec appears to be malformed. Learned data parsing stopped at $F006"

Is there anyway to bypass this error so I can create a map of my keyboard or at least keep it from erasing the data?

Posted: Tue May 07, 2013 11:08 pm
by 3FG
In Advanced, select Enable Raw Download, and then do a Raw download. Post the file here. If that doesn't work try using RMIR. If it also gives an error on a regular download, try a Raw download with it. We may be able to interpret most of the learns.

Posted: Wed May 08, 2013 5:37 pm
by abishur
Here is the raw dump, I'll download/setup RM tonight and see if I can't get farther with it. Thanks!

Per request, text was removed, here's the link to the file

https://www.hifi-remote.com/forums/dload ... e_id=11901

Posted: Wed May 08, 2013 6:15 pm
by abishur
Okay, I messed around with it a little in RM. Most the entries I learn with the remote say "multiple" under protocol and "malformed" under misc.

the handful that come out correctly say "Sejin-1-56" under protocol and "E=0, no end frame" under misc

Posted: Wed May 08, 2013 6:29 pm
by 3FG
OK, then please save an RMIR file and upload it here. (Don't post the text, upload the saved file into the File Section Diagnosis Area. While your're at it, would you mind replacing all that text in the previous post with a link to an uploaded file?)

It's good news that you're getting a Seijin decode. That means some of the signals are at least partially recognizable.

Posted: Wed May 08, 2013 6:38 pm
by abishur
Sure, it will take me a minute. One thing I'm kinda noticing is that signals that were an error before were being recognized when I did it again, so I think it's just being iffy on when I release the key on the keyboard.

While I'm getting this in place. For my other remotes I've been using Keymap master v9.22 to create custom maps of my various remotes. The end goal was to do this with the learned keys off the keyboard, but while I see the sejin-M-56 protocol discussed in the IR.html included with IR/RM, I don't see it as an option in Keymap master.

I'm guessing I need to manually enter the settings to do that, but how do I figure out the PID etc?

Posted: Wed May 08, 2013 6:53 pm
by abishur
I edited the text dump post with a link to the file, but here is the initial raw again

https://www.hifi-remote.com/forums/dload ... e_id=11901

Here's a second one, I cleared out all my previous learned signals, and through some trial and error have gotten the majority of the signals I want to download, downloaded though it varies greatly between key presses whether the signal is Sejin, JVA, Sony, etc.

https://www.hifi-remote.com/forums/dload ... e_id=11902

And the same thing from RM

https://www.hifi-remote.com/forums/dload ... e_id=11903[/img]

Posted: Wed May 08, 2013 9:48 pm
by abishur
So who knew RM was so amazing?! :lol:

I've been building the list of codes I need piece by piece and using RM to build the Key map instead of keymapper-master and it is working phenomenally! I'll let you know if I run into any other issues, but here is what seems to have worked for me

1) Delete all learned signals, RM found a lot more than IR did, I think there was some garbage stuck in there from a long time ago causing problems?

2) Slowly learn signals. It's hit and miss as to whether I hold the key too short or too long, but when I get it right RM and IR both see the proper Hex/OBC and device/sub device codes.

3) Repeat until you get everything!

Posted: Wed May 08, 2013 10:16 pm
by 3FG
I'm glad you're finding them all, and I assume by now you've seen that RMIR knows that your 10820B00 has a Seijin (0161) executor built in.

I doubt the problem is holding the button for the correct amount of time. The signals which aren't decoded have the first off period recorded as too long. Usually (but certainly not always) this is caused by having the two remotes at the wrong distance from each other-- or for the teaching remote to have weak batteries.

When I manually change that first off duration the signals do decode, but it isn't very convenient.

Posted: Thu May 09, 2013 6:26 am
by abishur
hm... the batteries in the keyboard are on the older side, I'll give them a charge and see what happens.

I'm keeping the learning remote within an inch of the keyboard which cleared up a lot of the malformed errors I was receiving.

Thanks so much for the assistance by the way! I know in the end it pretty much being user error :oops: but getting me on the right path was a huge help!

Posted: Thu May 09, 2013 8:33 pm
by abishur
Changing the batteries did not end up helping, but through patient repetition I did get all the codes learned and moved into a custom device. Except for the number 0, it never did like that one, but trial and error finally found the right code :D

Thanks again for the help!

Posted: Thu May 09, 2013 10:18 pm
by 3FG
Good. Make sure you upload your upgrade to the File Sexction Device Upgrades Keyboards,