RCA RCRP05B Null Signature

Fuzzlet · Post by **Fuzzlet** » Mon Jan 28, 2013 9:08 pm

Jp1xtest reports the following:

jp1xtest version 0.00


*** FOUND A JP1.2/3 COMPATIBLE REMOTE ON ! ***
Signature is (null)
Memory address is $0000
Memory size is $0000 (0)

Can't get RMIR to download from the device. Is my remote fried?

3FG · Post by **3FG** » Mon Jan 28, 2013 9:46 pm

I'm not sure what that means, but I doubt that it is caused by the remote, because even the COM port isn't identified.

Code: Select all

*** FOUND A JP1.2/3 COMPATIBLE REMOTE ON ! ***

should read

Code: Select all

*** FOUND A JP1.2/3 COMPATIBLE REMOTE ON COM3! ***  (or some other COM number)

Also, try downloading with RMIR, and upload the rmaster.err file (in the same directory as Remotemaster.jar) to the Diagnosis Area.

What interface cable are you using? What OS? Has this setup worked in the past? Any reason to think the remote has been fried?

Fuzzlet · Post by **Fuzzlet** » Tue Jan 29, 2013 7:38 am

Wow, I can't believe I didn't post more information then that. That's what you get for staying up too late working on things.

Anyways, the interface cable is an FTDI serial->USB adapter. This is my first foray into JP1 remotes. It is wired as follows:

Code: Select all

FTDI----------Remote
TXD----------->Pin4
GND----------->Pin3
RXD----------->Pin6
DTR----------->Pin2

(Determined from Tommy Tyler's "FT230X Interface.pdf")

My interface unfortunately doesn't have an RTS line available, but I believe read somewhere that DTR can be used as well. I have tried on windows 7 (using built in drivers for FTDI) and WinXP (downloaded latest drivers from ftdi website). The result is the same. The interface appears correctly as com port (4).

Another note, at first I was unable to get jp1xtest to even see the remote. (No JP1.2/3 Remote found etc) I then copied the latest jp12serial.dll from RMIR into the jp1xtest folder (renamed to jp1xserial.dll) and then was able to get Null signature result. Also, I was able to get the following output from RealTerm

31793179 is the proper signature but I'm not sure why there is the Nul char in there as well.

Rmaster.err file has been uploaded at http://www.hifi-remote.com/forums/dload ... e_id=11693

Fuzzlet · Post by **Fuzzlet** » Tue Jan 29, 2013 8:05 am

Oh, also when doing the test, I can see the remote Blink twice at the end. I believe this is signaling the remote being taken out of comm mode?

Thomas · Post by **Thomas** » Wed Jan 30, 2013 4:51 am

From my notes, you need to connect RTS to remote pin 2
and disconnect DTR.

For some remotes, you need to remove the connection to pin 5 entirely, at the pin. Any wire seems to act as an antenna and pick up unwanted signals.

Tom

Fuzzlet · Post by **Fuzzlet** » Wed Jan 30, 2013 9:29 am

I'm sorry just realised I had a typo in my pinout. I have DTR connected to Pin 2 of remote. Nothing connected to pin 5.

3FG · Post by **3FG** » Wed Jan 30, 2013 11:11 pm

JP12Serial.dll tries 4 different way to get the remote to respond, because JP1.1, 1.2 and 1.3 remotes have different ways of establishing a connection. Also, there have been more than one interface design. The DLL does pulse the DTR line while trying one of the 4 ways, and that may be just enough to get a reaction. Of course, you can use Realterm by directly manipulating the DTR line yourself.

As you have seen, full communication with JP1.3 remotes requires the RTS line be connected to pin 2. Are you sure that your cable can't be setup to provide a RTS signal? Also, your interface needs to be able to send a Break signal-- I think any FTDI device can do that.

If not, and you're comfortable working with C, you could try compiling a special version of JP12Serial that pulses DTR instead of RTS, but there is some risk in that. You could work off the V 0.18 source. It is quite a bit simpler than the 0.19 source, which supports JP1.4 and JP2 remotes.