DL900 connection problems

[Rustytek]

So, to start I hate GE tech support - especially Tim Clark. I called tech support because I was getting an error when attempting to connect to the NX-8E through a direct connection (RS-232 null modem cable) ... 0...0. In the diagnostic panel (in DL900) I was receiving back from the caddx "002D". I asked tech support about the problem. He asked what I was attempting to do. Naturally I responded "program my alarm system." His response was that DL900 only supported the NX584 and that my system did not support progamming with DL900. I of course pointed out the obvious - the RS-232 port and the button to use direct connect. He emphatically stated that the NX-8E was not programmable with the DL900 software. I continued to object to his claim and he forgot what his job was - customer service. Being very rude he refused to help me and told me to call someone else and that the NX-8E was not used for home automation and it CANNOT communicate through the serial port. I asked for his manager and then sat on hold for 20 minutes. The manager told me (who probably was not the manager but only his friend from the next cubicle over) that since I was not a licensed electrician with a security system installer certificate that they would not be able to help me. Now I hate GE tech support (esp. Tim Clark).

To the problem -

I finally got my computer to see the caddx NX-8E and through the diagnostic panel I was seeing the the return data "002D". In short, I was never able to communicate with the panel. I programmed all of my setting's to that described by Nitrox's guide at the homeseer forum and then attempted the changes mentioned by BSR (turn off all switches in location 211).

The primary problem is that the Caddx will not see any of my door/window contacts connected to the panel and I haven't a clue how to get the alarm panel to see them. I have connected them to every zone (1-8) without luck, the panel does not see them.

any advice?

 

[BraveSirRobbin]

First off, I can understand why your are upset. GE tech support is incorrect.

The DL900 CAN program an NX8e board (I'm doing it myself). I can even scan a document that came from GE support themselves which shows the connections they recommend to get the NX8e board to talk via the DL900.

I would also highly suggest that you call Jeff Carlson, Sales Engineer for Residential Solutions for GE Security, Inc. PM me and I'll send you his email. I'm sure he would be very interested in hearing of your experience with GE's tech support. I met Jeff and he is a "can do" type person so he would not take this lightly!

Also, kindly point Jeff to this post so he knows the number one security and automation support forum is monitorng this particular thread!

Second, when you say the panel is not "seeing" your zones, how are you monitoring them? Via keypad? That would seem to be the best way.

Do you have a keypad that you could see if the zones were open or closed? Do you have them set for EOL (if you are using them) or without that resistor (have to set that option in the DL900 or your zones would never change state).

Are you really connected via the DL900? Are you logging in with the administrators credentials?

Off the top of my head, those are the things I would look for.

Good luck,

BSR

 

[BraveSirRobbin]

Thinking about this a little more, can you take one of the EOL resistors and just place it across one of the zones and see if it changes status? If that doesn't do it try shorting it out with a plain wire.

Do you have some closeup pics of your setup? Can you list the pertinent settings that you programmed the NX8e board with? Did you double check those settings to make sure they were correct? Where did you get the settings from (a CocoonTech post in the past by me I'm guessing)?

 

[carry15+1]

GE/Caddx has never been big on end-user support.

I originally tried a dirrect connect to my NX8E, but gave up and bought the NX584 which makes life a whole bunch easier. It works fine with the DL900 software, and it clips directly to the data buss.

The NX584 is very reasonably priced and will make things easy for you. Buy it.

 

[HighTest]

GE/Caddx has never been big on end-user support.

I originally tried a dirrect connect to my NX8E, but gave up and bought the NX584 which makes life a whole bunch easier. It works fine with the DL900 software, and it clips directly to the data buss.

The NX584 is very reasonably priced and will make things easy for you. Buy it.

Does the NX-584 provide any additional capabilites over the NX8E? Just curious as I see many that are able to communicate to the NX8E without the NX-584 board. In addition, if one picked up an NX-8 V2 and added thte NX-584 board to the system, what features would be lacking in comparison to the NX8E?

Thanks! And sorry to thread hop.

 

[carry15+1]

I believe I quoted the wrong part should have said NX-586.

The 586 is a device that clips onto the 3-wire buss and plugs into a serial port for direct connection to the NX8E.

Check this link - don't know if the NX-588 was ever released.

http://www.gesecurity.com/portal/site/GESe...000592d7003RCRD

 

[Rustytek]

where can I turn off Eol resistors. I did not wire them into the walls (oops). I did attempt wiring one with a resistor to test but the panel still did not see it.

sorry for typos - using pda

 

[BraveSirRobbin]

where can I turn off Eol resistors.  I did not wire them into the walls (oops).

I didn't use EOL resistors either in my Caddx NX8e install.

Just go to the DL900 screen, then Advanced, Zone Types and select the desired zone type(s) you are using. Then just check the EOL resistor defeat for that zone type. Screen shot below shows how to defeat a "type 3" zone.

Don't forget to Send the setting to the panel after you save it in the DL900 software.

 

[Rustytek]

am currently on vacation - hence the pda. I have yet been able to get the dl900 to connect to the panel. I am able to toggle the chime with the HS plugin but get an error when attempting to connect with dl900 (this is where the issue with tech support came in). I cannot recall the error message right now (I think it was error code 83 - I think). I will be back home on tuesday so I will post the specifics then.