Connecting a JP1.1 remote via USB

[HamburgerHelper1]

This is an old JP1 ATLAS 4 Device type remote using FTDI cable with DYI jp1 adapter.
Cable/adapter works testing on known good remote.
(983) Remote Signature Blink Back returns 0102

rmaster.err uploaded

http://www.hifi-remote.com/forums/dload ... e_id=26330

[mdavej]

Atlases are JP1.3. They don't require the JP1 adapter.

[HamburgerHelper1]

This remote only has JP1 printed by the pins,
and what about the signature blink back of 0102 ?
Also the old RDF for the ATLAS 4-DEVICE (ATLTLO0A)
is JP1 so i assumed this is such an old remote that it actually is JP1

[mdavej]

Humor me

[HamburgerHelper1]

Label inside battery compartment
URC-4AEXXXXB03

[mdavej]

Just plug in the FTDI alone, upside down and rightside up and give it another try.

[HamburgerHelper1]

sorry but that is the 1st thing i did and no remote found then i noticed it has jp1 printed on it and tried adapter and again no remote found
The remote chart
http://www.hifi-remote.com/wiki/index.p ... emoteChart
does list a 4AXXX,B00 as JP1 and mine is URC-4AEXXXXB03

[mdavej]

Ok. Thanks. Sounds like we need a new RDF for that signature. I don't have any ideas about the download failing other than try fresh batteries and no batteries.

Also let us know if this old remote is really worth the trouble of making a new RDF.

[HamburgerHelper1]

To me personally no the remote is not worth making a new RDF or figuring why it won't download, But I know Mathdon And Robman both enjoy the challenge.
I normally give these remotes along with the tv's i repair to different donation places.
Since I work at an E-recycling place i get stuff for free and donate them.
I get more enjoyment out of repairing a tv than actually watching it
And actually we can probably just modify the ATLAS 4-DEVICE (ATLTLO0A) RDF
Once the download issue is solved

[The Robman]

Are you 100% sure about that signature blinkback? I've never seen a signature start with zero before.

[HamburgerHelper1]

I thought zero was weird too.
I have performed blinkback several times and always no blink on the "1" key.
I have used code search and have it controlling a vizio tv and i can confirm that
at least the "1" key does indeed work

[mathdon]

I can see no way of diagnosing why RMIR cannot read this remote. The rmaster.err file from the link in the first post says that the interface opened successfully, but I presume this means simply that RMIR can talk to the JP1 Adapter. The NullPointerException reported in the file means that the signature is read as Null. To get the signature, RMIR reads the first 10 bytes of the EEPROM (with this remote being JP1, I take it that it has an actual EEPROM). The signature is returned as Null if these 10 bytes cannot be read, so it seems that the EEPROM cannot be read. With the JP1 Adapter sitting between RMIR and the remote, I see no way of finding out why this is so. The problem might be with either the remote or the adapter. It just might be possible to find something out with an original JP1 cable, as this takes the adapter out of the picture, but I really doubt it is worth exploring the matter further.

[The Robman]

HH, do you have any old JP1 cables that you could try with this remote? Have you tried doing a 981 reset on it? These old remotes could sometimes be particular about their battery requirements, some liked brand new batteries, some preferred old batteries, and some even preferred no batteries.

Also, double check that you have the polarity right connecting the adapter to the cable, and connecting the adapter to the remote. You have twice the opportunity to get that wrong using the adapter, lol.

[HamburgerHelper1]

I have an old parallel cable i built need to see if i kept any computer with that port or borrow one from work. I have been playing around with different battery power levels including no batteries and no luck.
Yes cable/adapter in correct polarity tested it on RS 15-1994

[HamburgerHelper1]

And BTW
No matter if it works with RMIR or not

Thanks Guy's