2116 Erratic Behavior

[ek2116]

Hello All:

First, thanks for all the JP1 work. Those of you
involved in the development of IR.exe, etc. have
provided a great service to the user community.

Second, I did a search for this problem. I found some
references to other issues with the 2116, but
nothing describing my problem. If I missed
something, I apologize.

Now, here's my problem:

Background - been programming 2116 since 8/03. Just
installed extension 2. No problems with installation.

A few days ago, I started getting the "No response
from interface ..." message from IR. I checked the
interface cable and it worked fine. After plugging the
cable back in, communication was successful. It worked
fine for awhile, then the message started again, and
unplugging/plugging the interface did not resolve the
problem. So, I changed batteries. This resolved the
problem for awhile, but it returned. Each time it
returned, I removed/reinstalled (but didn't replace)
the batteries and the problem went away (temporarily).

Other than what I've mentioned, I haven't been able
to discern a pattern. It will work fine for several
uploads, then the problem will return and I'll have to
remove the batteries to "reset" it.

Any suggestions?

Thanks in advance.

[wwwoholic]

I have exactly the same problem (guess, you're using Simple interface). From what I gathered from reading and communicating here on the forum, it might be cured by slightly reducing resistor values. I did not try this. I simply reset remote every time (about once in 10-15 up/downloads) it happens.

[ek2116]

Thanks for the reply. I'm starting to notice a pattern. It seems to
be an issue with my home computer and not my work computer
(I'm not admitting that I do this at work!).

Could it be sending noise to the com port before the actual upload
begins?

Eric

[Capn Trips]

Hello All:

A few days ago, I started getting the "No response
from interface ..." message from IR. I checked the
interface cable and it worked fine. After plugging the
cable back in, communication was successful. It worked
fine for awhile, then the message started again, and
unplugging/plugging the interface did not resolve the
problem. So, I changed batteries. This resolved the
problem for awhile, but it returned. Each time it
returned, I removed/reinstalled (but didn't replace)
the batteries and the problem went away (temporarily).

Other than what I've mentioned, I haven't been able
to discern a pattern. It will work fine for several
uploads, then the problem will return and I'll have to
remove the batteries to "reset" it.

Any suggestions?

Thanks in advance.

Well, since you ask for "any suggestions". My limited, non-expert experience with a 2117 (same as 2116 for JP1 purposes) is that its ability to successfully communicate via the interface is quite sensitive to the battery voltage in the remote. If the batteries are too good, the computer (via the interface) can't put the remote into "reset" mode. If you remove the batteries, it won't work at all. After random success swapping in combinations of weaker and weaker batteries, I have a workaround that has (so far) worked every time.

To up/download, I REVERSE ONE BATTERY in the remote! Interface check passes every time, up/downloads work every time. The only nuisance is after an upload, you have to flip the battery around and it resets again, but I've found this to provide consistent results.

Your problem may be different, but this may be worth a try.

[wwwoholic]

To up/download, I REVERSE ONE BATTERY in the remote!

Are you serious?

[wwwoholic]

Could it be sending noise to the com port before the actual upload begins?

It looks more like the pins of the port are left in some random state, depending on the last operation performed, even on seemingly unrelated actions, like opening "print preview" in MS Word.
Sometimes the remote resets immediately upon connecting the cable. In this case I know for sure that up/downloading will fail until I remove the batteries.
Anyway, each time I have to tweak this, I'm telling myself - It's OK, you wouldn't need it again as soon as you finish with all upgrades. Unfortunately, in a week or so I find another feature to try and all this goes on again.

[Capn Trips]

To up/download, I REVERSE ONE BATTERY in the remote!

Are you serious?

As a heart attack!

[wwwoholic]

As a heart attack!

Have you ever heard about leaking or even blown up batteries? Now, THAT is known to cause a heart attack.

[johnsfine]

As a heart attack!

Have you ever heard about leaking or even blown up batteries? Now, THAT is known to cause a heart attack.

When you reverse a battery, you are recharging that (I assume non rechargeable alkaline) battery.

When you recharge a non rechargeable alkaline battery, usually it works (actually recharges the battery) though not as well as with a battery designed to be recharged, sometimes it makes the battery leak and very rarely makes it blow up.

BUT, you cannot combine the true facts in the above two statements to reach the untrue conclusion you seem to have reached.

It won't leak or blow up unless it is significantly heated by the recharge attempt. It won't be significantly heated by the insignificant amount of current drawn by a remote under the conditions that seem to apply here. (uploading/downloading, not even operating). Maybe, if you operated the remote with a battery reversed continuosly (press a key again before the backlight or lcd time out) for an hour or more, you might accumulate enough heat in the reversed battery to make it leak (not blow up) but I rather doubt it.

[wwwoholic]

Quote from www.duracell.com -
Attempts to recharge an alkaline battery may cause an imbalance within the cell, leading to gassing and possibly explosion on either charge or discharge cycles.
- end quote.

[Chuck_IV]

I had the same issues for a while, myself with my 2117, to the point where I would be lucky to get it to communicate 1 outta 10 times. By accident I knocked the parallel connection to my extention cable, off the top of my computer(where the JP1 cable connects to the Parallel extension cable I use). I picked it up and pushed the connection together firmly thinking the drop may have loosened it. Ever since I did that, the connection has worked like a charm.

So my suggestion would be to make sure the cable is firmly seated into the parallel socket.

[ek2116]

I think I'll just buy an 8810.

[The Robman]

If the problem is with your PC, the URC-8810 won't perform any better.

[Capn Trips]

Quote from www.duracell.com -
Attempts to recharge an alkaline battery may cause an imbalance within the cell, leading to gassing and possibly explosion on either charge or discharge cycles.
- end quote.

Look guys, I'm not a complete dolt! I know that PROLONGED reversal of a battery not designed to be reversed may lead to undesired consequences. Now I don't know about the rest of you, but when I upload/download, I immediately go out and test, so I'm not sitting around with reversed batteries in my remote. They're in that way, for about 30 seconds and then they're back to normal. No harm is done, and if that's what it takes to get the right output voltage from the series of batteries, and it works, then I see no harm there.

[ek2116]

[quote]If the problem is with your PC, the URC-8810 won't perform any better.[/quote]

D'Oh! I have to think before I type. I bought one anyway, just
because I wanted more keys. BTW, isn't the whole idea of
JP1 to elliminate multiple remotes? Now I'm thinking about the
next model to buy!

So, aside from all of the exploding battery debates, what would
cause the remote to behave better after reversing a battery?
Does it cause a momentary reverse current flow (until the
reversed battery's potential equals that of the rest of the
system) that discharges a component on the board?

Eric