I have a DSC 1864 House Alarm and I want to connect up my Raspberry Pi's GPIO to the Keybus (a serial data communication protocol used by the alarm). I would say my knowledge of electronics is novice to intermediate. Info: The Keybus is a 4 wire serial data bus - +12V, Ground, DATA and CLK. The clock runs at 1khz from what I've heard. Well, I’ve just finished integrating smartthings with my DSC Alarm system via an Arduino Shield. That was quite a project, but it’s well worth it. I changed a little bit the code from obycode to make it more responsive. I significantly increased the baud rate from 9600 over the RS-232 serial port (I haven’t seen this kind of port since the late '80!). I implemented system status checks.
Hello,I'm just new to ISY-99. Just bought one. I like what I read. I have a DSC Alarm system and I have a PC5401 serial module that provide a serial interface to the system. Is there someway I can plug that in to the Port B of IS-99/IR PRO and has ISY monitor messages to get status of alarm panel. That 's all I want to do right now. I want to detect door/window openings, motion sensor and alarm activation/deactivations.
The messages are very simple, ASCII text. Look at this for detailsIf that's possible, then at least some of us with DSC alarm panels can be more automated. I cannot afford to upgrade my panel to ELK now. Cslee,Thanks so very much for your order and feedback. We would love to make ISY more integrated with other products and we have been thinking of opening up that port for communications with other devices but here are my personal observations:Considering that our programs are based on the events that we know of thus the concept of detecting door/window openings, motion sensor and alarm activation/deactivation becomes a programming effort on our part because we do NOT know anything about them.
It could be contended that we could simply pass along messages and then the programs could simply do a pattern matching based on the received messages but, even this, causes a little bit of a problem:Different devices have different means of representing messages some of which are variable length messages with EOT characters. Do we then have to provide the means of specifying message characteristics?DSC, it seems, also has a network (DPWS) device which can be used to communicate with the DSC panels. Don't you think that would be a better route?With kind regards,Michel. Hello,I'm just new to ISY-99. Just bought one. I like what I read.
I have a DSC Alarm system and I have a PC5401 serial module that provide a serial interface to the system. Is there someway I can plug that in to the Port B of IS-99/IR PRO and has ISY monitor messages to get status of alarm panel.
That 's all I want to do right now. I want to detect door/window openings, motion sensor and alarm activation/deactivations. The messages are very simple, ASCII text. Look at this for detailsIf that's possible, then at least some of us with DSC alarm panels can be more automated.
I cannot afford to upgrade my panel to ELK now. Michel,Just passing along ascii strings would be a big step forward. However, there need to be some string manipulation operations to make is useful.E.g.If Port B.RX 609013.THENZone.13.Open is TRUEIf Port.B.RX 610013.THENZone.13.Open is FALSEIf Port.B.RX 6521.THENPartition.1.Armed is TRUEOne can build a whole set of the for each zone.
There must be something to tell us that a byte has been received. So that this routine can loop until the FIFO is empty.I dont know how much the DWPS module for DSC cost, but this PC5401 is only about $50. So it's cost effective.
Michel,Just passing along ascii strings would be a big step forward. However, there need to be some string manipulation operations to make is useful.E.g.If Port B.RX 609013.THENZone.13.Open is TRUEIf Port.B.RX 610013.THENZone.13.Open is FALSEIf Port.B.RX 6521.THENPartition.1.Armed is TRUEOne can build a whole set of the for each zone. There must be something to tell us that a byte has been received. So that this routine can loop until the FIFO is empty.I dont know how much the DWPS module for DSC cost, but this PC5401 is only about $50.
So it's cost effective. I too would like to see this supported. I would Like to use it with the AdemcoVista 128BP panel which also works on ascii strings. Perhaps you could allow a few options such asEOT characterReturn ASCII or HEX representation.Seems it could be done in a basic fashion that would require a little more programming on the users part but would make it a more generic interface.Another approach could be to have the ISY maintain a table of the strings we wish to be notified on. This table would have to allow for wild cards in the string. Generic ASCII would be satisfactory, yes. I've asked for this from the beginning, in order to interface my Ocelot.
The Ocelot also allows user-defined ASCII output strings, so pattern matching would be good.The Ocelot also accepts ASCII input, but only in very rigidly formatted strings, so in that way is more limited than the Stargate. However, free-form or pre-defined strings would work here as well, as long as they can be made to conform to Ocelot's requirements.It seems that generic ASCII (perhaps with wildcards, selectable EOL characters, and HEX representation) would go a long way to handling many devices out there, including those which have been mentioned in this thread.The problem, though, is that the ISY's second serial port is there specifically for emergency recovery, should the user not be able to reach the ISY via IP (including telnet). And I think that Michel may be reluctant to in any way impede that capability, and rightly so. So in order for this to work, we would need to come up with a way for that second serial port to serve a dual purpose, without compromising its primary purpose.One possibility might be to have ISY power-up in the recovery-port mode, and only switch to user-port mode upon a specific ISY program command, which would need to be defined. That command could be issued in a user's program, for those who wish to use it.
For those who don't, the ISY would simply remain in its current recovery-port mode. Such a command could could be placed in a user's program which was set to run at reboot, so that after a reboot the ISY could again communicate with a user-defined device.In order for recovery to take place, the ISY could be configured in firmware to never switch to user-port mode if no PLM was detected.
Then, should the user need to effect emergency recovery, he could simply power down ISY, disconnect the PLM, and then reboot.That's just one idea. Perhaps some better ones will be forthcoming. Hello,I'm just new to ISY-99.
Just bought one. I like what I read. I have a DSC Alarm system and I have a PC5401 serial module that provide a serial interface to the system. Is there someway I can plug that in to the Port B of IS-99/IR PRO and has ISY monitor messages to get status of alarm panel. That 's all I want to do right now. I want to detect door/window openings, motion sensor and alarm activation/deactivations. The messages are very simple, ASCII text.
Look at this for detailsIf that's possible, then at least some of us with DSC alarm panels can be more automated. I cannot afford to upgrade my panel to ELK nowThis is the only thing that held me back from switching over.
I have been using homeseer for years, and my DSC alarm connected via the PC5401. With HS I can do many functions both based on HS functions and alarm actions and status. DSC is a very popular alarm system too btw.It's just too important to me to have alarm interfacing to lose that feature. HS new hardware controllers have four serial ports. But of course they are more than double the price too. Hello,I'm just new to ISY-99. Just bought one.
I like what I read. I have a DSC Alarm system and I have a PC5401 serial module that provide a serial interface to the system. Is there someway I can plug that in to the Port B of IS-99/IR PRO and has ISY monitor messages to get status of alarm panel. That 's all I want to do right now.
I want to detect door/window openings, motion sensor and alarm activation/deactivations. The messages are very simple, ASCII text. Look at this for detailsIf that's possible, then at least some of us with DSC alarm panels can be more automated. I cannot afford to upgrade my panel to ELK nowThis is the only thing that held me back from switching over. I have been using homeseer for years, and my DSC alarm connected via the PC5401. With HS I can do many functions both based on HS functions and alarm actions and status. DSC is a very popular alarm system too btw.It's just too important to me to have alarm interfacing to lose that feature.
HS new hardware controllers have four serial ports. But of course they are more than double the price too. I also have a DSC panel with a PC5401 interface and would like to be able to connect it.butI really like the product as it is and would hate to see firmware development stall in attempts to accomodate a bunch of serial protocols.What I'd like to see is the ability to use some isy standard protocol on the serial port. If this were the case, an external device could communicate with it and perform one or more translations to other devices. I could build a box with one serial port for communication with isy and other serial/ethernet ports for communication with other devices.If you try to do it all in one box, it'll get messy, more complex, and price will go up. I also have a DSC panel with a PC5401 interface and would like to be able to connect it.butI really like the product as it is and would hate to see firmware development stall in attempts to accomodate a bunch of serial protocols.What I'd like to see is the ability to use some isy standard protocol on the serial port.
If this were the case, an external device could communicate with it and perform one or more translations to other devices. I could build a box with one serial port for communication with isy and other serial/ethernet ports for communication with other devices.If you try to do it all in one box, it'll get messy, more complex, and price will go up.
. DTR - Data Terminal Ready. DSR - Data Set Ready. RTS - Request To Send. CTS - Clear To SendThere are multiple ways of doing things because there were never any protocols built into the standards. You use whatever ad-hoc 'standard' your equipment implements.Just based on the names, RTS/CTS would seem to be a natural fit.
However, it's backwards from the needs that developed over time. These signals were created at a time when a terminal would batch-send a screen full of data, but the receiver might not be ready, thus the need for flow control. Later the problem would be reversed, as the terminal couldn't keep up with data coming from the host, but the RTS/CTS signals go the wrong direction - the interface isn't orthogonal, and there's no corresponding signals going the other way. Equipment makers adapted as best they could, including using the DTR and DSR signals.EDITTo add a bit more detail, its a two level hierarchy so 'officially' both must happen for communication to take place.
The behavior is defined in the original CCITT (now ITU-T) standard V.28.The DCE is a modem connecting between the terminal and telephone network. In the telephone network was another piece of equipment which split off to the data network, eg. X.25.The modem has three states: Powered off, Ready ( Data Set Ready is true), and connected ( Data Carrier Detect)The terminal can't do anything until the modem is connected.When the modem wants to send data, it raises RTS and the modem grants the request with CTS.
The modem lowers CTS when its internal buffer is full.So nostalgic! An important difference is that some UARTs (16550 notably) will stop receiving characters immediately if their host instructs them to set DSR to be inactive.
In contrast, characters will still be received if CTS is inactive. I believe that the intention here is that DSR indicates that the device is no longer listening and so sending any further characters is pointless, while CTS indicates that a buffer is getting full; the latter allows for a certain amount of 'skid' where the flow control line changed state between the DTE sampling it and the next character being transmitted. In (relatively) later devices that support a hardware FIFO it's possible that a number of characters could be transmitted after the DCE has set CTS to be inactive.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |