Elk rp dial in problem

[Lavasponge]

I've been trying to dial into my M1 system to program using elk rp without luck. I've set G01 to 2 and G29 to 2 also.

If I make a normal call into the panel it answers and asks for my code. This all seems to work. I can go through and get the status fine. I can try this locally with the *** so I feel confident I've got the phone line wired properly.

When I use rp to dial in I can hear the panel answer and then I hear rp dial a few numbers. Shortly after rp throws up an error that states the panel didn't answer. I never hear any modem tones.

Any suggestions as to what I may be missing?

 

[Lavasponge]

I figured out the problem. There is a setting in the modem configuration that sets the time rp will wait before it concludes the panel didn't answer. I didn't notice it before so it's either a default value or my computer played a cruel joke on me. Anyway the length was set to 0. Which explains why it was acting the way it was.

I noticed it takes a few seconds before the panel modem kicks in so I set rp to wait at least 30 seconds. It connects now no problem.

To think I used to surf what little the net was at 2400 Baud. Even at 2400 it's better than programming manually on the keypad.

 

[KenN]

Okay okay, I'm just gonna come out and ask this. Since you're stating that 2400 baud is faster than keypad programming, am I to assume that you are making the connection from somewhere at or close to the Elk panel? If so, why not just use the Elk serial port at the default 115.2 kbaud?

 

[Lavasponge]

It does sound dumb doesn't it ..... My panel was hit by lightning and I think some of the magic smoke escaped (all electronics works off magic smoke, if any ever gets out it doesn't work right anymore). Anyway lightning hit my house. I think it came in over my relay board I had setup to control my sprinklers. Outputs 9-16 won't shut off now and my xep wouldn't link with my new network switch. By the way the old switch died as well as the Ethernet port on my Mac mini.

I think the serial port died also because nothing will connect. I don't have hyperterm on my computer to see if the panel is broadcasting anything. The funny thing is the Ethernet trouble message went away when I connected the new xep so something works on it. Im not sure how the trouble message is reported.

I said all that to say that in an a attempt to get my new xep to work I defaulted the panel. Which by the way was still working fine as a plain security system. After the default the new xep wouldn't work still nor could I connect straight over the serial port. I then either had to reprogram the whole system by the keypad or dial in.

I now have to make a cheap circuit of some type to control the sprinklers. I still have outs 1-3 and 6-7. I can rig something up until I save up enough to replace the panel.