Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #8953
    JOHN WADE

      This should be an easy one…  We need to be able to configure the onboard relays through a pull down or otherwise to be alarm outputs.  With the board using its alarm outputs as speaker drivers, this would greatly simplify the use of external sirens, strobes and etc.  Should be an easy addition to the next firmware update.  Particularly needed on systems not connected to the web for rule creation, but a valuable item either way.

      #8955
      Michael Burrell

        John –

        Thank you for the recommendation. We will look at adding this to the standard output options, but I would like to note that on the next firmware release we will have the option to convert either of the two Alarm Outputs to 12v DC outputs for Alarm Output use. These will be a steady output for Burg Alarms and a Pulsing output for Fire Alarms.

        But having preconfigured options for outputs is something we have discussed internally, I will be sure to note this suggestion as well.

        Thanks,

        Mike

        #8957
        JOHN WADE

          Michael, do you know what the current limitations will be on those outputs?

          #8958
          Michael Burrell

            The Alarm Outputs will have a 1.75amp rating on them when in 12v DC operation.

            The form C relay on the control and the relay’s on the AEXOU are rated at 7Amps @28VDC, 10Amps @125VAC. The ten low current outputs are rated at 50ma each.

             

            #8964
            Ted Cargnino

              Do outputs have a log?

               

              #8965
              Ted Cargnino

                How to Access Output Log?

                #8968
                Michael Burrell

                  Ted,

                  There is currently no log for the activation of outputs. However, we do have a plan to add an option that would allow installers to enable history log entries for specific outputs, inputs, or automation devices. That said, there is no set timeline for when this feature will be implemented.

                  Thanks,
                  Mike

                  #8974
                  JOHN WADE

                    Michael, when the outputs, both  speaker and onboard relay become configurable, will they have the appropriate temporal actions such as continuous for burglar alarm, triple temporal for smoke and quadruple temporal for CO?  The same question could also relate to the low current trigger outputs.

                     

                     

                    #8975
                    Michael Burrell

                      John,

                      Firmware 0.5.62 was just published a little bit ago with the updates to the Alarm Outputs as well as several other additions. Here is a link to the release notes that were just posted: https://www.elkproducts.com/alarm-engine-support/ae-update-info/

                      In reference to your question, when utilizing the Alarm Outputs configured for 12v DC, the burglar alarm will be a steady output. The Fire/CO is a temporal pulsed output to correspond Fire or CO. Triple temporal pulse for Fire and quadruple temporal pulse for CO.

                      We have not implemented a configuration for standard outputs as of yet. It is on the list of to do.

                      Thanks,

                      Mike

                      #8978
                      JOHN WADE

                        Michael,  When will we be able to do these upgrades without a site visit?

                        #8979
                        Michael Burrell

                          John,

                          This is currently the primary focus of the web development team. It’s quite a bit of work, but they are actively working on it. This functionality will be included in the next feature update to the ElkConnect Web Portal.

                          The necessary work within the control panel has already been completed. Mobile app support will require updates to the web/cloud platform first, so it makes sense to roll out this functionality through the web portal initially. Once that’s in place, we’ll extend the capability to the mobile app as well.

                          In the future, the mobile app will instruct the cloud service to perform the update process, rather than performing the update directly from the app, which is how it’s currently done locally.

                          Thanks,
                          Mike

                        Viewing 11 posts - 1 through 11 (of 11 total)
                        • You must be logged in to reply to this topic.
                        Scroll to Top