URC-9960B01 extender release version available

unclemiltie · Post by **unclemiltie** » Wed May 16, 2007 12:34 pm

Interesting, you say that the key is lit in HT mode but....

I don't have my remote handy so I can't tell, but the table in the remote that is used to determine if a key is lit says that Setup is not lit for the HT screen.

Since this table is used to validate that the key is lit, I can't see any way around this. I'm sure that this is where the trouble lies as the extender checks for the key valid (lit) and it not goes back and waits for the next keypress using the lit keys table from the non-extended remote.

yesok · Post by **yesok** » Sun May 20, 2007 10:52 am

Hello Bill,

On opening the covers of URC-9960B01, I have found 2 sealed chips(U8A and U8B) and one PIC16LF72 chip.

Could you tell me what they do?
Which is the S3C80+?

Thanks in advance,

Yesok

unclemiltie · Post by **unclemiltie** » Sun May 20, 2007 5:10 pm

no clue

The S3C80 is generally mounted chip-on-board with a dab of plastic over it. But I'm not a hardware expert so I can't really tell you which is which

joedaring · Post by **joedaring** » Sat Jul 07, 2007 2:48 am

Hellò Bill,
How are you doing?

I've been checking the 9960 B01 Extender threads more or less regularly, but I see there hasn't been a lot of activity recently...

Are there any new releases/features/bugfixes waiting in the shadow?

Anything to be released before summer vacations?

Would love to see something new in both the Extender and the tools

Ciao Bill, ciao all JP1-ers

Pippo

unclemiltie · Post by **unclemiltie** » Sun Jul 08, 2007 12:28 pm

joe

to tell you the truth, I've not been that active on the extender for a while. No one has reported any bugs lately.

I had begun working on v1.3 with a couple of tweaks in it, mostly around code size. I have been trying to find a way to get RM to behave better because of the way that I laid out the device selection keys and also get the screen-dependent button selection/images but I'm stuck on that one.

Anyway, nothing substantially new to report.

-bill

joedaring · Post by **joedaring** » Tue Jul 10, 2007 4:17 pm

Hi Bill!

Oh! I see... well, there is nothing much to fix when there are no faults reported...

Anyway, I'll keep an eye on your threads, just in case you decide to release V.1.3 or some new tools...

I didn't install V1.2 because you announced that you were already working on V1.3, and the idea of re-writing my commands from scratch because of the extender's update didn't excite me..

If you aren't going to release the V1.3 I'll go and install 1.2

Thanks for your work Bill
My greetings
Joe

unclemiltie · Post by **unclemiltie** » Fri Sep 07, 2007 8:21 am

Note:

if you upgrade to RM 1.81 you will find that the extended B01 remote is not listed in the list of remotes. This is because RM 1.81 doesn't like not having a space between the signature for the remote and the "(" that starts the description of the remote.

a simple rename will fix this:

was: KASAKASX(URC-9960 B01...)
now: KASAKASX (URC-9960 B01...)

joedaring · Post by **joedaring** » Fri Sep 07, 2007 3:39 pm

Hi Bill,
This spoiled me at first, but then I recalled that latest RM was fixed to ignore strangely named RDFs...

Thanks for the head-up, anyway.

Bill, are you planning to release new stuff?

Ciao
Joe

unclemiltie · Post by **unclemiltie** » Fri Sep 07, 2007 4:24 pm

Joe

I got myself engrossed in:

1: fixing Extinstall so that it would deal with the newer remotes, and as a sideline fixed it to retain comments and it now works with Vicky's JP1.2 extenders.

2: thinking bout and getting ready to build an extender for a JP1.3 Atlas

So, I even though I have the 1.04 "done" I've done very limited testing on it. I wanted to hold it until I got Extinstall working right so that I didn't have to rebuild my configurations over again. (this was major surgery on the included protocols and how they are supported, but I took something like 30 bytes out of ToadTog, DSM and LDKP EACH!) Just copying and pasting thigns into the RAW data wasn't going to work this time!

I'm going to try to get some time on my two major 9960B01 configurations this weekend and then post the 1.04 release (with a bug fixed that someone just noticed yesterday)

If you'd like to give it a whirl as a beta tester, send me an email at wjackson@rochester.rr.com and I'll send you a ZIP that includes the extender, and the version of Extinstall that installs it.

joedaring · Post by **joedaring** » Sat Sep 15, 2007 12:19 am

Hi Bill,

I've been away for a few days and have just seen this msg...

I guess that 1.04 is closer to release now... if not, I'd love to have it for beta testing...

Ciao Bill, have a great weekend

Joe

unclemiltie · Post by **unclemiltie** » Sat Sep 15, 2007 1:50 pm

I have just uploaded V1.04 of the URC-9960B01 extender to the files section here:

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

This version has several improvements:

1: I fixed a bug mentioned elsewhere in the forum on the "ignore first key" logic

2: I have substantially reudced the size of ToadTog, LDKP and DSM protocols approximately 30 bytes each. This cost nothing other than using up some wasted space in the base extender.

3: I have made this version compatible with the new IR and Extinstall so that you can now install this extender from within IR.

The new package includes the new version of Extinstall, maps and images for RM, the RDF and the HEX file for use with Extinstall. This version also now includes the source for the extender

Enjoy!

yesok · Post by **yesok** » Mon Mar 03, 2008 3:30 am

Hello,

I see the signature mismatch warning when I upload same IR file twice, AFTER activating my URC-9960B01(with 4K EEPROM). But the warning does not appear when I upload the same IR file BEFORE activating. All codes(mostly DSM and LKP) are running as expected. I have the same warning for Ver 1.04 and 1.03.

I am worried whether something is wrong with my URC-9960B01 or any side effects.

Yesok Yoon

unclemiltie · Post by **unclemiltie** » Mon Mar 03, 2008 9:46 am

make sure that you have the "force > 2K" (or whatever it is) in the IR tab. The EEPROMS in this remote are a bit touchy and some of them IR can't figure out what size they are and then the data is off a bit.

yesok · Post by **yesok** » Mon Mar 03, 2008 5:32 pm

Hello,

unclemiltie wrote:make sure that you have the "force > 2K" (or whatever it is) in the IR tab. The EEPROMS in this remote are a bit touchy and some of them IR can't figure out what size they are and then the data is off a bit.

Thanks.

Yesok

unclemiltie · Post by **unclemiltie** » Fri Aug 26, 2011 4:27 pm

I got a PM from one of the 9960B01 extender users that the "ignore first key" setting isn't working. I had thought that I had fixed that a long time ago.

Before I go digging to find (1) my old 9960 and (2) my JP1 EEPROM cable and (3) the old source and then dust off the cobwebs on this extender, are others seeing the same issue?

Specifically, if you are using this setting and it's working for you, I'd like to know about it!

thanks

JP1 Remotes

URC-9960B01 extender release version available

Inside URC-9960B01

V1.04 posted

Signature mismatch warning - Ver 1.04/1.03