jp1.3 atlas remote issues

greenough1 · Post by **greenough1** » Fri Oct 12, 2007 9:36 pm

Hi,
Just received my atlas Jp1.3 remote and jp1.2 cable from diygadgets reseller. I've downloaded the latest tools (IR7.06, etc.). IR desn't recognize the interface, but the led (cbl button) blinks.

The jp1.x test program provides the following blinking sequence:
blink, blink (second blink is short)
pause
blink, blink

The program displays no JP1.x compatible remote found!

The interface is wokring and connected the remote.

I've been through Tommy's trouble shooting guide, and there's not much detail about what the blinks mean.

Best,
jeff

greenough1 · Post by **greenough1** » Fri Oct 12, 2007 10:35 pm

The remote remains functional, e.g. I can program it to control my Oppo dvd player using the 1525 setup code.

I've tried a reset (981) and that didn't help.

I downloaded the tester program in diagnostic area that had debugging info turned on, but it's a jp1.2 version and doesn't like jp1.3 remotes.

I am connected through the serial port on my ibm thinkpad (a22p). I don't have a usb to serial adapter to test on another computer.

It seems to be doing much more than just giving the 2 blinks at the end of the test. Anyone have any ideas?

greenough1 · Post by **greenough1** » Sat Oct 13, 2007 4:28 pm

No ideas?

unclemiltie · Post by **unclemiltie** » Sat Oct 13, 2007 6:29 pm

my first recommendation is to try another computer. I have one Dell (Latitude L400) that I can't get the JP1.x interface to work on to save my life and another Dell (Latitude D400) that it will work but only when plugged into the computer, not into the docking station.

If you're looking for a USB to serial converter, look for the topic where I asked about using them on a Mac, there's a link to the one I bought on ebay for something like $2.00 and a couple of bux shipping. It works perfect on my mac running Windows in a VM.

greenough1 · Post by **greenough1** » Sat Oct 13, 2007 7:57 pm

Thanks unclemiltie. I was thinking I needed to pick up an adapter (usb to serial), to rule out the latop. This laptop (that I'm typing on) is the one I use for all my JP1 work. It does have USB and now that it's running winxp, has a decent implementation of USB albiet version 1.

I'll try that see how I do. Did you ever see more than the final 2 blinks when you had issues with jp1.xtest?

I've never been clear on where one gets the drivers for the USB adapters. Does winxp have them natively, do you use the disc that comes with the USB to serial adapter, or get them elsewhere?

Best,
jeff

speaker.guy · Post by **speaker.guy** » Sat Oct 13, 2007 10:20 pm

I successfully communicated with that remote before I shipped it.....

greenough1 · Post by **greenough1** » Sat Oct 13, 2007 11:05 pm

Thanks Speaker guy. So it must be my port/connection. How did you interface with the remote, machine type, cable(s)?

Thanks,
jeff

Post by **vickyg2003** » Sat Oct 13, 2007 11:36 pm

Jeff, although the JP1.x interface doesn't have the battery issues that the simple JP1 interface does, have you in fact checked to make sure you have fresh batteries? When my batteries were failing I had all sorts of weird remote behavior. My symptoms were a 4 blink(weak battery), pause, 2 blink (reset), shortly after that I started getting a 2 blink on every key. It seemed I had a whole package of bad batteries.

greenough1 · Post by **greenough1** » Sun Oct 14, 2007 12:05 am

Hi Vicky, I tried two sets of batteries. With my luck lately, maybe third time will be a charm.

Tried 6 other pairs. no dice.

The laptop is clearly communicating with the remote via the port. If I change settings (speed, stop bits, etc.) on com3, the remote cbl light blinks.

What settings should my com port be set to?
My defaults on com3 are: 9600bps, 8 data bits, no parity, 1 stop bit, no flow control.
Resources tried wereI/O range 02f8-02ff, irq 3 as well as 03f8-03ff, irq 4.

I've tried 2 stop bits (as per Tommy's write-up).

Always the same behavior. (note that I editted the blink behavior in the top post.)

jeff

unclemiltie · Post by **unclemiltie** » Sun Oct 14, 2007 5:29 am

you should be at 38400 bps

greenough1 · Post by **greenough1** » Sun Oct 14, 2007 9:05 am

I've gone back to Tommy's trouble shooting guide. The version of comtest didn't work, so I went to B&B electronics and downloaded and installed it. The DTR (reset circuit) is working. No information seems to be received, when sent via comtest.

I'll get some resistors tomorrow and test the interface.

Also I think I'll ping the ebay seller and see about an exchange.

jeff

greenough1 · Post by **greenough1** » Sun Oct 14, 2007 9:06 am

I tested 38400 bps down to 300, no effect.

jeff

greenough1 · Post by **greenough1** » Sun Oct 14, 2007 4:01 pm

Ok. As I posted above the reset circuit is working as verified by comtest blinking the remote when toggling RTS.

Using Tommy's resistor debugging trick, I get no received characters. So either there's an assembly problem or the circuits in the interface are not working.

I verified that shorting pins 2 and 3 on the serial port gives echo of characters. Thus the serial port is working and transmitting.

I guess I need to open up the interface and see if I can see something obvious. I was trying to avoid this!

jeff

greenough1 · Post by **greenough1** » Sun Oct 14, 2007 4:13 pm

I looked inside and see nothing obvious. It is VERY small and I don't think I could fix it even if I knew what was wrong!

Anyone have an ideas?

Best,
jeff

unclemiltie · Post by **unclemiltie** » Sun Oct 14, 2007 7:09 pm

did you try another computer?

Seriously, I have the same symptoms on my Dell L400, remote blinks so it's getting the reset and the COMtest thing works but I cannot seem to make it communicate with a remote even though I am using an interface that works on another computer.