JP1 Remotes

I'm curious why you decided to trust that triangle
A few years of building computer cables e.g.

https://i.imgur.com/jXQbi8s.png

I did not realize I needed to interpret where Pin 1 was by examining the diagrams until 3FG responded.

Thanks for the BBCode clue, had no idea why my posts were ...

"I'm failing to see what you're seeing in the photos"

The triangle on a connector identifies Pin 1, in this case it does not.

Your link is to this entire thread, and not to an individual post
Thanks for your guidance.

The link is https://www.hifi-remote.com/forums/viewtopic.php?p=120954#p120954

The photograph I refer to is under "The following pic shows how the pins are numbered for the 6-pin connector in the remote ...

The failing was mine because I trusted the triangle, and everybody else has been smart enough to ignore it.

The photograph at https://www.hifi-remote.com/forums/viewtopic.php?t=16360 shows the triangle which typically identifies Pin 1 at top left.

My apologies for not thinking this through ...

Hi Robman,

The post at https://www.hifi-remote.com/forums/viewtopic.php?t=16360 has been stable for years, so it strikes me as odd that no one has identified what I feel is a serious error in pin numbering. If my logic is failing somewhere, can you straighten me out?

The arrow at upper left on a 6 ...

Definitely no reason to fix 2.02a, 2.03 did it already.

It is super-impressive that it is over 20 years since I programmed my first JP1 remote. There have been three JP1.x generations since then, and everything remains backwards compatibility to the first devices. If only Microsoft practiced ...

Thanks mdavej,

Specifying the COM port worked, and loading was successful with the Prolifics as well as the FTDI on 2.065.

The last time I needed to use JP1 was with RM 2.01. 2.01 told me No Remote and updating to 2.065 told me No Remote too, so that's what sent me down the rabbit hole of ...

If I need another adapter, no worries, and below is the error map.

I've removed most of the repetitive 'Generating deviceImporter...' content to reduce file size.

RemoteMaster v2.06 build 5
Legacy merge set = true
System Properties:
java.version = 1.8.0_144
java.vendor = Oracle Corporation
os ...

A JP1 adapter makes the remote appear as a JP1.x remote to RMIR (and IR.exe, if you insist on using obsolete software). So you don't need the Delcom driver, and if you are selecting the interface type in IR.exe (or RMIR) then it is JP1.x, not JP1, that you need to use.

I have a Prolific USB cable ...

I am in the situation of trying to use a Prolific JP1.x cable with JP1 adapter to update a well-loved RS remote.

The Prolific .exe driver was no problem, installed as COM 6.

IR 8.02 confirmed this, it gave an Interface/Driver Status of:

The serial/parallel driver is functioning properly
Delcom ...

> 1) VPT works in TV, VCR and CBL modes, just as...

Tivo 1 is Cable on CBL and Tivo 2 is VCR on VCR but only Tivo 1 has volume control. I'll look deeper, see if something else may be amiss.

> You can actually make VPT extend to a 4th device mode if
> you make the VPT device one of the other device ...

A search did not uncover any ideas on how others have handled conflicts between devices which have warring protocols and dominating Combiners.

The remotes are 15-1994s (VPT only works for CBL on this model, so volume control has to be coded for the other devices).

Protocol Clash:

- The Sony LCD ...

RM 1.86 is failing to load the RDF (latest copy dated Sat Jul 10 19:35:13 2010 which is 10502 bytes). Used -version to verify that the latest Java is installed: "SE Runtime Environment (build 1.6.0_20-b02)".

Below are details of the two Remote Load Errors extracted from master.err:

On another tack ...