Results 1 to 11 of 11

Thread: Serial STU Interface

  1. #1
    Senior Member IPAlarms's Avatar
    Join Date
    Jan 2008
    Posts
    671
    Thanks
    4
    Thanked 12 Times in 12 Posts
    Rep Power
    222
    Reputation
    94

    Default Serial STU Interface

    I did some research a long time back regarding serial output from alarm panels but found that there was no standard to work to and that all manufactures did things differently.

    Some kind person on here sent me the spec for NESS panels, so I will dig it out and study it.

    So, is the serial protocol for STU's different, or in addition to what most manufacturers output from their serial ports ?

    At the CMS end - is there a special receiver module for collecting the data ?

    Any information would be much appreciated
    Developer of VoIP2Go at ozvoip.net - Alarm compatible VoIP Network



Look Here ->
  • #2
    Senior Member
    intelliGEORGE's Avatar
    Join Date
    Jan 2008
    Location
    Sydney, AUSTRALIA
    Age
    43
    Posts
    4,106
    Thanks
    884
    Thanked 1,484 Times in 691 Posts
    Rep Power
    479
    Reputation
    7236

    Default

    We use two forms of STU's. Serial RS232 and TTL interface.

    These two formats cover the majority of panels we use.

    Serial RS232
    MCM, Concept, C&K, DSC, Genesis etc.

    TTL
    Tecom, NX, Bosch, Vision etc.

    I can take a STU and move it between panels i.e. RS232 STU from an MCM and whack it on a Concept panel, so the serial data should be standard I presume.

    P.s I have named more than 10% of the panels in the market

  • #3
    Senior Member
    Join Date
    Jan 2008
    Location
    Sydney :P~~~
    Posts
    1,051
    Thanks
    8
    Thanked 74 Times in 54 Posts
    Rep Power
    246
    Reputation
    657

    Default

    at the cms there is a host machine, which is used to "up" the stu (bring it online) and "poll" it to check the status of itself + the pin alarms on the STU itself.

    Aka, is the STU in Pin alarm (not talking to the main panel) e.t.c
    I believe that host machine is connected to the CMS monitoring software and it outputs the alarms in STU format

    There are also the old channel stu's v nasty..

  • #4
    Member
    Join Date
    Jan 2008
    Location
    Melbourne
    Posts
    370
    Thanks
    1
    Thanked 46 Times in 42 Posts
    Rep Power
    221
    Reputation
    596

    Default

    Quote Originally Posted by IPAlarms View Post
    So, is the serial protocol for STU's different, or in addition to what most manufacturers output from their serial ports ?

    At the CMS end - is there a special receiver module for collecting the data ?

    Any information would be much appreciated
    STU's all use the same RS232 protocol. Unless it is the older type channel STU which sent very limited data depending on state of its 8 channels. Both types get polled by a server in the closest Telstra exchange, once they receive a poll (about every 40 seconds) they can responed with any alarm state. These servers then deliver the alarm state to the correct CMS which has two receivers, the receivers then output the event to the CMS automation software.

    The alarm panel must be programed for Securitel reporting it then outputs RS232 in STU protocol to the STU from its serial port. This then generally disables the panel dialler depending on the panel type.

    I hope this helps your research Steve have a Merry Christmas.
    Last edited by kiwitech; 23-12-08 at 11:50 PM. Reason: add detail

  • #5
    Senior Member IPAlarms's Avatar
    Join Date
    Jan 2008
    Posts
    671
    Thanks
    4
    Thanked 12 Times in 12 Posts
    Rep Power
    222
    Reputation
    94

    Default

    Thanks for your help guys. The reason I ask is that we have a new combined IP/GPRS device on the way and I want to look at interfacing panels via RS232 and forwarding data to the CMS.

    If it's politically incorrect for anyone to post related info on here then an email would be much appreciated.

    Cheers ;-)
    Developer of VoIP2Go at ozvoip.net - Alarm compatible VoIP Network

  • #6
    Senior Member
    Arbiter's Avatar
    Join Date
    Oct 2008
    Posts
    1,408
    Thanks
    155
    Thanked 675 Times in 369 Posts
    Rep Power
    296
    Reputation
    3039

    Default

    Subscriber Terminal Unit Programmable Interface Device
    Kinda says it all.

  • #7
    Senior Member
    Join Date
    Jan 2008
    Location
    Sydney :P~~~
    Posts
    1,051
    Thanks
    8
    Thanked 74 Times in 54 Posts
    Rep Power
    246
    Reputation
    657

    Default

    We are using a device that interfaces with STU only panels, easy to install, 3 wires between panel and Monitoring device, works well (we also use them on Tecom's as the 232 connection between the panel and the device is totally supervised, just like the stu would go into allarm if D/C from the APC)

    (excuse the blandness of my reply, for obvious reasons i cant say too much)

  • #8
    Senior Member IPAlarms's Avatar
    Join Date
    Jan 2008
    Posts
    671
    Thanks
    4
    Thanked 12 Times in 12 Posts
    Rep Power
    222
    Reputation
    94

    Default

    Quote Originally Posted by Arbiter View Post
    Subscriber Terminal Unit Programmable Interface Device
    Kinda says it all.
    Incestuous Bunch Of Paranoid Pricks says it much better.
    Developer of VoIP2Go at ozvoip.net - Alarm compatible VoIP Network

  • #9
    Senior Member IPAlarms's Avatar
    Join Date
    Jan 2008
    Posts
    671
    Thanks
    4
    Thanked 12 Times in 12 Posts
    Rep Power
    222
    Reputation
    94

    Default

    Quote Originally Posted by keef82 View Post
    (excuse the blandness of my reply, for obvious reasons i cant say too much)
    Hey - it's no biggie. I don't expect anyone to let me have the protocol
    Developer of VoIP2Go at ozvoip.net - Alarm compatible VoIP Network

  • #10
    Senior Member bss904's Avatar
    Join Date
    Jan 2008
    Location
    NOT in Thailand
    Posts
    1,110
    Thanks
    523
    Thanked 251 Times in 153 Posts
    Rep Power
    295
    Reputation
    2964

    Default

    Quote Originally Posted by IPAlarms View Post
    Hey - it's no biggie. I don't expect anyone to let me have the protocol
    Come on Steve. Wakey wakey. I have told you who to ring to get the top secret protocol. Only a phone call away and a lot of groveling required.....maybe.

    By the way, merry christmas Steve from one of your adoring fans.



    ps
    Think big. 2009 might be the year you double your turnover by selling two of your non conforming product.

  • #11
    Senior Member IPAlarms's Avatar
    Join Date
    Jan 2008
    Posts
    671
    Thanks
    4
    Thanked 12 Times in 12 Posts
    Rep Power
    222
    Reputation
    94

    Default

    Quote Originally Posted by bss904 View Post
    Come on Steve. Wakey wakey. I have told you who to ring to get the top secret protocol. Only a phone call away and a lot of groveling required.....maybe.
    Oops - you'll have to remind me who I need to call.

    Quote Originally Posted by bss904 View Post
    By the way, merry christmas Steve from one of your adoring fans.
    Hey all the best to you and your family too.

    Quote Originally Posted by bss904 View Post
    Think big. 2009 might be the year you double your turnover by selling two of your non conforming product.
    Two? You reckon I could sell that many?

    Wow - now you've got me excited and I can't wait for the New Year
    Developer of VoIP2Go at ozvoip.net - Alarm compatible VoIP Network

  • 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
    •