357902 URC-625000-04R00 OSN JP1.4

[HamburgerHelper1]

Split from here:
http://www.hifi-remote.com/forums/viewt ... p?t=103431

Is it my imagination or is the pic of the JP1.4 Remote only showing 4 pins on the JP1 header instead of 6 ?
If it only has 4 pins you may have to trace the circuit to make sure your cable is connected correctly

[mathdon]

Your raw download shows that it really is a JP1.3 remote that we have never seen before. I await with interest the 5-digit signature that you will get from the JP1.4 remote.

[Tiku]

Tiku, I see from the raw download that you posted that you are using RMIR v2.12.8. Please update it to the current version, RMIR v3.0.12.

Yes i know, but since its working without any problem, so i am using old version, i tried with newer version, but sometimes it gets hanged.

Is it my imagination or is the pic of the JP1.4 Remote only showing 4 pins on the JP1 header instead of 6 ?
If it only has 4 pins you may have to trace the circuit to make sure your cable is connected correctly

Camera Fault, it has Six pin Header.

[Tiku]

Randy is right. You first do a long press of Setup until it gives two flashes, then follow his instructions. However, as this is a JP1.4 remote, you have to press 1 through 5, not 4, to get a 5-digit signature.

Here is the signature of both the remotes::-
Jp1.3 jp1.4
1-3 1-3
2-2 2-5
3-1 3-7
4-1 4-9
5-2 5-2

[The Robman]

Randy is right. You first do a long press of Setup until it gives two flashes, then follow his instructions. However, as this is a JP1.4 remote, you have to press 1 through 5, not 4, to get a 5-digit signature.

Here is the signature of both the remotes::-
Jp1.3 jp1.4
1-3 1-3
2-2 2-5
3-1 3-7
4-1 4-9
5-2 5-2

I think he's saying that the first remote is 32112 and the second remote is 35792

[Tiku]

yes exactly

[mathdon]

Because of the way that UEI represents signatures in the 983 command, this means that the true signatures are

JP1.3 : 32113211
JP1.4 : 357902

This JP1.3 signature agrees with that obtained from the raw data file that you posted earlier. The JP1.4 signature shows that this is a remote new to us, we do not have an RDF for it. But I am puzzled. We do have an RDF for a JP1.4 URC-625000 OSN remote with signature 348601 that I believe was created for you in 2021. If I am right, how many different URC-625000 OSN remotes do you have?

If you still get No remotes found when trying to download the JP1.4 remote with RMIR, can you please post the rmaster.err file from a download attempt for me to see. This will be in your RMIR installation folder.

[Tiku]

I am puzzled. We do have an RDF for a JP1.4 URC-625000 OSN remote with signature 348601 that I believe was created for you in 2021. If I am right, how many different URC-625000 OSN remotes do you have?

I am also confused, i have programmed atleast three OSN URC-625000 successflly in the past with CH340 Interface and these three remotes were in my wardrobe from months, cause i was not having FTDI Interface, for these remotes i bought FTDI interface.

Anyways here is JP1.4 emaster.err file:-
http://www.hifi-remote.com/forums/dload ... e_id=26854

[Tiku]

Anyways here is JP1.4 emaster.err file:-
http://www.hifi-remote.com/forums/dload ... e_id=26854

Graham Any Progress?

[mathdon]

There is nothing helpful in the rmaster.err file. To go further, we need error messages from jp12serial.dll, which is called from RMIR but not part of it. To get these, you need DebugView. This is a free Microsoft program that you can download here. If you have DebugView open when running RMIR then it will display a lot of messages. What we want is only messages related to a download, so use Edit > Clear Display (or the Clear icon on the toolbar) before you start a download attempt and then copy the text displayed when the attempt ends and paste it into Notepad or similar, save it as a text file and post it for me to see, or if it is short enough you can simply include it in a post. It should at least give more idea of how far the attempt goes before failing.

[Tiku]

[7420] Moving
[7420] COM6
[7420] to the head
[7420] Testing for JP2_14
[7420] JP2_14StartOrStopComm failed
[7420] JP2_14 test failed
[7420] Attempting to open remote on parallel port
[7420] Scanning port:
[7420] 0378
[7420] InpOut driver not open
[7420] Scanning port:
[7420] 0278
[7420] InpOut driver not open
[7420] Scanning port:
[7420] 03BC
[7420] InpOut driver not open
[7420] Closing InpOut driver...

[mathdon]

Thank you for that output. I am getting the feeling that there is something different in this remote that we haven't seen before. Before investigating further, can I please check that the remote actually works normally, as corruption might be the cause of the failures we are getting. If it does work normally, then I will produce a test version of JP12Serial.dll with additional diagnostics for you to try.

[Tiku]

can I please check that the remote actually works normally, as corruption might be the cause of the failures we are getting. If it does work normally

For this what next i have to do? As i don't have a original OSN stb to check the the remote ON,

Also what about 1.3 version remote? signature not found?

[mathdon]

On second thoughts, the fact that you could read the signature with the 983 command is probably enough to determine that the remote is working in normal mode, so ignore my previous post. I think that a broken connection to the RTS line may result, for a JP1.4 remote, in the the output you are getting. Can you do the following test. For this you need to install RealTerm, which you can download from Sourceforge at this link. When you have it installed, connect your remote to the PC then open RealTerm. Press the Port tab. If you only have one device connected, then the Port dropdown should display the COM port number of the port to which the remote is connected. If not, use the dropwon to select the correct port and press Change. The port number displayed at the bottom right of the display should now show the correct port. Don't bother about any other settings, the test is so simple that they are irrelevant. Now select the Pins tab. There is a box labelled RTS with two buttons, Set and Clear, and a box that should be Green. Press the Set button, it should remain Green. Now watch the remote while you are doing this and press Clear. The remote should flash twice and the box should be blank. Press Set again, remote should not flash and the box should return to Green. Press Clear again to check that again you get two flashes, then finally Set again. You can now close RealTerm and disconnect the remote.

If that has worked, then the RTS connection is good and I will add further diagnostics to JP12Serial.

There is no issue with the JP1.3 remote. It doesn't say signature not found, it says No RDF matches signature starting 3211. As I have said before, this means that we have no RDF for that remote. If you want one created, you will need to ask Rob if he is prepared to do that. RDFs for JP1.3 remotes is not something I can do.

[Tiku]

If that has worked, then the RTS connection is good and I will add further diagnostics to JP12Serial.

Your guess was right, there is a problem in the RTS Line, My device com port was correctly detected, there is no flash on the remote if i press Clear.
I also tried selecting hardware flow control to RTS/CTS in the port Section, also changed baudrate to 19200/115200, but nothing flashes on the remote.

If i press OK selection on the Remote i get yellow characters on the Realterm
Display Screen.

There is no issue with the JP1.3 remote. It doesn't say signature not found, it says No RDF matches signature starting 3211. As I have said before, this means that we have no RDF for that remote. If you want one created, you will need to ask Rob if he is prepared to do that. RDFs for JP1.3 remotes is not something I can do.

I had uploaded a new remote file for RDF from many days, but no one has a time to make RDF, Rob is also very busy, if no one has time to make RDF, than please make a Sticky Thread how to make RDF File, so one can self make RDF file for their Remotes.
Thanks