Elk M1 (Ness M1) Rules Memory expansion

Hello all,
 
I am new to Cocoon but have been using and programming the Elk M1 (Ness M1) here in Australia since 2005 (geez, time flies !!).
 
Just wondering if there would be any way to increase the rules capability (memory) to the M1 system?
I have on a few occasions run out of memory due to the scale of the project.
 
I am just on a project now where the existing  system is needing expanding and I am out of memory.
Previously I have installed 2 x M1's on a single project and had them communicate via IP access commands and text strings, but simply having more available memory even as an add-on would be far easier to manage.
 
Thank you,
Philip
(AMPCOM)

Only ways I know is either like you've discovered or to offload some of the items to a third party controller.
 
I still haven't figured out the M1/Ness connection, but Elk hasn't really performed any real hardware updates in years, I'd say they should almost engineer a new panel and make portions backwards compatible.

Hello DELInstallations,
 
Thanks for your reply.
 
Yes, I do off load as much/or where possible to other 3rd party controllers such as lighting controllers etc.
However on this job I am using the Access Control with the M1 with approx. 11 doors together with full blown security, and home automation. The Access control has rules per user. This is because on some access keypads depending on which user enters their code will either unlock the side door to give access inside or open/close the driveway gate (for gardener, pool cleaner etc). Many other requirements the client requires have been accommodated in programming such as auto timers, annunciations under certain conditions....and the list can go on and on.
 
I really like and think it is very intelligent how Elk haven't had to bring out a new panel, but brought out BUS modules over the years which a firmware upgrade on the original M1 is all required to support the new module.
I hope they continue to keep this philosophy with new features and technologies that become available and can adapt to the M1.
 
Cheers,
Philip

By the way DELInstallations, the connection between NESS M1 / Elk is that NESS over here in Australia are electronics manufacturers and were the original and exclusive (and still are) the distributors for Elk here in Aus. branded Ness M1". I believe they also make some components and parts for Elk whilst also importing direct from Elk.
The electrical / electronic and RF standards between the USA and AUS are different, hence why NESS would have parts to suit and comply with Australian regulations.
 
Cheers,
Philip

I'd like to be able to send more email messages. I send both email and text to multiple users and the 16 message limit isn't enough.
 
Mike.

I started with the Ness M1 many years ago for a home automation scenario but found it could be limiting.  Not that I hit any memory limits just constraints.
 
Not long after putting it in I found CQC and it had C-Bus and M1 drivers.  To me this was a godsend.  The M1 could talk directly to C-Bus, CQC could talk to C-bus and the M1.  This allowed more important lighting control to be taken care of by the M1 and lesser important by CQC.
 
Since then CQC has allowed me to integrate everything I can think of - TV's, amps, electric fences, PLC's, solar inverter and weather stations.
 
And yes, when I did my Ness M1 training many many years ago, they commented on how they make products for Elk under licence and are the sole distributor for Elk in Australia.
While it adds a third component into the system, the fact that it runs on a PC means that its not under fixed memory constraints. 

I agree about the Ness/M1 connection, but really, other than the voltages (transformer) there's really not too much other than the applicable listings in the respective countries (while some things are omitted due to listing).
 
I think you're probably going to need to offload the access into another M1. Think between ASCII between the two and hard connections, probably the only logical way I can see without grabbing a 3rd party access device and using the M1 to spit weigand strings to it (since access panels are generally far more robust when it comes to options like that) or go the reverse, have the access control run the schedules and complex events and let those I/O drive the M1.
 
Probably not much of a cost difference given the price of peripherals and multiple panels.

Thinking outside of the box - why not take a look at the Koyo Click PLC for all non-security logic and I/O.  Its cheap at ~$100 and has a serial port so you can talk between the m1 and the PLC.  The newer one has Ethernet as well
 
Don't be put off by the fact that its a PLC - its easy to configure, expandable and for me has a CQC interface as well.
 
Cheaper than another M1, unload the M1 and let it do security and access control and then let the PLC do the rest.
 
I have two in my house with a third planned

You could use a universal devices ISY to carry the rule load. It's integration with the M1 is flawless and instantaneous. 

Hello everyone,
 
Thank you very much for all your responses. They have been great and very helpful.
I am leaning towards an interface that does not have to have a PC running 24/7 which I believe CQC requires. So I may leave CQC out of the options on this instance.
 
Cheers,
Philip

For something like CQC the PC can be very small for a small system, so it's not like it's some sort of big power suck or anything.