-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DSC Classic series support testing/feedback #196
Comments
I've just tested new develop branch on PC560 panel (keybus output should be same as for PC500, PC510, PC550) which doesn't support PC-16 output module. So my question, is PC-16OUT PGM output really necessary or panels can work without them programmed, for example on PC1550 - how limited it would be without PC-16OUT PGM connected? At weekend-house I have PC2550 panel, surely I'll take the logs but is there something specifically you're interested into or just doing basic arm-disarm stuff and verifying it's recognized correctly? Oh BTW, in every .ino sketch example the section for enabling PC16-out module on PC1500/PC1550 is misspelled. It should be section 13, not 19. Section 14 for PC2500, 16 for PC2550 and 19 is for PC3000. And there's typo in readme.md, TinyGMS-SMS should be TinyGSM-SMS. |
Hi @kricon,
Thanks for testing! The Classic series is extremely limited as far as the info available, there's info on the protocol at: https://github.com/dougkpowers/pc1550-interface Without PC16-OUT, the data is just zone lights and keypad lights. At least on PC1500/PC1550, the PGM can be configured to trigger when the alarm is tripped, but this isn't an option for PC560. It looks like the PC560 PGM can only be set to trigger when the system is armed/disarmed, so it'd take some context clues to figure out if the alarm is tripped. Even with PC16-OUT mode, I needed to setup a Rube Goldberg-esque series of checks on the data to see if various keypad lights were on, blinking, and then combining that with the PC16 data to work out the panel status (which is why I'm expecting bugs, there's probably some panel modes that I didn't test). Something similar may be possible for the PC560 but since
Sounds great, all of the above would be useful. I haven't seen any info on the PC2500/PC2550/PC3000 protocol, it may be different than the PC1500/PC1550 with their support for partition-like sides A & B.
Thanks! Fixed. |
I was finally able to do some experiments with PC2550 V1.3R. The protocol seems to be the same, even the PC1500RK keypad works fine with it so it seems that keypads are interchangable (except of lacking zone 7-8 and fire/program lights). I've opened both and internally PC1550RK and PC2550RK seems to have same quantity and same chips. I don't know for PC3000 though, im suspecting it to have more chips (as it have smaller FEP/FAP keys, so probably chips are populated PCB below it) and different protocol (one byte more)? The things I noticed so far:
Side A and Side B split arming works like it's described in manual, each side have it's own code for arm/disarm. And when only one side is armed, armed light blinks together with flashing zones that are associated to that side and are armed. Also, the KeybusReader output is printed multiple times, often 2 or 4 times, even the pressed keys. I don't know if that's related just to PC2550, I'll test it with PC1550 v2 and v4 when opportunity comes up. |
Hi @kricon - thanks for testing this! Good to hear that the PC2550 essentially uses the same protocol.
Great, updated the decoding for these bits.
Added to the TODO list, I'll have to see if there's a good way to distinguish between the PC1500 and PC2550 to be able to handle this. What happens when both sides A & B are armed?
Do you have logs for this? It should be possible to limit the panel data but the keypad data will show repeats, it's how the keys work for the classic series. The keypad sends the key data continuously as long as the key is pressed, the panel figures out if a new key is being sent if there's a time interval between key data. |
The system behaves normally, just like PC1500/PC1550 (trouble/bypass etc lights shut off and just Armed light stays on). Even if alarm triggers on one side you doesn't have any indication on that until you disarm any side. However, only when both sides are disarmed the system will automatically get you into *3 alarm memory menu. Also keep in mind that PC16out correctly reports zone alarms only on zones 1 through 4. On PC2550, Zone 5 alarm is indicated for alarm on any of the zones from 5 to 8 and on PC3000 zone 6 alarm indicates that alarm occured on any of the zones 9-16.
Sure, I have panel available and ready for testing/taking logs from. Here is sample of arming side A with bypassed zones then immediately arming side B and after was system armed, disarm side B and after disarming side A I got 20+ messages in less than second and half. In that example, I noticed that exit delay can be triggered only once, because Side A was armed 2 seconds before side B, and both sides get armed immediately together. When arming with bypassed zones, it says armed stay which is wrong and after any key press it immediately says Armed away. Zone open/close status doesnt change output:
It seems that sketch is calculating only based on considerations of Side A arming state, as there aren't "armed with zone bypassed" status when both sides are armed together with common user code or *0. Messages "Partition Disarmed" or "Armed stay/away" is displayed only when Side A is armed. For that reason, "partition 1 (not)ready" message is many times wrong.
When Armed light is flashing, the zones corresponding to armed side flash together aswell - it's then obvious that only one side is armed so status should be something like "Split-armed zones: Zone 1, Zone 2..". When only armed light is flashing, you can distinguish that system is armed with no entry delay. |
PR #296 is tested against a PC3000 series, is anyone available to test on the PC2550 or PC1500? |
I'll be able to test it with PC1550 v4 next week, and with PC2550 v1.3R and also PC1550 v2.x in a month or so. |
Hi |
I have a PC3000 to test. I'm not clear whether PC16-OUT is needed or not. KeybusReaederIP is working (I think) - I can see output when I press the keypad and I can type in my code and it works. Unlocker is not working for me - it never gets to print 'connected'. I see it doesn't use dscClassicInterface so I'll try changing that. |
I found my issue - I cloned @sfossen's fork but the PC3000 changes are in a different branch All I had to do was cd into the repo and run |
I dug up the old pc2550 control panel from 92 version v1.1 and connected it to the arduino and to my amazement it flashes with the status sketch, i can arm, disarm the system, blindly programmed. I have a second year younger from 93 and pc1550 from 98r + pc16out module. I will test them in my free time. I quickly looked at other sketches and there was a problem with them, only status work`s ok. I didn't look exactly where it was, but it didn't work. Will virtual keypad or blynk work with it too? I check virtualkeypad web (esp8266), and only works keypad and info about armed system, nothing else not working like zone or trouble status. This is normal? Email sketch (esp8266) works preety well, like trouble status, zone status after alarm, etc. |
Hi - I have the same system, PC2550 v1.1 - hoping you can shed light into any configuration changes you may have made. I am having issues getting status info (panelData from dscClassic.cpp) to my Arduino Uno. KeybusReader works correctly, and it appears pc16 does as well (I got the "Zone alarm: / Zone alarm restored: " printouts when tripping my system and running Status.ino, which seems to stem from pc16). I have options 16 and 30 properly set for PC16/PGM, but pretty stumped as to why I can't get status. I reduced my setup down to just DSC Yellow and DSC Green wired up, but still only get Keypad readbacks. Appreciate any help. |
Hello all! I just moved into a house that has an existing PC3000 and I'm all for getting this thing integration operational. I've successfully connected with the DSC Keybus Reader and am getting correct readings. Really hoping this project isn't dead. I know that the PC3000 was only in production/installation for a couple of years but don't really want to replace it just yet. kricon, as part of issue #303 you stated that a different library was needed: dscKeybusInterface_PC3000. I haven't been able to find this library and if this is the remaining piece to the puzzle then I'm all for it! Thanks for any help you guys can give! |
This works with PC3000: https://github.com/sfossen/dscKeybusInterface/tree/DSC_PC3000 |
You rock! Deleted old library files and recompiled with new libraries now everything is working properly! Thanks for the quick reply too! |
I've now had the ESP hooked up for a while and successfully reading zone data for a few days. Only issues I've noticed have been either strange wiring/jumpers in the control panel, or issues with sensors not updating that appear to be caused by static electricity (very low humidity this time of year). Finally got some kid free time to become familiar and test the alarm system. I have confirmed my master code operates the system at the keypad. Arming the system at the keypad constantly returns "Pending." Attempts to arm or disarm from the ESP have been unsuccessful. I've verified my circuit board was connected & wired properly. Anything I might be missing? |
I used Unlocker.ino to recover the master and installer codes so I know the keybus works. My ESP is powered from the alarm panel 12V. It's convenient, battery backed and less chance of noise. |
Ah geez. Rookie mistake. When I wired up my transistor, and subsequently when I verified my diagram, I never noticed that my pinout for my 2N4401 transistor was "bottom view." Quickly desoldered and reoriented the transistor, and now I'm successfully arming and disarming the system with the ESP. Still having trouble with it constantly saying "Pending" on the ESP. The DSC arms, bypasses, and alarms all normally. Just to double check, I'm using the: along with the appropriate library. Thank you so much for your help so far jpmorrison! |
Hi all, after some time (insert montage of seasons changing, stars exploding and being reborn, etc) the For now, the Classic series code doesn't handle split-armed systems - it will handle side A as partition 1 and ignore side B. I'm looking into treating side B as partition 2, this will depend on enough info being available from the panel, thanks to @kricon for the detailed notes and logs on this. As the implementation is different, I've merged #296 to a separate pc3000 branch so it's also available, it would also be good to get feedback on how this works vs the develop branch. |
Support for DSC PC1500/PC1550 is now in
develop
- this uses the same interrupt-based data capture as the PowerSeries, and like dougkpowers/pc1550-interface, requires configuring the panel PGM in PC16 mode.Most sketches are supported and require minimal changes, excluding
TimeSync-NTP
(should be possible to support) andEdit:Unlocker
(likely will not be supported as there is very little data feedback on the Classic series Keybus).Unlocker
now supports Classic series (2024.03)Post results from testing/feedback here - if you have a PC2500/2550/3000 panel, data captures from
KeybusReader
would be useful to see if support for these panels can be added.The text was updated successfully, but these errors were encountered: