Timeout pb with IR.exe and SA AT2000-4

nioux · Post by **nioux** » Thu Jul 21, 2005 1:26 pm

Hello,

I discover the JP1 protocol since few days to program my remotes :
- a Scientific Atlanta AT2000-4 and
- another Scientific Atlanta E2050-ER1.

So I have built a simple interface (parallel with 2 R=10K and one 1N4148) and I test it with the remote E2050ER1. It looks good : IR.exe recognize my remote (signature is "ER10m66"). When clicking on "Download from remote", the led on remote blinks twice immediately.

But when I try to "Download from remote" with the AT2000-4 remote, the IR.exe warned me with "Did not rcv response ... after sending bus address (ErrNo=6, Param=0)" while the led on the remote blinks twice but 2 seconds later. I think the remote is slow to give an ack and IR.exe aborts by showing me the message.

So I got a question : is it possible to have a timeout in IR.exe between sending a command and waiting for the response ? I tried to change the "Transmission delay" with no success.

I also ask if someone has already used JP1 tools (IR, KM and RM) with these remotes ?

I thank by advance for your answer,

Nioux

whompus · Post by **whompus** » Thu Jul 21, 2005 1:39 pm

The last page on this thread has turned to that remote.

Post by **The Robman** » Thu Jul 21, 2005 2:19 pm

nioux wrote:So I have built a simple interface (parallel with 2 R=10K and one 1N4148)

You must have found an obsolete design for the Simple Interface, the current design calls for 1k resistors instead of 10k. We have also found that a Schottky Diode 1N5818 works better than the more traditional 1N4148.

nioux · Post by **nioux** » Thu Jul 21, 2005 4:09 pm

Hi,
thank you Whompus and Rob.

I read the end of the thread and I download the RDF, it would help me later if IR.exe recognizes my remote.

I would build a new interface with 1k resistors and 1N5818 diode but I am not sure that is the cause of my problem (but I may be wrong). My remote takes too much time to ack the IR.exe command but it does. So I could think the interface is nearly good and the problem is that IR.exe don't wait too long for remote's ack.

Can my old interface design affect the remote response delay ?
Do you think that a new one (R:1K D:1N5818) may shorten this delay ?
In the case it does not : is it possible to have a longer timeout fonctionnality in IR.exe ?

And I thank you again for your answers ...

Nioux

Mark Pierson · Post by **Mark Pierson** » Thu Jul 21, 2005 6:01 pm

nioux wrote:is it possible to have a longer timeout fonctionnality in IR.exe ?

Try increasing the transmission delay (Advanced, Transmission Delay).

Capn Trips · Post by **Capn Trips** » Thu Jul 21, 2005 7:47 pm

Try various combinations of batteries in the remote during read/write cycles. Try with fully charged batteries, with removed batteries, with partially or completely discharged batteries (simulate by reversing one or two - if a 4-battery remote)

new-guy · Post by **new-guy** » Fri Jul 22, 2005 8:33 am

I have been working with one of the gurus here on getting that RDF ready.

so far I have not had any issues with communicating with the remote. It should work with the batteries in. I am also using the simple interface. I cannot remember right now which diode I am using or the resistance values.. all i remember is that it was the latest rev of the design that I used maybe 6 months back.

In any case find that latest rdf and you should be having more luck with it.

nioux · Post by **nioux** » Mon Jul 25, 2005 8:41 am

Hi,
thanks for your replies.

Try increasing the transmission delay (Advanced, Transmission Delay).

I already tried to increase the transmission delay up to 750 but it did not change anything. So I tried bigger values like 5000 or 50000. All it does is that the error message is displayed later but the remote's led blinked twice 2 seconds after the error message. It does not change anything.

Try various combinations of batteries in the remote during read/write cycles. Try with fully charged batteries, with removed batteries, with partially or completely discharged batteries (simulate by reversing one or two - if a 4-battery remote)

I tried various combinations and as new-guy said :

It should work with the batteries in

I tried :
- with full batteries => Error message "Did not rcv response after sending bus address ..."
- with used batteries => Same error message (maybe the batteries were not enough used)
- with no batteries => Same error (it is curious)
- with the JP1 unplugged => Another message saying "No response from interface ..." (that's normal)

I have been working with one of the gurus here on getting that RDF ready.

so far I have not had any issues with communicating with the remote. It should work with the batteries in. I am also using the simple interface. I cannot remember right now which diode I am using or the resistance values.. all i remember is that it was the latest rev of the design that I used maybe 6 months back.

In any case find that latest rdf and you should be having more luck with it.

I sorry but my english comprehension is not really good. Do you mean that you never had problem with an AT2000-4 remote ? Do you remeber which version of IR.exe did you use ?

Thank all, I will try with another AT2000-4 remote and if it does not work,
I would try with a newer interface.

Nioux

JP1 Remotes

Timeout pb with IR.exe and SA AT2000-4

Timeout pb with IR.exe and SA AT2000-4

Re: Timeout pb with IR.exe and SA AT2000-4