› M1 Support Forum › 1141 = Expansion Module Trouble Message
- This topic has 11 replies, 2 voices, and was last updated January 19, 2026 at 4:40 pm by Gary Hansen.
-
AuthorPosts
-
October 24, 2025 at 3:01 pm #9627Gary Hansen
A client with an M1G which I installed several years ago has been encountering a number of errors for “1141 = Expansion Module Trouble.” Each trouble message is followed by a “1161 = Expansion Module Restored” message. the Extended Data for both is “Input Exp. 2.” In one instance powering off the panel and powering it back on resulted in a 5 hour period of no error messages. What should I look for?
October 27, 2025 at 12:29 pm #9631Brad Weeks
The ELK M1 Gold supervises the data bus and each device connected to the data bus. If a bus device fails to check-in the M1 will Log Expansion Module Trouble and when the device does check in the M1 will Log a Restoral of that bus device. Several reasons why a bus device might fail to check-in could include a voltage drop at the bus device, issues with the data across Data A and Data B, noise on the data bus or perhaps a faulty bus device. The voltage at each bus device should be ~12-14 VDC. There are three methods to wire the M1 Data Bus 1) M1DBH Data Bus Hub which requires a Cat5/6 from the M1DBH all the way to each bus device, 2)M1DBHR Data Bus Retro Fit Hub for existing 4-Conductor Home Runs, 3) Daisy Chaining Bus Devices. There should Never be more than two home runs connected to the M1 Data Bus. With the M1 powered off including any secondary power supplies powering Bus Devices measure the resistance across Data A and Data B at the M1 Main Board — you should measure ~60 – 70Ω Ohms. A reading of 120Ω Ohms means you are missing a terminating jumper on the data bus and a reading of 40Ω or less would indicate too many terminating jumpers are installed.
October 27, 2025 at 4:04 pm #9634Gary HansenBrad, thank you very much.
November 13, 2025 at 10:41 am #9674Gary HansenBrad, my client continues to have the problem I have described above. I ran Menu 8 6 from the most commonly used keypad and got a “DataBusErrors Retry T2A2 01925” response. The system had run fine for many years with no such error, and nothing had been changed for some time previous to receiving the errors. No jumpers had been added or removed. There have been no changes in any of the wiring. The system has a single ELK-M1XRF2H expansion module and 2 ELK-M1KP2 keypads. What should I check?
November 14, 2025 at 12:41 pm #9676Brad Weeks
Does the Missing Expansion Module happen at certain times for example 12:00 AM, 4:00 AM, 8:00 AM, 12 PM, 4:00 PM , 8:00 PM? Check the voltage at the M1XRF2H to make sure it is 12 – 14 VDC. Have you tried replacing the M1XRF2H?
December 4, 2025 at 2:01 pm #9710Gary HansenBrad, Thanks for the reply.
It does it a random times. I can provide a spreadsheet that contains a segment of the log for this unit. The expansion module is daisy chained to the data bus along with one of the keypads.
I went over to the client’s house to check the voltage for the ELK-M1XRF2H expansion module. It was installed a long time ago, and there has been some remodeling done in the house. Consequently, I was unable to find the module. Are you able to offer any suggestions?
In your reply from October 27, you suggested “With the M1 powered off including any secondary power supplies powering Bus Devices measure the resistance across Data A and Data B at the M1 Main Board — you should measure ~60 – 70Ω Ohms.” In a situation like this, is there a secondary power supply providing power to the expansion module?
January 12, 2026 at 10:54 am #9812Gary HansenBrad, I redoubled my efforts and found the M1XRF2H. I checked the voltage and it was 13.86. It is the original unit – it has not been replaced. I will go back and check the resistance across Data A and Data B. There are no secondary power supplies providing power to bus devices. Should I just go ahead and order a new M1XRF2H?
January 12, 2026 at 12:00 pm #9813Brad Weeks
It might be a good plan to bring a replacement M1XRF2H to see if this makes a difference.
January 13, 2026 at 11:41 am #9814Gary HansenI checked the resistance across Data A and Data B. It was a little over 120 ohms which you have indicated means a terminating jumper is missing. I checked inside the primary M1KP2 and I saw no terminating resistor. I presume where this should be placed is on the 2 pins toward the bottom edge of the printed circuit board, but I am not sure. are you able to post a drawing or picture for me to verify. If it is missing, how can I get replacements?
If it is indeed missing, would this cause the Expansion Module Trouble error?
Thanks again for the help.
January 13, 2026 at 6:23 pm #9818Brad Weeks
Is the M1KP2 the last device on the home run? If so then the black shorting cap should be across the two PINs JP1 “Term” NOT the white header pin labeled D0 D1. If you do not have a black shoring cap you can remove the JP2 X10 1-Way/2-Way jumper from the main board in the upper right hand corner to the left of the RS232 Serial Port and use it on the back of the keypad.
Yes not properly terminating the RS485 Data Bus could result in communication issues including Expansion Module Trouble.
January 15, 2026 at 4:09 pm #9830Gary HansenBrad, I removed the JP2 X10 1-Way/2-Way jumper from the main board in the upper right hand corner to the left of the RS232 Serial Port and use it on the back of the keypad. I then checked the resistance across Data A and Data B. It showed up as 66 ohms. I powered the system back up, and it appears to be working properly. I’m guessing we’ll need to keep an eye on it for a few days. If the Expansion Module Trouble error reappears I will replace the Expansion Module.
Thanks again for the help.
January 19, 2026 at 4:40 pm #9850Gary HansenBrad, it appears that my failure to put the jumper on the keypad was the cause of all of the Expansion Module Trouble errors. We’re five days after I moved the jumper per your suggestion, and the error is not reappearing.
Thank you very much for your help.
Gary
-
AuthorPosts
- You must be logged in to reply to this topic.
