JP1 Remotes

That ccf was posted by someone at company's website but I'm not sure how clean it is.

Back when I was messing with the iMon signals I tried at guessing the missing OBCs without any luck. What exactly do you mean by the gap OBCs?

If I can figure out the arrow buttons and figure out why the slingbox upgrade won't let you repeat the same button I'd be golden.

Gap OBCs are ones that are not already in use in the upgrade. Hint: try copying the function/OBC list over to a spreadsheet and then sort on OBC as this will let you see where the gaps in the range are.

If the buttons can only be used once, there's obviously a toggle bit in there that my upgrade is not replicating. Did you also try the official UEI iMon upgrade?

Yes I've tried both but I will try more of the gap OBCs. When I tried last time I spent hours and never ended up getting the arrow buttons to work. I'll work on it and see if I can get it all going but I know I'll still have the problem of the button release/toggle not working. For instance, if I enter channel 595 it works fine. If I enter 555 it will only do the one 5.

UPDATE - spent another 2 hours trying other OBCs on the iMon-Pad upgrade and trying to get it mapped correctly but it seems I've gotten nowhere. I only seem to have a few of the functions working now and still the problem of not being able to repeat a button. I wasn't able to find the up/down/left/right either.

OK, I've tested it this time and now it's producing the signals that I intended. There is a long OFF time between the two parts of the signal where the time appears to be completely random, so I just picked a value and ran with it. Hopefully it doesn't matter what the time actually is.

https://www.hifi-remote.com/forums/dload ... le_id=5760

No go Rob. Maybe I'm doing something wrong with the KM file you provided? I loaded your latest KM file in RM and exported a slingbox PL bin. None of the buttons are working on my slingbox.

I'm using remote master 1.83 with the 'Slingbox with UIE PL Chip' remote.

Well at least I tried. The tricky thing with this protocol is that each bit only uses half a pair (ie, ONE = +800 -0 and ZERO = +0 -800) and everytime the binary changes from 1 to 0, the last 1 bit is shorter than the rest (ie, +500 uS rather than +800 uS) and the next 0 bit is longer (ie, -1100 uS rather than -800 uS). Rather than try and replicate this in the executor, I treated the first three bits as a lead-in pair (the first 6 bits are contant) and I shortened the ON part of the leadin pair by 300 uS. Maybe this assumption was incorrect.

Also, like I mentioned earlier, the gap time between the two parts is wildly different for each of the buttons in the CCF and I can see so reason for it being so. Therefore, my assumption is that the two parts are really a button-down and a button-up sequence, where the random gap between them is caused by the variances of how long the user pressed the button down. I just picked a time that was somewhere in the range of times. Maybe this assumption was incorrect.

Furthermore, as you are not able to load this CCF file into a Pronto and test it yourself, we're not 100% positive that it actually controls your device in the first place.

Regardless, I will ask the folks at UEI to take a look at this next week to see what they come up with.

I agree with your assumptions and the most important issue is that we don't know how clean that CCF is or if it even controls the device. I'm pretty sure the Logitech folks were given the same CCF and they FINALLY got their harmony remotes to be able to control the cw3000hd. I know my harmony 880 works perfectly now.

Hopefully UEI will be able to come up with something. Thanks for your efforts Rob! I really appreciate it and I know that if we figure something out there will be a good number of happy cw3000hd users.

I'm still trying to contact the iMon-pad folks because I'm certain they manufactured the cw3000hd remote for captiveworks.

Hey Houdini,
Neither of the links in your original post (below) work anymore, did the thread and file get deleted or just moved? If you can find any discussion threads about the CW signal could you please post links to them, I want to see if there's any technical info in there that I can use.

Thanks,
Rob

houdini wrote:Anyone get this working on slingbox?

Rob was kind enough to help me with the captiveworks 1000 back when I had that. Now I have the 3000 and would like to get it working.

http://captiveworks.org/forum/comments. ... _codes.zip is the pronto file and ccf that they posted on captiveworks support site.

http://captiveworks.org/forum/comments. ... ionID=2081 is a link to the discussion they had about getting it to work with the harmony remote.

Yeah their forum crashed a while back and all of the users lost a LOT of valuable information. I'll try to see if there is anything else of relevance in the forum.

I'll update this post if I find anything.

UPDATE: These are the only remaining threads that pertain to universal remotes and the ccf file:

http://captiveworks.org/forum/comments. ... ionID=1867
http://captiveworks.org/forum/comments. ... ionID=1537

I've created a new file, give it a try (same address as before)

Wow, we're so close. The left, right, up, and down are actually working now but we still have the problem of button repeats not working...most likey because the button release/up is not working.

How did you find the left,right, down, up? Just the gap obcs? I tried a bunch of them and never guessed correctly.

I finally figured out that the signals in the CCF are the same signals as the iMon signals. I found my old files on iMon and re-figured out how to decode the signals. As I suggested earlier, the arrow buttons use "gap" OBCs. Regarding using the same button twice, I had hoped that I'd fixed that because I added the toggle to the protocol. Maybe the delay between the two halves of the signal is too much.

If you want to try reducing the delay, once you have the upgrade open in RM, select Advanced > Manual Settings then double click on the protocol code listed for the "S3C80" processor. The code will look like this...

43 8A 41 8B 12 8D 04 07 08 01 A1 00 00 00 00 01
8D F6 E8 00 E1 00 00 E6 10 01 E6 11 03 18 07 28
07 38 07 48 07 56 C1 03 90 C1 56 C2 30 56 C3 0C
E0 C3 56 C4 C0 B4 C1 03 B4 C2 04 B4 C3 04 B4 C4
05 F6 01 46 5C 05 C4 1C F8 F6 01 58 F6 01 0A FB
0B 5A F3 46 29 01 B6 05 40 F6 01 49 AF

The byte in red is the one that controls the delay, if you reduce this the delay between the two halves of the signal will reduce.

houdini wrote:... but we still have the problem of button repeats not working...most likey because the button release/up is not working...

When you say the repeat isn't working, are you saying that you can't hold the button down and have it repeat, or are you saying that you still can't use the same button more than once? I had hoped that I had fixed the latter case with the addition of the toggle bit to the protocol code. You can't make buttons repeat on a Slingbox, you only get one press. Now, I can change how long that one press is by changing the delay between the two parts of the signal, but it would be the same amount for all of the buttons. If you were using a regular JP1 remote, you would be able to hold the button down and have it repeat properly.

Can you check if all the other buttons are correct? There are a few button codes in the old iMon file that are not in the CW3000HD CCF, so if you find some buttons missing, it might be those.

Buttons in the iMon upgrade that are not in the cw3000hd CCF include:
Backspace
ContextMenu
Windows Key
Right Click
Left Click

Plus, there are some buttons that share a code but have different meanings. Here's a quick sample::

iMon --> CW3000HD
Bookmark --> Menu
My Movie --> All
Tab --> Recall
My Photo --> Sat
My TV --> Search
Shift Tab --> Erase
Application Launcher --> Green

Yeah I was aware of that limitation on slingbox where you can't hold buttons for repeats...but I was talking about not being able to press the same button more than once without first pressing a different button. For example, if I want to enter channel 555 it will only do the first 5. If I want channel 595 it works fine.

What exactly do you mean by lowering the byte in red. I've tried a few things and still can't get it to work.

All the other buttons work fine and I mapped them how I think they should be on the slingplayer remote. I am aware there were functions in the iMon pad that are not on the captiveworks remote and that certain functions mean different things. I've mapped them correctly and they are all working except for being able to hit the same button twice in a row. I'm not talking about 'holding' down the buttons.

Do you have any other idea why I wouldn't be able to press a button twice in a row?

The data in the CCF file indicates that there's a "toggle bit" in the signal, a "toggle bit" is a binary bit that changes it's state. Usually such a bit would change it's value with each button press, but in the CCF data, it appears that the bit simply changes it's value from the 1st part of the signal to the 2nd. The original iMon code didn't include the toggle bit, but I did include it in the latest version of the CW code that I loaded. I did test the signal and the correct bit is being toggled.

I just looked at the CCF file that Juppers loaded last year and while it confirms that the toggle bit is there, it also shows that the arrow buttons don't use the toggle bit and when the arrow buttons are held, they repeat the data portion rather than just extending the gap between the two halves.

Could you invite Juppers back into this conversation (he's in the CW forum) and ask him to test the official CCF file in his Pronto to let us know if he can use the same button repeatedly (eg, tuning to channel 555).