"Failed to open JP1.x interface" w/DIY cable

e.axel · Post by **e.axel** » Tue Sep 12, 2006 6:37 pm

tlad wrote:
e.axel wrote:My interface cable was supplied by DIY. I just added 2 resistors and a capacitor, both supplied with the cable. Pretty hard to screw THAT up!
What remote do you have?

URC-8820

Tommy Tyler · Post by **Tommy Tyler** » Tue Sep 12, 2006 8:15 pm

For those of you trying to get your new JP1.x interface up and flying, let me suggest that you not use any of the application programs for testing, since they are still under development, and that just adds one more variable to the equation. Instead, I suggest a simple test program Greg designed specifically for testing interface response. I've posted it at:

https://www.hifi-remote.com/forums/dload ... le_id=3571

Unzip and put the four files in a temporary directory. Double click on the batch file and you should get:

C:\temp>tester
tester version 0.00
jp12io.dll version 0.00
Parsing command list file tester.dat
Opened COM1
JP1.2 remote found! (or JP1.1 remote found!)
C:\temp>pause
Press any key to continue . . .

If the interface fails to communicate with the remote, you'll get:

C:\temp>tester
tester version 0.00
jp12io.dll version 0.00
Parsing command list file tester.dat
Opened COM1
Opened COM4 (or other COM ports in your PC)
Unable to connect
C:\temp>pause
Press any key to continue . . .

Once you know the interface can find the remote, you can quit worrying about whether it's assembled correctly and concentrate on other problems.

Tommy

tlad · Post by **tlad** » Tue Sep 12, 2006 8:33 pm

Fantastic Tommy.

Thanks. That does make the troubleshooting a lot easier.

Tim.

e.axel · Post by **e.axel** » Tue Sep 12, 2006 8:40 pm

Get an error "Tester is not recognized as an internal or external command, operable program or batch file", goes to press any kewy to continue, and exits.....

e.axel · Post by **e.axel** » Tue Sep 12, 2006 8:44 pm

.......
Open com1
Open com4
Escapecommfunctionerror. error 87.The parameter is incorrect......

tlad · Post by **tlad** » Wed Sep 13, 2006 5:27 am

Same error as e.axel (on my old interface)

Open com1
Open com3
Escapecommfunctionerror. error 87.The parameter is incorrect......

Bought some new components today will build a new interface and test

Tim.

gfb107 · Post by **gfb107** » Wed Sep 13, 2006 5:52 am

The messages you guys are reporting aren't what tester would display.

It should say "Opened" instead of "Open" and the port names should be upper case (COM instead of com).

Is that just a typing issue? It's usually better to copy'n'paste this kind of information to make sure to get it right.

tlad · Post by **tlad** » Wed Sep 13, 2006 6:49 am

Yeah, Opened and COM in upper case.

I just copied e.axel's when I saw he had the same error as me.

Tim.

e.axel · Post by **e.axel** » Wed Sep 13, 2006 8:24 am

Sorry, it does say opened. Rest of result is accurate (unexpected error, undocumented)
I am abandoning this effort for the present. Too many unproven variables. It is early here, and I will completely document my effort later today....
Thanks for all the help guys!

e.axel · Post by **e.axel** » Wed Sep 13, 2006 8:59 am

Here is the final review:
1. Remote - brand new 8820 supplied by UEIC in exchange for a 6011 I asked them to add some codes to. Got it and started with JP1.2 just to extract the code data. AFAIK works fine with all devices tested. JP1.2 interface condition unproven.

2. Interface - from DIY, added 2 resistors and cap per their instructions. Completely unproven, have nothing to compare it to.

3. PC serial port - used with other devices AFAIK OK.

4. IR7 Beta - Unproven with this interface/remote

5. Tommy's tester - Unproven with this interface/remote, Gives undocumented Error 87.

So that is where i will leave it for the time being. I will continue to monitor this thread.
Thanks again for all the other contributions.

binky123 · Post by **binky123** » Fri Sep 15, 2006 8:07 am

This quote is from here

Figure 6 shows the first version of the interface to combine support for JP1.1 and JP1.2 without switches. A number of these were sent out for field testing, and problems showed up immediately. The connection between pins 7 and 8 of the DB9 connector were to provide a loop-back feature to enable software to find which port the interface is plugged into. Apparently that is a "no-no" with the Windows API, because it causes the interface to fail communications.

Have you tried checking the connection between pins 7 and 8 of the DB9 connector? Maybe they are still connected.

e.axel · Post by **e.axel** » Fri Sep 15, 2006 9:12 am

They are not.

binky123 · Post by **binky123** » Fri Sep 15, 2006 11:58 am

In a previous post, user prelude(DIY owner), said he plugged in a JP1.2 cable(original design) and the software worked with it. He then plugged in the JP1.x cable that didn't work previously and it also started to work.

Is it possible for you to convert your JP1.x cable into a JP1.2 only cable? What operating system are you using? Maybe there is a registry setting that you can clear out(this might have happened to prelude by using the JP1.2 only cable). Maybe it's a port permissions issue?

jetskier · Post by **jetskier** » Fri Sep 15, 2006 12:17 pm

Maybe it's time to scrap the modified DIY cable. Go to Radio Shack. Get the parts listed in the latest cable document and build a new fresh one. As of my post, Tommy has just uploaded it today - Sept 15th, 2006. When all else fails, go back to basics.

When I bought my USB JP1 cable from DIY, it never worked. Something with my motherboard and current windows settings. I parted it out for the 6 pin IDC. It proved to be useful for thie JP1.x cause.

e.axel · Post by **e.axel** » Fri Sep 15, 2006 2:04 pm

I'm glad to know that I am not alone!