› M1 Support Forum › System startup event 1367 exactly every 4 hours
- This topic has 2 replies, 2 voices, and was last updated June 28, 2021 at 4:55 pm by Brad Weeks.
June 14, 2021 at 4:03 pm #5224D Simon
We have a system that’s been in place for over 10 years. Several months ago, we added an input expander to accommodate a few new sensors.
When checking the logs, we now have an event “1367=System Start Up” for Input Expander 4 (newly added expander). The odd thing is that this occurs exactly every 4 hours on the minute. At midnight, 04:00, 08:00, 12:00, 14:00, 18:00, 21:00 and repeats like this daily.
What could cause this? I’ve already checked terminations/ resistance on the bus etc.June 14, 2021 at 5:22 pm #5225D Simon
Typos, meant to say:
“At midnight, 04:00, 08:00, 12:00, 16:00, 20:00, and repeats like this daily.”June 28, 2021 at 4:55 pm #5241Brad Weeks
The M1 System performs a Battery check every 4 hours starting at midnight (0000, 0400, 0800, 1200, 1600, 2000) with the Primary Battery Test being performed at 4:00 PM (1600) . When the test is performed the AC voltage is removed momentarily. 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.
In your case the System Startups are occurring during the Battery check/test and I suspect you may be drawing too much power from the main board
- You must be logged in to reply to this topic.