It was on a system tested March of last year, the zone status was working. The driver at the time was HS2064_3.0000.0005IP from what I see in the program we tested. I have a co-worker who rolled out a panel recently and had the zones reporting pretty fast with HS2064_3.0101.0018IP... before they decided to change the DSC board(!), now the integration is fully broken even with the settings adjusted. Will update when we can test again

I'm aware of the Zone Status driver, but it didn't work. I also checked the notes in the dat file which state it's not supported. Did you use it with a Neo panel?

They updated the Neo driver last year - maybe they removed that feature :-)

There has been a zone status module added awhile ago, CRESTRON CERTIFIED DRIVERS SECURITY SYSTEM ZONE V1.0.
Worked well and pretty fast to report last time I tested last year.

I got this working, and setup wasn't as difficult as the Help document makes it seem.? It probably only took about 15 or 20 minutes, and would be even less if I ever had to do it again.

I've let it run for a few days and it seems to work well, however there are two pretty big caveats...

#1 - It only provides keypad emulation, which is good to have, but there is NO discrete zone status.? So it's difficult to do things like trigger other logic when a door is opened or motion is sensed.? Technically, the keypad's display output could be run through an SIO, but that's not ideal.

#2 - As Gregory and others have mentioned, it takes a FULL ten minutes to connect initially, and after any reboot.? I asked Crestron about it, and their exact words were "that is normal behavior".

I think we're eventually going to have to embrace these newer panels, but ten minutes (actually 12 to 16 minutes in my tests) to reconnect is simply unacceptable.? I advised the client to go with an Elk until a better option is available.? Fortunately the security contractor is fine with Elk, although they do prefer the DSC.

I don't know why that is but it is important to know?

It was integrated about a year ago and has been solid

I might be building my own Crestron DSC driver pretty soon out of need, similar to my Interlogix NX-8E interface (which I’ve improved significantly since I last talked about it)

the bulk of the low level protocol will likewise be on an Arduino-style board so that the Crestron processor sees simple high-level messages and isn’t running a time sensitive protocol.

I’m not enthusiastic of 10 minutes for a device to sync without good reason or explanation, and I like using my Arduinos that fully boot in milliseconds, keep protocol timing commitments to the microsecond, and can be integrated to Crestron with nothing more than basic text commands over serial send/receives or their IP counterparts. ?This way pretty much eliminates all risk of causing lockups or resource leaks on the processor. ?Also makes for novel ways to debug — like if I select an Arduino with a built in LCD display where I can show debug and protocol status info.?

if I come up with something good, I’ll either be sharing it or selling it. Will say more when I have something to show. Mike

On Wed, May 22, 2024 at 06:13 PM, Gregory Oldacre wrote:

it takes like 10 minutes to connection...

Mmmmm....That tells me alot!!

Thanks for the feedback, Gregory.

How long ago was it integrated, and has it been reliable?

I have the DSC NEO successfully working on a job.? Was a pain to setup.? ?Just make sure all settings on alarm system are correct, check documentation for module.? It takes like 10 minutes to connection so have to be patient when seeing if it is actuallyworking.

I was asked months ago to integrate it in a system and, after months of the alarm integrator sending me incorrect information, and not understanding what I needed to even attempt to get it to work, I told the dealer to tell their client to replace the alarm system with something that is known to integrate well or remove alarm integration from the system. I have yet to find anyone who has had a positive experience or suggests integrating the DSC Neo with Crestron.

A friend had a project with one a few months ago...
How much can you charge your client for it???...;)
It was a miserable experience for him. I'm not sure if the second one would be better (probably somewhat), but I personally am staying away from it...

The lack of refinement in product and software/interface development and the dumbing down of expectations, both for clients and dealers, is really troubling.
I will not support CCD/PKG interfaces as IMHO they are at best poorly conceived and documented.

We're holding firm that we will only integrate with Honeywell and Elk. If their security guy can't accommodate, we recommend replacing them with a contractor that can.

I guess it's time to revisit this.? I've had three clients recently inquire about integrating Neo panels - with Simpl, not CH.

The last time I tried was a couple of years ago, and it didn't go very well.? Has anything improved since then?? Has anyone gotten the CCD driver to work properly, reliably, and continuously - in a Simpl program???

?

Thanks in advance!

开云体育

Thanks.? As I said, I don't really have an issue with the modules.? Over the years, I've simply seen other people complain at creating an exact duplicate of the ELK keypad on a TP to be an issue for them.? For example, if I remember correctly the original ELK demo program uses a second page to provide buttons for bypassing zones vs. having a bypass button on the keypad.? Personally, I think the second page of buttons, which can each be labeled with the zone name, to be a better solution.

Thanks again

Jay

We have the Alarm programmer set up the ELK so that the F keys (F1 F2 F3 F4) do things like bypass or panic as needed.
That way we can label a button "Bypass" and send F4 to elk which is programmed to bypass. Maybe that will help you work
around the missing buttons Jay?

Thanks, Jay!

开云体育

This isn't something that bothers me but for those that want to create a perfect copy of the standard ELK keypad in crestron I believe, if memory serves me correctly, that there are a few things you can't implement in a way that exactly matches the keypad.? For example, I don't believe the chime and bypass keys are included in the modules but they exist on the keypads.? I also don't think the * and # keys on the keypad have equivalents in the modules.?

There is certainly the ability to bypass zones in the modules but it is implemented differently on a keypad.?

So, I believe the functionality you need is all included in the modules.? But if you are trying for perfect emulation of a keypad it isn't quite the same.

Jay

OLD modules are DEFINITELY BETTER!!!...:)? ?(and not just because I'm old!!)

It's good to hear that ELK is still a good option...? What issue have you had with KPD emulation?

That's good news, assuming the new modules are at least as robust as the old ones - and they're not "Crestron Home only" :-)