URC-10820 Interface Problem

pfiesm · Post by **pfiesm** » Tue Feb 13, 2007 5:36 pm

First time I ran it I got this:

tester version 0.00
jp12io.dll version 0.00
Parsing command list file tester.dat
Opened COM1
Got 00 instead of an ACK!
JP1.2 remote found!

Subsequent times I got this:

tester version 0.00
jp12io.dll version 0.00
Parsing command list file tester.dat
Opened COM1
Opened COM3
Got 45 instead of an ACK!
JP1.2 remote found!

Then I ran the newer version from the link you gave first:

tester version 0.01
jp12io.dll version 0.00
Parsing command list file tester.dat
Openning COM1
DCB paramaters:
DCBlength=28
BaudRate=38400
fBinary=1
fParity=0
fOutxCtsFlow=0
fOutxDsrFlow=0
fDtrControl=1
fDsrSensitivity=0
fTXContinueOnXoff=0
fOutX=0
fInX=0
fErrorChar=0
fNull=0
fRtsControl=1
fAbortOnError=0
fDummy2=0
wReserved=0
XonLim=2048
XoffLim=512
ByteSize=8
Parity=0
StopBits=0
XonChar=17
XoffChar=19
ErrorChar=0
EofChar=0
EvtChar=0
wReserved1=0
Got 00 instead of an ACK!
JP1.2 remote found!

Not sure I know how to interpret these results?

binky123 · Post by **binky123** » Tue Feb 13, 2007 6:53 pm

The byte should not be 00 but 06. I see you did get 45 returned from COM3. The other thread suggested deleting/disabling any onboard modems that you might have.

You can run the same programs against your working remote to see if there are any differences in the output.

pfiesm · Post by **pfiesm** » Tue Feb 13, 2007 7:03 pm

This is the output from the latest tester version on my working remote:

tester version 0.01
jp12io.dll version 0.01
Parsing command list file tester.dat
Openning COM1
DCB paramaters:
DCBlength=28
BaudRate=38400
fBinary=1
fParity=0
fOutxCtsFlow=0
fOutxDsrFlow=0
fDtrControl=1
fDsrSensitivity=0
fTXContinueOnXoff=0
fOutX=0
fInX=0
fErrorChar=0
fNull=0
fRtsControl=1
fAbortOnError=0
fDummy2=0
wReserved=0
XonLim=2048
XoffLim=512
ByteSize=8
Parity=0
StopBits=0
XonChar=17
XoffChar=19
ErrorChar=0
EofChar=0
EvtChar=0
wReserved1=0
JP1.2 remote found!

binky123 · Post by **binky123** » Tue Feb 13, 2007 9:52 pm

The output parameters look the same except this remote sent back 06 so you don't see the "got 00 instead of ACK" msg. I'm out of ideas. There is something odd about your remote.

binky123 · Post by **binky123** » Wed Feb 14, 2007 8:28 am

You might want to use your voltmeter to check voltage at IDC-4. It should be +3.3v when tester is not running. When tester is running it should fluctuate between 3.3v and 0v. After verifying that it is receiving a byte, you can try the same thing on IDC-6 to verify that the remote is sending a byte.

pfiesm · Post by **pfiesm** » Thu Feb 15, 2007 7:06 am

Had a few minutes to play with this last night. Here is what I found:

Hooked up the volt meter on the bad remote. Pin 4 was 3.3v and fluctuated when running the tester. Pin 6 was 2.6v and also fluctuated when the tester ran.

Now it starts to get interesting. I did the same voltage tests on the working remote and had the same results. But, while I was runing this test, I noticed the tester would sometimes report 'Got 00 instead of an ACK! ' on this one also.

Then I tried the working remote in IR using 'Check Interface' and it was still OK, so I tried the bad remote, and it was also OK. I tried this a little more and I think what I came up with was: If you run the tester first on the remote, then run IR, it seems to work, but this was far from consistent. If you disconnect the remote, then reconnect it, you need to run the tester again.

At the end of the day though, I was able to write to the remote. I still don't think it would work without first running the tester, but I need to play with that a little more.

binky123 · Post by **binky123** » Thu Feb 15, 2007 10:05 am

Ok, this seems to suggest that resetting is ok, sending to the remote is ok, the remote sees it ok and sends something back. Maybe the +2.6v on IDC-6 is an issue? I measured the voltage on my URC-10820 and I'm seeing +3.6v. Can you measure the voltage after the R4 100K resistor? Also, can you measure the voltage at DB9F-2? It should fluctuate between 0v and +10v. Maybe there is something along this path of the circuit. Can you also measure voltage at DB9F-4? I believe it should be +10v after reset of remote.

If voltage at IDC-6 is an issue, you may need to add a pull-up resistor from IDC-6 to IDC-1 or remove/reduce the R4 100K ohm resistor into the base of Q4. My guess is that the Q4 transistor is inconsistently switching so DB9F-2 stays at +10v which will be seen as a zero bit(Space). Hence, tester says got 00 instead of ACK byte.

pfiesm · Post by **pfiesm** » Thu Feb 15, 2007 5:04 pm

OK, I think I found something. When I hook up the voltage meter to IDC 6 I don't always see a voltage. If I wiggle the connector around, I can get it go to 2.8v, but it's pretty positional. I think I just got lucky a couple times last night. If I do get it in the right position and there is a voltage, then IR will work. Wiggling the connector in my other remote makes no difference, so I don't think its my connector, I think it's the header in the remote that must have a loose solder joint on pin 6. So, I guess I'll try to get the case open and see if I can resolder it.

I really apprieciate all your help Binky!

Marty

binky123 · Post by **binky123** » Thu Feb 15, 2007 6:59 pm

You might be able to just heat pin 6 enough so it re-melts the solder on the other side. If not, then opening the case to look at the solder joint is a good idea. Good luck.