JP1 Remotes

[IBNobody]

My Atlas OCAP 1056 (30333033) will not connect with IR.exe.

When I try to download data (even RAW), I get a message:

"Jp12 read failed -1."

Tommy's JP1xTest program returns:

[binky123]

Try copying the jp1xserial.dll into your IR7 folder and name it jp12serial.dll. There have been some timing changes over time which may be affecting your cable and the JP1.3 remote. Send me a PM so we can try to figure out what's going on.

[binky123]

Based on some logs provided by IBNobody, The "Jp12 read failed -1" error means the address to read data from is out of range. That was one of the changes made to the driver as the original one wasn't correctly checking the EEPROM address range.

I'm still trying to figure out why it is using a bad address in the first place.

[jetskier]

Binky,

FWIW, I had to revert to an older copy (June?) of the jp12serial.dll. The new version will not work with my interface and/or remotes (10820s).

[IBNobody]

Ok... I've put my PS3 adapter on hold to focus on this issue. I'm in talks with Binky123 to help get my JP1.3 working.

As we speak, I have Tommy's JP1x test running in a batch loop, and I have my Intronix LogicPort logic analyzer monitoring all 4 signal lines. (BTW: That little thing rocks.)

Using my 10251025 atlas remote (JP1.2), I get RS232 packets coming out showing the 10251025 sig in ASCII.

When I hook up either of my 30333033 Atlas 1056 OCAPs, I get zilch.

I've been able to pull out the 30333033 sig before, but it was never a constant thing. I haven't been able to do it recently. The whole darn setup is just too intermittent.

How intermittent? Well... The 10251025 doesn't always work. I fought at home for hours trying to get it to work. Other times, it works flawlessly.

I've noticed something odd, though. Sometimes when the 10251025 fails, it fails because it doesn't recognize a seemingly valid 0x06 ACK signal. I've looked at a bad and a good, and the differences between the two were less than 100ns.

[greenough1]

Hi IB,
I think you're running into the same issue I am/was. I've sent my interface and remote off for "analysis".

I believe that my serial port is working, but there's an issue with the remote and/or interface. I wish I had a jp1.2 remote to test.

This doesn't help you, but I think there's some software/hardware issue at play, probably at initialization of the remote to put it into serial mode. Maybe in a couple of days, after analysis, we'll get some good information.

Best,
jeff

[IBNobody]

[greenough1]

I got Tommy Tyler interested in my issue, I think, because I went through all of his trouble-shooting guide and helped him update it. I sent my remote and interface to him.

[IBNobody]

[greenough1]

Hi IBNobody,
Check your forum pm

jeff

[IBNobody]

Ok... After talking with Tommy and Binky123, here are my personal findings:

1. My personal JP1.X interface is flaky. Pure and simple, it's poor workmanship on my part.

2. My DIY-bought JP1.2 interface had R7 and C2 swapped. Swapping them back fixed all problems. Jeff's interface appears to have the same problem. I've let the DIY guy know.

I can now access JP1.2 and JP1.3 remotes using the DIY-bought interface.

[greenough1]

Tommy can chime in and correct me, by mine was worse, a resistor had one end unsoldered. The pull-up resistor location had a cap installed...

Based on these two samples, what would a swap have produced (no slam intended, just a rhetorical question).

Tommy to the rescue!

jeff

[Capn Trips]

Well, it appears that DIY is having some quality control problems, then. I bought my JP1.2 cable from them in June and it works fine with my JP1.2 and 1.3 remotes through a serial-USB adapter. Perhaps they have had a bit of a lapse in their advertised claim:

[IBNobody]

[pmiller056]

I have had similar errors with home made discrete transistor interface caused by low gain transistors. Please see http://www.hifi-remote.com/forums/viewtopic.php?t=6950 thread in Hardware section for further info.

Peter