FYI New version of ElkRP2
- Thread starter mikefamig
- Start date
Ampcom
Member
Hello,
I upgraded to v2.0.36 on the 22nd Dec 2017.
Since then have connected to several panels, including remotely and have experienced no problems.
The release notes explain what the update included:-
Dec 18, 2017 - ElkRP2 Software Release 2.0.36
1. ELK-M1XRFTWM Wireless Receiver - ElkRP is now aware of this new “M” version wireless receiver.
2. Voice Word appearances - Fixed issue with how voice words appeared on the Lighting, Tasks, and Outputs pages.
3. Spurious Username/Password pop-up when opening M1XEP Setup Window - Found and fixed.
4. User ACCESS Fobs/Cards - Corrected an issue that seemed to cause certain combinations of site code and card number entries to change when clicking away from and then back to a user screen.
5. Creating New Account using Copy From or Save As - An issue was fixed where Keypad F-Key emergency RC (Report Codes) were not properly saved after a Copy from or during a Save As.
6. Changed & Saved Date on Account Details Page - Fixed issue with this date not getting updated when user made changes only to report codes.
7. C1M1 Connectivity - Adjusted some timeouts to improve connections made over cellular.
8. Templates Folder - When ElkRP is installed (new installations only) a folder called _Templates will be created where all Elk supplied special accounts will be stored.
9. Sunrise/Sunset - Also on new ElkRP installs the default longitude setting will now be “longitude west”.
10. Whenever Rules - Fixed some incorrectly displayed option selections on rules containing: “Whenever Any Alarm” or “Whenever Fire Alarm.” This fix also resolved an error that occurred if options selected were not correct.
11. Lutron references - Because M1 now supports 3 models of Lutron products, the suffix “RA2” was removed.
12. Rule Comments - Fixed issue that could cause rule comments containing quotation marks to be lost.
13. Windows 10 - Corrected issue that caused some TLS connections from Windows 10 to fail.
The difference I have found is that using the 2way wireless Transceiver with previous versions of RP used to have model as "Unknown" in the Enroll/Update Control & Devices.
With RP v2.0.36 2way wireless Transceiver model is now shown.
Cheers,
Philip
I upgraded to v2.0.36 on the 22nd Dec 2017.
Since then have connected to several panels, including remotely and have experienced no problems.
The release notes explain what the update included:-
Dec 18, 2017 - ElkRP2 Software Release 2.0.36
1. ELK-M1XRFTWM Wireless Receiver - ElkRP is now aware of this new “M” version wireless receiver.
2. Voice Word appearances - Fixed issue with how voice words appeared on the Lighting, Tasks, and Outputs pages.
3. Spurious Username/Password pop-up when opening M1XEP Setup Window - Found and fixed.
4. User ACCESS Fobs/Cards - Corrected an issue that seemed to cause certain combinations of site code and card number entries to change when clicking away from and then back to a user screen.
5. Creating New Account using Copy From or Save As - An issue was fixed where Keypad F-Key emergency RC (Report Codes) were not properly saved after a Copy from or during a Save As.
6. Changed & Saved Date on Account Details Page - Fixed issue with this date not getting updated when user made changes only to report codes.
7. C1M1 Connectivity - Adjusted some timeouts to improve connections made over cellular.
8. Templates Folder - When ElkRP is installed (new installations only) a folder called _Templates will be created where all Elk supplied special accounts will be stored.
9. Sunrise/Sunset - Also on new ElkRP installs the default longitude setting will now be “longitude west”.
10. Whenever Rules - Fixed some incorrectly displayed option selections on rules containing: “Whenever Any Alarm” or “Whenever Fire Alarm.” This fix also resolved an error that occurred if options selected were not correct.
11. Lutron references - Because M1 now supports 3 models of Lutron products, the suffix “RA2” was removed.
12. Rule Comments - Fixed issue that could cause rule comments containing quotation marks to be lost.
13. Windows 10 - Corrected issue that caused some TLS connections from Windows 10 to fail.
The difference I have found is that using the 2way wireless Transceiver with previous versions of RP used to have model as "Unknown" in the Enroll/Update Control & Devices.
With RP v2.0.36 2way wireless Transceiver model is now shown.
Cheers,
Philip
Never mind I just found the answer to my own question in the install manual.
The letter "M" in the M1XRFTWM receiver part number stands for "multiple receiver capable". The previous Elk two way receiver (M1XRFTW) was occasionally installed in multiples on a single installation. The intention and benefit of multiple receivers was for added coverage in super large buildings. It was discovered however that if the multiple receivers were not spaced far enough apart then their overlapping coverage area could cause processor memory overflow if the multiple receivers too often heard the same transmission from one or more sensors. This could then lead to false supervisory troubles or other issues. Not all installations experienced this and some continue to work fine with no issues. It can largely depend on the installation or environmental conditions. This new M1XRFTWM receiver is especially designed to filter out duplicate transmissions and recover from memory issues should they ever occur.
The letter "M" in the M1XRFTWM receiver part number stands for "multiple receiver capable". The previous Elk two way receiver (M1XRFTW) was occasionally installed in multiples on a single installation. The intention and benefit of multiple receivers was for added coverage in super large buildings. It was discovered however that if the multiple receivers were not spaced far enough apart then their overlapping coverage area could cause processor memory overflow if the multiple receivers too often heard the same transmission from one or more sensors. This could then lead to false supervisory troubles or other issues. Not all installations experienced this and some continue to work fine with no issues. It can largely depend on the installation or environmental conditions. This new M1XRFTWM receiver is especially designed to filter out duplicate transmissions and recover from memory issues should they ever occur.
I just updated to 2.0.36 a little while back.
Then I tried to Import a saved export .exp file and I get an error:
"Exported account file : Bla.exp is an 5.3.8, not an M1G.
Please create or open an 5.3.8 account to import this file into."
This makes no sense. 5.3.8 is the firmware version. M1G is the Product. They are all M1G and this open account was a 5.3.8 copy of the existing account.
I tested exporting an account from 2.0.36 and then tried to import that same file no luck same error.
Come on guys. Please test your software before you release updates.
2.0.36 still didn't fix ElkRP2 crashing on close and other bugs (still gives the appearance of 2nd rate development)
Just wondering when Elk will completely abandon the M1. I guess as long as they release the system as Opensource we should be fine (probably a lot better off actually).
Then I tried to Import a saved export .exp file and I get an error:
"Exported account file : Bla.exp is an 5.3.8, not an M1G.
Please create or open an 5.3.8 account to import this file into."
This makes no sense. 5.3.8 is the firmware version. M1G is the Product. They are all M1G and this open account was a 5.3.8 copy of the existing account.
I tested exporting an account from 2.0.36 and then tried to import that same file no luck same error.
Come on guys. Please test your software before you release updates.
2.0.36 still didn't fix ElkRP2 crashing on close and other bugs (still gives the appearance of 2nd rate development)
Just wondering when Elk will completely abandon the M1. I guess as long as they release the system as Opensource we should be fine (probably a lot better off actually).
