Page 6 of 7 FirstFirst 1234567 LastLast
Results 101 to 120 of 126

Thread: Ness D8X / D16X Serial Comms

  1. #101
    Junior Member
    Join Date
    Dec 2017
    Posts
    14
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0
    Reputation
    50

    Default

    Definitely set as 9600 8N1 which is what the book says? All the codes returned are repeatable. That is these numbers arent random just not what I was expecting?



  • #102
    Junior Member
    Join Date
    Dec 2010
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    OzTynker, have you abandoned the arduino communication?
    My plan was to connect an ESP8266 and hook it into HASS via MQTT.
    However I think this serial decoding is over my head.
    If you can get a basic arduino sketch to read the status then I can wire up the rest.

  • #103
    Junior Member
    Join Date
    Dec 2017
    Posts
    14
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0
    Reputation
    50

    Default

    No but I haven't had time to play with it anymore. I will update this if and when I can finally get around to it.

    And yes I was going to use an ESP8266 which connects to a MySensors Gateway.
    Last edited by OzTynker; 11-05-18 at 10:18 PM.

  • #104
    Junior Member
    Join Date
    Jan 2012
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default Count me in ....

    Quote Originally Posted by OzTynker View Post
    No but I haven't had time to play with it anymore. I will update this if and when I can finally get around to it.

    And yes I was going to use an ESP8266 which connects to a MySensors Gateway.
    I'm looking to head down this path too ..... Originally I was looking at using something like konnected i.e hooking konnected into the NESS PIRs etc and then integrating it into my Home Assistant, but if I can just tap into the NESS serial via a Pi/Uno/ESP8266 , I'd be happier to do that and leave the NESS in place.

    Keen to hear if you are progressing .....

    Cheers,
    Chris
    Last edited by mtv; 26-08-18 at 05:00 PM. Reason: link removed

  • #105
    Junior Member
    Join Date
    Jan 2008
    Posts
    22
    Thanks
    2
    Thanked 1 Time in 1 Post
    Rep Power
    197
    Reputation
    15

    Default

    Quote Originally Posted by FrontBottom View Post
    I'm looking to head down this path too ..... Originally I was looking at using something like konnected i.e hooking konnected into the NESS PIRs etc and then integrating it into my Home Assistant, but if I can just tap into the NESS serial via a Pi/Uno/ESP8266 , I'd be happier to do that and leave the NESS in place.

    Keen to hear if you are progressing .....

    Cheers,
    Chris
    +1

    Seems to be a real opportunity for someone to really make these panels shine, and possibly integrate into other things. ITTT integration would be fantastic, for example.

    Any specs on the protocol/standards of the Comms?

  • #106
    Junior Member
    Join Date
    Jan 2012
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Quote Originally Posted by sulrich View Post
    +1

    Seems to be a real opportunity for someone to really make these panels shine, and possibly integrate into other things. ITTT integration would be fantastic, for example.

    Any specs on the protocol/standards of the Comms?

    This post has link to the protocol:

    Cheers

  • #107
    Junior Member
    Join Date
    Jan 2008
    Posts
    22
    Thanks
    2
    Thanked 1 Time in 1 Post
    Rep Power
    197
    Reputation
    15

    Default

    Thanks!

  • #108
    Junior Member
    Join Date
    Sep 2018
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Hi all - hopefully someone is still reading this very old thread

    I have a DX8D. I tried to send a command but I think I crashed the device because it stopped responding after that and I had to reboot everything

    Just wondering whether i need to convert the command to ASCII before I send the panel anything?

    Advice appreciated (I'm scared to send anything else in case I crash the system again)

  • #109
    Junior Member
    Join Date
    Dec 2017
    Posts
    14
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0
    Reputation
    50

    Default

    Sorry guys no progress yet. Other parts of life has this on the back burner. I didnt have any issues with crashing the panel and I was trying all sorts of things to get a response so cant help you there.

  • #110
    Junior Member
    Join Date
    Oct 2018
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Hi, I purchased a Ness DX16d early this year and could not fin any info on the net other than what is contained in this thread. The best info was by RobLS
    What i wanted was a way to get reports from the alarm so I used the info contained above and logged all the serial output from the panel. An example:
    To get serial data from ip adaptor use from Linux (substitute your IP):
    [/usr/bin] # curl 192.168.100.40:2401


    8700836132970018020323192251
    870003613197001802032321509c
    870083612f0101180203232209f9
    8700036124010118020323223756
    87008361220001180203232238d8
    8700036123000118020323233658

    I run my perl program on a Qnap server, it has been running continuous since Feb this year and sends me a text and email when the system is armed or disarmed that includes the persons name: Eg: 08/10/18 09:55:49 Alarm System Disarmed - User Jono Area:01

    We also have a txt message server running to send sms to customers when jobs are ready to pick up etc so I also inject the alarm messages into it.

    After arming/disarming the system I usually get a text withing 10 seconds. I know when any workers enter or leave the workshop. It also sends email/text on any events, Alarm, Power fail or restore etc.

    The perl script is over 800 lines,it may be too long to post here.
    If I can help out just ask.
    I originally thought of using Arduino but found using the ip adaptor and letting the perl script monitor all the events coming out and acting on them a lot easier.

    Regards
    Dave

  • #111
    Junior Member
    Join Date
    Jan 2012
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Quote Originally Posted by OzTynker View Post
    Sorry guys no progress yet. Other parts of life has this on the back burner. I didnt have any issues with crashing the panel and I was trying all sorts of things to get a response so cant help you there.
    Hey OzTynker

    Would you be willing to share any of your Arduino code to-date?

    Cheers

  • #112
    Junior Member
    Join Date
    Jan 2012
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    And on another note - I've just noticed this GitHub repo ... don't know if it is one of "us" or not ....



    Cheers

  • #113
    Junior Member
    Join Date
    Jan 2008
    Posts
    22
    Thanks
    2
    Thanked 1 Time in 1 Post
    Rep Power
    197
    Reputation
    15

    Thumbs up

    Quote Originally Posted by FrontBottom View Post
    And on another note - I've just noticed this GitHub repo ... don't know if it is one of "us" or not ....



    Cheers
    This has been updated a bit by the author as well in the last few days

  • #114
    Junior Member
    Join Date
    Jan 2019
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Hi Guys,

    I really hope this thread still has some like left in it! Its been so helpful for me. I have a D16x with firmware 7.8. My panel is the touch screen model.

    I am stuck on AUX Controls, I can't get my panel to respond. I can arm and disarm using the methods indicated in the ASCII protocol but when I send 22* to activate the AUX 2 I get no response (no beeps or anything). I don't have any other AUX inputs connected but if I sent the AUX 1 code 11* I get a single beep. I am just wondering if there is something I am missing;
    Here is my Aux 2 syntax: 830036022*E

    I have been successfully using the Ness iComms app for a while, but I want Siri integration/Shortcut which the app does not offer. So my plan is to integrate these codes into the iOS shortcut app.
    Basically I want to be able to ask Siri to;

    1. Turn on Alarm - Sends Arm cod e.g. 8300560A123E7E
    2. Turn off Alarm - Sends Disarm Code e.g.8300460123EC0
    3 Open Garage (AUX 2) - Send Code e.g. 830036022*E
    4. I am Home (Disarm and Aux 2) - Send code e.g. 8300460123EC0 ? 830036022*E

    I am so close, I just need the AUX 2 code to work.
    Would really appreciate anyones assist on this.

  • #115
    Junior Member
    Join Date
    Jan 2012
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Quote Originally Posted by sulrich View Post
    This has been updated a bit by the author as well in the last few days
    For those who are also Home Asssitant users - looks like Nick's goal all along was to integrate into HA; this was my goal too. I've wasted so much time trying to do it myself using ESP based devices and my own code, so think I will just go down this path now



    Cheers,
    Chris

  • #116
    Junior Member
    Join Date
    Dec 2017
    Posts
    14
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0
    Reputation
    50

    Default

    Yes looks good but how has he done the hardware interface?

    Edit: Ah.... I see.... an off the shelf ethernet module

    This is perfect!
    Last edited by OzTynker; 03-02-19 at 12:15 PM.

  • #117
    Junior Member
    Join Date
    Dec 2017
    Posts
    14
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0
    Reputation
    50

    Default

    Also these non-NESS converters apparently work well
    Last edited by OzTynker; 06-02-19 at 10:40 AM. Reason: typo

  • The Following User Says Thank You to OzTynker For This Useful Post:

    cozzmo (03-01-21)

  • #118
    Junior Member
    Join Date
    Mar 2019
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Hi. I seem to be having the same problem Venturis was having in #24 of this thread where he couldn't get the panel to talk unless he was in installer mode. I haven't been able to find a solution to that, and was hoping Venturis or someone else here might know what the problem was.

    I have the same D8x v5.8 PCB as Venturis has.

    Thanks.

  • #119
    Junior Member
    Join Date
    Mar 2010
    Posts
    30
    Thanks
    4
    Thanked 1 Time in 1 Post
    Rep Power
    173
    Reputation
    30

    Default

    Quote Originally Posted by DoubleYou View Post
    Hi. I seem to be having the same problem Venturis was having in #24 of this thread where he couldn't get the panel to talk unless he was in installer mode. I haven't been able to find a solution to that, and was hoping Venturis or someone else here might know what the problem was.

    I have the same D8x v5.8 PCB as Venturis has.

    Thanks.
    If you are talking about Nesscomms not working unless its in installer mode, then yes that is the way it operates. Needs to be in installer mode before it can be used.

    Matt

  • #120
    Junior Member
    Join Date
    Mar 2019
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Quote Originally Posted by auMatt View Post
    If you are talking about Nesscomms not working unless its in installer mode, then yes that is the way it operates. Needs to be in installer mode before it can be used.

    Matt
    Ah, right. That solves part of the mystery, thanks. I also have a problem when the system is in normal mode. I can receive and decode arm/disarm and exit delay messages when the alarm is armed manually. I haven't found any way to get it to respond to status requests or arm/disarm commands, though. I've set the P90E flags for remote operation, just to be sure.

    Example S14 status packet request: 8300360S14E4\r\n
    Example response packet: [tumbleweed]

    I'm confident the port settings and cables are good, given Nesscomms works fine. That leaves the format of the request packet, the checksum, and the alarm itself.

  • Page 6 of 7 FirstFirst 1234567 LastLast

    Similar Threads

    1. "Comms fail route1" on Bosch Solution 16+
      By autertip in forum Security Alarms
      Replies: 8
      Last Post: 02-06-18, 10:40 PM
    2. Replies: 1
      Last Post: 17-09-09, 11:25 PM
    3. Comms,networking machine linking ????
      By redmick in forum Networking - Wireless and Cabled
      Replies: 1
      Last Post: 23-04-09, 07:55 PM
    4. Comms Receiver WTB
      By Variable in forum Buy Sell and Trade
      Replies: 0
      Last Post: 25-02-09, 09:55 PM
    5. Ness D16x Questions
      By 7polly7777 in forum Security Alarms
      Replies: 1
      Last Post: 26-03-08, 02:11 AM

    Tags for this Thread

    Bookmarks

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •