Announcement

Collapse
No announcement yet.

Caddx plugin

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by simonmason View Post
    I am (finally) in the process of switching to HS3. I cannot connect to the panel.

    The only thing I see in the log when I check debug is:

    Caddx Error Plugin: CaddxError in Com Open moduleThe port 'COM' does not exist.

    My ini file shows:

    [Settings]
    Version=3.1.0.0
    [Panel]
    PanelPinCode=HSENC2Ko5v0NU+4To1YtAeNT+qKw==
    ValidPinCode=0

    I have confirmed that I can login using DL900 with user01 and the pin I specify in the config.

    It would seem to me that there should be more settings in the ini file - com, baud, etc? Thanks.
    Strange. Did you save your settings with the save button ?

    There should be at least the following in the ini file:
    [Settings]
    Version=3.1.0.0
    cb_debug_checked=0
    ComPort=13
    BaudRate=9600
    cb_connectatstartup_checked=0
    [Panel]
    PanelPinCode=
    PanelModel=Caddx NX-8
    PanelMaxZones=48
    ValidPinCode=1
    [Zones]
    Regards,

    Rien du Pre
    The Netherlands
    Using:
    Homeseer PRO latest HS4 BETA on a Raspberry
    Plugin's:
    RFXCOM, mcsMQTT, Z-Wave

    Comment


      I am all connected. I ran a get zones and after leaving it for sometime I don't see my zone names showing up in the config.

      Here is my debug log:

      Sep-26 11:28:01 AM Caddx Plugin: Caddx ComRxLine()- Bytes to read = 0
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished ComRxLinemodule
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished ProcessCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished IntrepretCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started ZoneSnapshot module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Processing message: 05
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Intrepret message = 0A05000440040000000800DFAF
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started IntrepretCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished AwknowledgeTheMessage module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished ComTxLine Open module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ComTxLine - myRquest = 011D1E1F
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Entering ComTXLine module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started AwknowledgeTheMessage module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started FletcherChecksum module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started ValidFletchSum module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started ProcessCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ComRxLine()- Data Received is 0A85000440040000000800DFAF
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ComRxLine()- Bytes to read = 0
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished ComRxLinemodule
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished ProcessCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished IntrepretCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ZoneStatus - myZoneTypeFlags =5813F0
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ZoneStatus - myZone =10
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ZoneStatus - Message received =080409015813F00002F48C
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started ZoneStatus module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Processing message: 04
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Intrepret message = 080409015813F00002F48C
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started IntrepretCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished AwknowledgeTheMessage module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Finished ComTxLine Open module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ComTxLine - myRquest = 011D1E1F
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Entering ComTXLine module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started AwknowledgeTheMessage module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started FletcherChecksum module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started ValidFletchSum module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx Started ProcessCaddxMessages module
      Sep-26 11:28:01 AM Caddx Plugin: Caddx ComRxLine()- Data Received is 088409015813F00002F48C
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ComRxLine()- Bytes to read = 0
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished ComRxLinemodule
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished ProcessCaddxMessages module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished IntrepretCaddxMessages module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started SetDeviceStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started ZoneSnapshot module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Processing message: 05
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Intrepret message = 0A05000440040010000800EFEF
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started IntrepretCaddxMessages module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished AwknowledgeTheMessage module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished ComTxLine Open module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ComTxLine - myRquest = 011D1E1F
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Entering ComTXLine module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started AwknowledgeTheMessage module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started FletcherChecksum module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started ValidFletchSum module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started ProcessCaddxMessages module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ComRxLine()- Data Received is 0A85000440040010000800EFEF
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ComRxLine()- Bytes to read = 16
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished ComRxLinemodule
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished ProcessCaddxMessages module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished IntrepretCaddxMessages module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ZoneStatus - myZoneTypeFlags =5813F0
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ZoneStatus - myZone =10
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ZoneStatus - Message received =080409015813F00102F58E
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started ZoneStatus module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Processing message: 04
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Intrepret message = 080409015813F00102F58E
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started IntrepretCaddxMessages module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished AwknowledgeTheMessage module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Finished ComTxLine Open module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx ComTxLine - myRquest = 011D1E1F
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Entering ComTXLine module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started AwknowledgeTheMessage module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started FletcherChecksum module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started ValidFletchSum module
      Sep-26 11:27:58 AM Caddx Plugin: Caddx Started ProcessCaddxMessages module
      Last edited by simonmason; September 26, 2015, 10:16 AM.

      Comment


        CADDX Plug-IN Not Recognizing NX-8E Panel

        I am in the process of converting from HS2 to HS3. One of the last transfers is the CADDX plugin. I am using the jvCaddx plug-in on HS2. I am looking at the setup on HS3 using your new CADDX plug-in v3.1.

        I have two security panels. An older NX-8V2 and a newer NX-8E. The problem seems to be when trying to talk with an NX-8E panel.

        On the NX-8V2 panel I am using the Automation add-on card and have a serial cable connected between that card and the COM1 port on my system. That works great. I am able to "connect" to the panel and get NetworkX NX-8v2 as the panel type. I use my master code as the pin and I get a pin code verified. I am able to scan zones and create zone devices. I am able to scan partitions and create devices. Motion sensors are reporting correctly when I move around the area.

        I am not having the same success with the NX-8E panel. I am using the on board automation interface that uses the PC-0003 ribbon cable terminated in the serial cable connector. A serial cable is connected to COM1 on my computer ( I have disconnected the 8V2 panel). I have (I think) setup the automation settings in the 8E panel using my DL900 interface. These are the settings for locations 207-211. I am not using Ascii. Once connected, I can connect to the panel but it does not echo the panel type and in the INI file the panel type is empty. I can enter the 8E master code and I get a pin verified message. If I do a zone scan it lists the available 48 zones and it lists the types but not the names. If I scan partitions, it shows part #1 as valid. I am able to create devices for zones and the one partion. I can view the devices in the Device Management list. However I have no control and if I trip motion sensors, they do not fault. I expect this is because the panel type is not being discovered for the NX-8E panel. Looking for suggestions on where to look fort the problem.

        Location Data to be entered:
        LOCATION #207 - 1 ON (Serial Port Enable for Home Automation)
        LOCATION #208 - 2 ON (Serial Port Baud Rate = 9600)
        LOCATION #209 - SEGMENT #1 : 1 (Set the Home Automation protocol to ASCII): 1 ON
        LOCATION #210 - SEGMENT #1 : 2 5 6 7 8 ON
        LOCATION #210 - SEGMENT #2: 1 3 4 ON
        LOCATION #211 - SEGMENT #1: 2 4 5 6 7 8 ON
        LOCATION #211 - SEGMENT #2: 1 3 4 5 ON
        LOCATION #211 - SEGMENT #3: 1 2 3 5 7 ON
        LOCATION #211 - SEGMENT #4: 3 4 5 6 7 8 ON

        [Settings]
        Version=3.1.0.0
        cb_debug_checked=1
        ComPort=1
        BaudRate=9600
        cb_connectatstartup_checked=0
        [Panel]
        ValidPinCode=1
        PanelModel=
        PanelMaxZones=48
        PanelPinCode=HSENC2fdnma3S1/b7oMCFgUBFV2w==
        Last edited by cbabkirk; January 21, 2016, 10:29 PM.

        Comment


          I think you issue is related to Baud Rate ?



          Location Data to be entered:
          LOCATION #207 - 1 ON (Serial Port Enable for Home Automation)
          LOCATION #208 - 4 ON (Serial Port Baud Rate = 31600) <---
          LOCATION #209 - SEGMENT #1 (Set the Home Automation protocol to BINARY): 1 OFF
          LOCATION #210 - SEGMENT #1 : 2 5 6 7 8 ON
          LOCATION #210 - SEGMENT #2: 1 3 4 ON
          LOCATION #211 - SEGMENT #1: 2 4 5 6 7 8 ON
          LOCATION #211 - SEGMENT #2: 1 3 4 5 ON
          LOCATION #211 - SEGMENT #3: 1 2 3 5 7 ON
          LOCATION #211 - SEGMENT #4: 3 4 5 6 7 8 ON

          [Settings]
          Version=3.1.0.0
          cb_debug_checked=1
          ComPort=1
          BaudRate=9600 <------
          cb_connectatstartup_checked=0
          [Panel]
          ValidPinCode=1
          PanelModel=
          PanelMaxZones=48
          PanelPinCode=HSENC2fdnma3S1/b7oMCFgUBFV2w==
          ***************

          I`m using an NX8 Panel with the Automation Module on 9600 BAUD and it is working fine. I made al configuration using DL900 (Wich can also connect using ASCI just to check your serial port)

          Comment


            Go Back HomeSeer Message Board &gt; 3rd Party Plug-Ins/Scripts &gt; Plug-ins by Author

            Hello,

            Sorry for the confusion. The text where you see the location programming info is clipped from another post. It was put there to show what I have programmed for locations 207-211. I am using 9600 baud on the COM1 port and 9600 is set in location#208.

            I use binary for the DL900 connection but ascii for the panel to HS3 connection. Since the working configuration NX-8V2 uses a different serial interface and cable than the NX-8E (built in) it may be a cable wiring issue.

            I think I will switch the DL900 to ascii just to make sure that com #1 is working properly. I have debug logging turned on but cannot interpret the logs to tell if the "conversation" is showing errors or not.

            I know the plug-in works for the NX-8V2 cable and panel. I actually had a connection and verified pin code earlier today for the NX-8E panel but no control. In the process of tinkering to try to get control, I no longer can get a valid pin code. Looks like one step forward and two steps back.

            Cable is std null modem cable with only 2,3,5 connected and 2 & 3 crossed. Not sure I need the handshaking lines connected or not.

            Is there any aspect of having to restart the plug-in or recycle HS3 after a particular step as a best practice or that is not really needed?

            Thanks for taking a look at my post...

            Comment


              CADDX Plug-IN Not Recognizing NX-8E Panel

              An update...

              I am using the NX 586E with the DL900 to interface between the HS3 computer com port 1 and the NX-8E panel DATA line. The NX586E interface requires a binary connection. I attempted ascii bit got a bunch of com errors. HELP in the DL900 indicates 586E can only use Binary for programming and suggest 9600 baud as the preferred rate.

              All the post I have read here seem to indicate that location 208 should be set to "1" to enable ascii.

              I corrected the earlier post to reflect the actual programmed location values..

              Location Data to be entered:
              LOCATION #207 - 1 ON (Serial Port Enable for Home Automation)
              LOCATION #208 - 2 ON (Serial Port Baud Rate = 9600)
              LOCATION #209 - SEGMENT #1 : 1 (Set the Home Automation protocol to ASCII): 1 ON
              LOCATION #210 - SEGMENT #1 : 2 5 6 7 8 ON
              LOCATION #210 - SEGMENT #2: 1 3 4 ON
              LOCATION #211 - SEGMENT #1: 2 4 5 6 7 8 ON
              LOCATION #211 - SEGMENT #2: 1 3 4 5 ON
              LOCATION #211 - SEGMENT #3: 1 2 3 5 7 ON
              LOCATION #211 - SEGMENT #4: 3 4 5 6 7 8 ON

              The quest continues....

              Comment


                Do you use a USB to serial cable ? There have been some reports that some types do no work with the NX-584 module.
                Regards,

                Rien du Pre
                The Netherlands
                Using:
                Homeseer PRO latest HS4 BETA on a Raspberry
                Plugin's:
                RFXCOM, mcsMQTT, Z-Wave

                Comment


                  CADDX Plug-IN Not Recognizing NX-8E Panel

                  I am not using the NX-584 card. That is required for the NX-8 or NX-8V2. I have the plug-in working on my NX-8V2 system.

                  The issue is when trying to connect to an NX-8E board with the built in serial interface that uses the P0003 10pin header-to-RS232 cable. I expect it is a cabling issue. The plug-in appears to connect to the panel but does not echo a system type such as Caddx NX-8V2. I expect it should get back either Caddx NX-8E or NetworkX NX-8E as the type but is puts nothing in the INI file. I expect I can write to but not read from the panel.

                  I am not sure I have an "authentic" P0003 cable. It orients correctly on the board with the RED wire toward the board edge. The cable appears to be "straight thru" one-for-one connections to the male DB9 connector with pin 10 on the header not used. I cannot find anywhere a description of the wiring pin-to-pin to tell if what I have is a P0003 cable. I am not sure if pins 2 & 3 on the DB9 of the P0003 cable is the true TX & RX lines. I understand that I should be able to find the TX and RX by testing voltage to gnd and find -10v and +10v if they are there but not sure which is which. I have created my own null modem cable with pins 2 & 3 crossed and pin 5 for gnd. I really don't want to buy a new P0003 if the one I have is okay. Not sure how to verify. Perhaps someone here can verify that a true P0003 is pip-for-pin straight thru from header to DB9. That way I can concentrate on the RS232 cable as the problem.

                  As mentioned before, I am able to connect to the panel using my DL900 and a NX 586E interface. I have verified the settings required for NX-8E using the built in serial interface. One concern is depending on which post I look at, about half say that location 209 is set for ascii and the other half say turn off ascii and use binary. I am using ascii.

                  Even though it says connected and cannot verify the pin code, if I run either a zone scan or partition scan, I get log entries that it is scanning the zones or the partitions but not getting the results back.


                  Jan-22 9:04:54 PM Caddx Plugin: Caddx ComTxLine - myRquest = 022301264D
                  Jan-22 9:04:54 PM Caddx Plugin: Caddx Entering ComTXLine module
                  Jan-22 9:04:54 PM Caddx Plugin: Caddx SendRequestToPanel - Requesting = 022301264D
                  Jan-22 9:04:54 PM Caddx Plugin: Caddx Started FletcherChecksum module
                  Jan-22 9:04:54 PM Caddx Plugin: Caddx getZoneInfo - Getting zonename for zone = 2
                  Jan-22 9:04:52 PM Caddx Plugin: Caddx Finished ComTxLine Open module
                  Jan-22 9:04:52 PM Caddx Plugin: Caddx ComTxLine - myRquest = 022300254C
                  Jan-22 9:04:52 PM Caddx Plugin: Caddx Entering ComTXLine module
                  Jan-22 9:04:52 PM Caddx Plugin: Caddx SendRequestToPanel - Requesting = 022300254C
                  Jan-22 9:04:52 PM Caddx Plugin: Caddx Started FletcherChecksum module
                  Jan-22 9:04:52 PM Caddx Plugin: Caddx getZoneInfo - Getting zonename for zone = 1
                  Jan-22 9:04:28 PM Caddx Plugin: Caddx Finished ComTxLine Open module

                  ------------------

                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 2 - Chime? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 2 - Trouble? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 2 - Ready? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - Valid? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - Fire? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - SireneOn? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - Stay? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - Armed? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - Chime? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - Trouble? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx getPartitionInfo for Partition 1 - Ready? = False
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx Finished ComTxLine Open module
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx ComTxLine - myRquest = 01272829
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx Entering ComTXLine module
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx SendRequestToPanel - Requesting = 01272829
                  Jan-22 9:12:31 PM Caddx Plugin: Caddx Started FletcherChecksum module
                  Jan-22 9:12:07 PM Caddx Plugin: Caddx Finished ComTxLine Open module

                  Comment


                    CADDX Plug-IN Not Recognizing NX-8E Panel - RESOLVED!

                    Problem resolved.

                    It was a cabling problem. The ribbon cable was in fact a genuine P0003 cable with straight thru wiring from 10-pin header to DB9 connector. The key to resolving this was to read thru the post between Nitrox and Timoh from Mar 2004 "Almost Configured...missing one last piece" in the Caddx (3P) forum. In this post I learned which pins the RX, TX, and GND signals were on in the 10-pin header coming off the NX-8E board. Once I had that, I was easily able to create a cable that mapped those signals to pins 2, 3 & 5 on the PC DB9 female connector.

                    Ribbon Cable:
                    NX-8E 10-pin header >> DB9 connector

                    3 >> 2 (tx)
                    5 >> 3 (rx)
                    9 >> 5 (gnd)

                    Once connected I was able to connect to the panel and get the Caddx Panel Type : NetworkX NX-8e. I was able to verify the pin using the master code. I did a zone scan and partition scan and created the devices and all seems to be working just fine. Thanks to those that asked questions and made me think further about what could be the problem.

                    Comment


                      Can't get pincode to verify

                      I have updated my HS3 pro to the latest and loaded your plug-in but I can't get the pincode to verify. I am connected to the caddx NX584 and I know the pincode that I am entering is correct. I have read all of the posts regarding this problem and have taken all the steps including setting the bytes in the NX584 having to do with pincode. I saved it before hitting verify - no joy.

                      Where do I go from here?

                      Comment


                        Originally posted by noopara View Post
                        I have updated my HS3 pro to the latest and loaded your plug-in but I can't get the pincode to verify. I am connected to the caddx NX584 and I know the pincode that I am entering is correct. I have read all of the posts regarding this problem and have taken all the steps including setting the bytes in the NX584 having to do with pincode. I saved it before hitting verify - no joy.

                        Where do I go from here?
                        Hi,

                        Almost al of the issues with the pincode were related to the USB/Serial connection. So please check the baudrate on both sides, try a different USB to serial converter, check the Ascii and binary option etc...
                        Regards,

                        Rien du Pre
                        The Netherlands
                        Using:
                        Homeseer PRO latest HS4 BETA on a Raspberry
                        Plugin's:
                        RFXCOM, mcsMQTT, Z-Wave

                        Comment


                          Thanks Rien,

                          Using DL900 on the Automation Module (NX584) screen I see that ASCII is checked and the baud rate is set to 9600 on this screen as well as on your plug-in. I also have every other option on this screen checked except for Log event message and X-10 message received. This is the same set up I have with jvCaddx and Stargate before that. On the Request enables screen I have everything checked except the same two above and Store com event.

                          I connect to the NX584 with a serial connection which has been working fine for more than 10 years and works fine with the jvCaddx plug-in and DL900.

                          Caddx Panel type: is showing Caddx NX-8 in green with a Disconnect Panel button.

                          I just now did another test on some zones and they are showing up now in the when I fault them. I don't know why it wasn't before?? Anyway, I guess everything is working. I haven't tried any events or scripts yet to see if there are any problems. The Pincode error still shows when I try and Verify PinCode on the Config page. I guess it doesn't matter??

                          Here are the first 11 lines of the ini
                          [Settings]
                          Version=3.1.0.0
                          cb_debug_checked=1
                          ComPort=3
                          BaudRate=9600
                          cb_connectatstartup_checked=0
                          [Panel]
                          ValidPinCode=0
                          PanelPinCode=HSENC2zONDXScsXkOMhzkVR31gsA==
                          PanelModel=Caddx NX-8
                          PanelMaxZones=48

                          I am able to disconnect and connect without any problems using your config general settings page. I checked Debug enabled and saved the page and then disconnected and connected and Verify PinCode and then looked for a debug log but was unable to find one.

                          I went through the process of getting partition and zone info from the panel and it worked perfectly. I created HS devices and can see them on the device list. So it would seem, at least so far, that there is coms to and from the panel.

                          I faulted some of the zones and they don't show up as faulted by the plug-in. So it would seem that the inability to verify the PinCode is causing a problem??

                          Perhaps you could provide an option to use the plug-in with or without the pincode?

                          I just ran another test on some of the zones and they are now showing up as faulted. I don't know why they didn't work before. I still am unable to verify the pincode. I still get the same error. I guess it doesn't matter??
                          Last edited by noopara; February 11, 2016, 04:38 PM.

                          Comment


                            The verify pincode is just an extra check to make sure communication is okay.

                            But in your case it seems to work without this check, and it should not have any negative side effects.
                            Regards,

                            Rien du Pre
                            The Netherlands
                            Using:
                            Homeseer PRO latest HS4 BETA on a Raspberry
                            Plugin's:
                            RFXCOM, mcsMQTT, Z-Wave

                            Comment


                              Originally posted by cbabkirk View Post
                              CADDX Plug-IN Not Recognizing NX-8E Panel - RESOLVED!

                              Problem resolved.

                              It was a cabling problem. The ribbon cable was in fact a genuine P0003 cable with straight thru wiring from 10-pin header to DB9 connector. The key to resolving this was to read thru the post between Nitrox and Timoh from Mar 2004 "Almost Configured...missing one last piece" in the Caddx (3P) forum. In this post I learned which pins the RX, TX, and GND signals were on in the 10-pin header coming off the NX-8E board. Once I had that, I was easily able to create a cable that mapped those signals to pins 2, 3 & 5 on the PC DB9 female connector.

                              Ribbon Cable:
                              NX-8E 10-pin header >> DB9 connector

                              3 >> 2 (tx)
                              5 >> 3 (rx)
                              9 >> 5 (gnd)

                              Once connected I was able to connect to the panel and get the Caddx Panel Type : NetworkX NX-8e. I was able to verify the pin using the master code. I did a zone scan and partition scan and created the devices and all seems to be working just fine. Thanks to those that asked questions and made me think further about what could be the problem.
                              Thanks so much for this post. Never would have guessed that the stock cable didn't connect correctly to a PC. Stock wiring is as follows:

                              NX-8E 10-pin header >> DB9 connector

                              3 >> 3
                              5 >> 2
                              9 >> 5

                              So tx/rx are flipped!

                              Comment


                                Sounds like null modem cable vs standard serial. Man, that takes me back 25+ years.

                                Sent from my SM-N975U1 using Tapatalk

                                Comment

                                Working...
                                X