Jump to content

- - - - -

Is M1G multitasking or serialized?

  • Please log in to reply
2 replies to this topic

#1 Ira


    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 551 posts

Posted 10 June 2012 - 02:34 PM

Is the M1G capable of multitasking (processing one or more events/triggers simultaneously or interleaved), or is it serialized?

More specifically, if sensor S1 triggers followed by sensor S2 triggering a split-second later, will all of the rules that will run as a direct result of S1 triggering run before any rules that will run as a direct result of S2? For example, if an S1 rule causes output O1 to be turned on, is it guaranteed that O1 will be turned on before any S2 rules are triggered, and therefore, any S2 rules that check the state of O1 will see it as on (unless it was subsequently turned off)? If S1 triggers multiple rules that take several seconds to run, and S2 triggers less than a second after S1 triggers, will S2 rules wait until all of the S1 rules have been run?

I assume that in the above example, any rules that might run because of O1 being turned on are a separate "unit-of-work", and may or may not run before the S2 rules depending on when O1 was turned on relative to S2 changing state.


#2 DELInstallations



  • Professionals
  • PipPipPipPip
  • 5400 posts
  • Software:Custom
  • Hardware:Custom
  • Tech:ZigBee
  • Audio:Custom
  • Video:Custom
  • CCTV:analog, ip, dvr

Posted 10 June 2012 - 07:57 PM

Why not ask Brad or the other guys at Elk regarding your concern with rules and specific application? I would assume that you are running some tight tolerance timing or similar?

#3 Lou Apo

Lou Apo


  • Registered
  • PipPipPipPip
  • 2703 posts
  • Location:Austin TX
  • Experience:average
  • Hardware:ISY-99
  • Tech:INSTEON
  • Audio:Custom
  • Video:Windows Media Center
  • CCTV:analog, dvr

Posted 11 June 2012 - 07:21 PM

Not that this answers your question, because it doesn't, however. . .

I do know that ISY uses what is called "event driven" control. Which means that new events will start processing as soon as they happen regardless of whether a previous event and it's triggered processes have completed. So, basically, multi-tasking.

Elk programming is much less complex than ISY so it would be less likely to be a consideration, but it sounds like you might have one of those situations.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users