Jump to content

- - - - -

M1XEP Firmware

  • Please log in to reply
5 replies to this topic

#1 gatchel



  • Professionals
  • PipPipPipPip
  • 1836 posts
  • Experience:average
  • Hardware:Elk M1, ISY-99
  • Tech:INSTEON, Z-Wave
  • Audio:Sonos
  • CCTV:analog, ip, dvr
  • Phone:POTS

Posted 04 November 2010 - 06:04 PM


I'd thought I'd post the its a very bad idea to roll back the firmware as part of the troubleshooting process.

IT BRICKS THE M1XEP. The only fix...Send it back.

It's very common with some of the other devices I work with to roll back the firmware as part of a troubleshooting process when all else has produced no results.

I had problems with verizon FIOS email. As part of the previous troubleshooting I updated from 1.3.10 to 1.3.20. Since them I have abandoned the verizon email to try gmx.com email as suggested. Nothing, I mean absolutely nothing would work as far as different settings, router reboots, DNS servers, email server IP, email server name, etc, etc...

I am so frustrated. I would think that RP2 would not let you roll back to an older version if it will destroy the XEP. GUESS NOT!!!!

It's hard to believe that there's no way to fix this, FTP, telnet, something. Tech support said NOPE!

Edited by gatchel, 04 November 2010 - 06:07 PM.

#2 Dan (electron)

Dan (electron)

    CocoonTech Admin

  • Admin
  • PipPipPipPip
  • 10857 posts
  • Twitter:@CocoonTech
  • Location:Central NY
  • Experience:guru
  • Software:EventGhost, HomeSeer
  • Hardware:Elk M1, Mi Casa Verde Vera, Ocelot
  • Tech:X10-RF, UPB, Z-Wave, ZigBee
  • Audio:AirPlay
  • Video:SageTV
  • CCTV:analog, ip, dvr
  • Phone:OBi100/110

Posted 04 November 2010 - 07:09 PM

wow, sorry to hear about your trouble, thanks for the headsup! This topic has been pinned!

#3 panamanian


    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 155 posts
  • Hardware:Elk M1

Posted 06 January 2011 - 01:40 PM

what if you disconnected your module prior to rolling back ?
or what if you rolled back the module firmware first then the control then update both?
it makes sense that sometimes both control and module have to operate with upgraded or downgraded firmwares.

its kind of like an iphone...you can downgrade the iphone os but you cant downgrade the baseband which is the internal iphone firmware that controls the hardware locking the phone sometimes useless.

so an elk module with a higher firmware wont work with a downgraded control firmware and it would lock it

#4 jschumann



  • Registered
  • PipPip
  • 27 posts
  • Location:Ledyard, CT
  • Experience:average
  • Hardware:Elk M1
  • Phone:VoIP via ISP

Posted 28 July 2012 - 11:23 AM

I see there is a new Firmware for the M1 Gold/EZ8 (4.6.8 or 5.2.10). I downloaded and installed with no issues. Release notes are posted on ELK website.

#5 treo650


    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 182 posts

Posted 29 July 2012 - 08:02 AM


Any new improvements that you

Or anyone with a change log?

#6 jschumann



  • Registered
  • PipPip
  • 27 posts
  • Location:Ledyard, CT
  • Experience:average
  • Hardware:Elk M1
  • Phone:VoIP via ISP

Posted 29 July 2012 - 08:11 AM

July 9, 2012 - M1 Firmware 5.2.10 ** Not Evaluated by UL

ElkRP Software 2.0.14 or later is recommended with this firmware.

1. The firmware is required for utilization of ELK’s M1XRFTW "Two Way Wireless" products. NOTE: The first M1XRFTW must
be enrolled at data bus address 2 in order for the two-way and sensor auto-sync to work properly. Redundant M1XRFTW
receivers must be addressed as 3, 4, or 5. ElkRP version 2.0.14 or higher is required for enabling the two-way auto-sync.

2. Fixed a problem in the lighting section that occurred with an ISY controller. If a lighting rule was used to "Then Turn On for
xx min/sec" and the light was then manually turned off before that timer expired, the light would turn back at the end of the
timer due to the fact that the panel had mistakenly used the toggle function instead of the Off command.

3. Additional fixes were made to the daylight savings time section.

4. Fixed problem with 24 hr burg or box tamper zone being silenceable by the * key.

5. Fixed problem with with acces of submenus 13 and higher in the Installer Level Menu 08 programming.

6. Change - If the M1’s RS232 "Port O" is set at a baud rate lower than 9,600 then it will no longer broadcast state changes.

7. Fixed problem with the retriggering of box tamper zones.

8. Fixed problem with Thermostat Change of State Flags not being reset following a Rules or ASCII message activation.

9. Added time delay (similar to M1XIN) on the Output Expander (M1XOVR) code to make it more tolerant of an occassional
missed data bus response.

10. Fixed an issue with cancel report timer not getting set when the Ethernet reporting format was engaged.

11. Modified the Contact ID code to be 381 upon a loss of supervision on a Keyfob defined zone. It previously reported 150.

12. Fixed an issue with the ASCII "AS" command and common area repeat messages on the RS232 "Port O."

13. Fixed a problem with the Chime enable function from a rule.

14. Fixed a problem with the tamper on wireless glass break detectors.

15. Change - When enrolling wireless sensors there is now a mandatory 4 second wait between successive sensors.

16. Fixed a problem with Fire Restorals not not always being placed into the event log, especially after a 5 sec. Smoke Reset.

17. Added - Tamper switches on wireless sensors (GE and Honeywell format) can be disabled (ignored by M1) by setting the

Zone Type as "Type 1 - Normally Closed."

July 9, 2012 - SUNSET of support for Caddx firmware version (M1 Firmware 4.6.8)

Announcing the Sunset (end of updates) of support for the M1 firmware 4.x.x versions. The 4.x.x range of firmware supported
the Caddx Networx "NX" branded wireless receiver. 4.6.8 was the last and final version of this firmware. Customers wishing
to benefit from any new features and/or fixes are encouraged to replace their Caddx branded wireless receiver with an ELK-
M1XRFEG Wireless Receiver (GE compatible). Doing this will enable the M1 control to be updated to firmware version 5.x.x
which will continue to be supported with future firmware updates.

Edited by jschumann, 29 July 2012 - 08:12 AM.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users