JP1 Remotes

[nitramsen]

Hi,
I am trying to get my URC-7962 to work with RemoteMaster IR V2.02 Beta 15v (The version I have to use for JP3 remotes from what I have read in other posts on this forum).
I have been trying to get this to work for 20 days (First many days spend on a Prolific cable:( , but that apparently does not like the 2 stopbits used by RM). I have finally managed to get RemoteMaster IR to recognize the remote with a FTDI 232R cable on Windows XP x86 , but once the downloading starts RemoteMaster IR hangs and does nothing (Downloading still displayed in the bottom status bar).

From the log file rmaster I have the following:

Testing interface: JP1.X Serial
Interface matched. Trying to open remote.
Opened
Interface opened successfully
Base address = $1DC00
Interface type = 257
Searching for RDF
Final signature sought = 204907
Remote identified as: URC-7962 OFA Smart Control Motion
ERROR: ButtonMap 0 includes unknown keycode $70, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $71, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $72, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $73, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $74, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $75, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $76, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $77, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $78, Creating button!
ERROR: ButtonMap 0 includes unknown keycode $79, Creating button!
Number of bytes read = $FFFFFFFF
Ending normal download
Data parsing started

Portmon gives me the following:
IRP_MJ_WRITE Serial0 SUCCESS Length 4: 00 02 51 53
IRP_MJ_READ Serial0 SUCCESS Length 4: 00 02 00 02
IRP_MJ_WRITE Serial0 SUCCESS Length 4: 00 02 50 52
IRP_MJ_READ Serial0 SUCCESS Length 8: 00 08 00 03 15 00 00 C4
IRP_MJ_READ Serial0 SUCCESS Length 2: 4E 94
IRP_MJ_WRITE Serial0 SUCCESS Length 10: 00 08 01 00 00 C4 4E 00 3E BD
IRP_MJ_READ Serial0 SUCCESS Length 66: 00 40 00 32 30 34 39 30 37…
IOCTL_SERIAL_PURGE Serial0 SUCCESS Purge: RXCLEAR
IRP_MJ_WRITE Serial0 SUCCESS Length 4: 00 02 52 50
IRP_MJ_READ Serial0 SUCCESS Length 4: 00 02 00 02

I have also tried on windows 8 X64 but it seems the Serial drivers are not working on x64. I have also tried with RM 2.03 beta but that does not recognize the remote.

If anyone has, an idea what I could try next please let me know.

I am try to make a custom IR file for a slingbox, based on the learned IR codes, is there any other way to do this?

[3FG]

I don't think that RMIR v2.02Beta1.5v should work with the URC-7962 if the remote contains learned signals. The 7962 uses a different learned signal format which was addressed in later versions of RMIR.
Instead I think (but I don't have a 7962) that you need to use RMIR release 2.02a, but take the dll from 1.5v and copy it into the 2.02a\Windows-x86 directory. You need JP12Serial version 0.20, and not 0.19. So far as I know, we don't have a 64 bit dll made from the 0.20 source, nor Linux or Mac versions. That's why 0.20 wasn't included in the 2.02a release. Anyway, do Help\About to check the dll versions.

Also, the RDF distributed with 1.5v has several errors. Use this one instead.

The Prolific chipset tends to have problems with MAXQ processors, but I'd be surprised if it relates to two stop bits. Have you seen something to suggest that Prolific has trouble with two stop bits? The problems we've seen so far are difficulties in reading from the remote, even though writing to the remote seems to work. BTW, RMIR uses two stop bits because tha's the way UEI designed the communications protocol.

[mathdon]

[nitramsen]

Thanks for the reply from both of you.

I have tested the X64 but I get the same result as under X86 (not downloading).

I think it may have to do with the signature from the remote, as my remote returns:
00 40 00 32 30 34 39 30 37 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00 0A 00 00 00 C4 4D 00 00 C4 86 00 01 DB FF 00 01 DC 00 00 01 3D 0D 02 00 0B 45 3D 18 62 4C 66 11 6A FC E6


From what I read in another thread that would mean that the Flash starts at 1dc00 but ends at 13d0d (Kind of impossible) . This is maybe why RemoteMaster logs “Number of bytes read = $FFFFFFFF (-1), could it be that the signature decoder is not correct and 13D0D is not the end but something else?

Regarding the Prolific I am pretty sure it is because of the two stop bits. I made a test from a small program I made and with two stop bits the reply to 02 51 53 is 00 20 02 or worse sometimes. As soon as I change the stopbits setting to 1 bit, I get the expected result. I have also read correct signature etc with the Stopbits set to one on the Prolific (2303HXA).

Is it the RDP file that sets the Flash end (Or where to find it) or is this hard coded in Remote Master or the serial dll?
Thanks Martin