Page 3 of 3

Posted: Thu May 16, 2019 8:46 am
by The Robman
Hard drives are very cheap now, so it might be a good idea to buy another, and maybe get a big one while you're at it, like 1tb or 2tb or whatever your PC supports.

Delcom JP1 USB installation

Posted: Sat May 18, 2019 7:24 am
by HamburgerHelper1
vickyg2003

I will try and make a bootable flash drive with linux and RMIR on it
If i am succesful i can give that to you.
If I ever have the time to make it i am very busy right now
It may not help you now but maybe in the future anyway
I will let you know when /if i ever get it done

Posted: Sun May 19, 2019 6:02 pm
by vickyg2003
I now have two working Windows 7 machines!

I started out with the broken one, and restored it to my 2013 image, which had all the software for everything. That worked great, 185 updates later and I'm back in business with a working drive.

Next to be tackled was my husband's old DELL N5110. Glad I didn't start there, because I've worked on this for over 12 hours to get it up and running.

Since this computer was working I have a SATA cradle, I followed the instructions to clone a disk. The instructions on moving to an SSD drive failed to include a key step. After figuring that out I was back in business for a bit.

The Dell R5110 doesn't have access from the bottom. You have to remove everything.
You open the trap door, remove the memory.
Remove 10 screws off the bottom
Remove the DVD drive,
Remove the SD card blank face
Pry off the keyboard.
Disconnect the keyboard from the mother board.
Disconnect the remaining ribbons
Remove 4 screws
Pry off the face plate
Disconnect the wifii
Disconnect the monitor
Remove 4 more screw
remove the monitor
disconnect the wires from the mother board
Unscrew 5 more screws
Pry out the motherboard
Screw out 2 more screws 6 more screws and you have the hard drive out.
When putting it back to gether, I dropped a screw inside.
When I turned it back over, the screw, two cylinders and a mini circuit board were lying on my white paper towel. Oops.

Cylinders were the posts for the right hinge of the monitor.
mini circuit board was a Reed Switch Sensor Circuit Board - H7PRC , took me an hour of googling to figure out what that was and where it went.

Put the whole thing back together, and the keyboard didn't work, undo undo undo. Redo, redo redo.

It works! The spreadsheet that used to take 2 minutes to open now opens in 4 seconds.

I learned so much, but needless to say getting a spare hard drive to play this game all over again is outside what I'm willing to do in the name of JP1ing.

Posted: Wed May 22, 2019 8:31 pm
by vickyg2003
user jmezz13 helped me get the Delcom issue sorted out, without his help, I'd still be twiddling my thumbs.

I also have my Jp1.2/3 cable running on 10

Here is a write-up of the procedure with screen shots.
https://www.hifi-remote.com/forums/dload ... e_id=25588

I updated the Delcom drivers with the words **Not for Windows 10** and I popped the writeup with the drivers too.

Edit: May 23, updated the document with pictures of the cable, and copied the verbose instructions on using a WinUSB by class ID for the more technical adept.

Posted: Wed Jul 24, 2019 3:47 am
by joegovernale
Thanks for the write-up on how to use legacy on WIN 10. After installing the WinUSB Device driver and editing the registry, I still cannot get my JP1 USB Delcom cable to work. FWIW my OCAP adapter is working fine however I would like to update all my URC 8910s and 9910s.

My registry also contains an additional DeviceInterfaceGUIDs multiString setting that I notice the PDF example did not. Is this an issue?

Posted: Wed Jul 24, 2019 10:23 am
by mathdon
joegovernale wrote:My registry also contains an additional DeviceInterfaceGUIDs multiString setting that I notice the PDF example did not. Is this an issue?
Yes. I had exactly the same issue when following Vicky's instructions, that the cable didn't work and this entry was present. I just deleted that entry and then all was well.

Posted: Wed Jul 24, 2019 7:21 pm
by joegovernale
mathdon wrote:
joegovernale wrote:My registry also contains an additional DeviceInterfaceGUIDs multiString setting that I notice the PDF example did not. Is this an issue?
Yes. I had exactly the same issue when following Vicky's instructions, that the cable didn't work and this entry was present. I just deleted that entry and then all was well.
Thanks for the reply.
Yes, I tried deleting the MultiString GUIDs entry, tried different remotes, rebooted several times. Even changed to other USB ports (both USB 2.0 and USB 3.0) editing the registry for each. The interface check succeeds and the driver status shows OK but I continue to get "JP12 Read failed 0.".

Posted: Thu Jul 25, 2019 4:18 am
by mathdon
joegovernale wrote:I continue to get "JP12 Read failed 0."
That explains it! That is a message from IR.exe trying to read a JP1.x remote. If you must use IR.exe, then make sure you have selected the JP1 interface, not the JP1.x interface. However, IR.exe is obsolete and I would recommend instead that you use RMIR. If you have further problems, I can help with RMIR but not IR.exe. If you don't already have RMIR then please see this announcement of RMIR v2.08, the current version.

Posted: Fri Jul 26, 2019 1:40 am
by joegovernale
RMIR replies "No remotes found". RMIR works for my OCAP remotes so thanks for bringing me up to date on that.
I can use IR to WAV to upload, I am trying to download learned commands. I am suspecting my JP1 cable is the issue.

FWIW, IR returns "No response from interface" when I set it to JP1. That's why I had tried JP1.x.

Posted: Fri Jul 26, 2019 3:37 am
by mathdon
If your Delcom cable is dead, you might like to know about this adapter from DIYgadget that enables you to program a JP1 remote with a JP1.x cable.

Posted: Fri Jul 26, 2019 4:24 am
by joegovernale
Thanks for the lead. And thanks for continuing to support this community.

Posted: Fri Jul 26, 2019 8:47 am
by The Robman
If you do decide to get the DIY adapter, you can get an FTDI cable on ebay for under $10 shipped, see the following thread for details:

https://www.hifi-remote.com/forums/viewtopic.php?t=16360

Posted: Fri Jul 26, 2019 10:50 am
by vickyg2003
When i was dinking around with the wrong settings my remote became unresponsive and required a 981 reset before it would work.