Can't connect to P3200

[Lou Maresca]

I have a brand new p3200 (72c4 firmware) that the plugin will not connect to. Works fine with Quickloader and I can see keypad messages coming out to a terminal program(Putty).
I've attached some log data that might be of help. I'm using a PC-Mini but as I said, Quickloader is happy with it. Any ideas? Napco.txt

[nfrobertson]

Please see the comment in the top sticky post (also copied below). You might try turning off TCP Communications to get the panel to work with the plugin. If that's not an option for you maybe due to panel devices you plan to use, then your panel may not be compatible with this plugin. There are currently no plans to enhance this plugin to support the newer features of Napco panels like TCPIP (unable to get developer documentation is primary issue). This plugin was created under HS3 to maintain compatibility after the HS2 to HS3 upgrade a few years back.

NOTE! P3200 panels with hardware V20 and newer (circa 2003) may or may not support GEM-AUTOMATION. There have been conflicting reports of success with newer panels as long as "the TCP Communications is not checked." Older P3200 with V11 hardware reportedly do.

[Lou Maresca]

TCPIP isn't turned on. It just doesn't want to work. If you have any other ideas, I'm willing to try them. Thanks

[nfrobertson]

You could turn debug logging on and post your log. That will help see what is or isn't working.

[brianjhomeseer]

So, I have 9600 panel with the following software version: GP9600.V72C31/04/02. TCP/IP is not checked. Quickloader works fine on the same PC that HS3 is installed on. When I start up, it doesn't connect to panel, but I do see status updates in the log file. I was searching Napco's web site and finally found a "newer" version (2013) of the GEMINI Home / Building Automation Development Specification. In it, it says the following:

Alternate Master/Slave Communication (NOT requiring RTS/CTS)
(supported in version 40b and above for GEM-P3200, 30B and
above for the GEM-P9600, version 4A and above for the GEM-X255)

In order for the PC to get the attention of the panel, the following protocol is to be followed:

1. PC sends 87H out serial port.
2. When panel is ready, it will respond with 88H (usually responds within 250ms).
3. The PC then issues the following commands:

● Security Check
● Master/Slave Commands (repeated until all desired data is sent)

4. If commands stop for more than 5 seconds, the panel returns to normal operation and outputs a packet
that means the panel is no longer busy (i.e., 7FH in command byte location).

Note: If using a GEM-RS232, PCI2000 or PCI-Mini connected to the serial RJ12 connector, the signals
will get inverted.

Are you using this method as well as the old one for initiating communications with the panel? Otherwise, can I suggest that you attempt to reverse engineer how QL talks to the panel? I downloaded a Serial monitoring tool (trial) and it looks like QL changes the baud rate all over the place. Not sure why it does this. Here is my log:




8/19/2019 7:51:47 AM ~ Napco Gemini ~ INFO ~ ---------------------------------------------------------------------
8/19/2019 7:51:47 AM ~ Napco Gemini ~ INFO ~ Starting Up... Napco Gemini plug-in version = 3.0.2.1
8/19/2019 7:51:47 AM ~ Napco Gemini ~ INFO ~ ---------------------------------------------------------------------
8/19/2019 7:51:47 AM ~ Napco Gemini ~ INFO ~ hs.Version = 3.0.0.548
8/19/2019 7:51:47 AM ~ Napco Gemini ~ INFO ~ hs.InterfaceVersion = 4
8/19/2019 7:51:47 AM ~ Napco Gemini ~ INFO ~ hs.GetOSType/Version = Windows 6.2.9200.0
8/19/2019 7:51:47 AM ~ Napco Gemini ~ INFO ~ hs.PluginLicenseMode = Registered. Thank you!
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ INI values from hspi_napco_gemini.ini
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ INI Version = 3.0.2.1
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ COMPort=COM4
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ MaxZones=32
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ CmdTimeout=5
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ MaxRetry=4
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ UseIcons=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ Log Incoming Status=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ Log Outgoing Commands=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ Log Debug Info=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ WebArmButton=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ WebDisarmButton=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ WebBypassButton=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ WebRelayButtons=True
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ UseSerialPortTimer=False
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ KeypadRefresh=20
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ LogZonesStr=*
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ LogZones =
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ BypassZonesStr=
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ BypassZones =
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ logFileDebug=C:\Program Files (x86)\HomeSeer HS3/Logs/NapcoDebug.log
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ logLvl=79 [Always] [Err] [Info] [Incoming] [Outgoing] [Debug]
8/19/2019 7:51:47 AM ~ Napco Gemini ~ DEBUG ~ ---------------------------------------------------------------------
8/19/2019 7:51:48 AM ~ Napco Gemini ~ DEBUG ~ PanelConnect - Open new connection to the panel
8/19/2019 7:51:48 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:51:48 AM ~ Napco Gemini ~ OUTGOING ~ SENDING: 1A,6,0,0,0,0,2A,2A,2A,2A,2A,2A
8/19/2019 7:51:48 AM ~ Napco Gemini ~ DEBUG ~ ProcessPanelUpdate - STATUS_UPDATE - IGNORED (waiting on InitIO) [7F, 00, 00]
8/19/2019 7:51:53 AM ~ Napco Gemini ~ DEBUG ~ Timed out waiting for reply.
8/19/2019 7:51:54 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #2
8/19/2019 7:51:54 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:51:59 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:52:00 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #3
8/19/2019 7:52:00 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:05 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:52:06 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #4
8/19/2019 7:52:06 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:11 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:52:11 AM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for version check
8/19/2019 7:52:17 AM ~ Napco Gemini ~ INFO ~ Panel Startup Initialization attempt #2
8/19/2019 7:52:17 AM ~ Napco Gemini ~ DEBUG ~ PanelConnect - Open new connection to the panel
8/19/2019 7:52:17 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:17 AM ~ Napco Gemini ~ OUTGOING ~ SENDING: 1A,6,0,0,0,0,2A,2A,2A,2A,2A,2A
8/19/2019 7:52:17 AM ~ Napco Gemini ~ DEBUG ~ ProcessPanelUpdate - STATUS_UPDATE - IGNORED (waiting on InitIO) [7F, 00, 00]
8/19/2019 7:52:22 AM ~ Napco Gemini ~ DEBUG ~ Timed out waiting for reply.
8/19/2019 7:52:23 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #2
8/19/2019 7:52:23 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:28 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:52:29 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #3
8/19/2019 7:52:29 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:34 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:52:35 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #4
8/19/2019 7:52:35 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:40 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:52:40 AM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for version check
8/19/2019 7:52:46 AM ~ Napco Gemini ~ INFO ~ Panel Startup Initialization attempt #3
8/19/2019 7:52:46 AM ~ Napco Gemini ~ DEBUG ~ PanelConnect - Open new connection to the panel
8/19/2019 7:52:46 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:46 AM ~ Napco Gemini ~ OUTGOING ~ SENDING: 1A,6,0,0,0,0,2A,2A,2A,2A,2A,2A
8/19/2019 7:52:47 AM ~ Napco Gemini ~ DEBUG ~ ProcessPanelUpdate - STATUS_UPDATE - IGNORED (waiting on InitIO) [7F, 00, 00]
8/19/2019 7:52:51 AM ~ Napco Gemini ~ DEBUG ~ Timed out waiting for reply.
8/19/2019 7:52:52 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #2
8/19/2019 7:52:52 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:52:57 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:52:58 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #3
8/19/2019 7:52:58 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:53:03 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:53:04 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #4
8/19/2019 7:53:04 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:53:09 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:53:10 AM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for version check
8/19/2019 7:53:16 AM ~ Napco Gemini ~ INFO ~ Panel Startup Initialization attempt #4
8/19/2019 7:53:16 AM ~ Napco Gemini ~ DEBUG ~ PanelConnect - Open new connection to the panel
8/19/2019 7:53:16 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:53:16 AM ~ Napco Gemini ~ OUTGOING ~ SENDING: 1A,6,0,0,0,0,2A,2A,2A,2A,2A,2A
8/19/2019 7:53:16 AM ~ Napco Gemini ~ DEBUG ~ ProcessPanelUpdate - STATUS_UPDATE - IGNORED (waiting on InitIO) [7F, 00, 00]
8/19/2019 7:53:17 AM ~ Napco Gemini ~ DEBUG ~ ProcessPanelUpdate - STATUS_KEYPAD_AREA1 - IGNORED (waiting on InitIO) [%SYSTEM READY 08/19/19 07:54AM]
8/19/2019 7:53:21 AM ~ Napco Gemini ~ DEBUG ~ Timed out waiting for reply.
8/19/2019 7:53:22 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #2
8/19/2019 7:53:22 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:53:27 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:53:28 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #3
8/19/2019 7:53:28 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:53:33 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:53:34 AM ~ Napco Gemini ~ INFO ~ Start Session to Napco Panel attempt #4
8/19/2019 7:53:34 AM ~ Napco Gemini ~ DEBUG ~ StartSession - HAIL panel
8/19/2019 7:53:39 AM ~ Napco Gemini ~ INFO ~ TIMEOUT waiting for panel to be ready for our command
8/19/2019 7:53:39 AM ~ Napco Gemini ~ DEBUG ~ Unable to establish session to panel for version check
8/19/2019 7:53:44 AM ~ Napco Gemini Error ~ Panel Startup Initialization : Unable to establish a good connection to the Napco Panel!


EDIT:
Also, could you perhaps allow the plug-in to receive status updates and function even if it can't send commands to the panel? That will be better than nothing! Thanks!

EDIT2:
I noticed the 2A,2A,2A,2A,2A,2A where the master code is supposed to be - do you do this so it doesn't show in the log or is this what is really being sent? I do have the correct code set in the GUI.

[nfrobertson]

The Napco plugin here implements the GEM-AUTOMATION protocol and uses the RTS/CTS communications mechanism. I did experiment with the alternate communications protocol without any serious progress a couple years back. Unfortunately as time goes on Napco has evolved their newer panels and access to developer documentation to continue upgrades has not been possible. This plugin was created to maintain the same functionality that existed with HS2 as the move to HS3 was done and HST decided not to upgrade their HS2 version plugin.

The plugin has 2 modes of communication, encrypted and non-encrypted. It receives the bus feed even if it wasn't able to log you in. Unfortunately, without successfully logging in it can't map the zones/areas to make meaningful use of what's coming over the un-encrypted (non-logged-in) bus feed.

Yes the masked 2A2A etc. echo is so your master code doesn't show in every log message.

Please see my other post here today. If a Napco dealer can get me access to new (and useful) developer documentation and to new hardware to test with I might be able to look into these issues with newer panels. Until then I'm afraid I may not be able to help if the newer panels don't implement the same GEM-AUTOMATION protocol standards as the previous generation did.

Nathan

[brianjhomeseer]

Thanks for the response Nathan! You say that "Unfortunately, without successfully logging in it can't map the zones/areas to make meaningful use of what's coming over the un-encrypted (non-logged-in) bus feed." But, what if you had a "learn" mode that could be turned on, then the user would open/close each door, etc. so you would *see* the zone name/number and you could update your database that way? You would still need to type in things like Fire zones, but I think you could get 90% of the functionality this way, They only things you wouldn't be able to do is arm/disarm the system and control relay outputs, right? I think I can get around that by programming a keyswitch input on the panel and using a relay (or 2 to prevent false arming/disaming) so I would be back to 100% working!

Brian

[nfrobertson]

That sounds like a possible concept (needs more review/thought) however it would be a significant architectural change to the plugin. Right now I'm not in a position to take on that endeavor (day job taking all my free time). I'll put that on the todo pile and see if I can incubate it a bit.

Nathan

[cjin]

That sounds like a possible concept (needs more review/thought) however it would be a significant architectural change to the plugin. Right now I'm not in a position to take on that endeavor (day job taking all my free time). I'll put that on the todo pile and see if I can incubate it a bit.

Nathan

Instead of the “learn mode”, is it possible (maybe this doesn’t require as much architectural change to the plug in) for user to manually set up all the zones?

[cjin]

That sounds like a possible concept (needs more review/thought) however it would be a significant architectural change to the plugin. Right now I'm not in a position to take on that endeavor (day job taking all my free time). I'll put that on the todo pile and see if I can incubate it a bit.

Nathan

Another thought, how about using setup files from Quickloader to populate zones in HS3, then the plug in can update status using messages sent front the panel? Not ideal but a lot better than nothing....

[brianjhomeseer]

Nathan,
I finally got just a board for a P9600 so I can mess with it - if it works (got it used from ebay) and I send it to you, do you think you could try to get this going on the newer firmware? My house system uses the same firmware, so I could also beta test for you.

Thanks!
Brian

[jackallweiss]

Has the Napco plugin been tested by anyone with HS4? I am running HS3 and a 9600 panel that has worked fine for years!

[brianjhomeseer]

Ok, so I couldn't get the P9600 board working with Quickloader, so I returned it. I got a P3200 board and had the same issue - but I also got the TCP/IP interface (I bought 4 of them!) and that works. I don't know why I can't talk to board over the serial link anymore - if I go into a terminal program, I can see the un-encrypted keypad output, but QL won't talk to it! And, when I setup the NL-MOD and plug it in to the same port, I can then upload/download the panel all day - weird. Anyone have any Napco programming experience? Is there something that has to be enabled in the panel in order to upload/download it? I can talk to my P9600 installed in my house just fine over serial, so I know the hardware works.

[nfrobertson]

Hi Brian,

I took another look at the Napco technical documents library and still the only development specification they've published is the old March 2013 doc that this plugin was based on. Looking at their public efforts around integrating full security and IoT platforms, I'm guessing they've long ago decided that publishing 3rd party development specs for their newer hardware isn't in their business model. I'm wondering if this is demonstrated by your experience where NL-MOD works talking to the panel but the old traditional serial methods do not.

I'm not sure how much demand there would be for a very limited version of this plugin where you have to predefine everything and then simply consume status messages from the unencrypted bus? I looked at the current code and right now I extract area number and armed/not-armed and display the text lines 1 & 2 for the web status interface and debug log. We would have to do text matching on what comes across that keyboard status bus and make some pretty gross level assumptions.

Right now I'm trying to decide if I even port this from HS3 to HS4 or leave as Legacy-plugin with HS3. It appears to work ok on HS4 as a legacy-plugin.

Sorry, I know this isn't the answer you wanted to hear but I did want to let you know the latest.

Nathan

[cjin]

Hi Nathan, I'd be interested in the plug in, even if I need to predefine everything. In addition to getting zone status, can it arm/disarm the system?

It would help if it can read those information from quickloader files, but that's not a deal breaker.