Page 5 of 8

Posted: Fri Sep 22, 2006 10:58 am
by e.axel
First: I am a retired engineer with neither modern programming or hardware design skills.
My question is the same as it was when I opened this thread; "Where are we?"

We have a cable design from a reputable source (DIY) that even he admits only works with one of his computers. We have debugging and Beta application software that don't look like they are telling us much about what the problem is. Prelude has submitted all of his debug run results, and no one else has commented.
I have not seen any comment/comparison of that cable design with others which may work "better".
Unfortunately, Prelude will not return my cable before I go away on vacation for the month of October, so I can't follow up on the latest debugger until November. I will continue to monitor this thread...
See you all in November.

Posted: Sun Oct 01, 2006 12:34 pm
by prelude
Just downloaded IR7.0 beta2d, same problem.

I have removed D1 and Q1 from the PCB, IR7.0 Beta2 works fine. I have also updated the instructions on my site.

So, you can convert a jp1.x interface to a pure jp1.2 interface and it works great.

Posted: Sun Oct 01, 2006 12:52 pm
by e.axel
Just sailed from Valencia, Spain. I'll try it when I get home!
Thanks!
Elliot

Posted: Sun Oct 01, 2006 3:16 pm
by binky123
prelude wrote:Just downloaded IR7.0 beta2d, same problem.

I have removed D1 and Q1 from the PCB, IR7.0 Beta2 works fine. I have also updated the instructions on my site.

So, you can convert a jp1.x interface to a pure jp1.2 interface and it works great.
Removing Q1 basically disconnects RTS from the IDC-5 JP1.2 BKGD pin. If this works then that might suggest that the BGKD pin is being held low coming out of reset of the remote.

With the new jp12serial.dll driver included with beta2d, you should be able to just solder IDC-4 and IDC-5 together to get a JP1.1 compatible cable. There should be no need for Q1/R1/D1.

Posted: Tue Oct 03, 2006 4:31 pm
by CindyD
Hi prelude
I got my cable yesterday from diygadget and have tried several things to get it working. Here is my thread. http://www.hifi-remote.com/forums/viewtopic.php?t=7077
I tried the second tester and it says " This application has failed to start because jp12serial.dll was not found. Re-installing the application may fix this problem. I re-istalled x3 and I still get this message. Do you have any suggestion to get this cable working?

Posted: Wed Oct 04, 2006 1:53 pm
by prelude
sorry I didn't monitor the other thread but looks like you have solved your problem?

CindyD wrote:Hi prelude
I got my cable yesterday from diygadget and have tried several things to get it working. Here is my thread. http://www.hifi-remote.com/forums/viewtopic.php?t=7077
I tried the second tester and it says " This application has failed to start because jp12serial.dll was not found. Re-installing the application may fix this problem. I re-istalled x3 and I still get this message. Do you have any suggestion to get this cable working?

Posted: Mon Oct 30, 2006 2:19 pm
by e.axel
Finally got back from vacation, got the cable, removed q1 and d1, and when I got the cable plugged in the right way, it worked fine!

db-9 jp1.x results

Posted: Tue Oct 31, 2006 12:07 pm
by tennisman
I built from scratch the db-9 serial version of tyler's jp1.x interface from the latest pdf file. Hooked it up to a comcast 1067(jp1.2) and it didn't work with IR7.0 beta2d. Also failed the tester.bat program. Then I removed the leads connecting to Q1 and R1 making it into a jp1.2 version. It worked! Passed the tester.bat and uploaded and downloaded to the comcast 1067. Then I connected just the pin 5 lead(from the collector of Q1) to the IDC and plugged it into the comcast 1067 and it didn't work. Verified this back and forth several times. Thought I'd pass along my experience. Thanks to everyone involved in this forum.

My own strange JP1.2 experience...

Posted: Fri Dec 01, 2006 10:40 pm
by JoeVulture
I purchased a JP1.2 cable from DIY Gadget, received it tonight.

It won't work on the serial port of my Dell Inspiron 600m with Windows XP Professional, but it does work if I use my USB to serial adaptor (a Keyspan USA-19QW) instead (on the same laptop). Go figure.

I decided to share this in case it helps somebody out.

-- Joe

Posted: Sat Dec 09, 2006 3:24 pm
by prelude
This is strange... did you select the correct COM port?

Posted: Sat Dec 09, 2006 5:09 pm
by JoeVulture
prelude wrote:This is strange... did you select the correct COM port?
If you're referring to me, then yes, I did try all COM ports. I ran the tester program mentioned earlier in this thread, and it didn't pick up the remote (although for some reason, the cable light would blink as if it was working). When using the USB to serial cable, it worked fine.

-- Joe

Posted: Fri Feb 02, 2007 11:26 pm
by cursedgriffin
i purchased a JP1.2 cable from diygadget and all i get is the "failed to open JP1.2 interface" error.

When i run the tester program it says it found a JP1.2 remote.

The only thing i can think of is that IR7.00 beta 3 needs to be updated

Posted: Sat Feb 03, 2007 12:54 am
by cursedgriffin
i just tried to get IR7.00 beta 3 to work on 2 computers and it still says "failed to open JP1.2 interface"....and on both comps the test program says "found a JP1.2 remote".....i will officially start pulling my hair out. :evil:

Posted: Sat Feb 03, 2007 1:44 am
by cywelchjr
Make sure there is not a modem or other serial device on a lower com port number than the interface is on.

I have also found that sometimes with a USB to serial adapter that it will only work if I plug in the adapter before I turn on the computer.

I found 100% failure if I had the cable on COM5 unless I disabled my modem on COM3. If I moved the cable to COM 1 or 2 then it worked even with the modem enabled unless I plugged it in with Palm hotsync enabled for serial connection in which case hotsync seems to think it's supposed to open the new port and IR can't open the port.

Posted: Thu Feb 15, 2007 11:33 am
by binky123
cursedgriffin,
Are you able to measure the voltage at the remote pin 6? Another user is reporting similar issues and measured +2.6v at this pin. My guess is that this is marginal and is causing switching problems for the Q4 transistor.