M1 Support Forum Control System Startup Randomly

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #5622
    Doug G


      I was just relaxing and heard my M1 Beep at me. So I checked the logs and I see Event 1367 = System Start Up. I have not noticed this before. There are no others events minus that one. Is this normal operation? I mean the M1 works great just trying to understand what that event is and is it normal to start up at a random time. Any advise would be greatly appreciated. Thank you.

      Brad Weeks

        How many total bus devices are connected to the M1 System and how are they wired 1) M1DBH, 2) M1DBHR or 3) Daisy Chained? Are there more than two home runs connected to the M1? If using the M1DBH is the overall Data Bus wiring less than 2000 feet or if Daisy Chaining less than 4000 feet?  If you have a secondary power supplies powering bus devices then you will need a Common DC Negative between the M1 and the secondary power supply.  In the case of a secondary power supply the +12V of the M1 should not be connected to the device if using a secondary power supply. With the entire system powered down including any secondary power supplies measure the resistance across Data A and Data B at which time you should measure ~60-70Ω Ohms. If you measure 120Ω we’re missing a terminating jumper and if less than 40Ω too many terminating jumpers. With the system powered UP measure the voltage at each device. You should measure 12-14 VDC. If less than 12 this could cause issues.


        The M1 System has been designed in that if it detects any operational anomalies, regardless how small or big or the cause it will attempt to “Self-heal Itself” in the most expedient manner. It does this in order to restore itself to a functionally operational state. This event is logged as a System Startup – Control. Has anything changed either with the M1 System or the environment at this locations? The reasons which could cause a System Start Up vary including data bus wiring, data bus termination,  voltage drops, environmental, transient spikes,  rules which might cause some type of endless loop or perhaps a faulty circuit board. In these scenarios we need to check / verify proper data bus configuration and termination, proper voltage levels at each device and that devices which are powered from the M1 are working properly.

        Doug G

          The system has not changed in the 7 years it has been installed. All the devices on the bus are on wireless, minus the three wired keypads, one Elk Ethernet Port interface, one siren, and two wired garage sensors using the ELK M1DBH Data bus. There have been no issues up until the past few days as I stated in my previous post. There is only one home run (M1 installed) and no secondary power supplies. I do run the ELKM1XSLZW for the Leviton Zwave module for my lights and I think it is pretty simple setup. How can I see what has went bad on the system or if something is failing? Nothing has changed at all. I am just trying to start with basics as of right now it has run fine with no issues. That just happened twice within the past maybe month. It does not do it often enough for me to worry, but I want to make sure nothing is failing or going to fail. Thank you Brad!

          Hugo Lyppens

            I have the same and I just ordered a replacement ELK M1 Gold. I hope that will fix it. Between Oct 2021 and now, have you been able to find the cause of the System Startup events?

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