JP1 Remotes

mathdon · Posted: Sun Mar 17, 2024 10:25 am Post subject:

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.
_________________
Graham

Tiku · Joined: 11 Mar 2014 Posts: 104

[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 · Posted: Tue Mar 19, 2024 10:20 am Post subject:

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.
_________________
Graham

Tiku · Joined: 11 Mar 2014 Posts: 104

mathdon · Posted: Tue Mar 19, 2024 2:20 pm Post subject:

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.
_________________
Graham

Tiku · Joined: 11 Mar 2014 Posts: 104

mathdon · Posted: Wed Mar 20, 2024 7:33 am Post subject:

Thank you for the disappointing news that the test of the RTS line fails. I see no point in progressing further with that remote, but if you want to continue experimenting with Realterm, the correct baud rate is 38400. As the RTS test doesn't depend on baud rate, I didn't bother to suggest setting that in my earlier post.

Creation of an RDF requires a great deal more information than that in the file you posted, a lot more knowledge of the workings of these remotes than you have, and a lot of experience too. That is why I cannot create RDFs for JP1.3 remotes and why it is not possible to give a simple explanation of how to create one yourself. You really do need an expert in JP1.3 remotes to do it.
_________________
Graham

Tiku · Joined: 11 Mar 2014 Posts: 104

mathdon · Posted: Thu Mar 21, 2024 6:24 am Post subject:

Both JP1.4 remotes? You have only mentioned one in your previous posts, the one with signature blink-back 35792, giving a true signature of 357902.
_________________
Graham

Tiku · Joined: 11 Mar 2014 Posts: 104

At present i have total 3 OSN Remotes, one is jp 1.3 and two is jp1.4
Unfortunately both 1.4 version shows Remote Not Found, and neither of them blinks in Realterm only 1.3 version blinks which also shows signature not found 3211 in RMIR.
I Have upgraded couple of JP1.4 Versions in the past for Friends.
Don't have any of the previous remotes with me now.

The signature is the same in both 1.4 remotes, which you mention in above post.

mathdon · Posted: Thu Mar 21, 2024 2:32 pm Post subject:

Tiku · Joined: 11 Mar 2014 Posts: 104