Jump to content
c4toys

NX-8 security V2 proxy upgrade?

Recommended Posts

On 6/22/2019 at 11:09 AM, Kevin L said:

NX8 NX8V2 require the NX584 automation module

NX8E requires the P-0003 Ribbon to DB9 cable 

The units work fine on OS3 as long as you are using the above parts, the correct driver, and setup the panel and driver per the instructions in the driver. 

Do you know what the name of the the diver is i cant seem to locate it 

 

Share this post


Link to post
Share on other sites

On 7/21/2019 at 3:00 PM, dave8788 said:

Do you know what the name of the the diver is i cant seem to locate it 

 

It's been named , what, 3 times in this thread? Search for NX584

Share this post


Link to post
Share on other sites
On 7/12/2019 at 10:25 AM, grant0830 said:

sonit has been initializing for about 3 hours. Stills shows this ... 

36C08B4D-10A3-4613-B6E6-EBDCFE8D0C3D.pngD

Did this ever resolve itself after those 3 hours?

Share this post


Link to post
Share on other sites

Resurrecting this thread.  I made the move to OS 3 and it took out my NX-587.  So I've ordered the 584, but it sounds like there is some panel programming that is necessary?

The unfortunate part is my alarm/local C4 company really doesn't support the NX panel any longer (they've moved on to other alarm suppliers), so I'm a bit SOL with them supporting me.  To the point where I've been debating whether to just abandon the NX panel and go with something else.  If anyone knows how to easily get the 584 to work after going from the 587, I would greatly appreciate it.

I really have no issues with the NX setup, when it integrates with C4, it's certainly nice to have. 

Share this post


Link to post
Share on other sites

@Scrib it's relatively straight forward.  With the 584e connected to the system, just entering and exiting programming mode on the NX panel should add the 584e to the system (you don't need to remove the 587e - just disconnect it) - note that there is a delay after exiting as the panel checks for devices.  In programming mode on the NX panel, you need to set it up per the 584e driver instructions (the instructions tell you settings to use) - there are only a few changes compared to the 587e configuration.  Note that the driver says to disable any unused partitions/zones as otherwise they will show up in the C4 interface.

The instructions say that a NULL modem cable is needed - not sure that's the case with the 587e, but I had to change my wiring to get the 584e to work with my cable (so, I'm thinking that the 587e didn't need a null modem cable).

When all connected up, the 584e driver will report "Driver Initializing" while it reads in the partition/zone information from the panel.  If you turn on trace Log Level in the Properties page of the 584e driver you can see the communication between the panel and the driver as the initializing process works - if you don't see any activity, then I'd check your cable...

the 584e installation manual should come with your 584e and has the installation instructions to follow.  You can find it here too: https://www.surveillance-video.com/media/lanot/attachments/customimport/NX-584E-Installation-Manual.pdf

Reach out if you have questions...

 

Share this post


Link to post
Share on other sites

Thanks.  I am way out of my league on NX programming.  I'll get a copy of the instructions and see what needs to happen.  The install manual is rather greek to me.

Share this post


Link to post
Share on other sites

@brente, do you happen to have the 584 C4 instructing handy?  I don't have the driver installed, yet but trying to find them online so I can program my panel accordingly.

Share this post


Link to post
Share on other sites
On 6/22/2019 at 9:09 AM, Kevin L said:

NX8 NX8V2 require the NX584 automation module

NX8E requires the P-0003 Ribbon to DB9 cable 

The units work fine on OS3 as long as you are using the above parts, the correct driver, and setup the panel and driver per the instructions in the driver. 

Want to upgrade to OS3. I have E5 Controller and NX-8E/NX-8E Ver 17. The current driver is securitysystem_232_genetworx.c4i. What driver do you use for the security system to work with OS3? The upgrade reports indicates: "To continue you will need to remove this driver or apply an updated driver which uses a V2 Security proxy for this device."

Share this post


Link to post
Share on other sites
On 6/22/2019 at 10:09 AM, Kevin L said:

NX8 NX8V2 require the NX584 automation module

NX8E requires the P-0003 Ribbon to DB9 cable 

The units work fine on OS3 as long as you are using the above parts, the correct driver, and setup the panel and driver per the instructions in the driver. 

Do you know if you can use the 584 with the NX8e?  The panel is a long way from the controller, so the P-0003 Ribbon really won't work.  However, I do have a 584 board but can't seem to get it to work.

Share this post


Link to post
Share on other sites

This is the error I keep getting.  On the GUI, it keeps says "Driver Initializing..." and will work some of the time, but look it it keeps timing out when calling for the zone names.  There are no names in that tab in Composer.

 

Starting Timer: Log Timer
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(Zone 1)
Request.ZoneName called for zone [1]
SendMessageCB:    Request[
022300254C
]
Starting Timer: SendCommand
Starting Send Timer:  2 for  (timer_interval = 250, timer_units = MILLISECONDS)
Send Timer expired
DeviceConnectionBase:SendNextCommand
SystemInitComplete(ZonesNameInitialized)
Received Data: [
011C1D1]
ReceivedFromCom  ReceiveBuffer is now {{{
011C1D1}}}
Received Data: [E
]
ReceivedFromCom  ReceiveBuffer is now {{{
011C1D1E
}}}
HandleMessage: Message[1C]
HandleMessage: MessageType[1C]
DispatchMessage: Function[Response.CommandRequestFailed]
Response.CommandRequestFailed received
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
Sending Display Text on Binding 5002: Driver Initializing...
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(Zone 1)
Request.ZoneName called for zone [1]
SendMessageCB:    Request[
022300254C
]
Starting Timer: SendCommand
Starting Send Timer:  2 for  (timer_interval = 250, timer_units = MILLISECONDS)
Send Timer expired
DeviceConnectionBase:SendNextCommand
SystemInitComplete(ZonesNameInitialized)
Received Data: [
011C1D1]
ReceivedFromCom  ReceiveBuffer is now {{{
011C1D1}}}
Received Data: [E
]
ReceivedFromCom  ReceiveBuffer is now {{{
011C1D1E
}}}
HandleMessage: Message[1C]
HandleMessage: MessageType[1C]
DispatchMessage: Function[Response.CommandRequestFailed]
Response.CommandRequestFailed received
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
SystemInitComplete(ZonesNameInitialized)
Sending Display Text on Binding 5002: Driver Initializing...
SystemInitComplete(ZonesNameInitialized)
OnPropertyChanged(Log Mode) changed to: Off

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...