No announcement yet.

ocelot memory limitations?

This topic is closed.
  • Filter
  • Time
  • Show
Clear All
new posts

    ocelot memory limitations?

    new to ha, writing a web based ha scheduling program for pc illiterates. im looking for a hardware controller that can retain scheduling, on a monthly basis - pc would be turned on monthly to update hardware for following month. can someone explain to me what the 16k memory of the ocelot actually holds. can i have 15 different timed events per day on a 7 day rotation. where sunday is different that monday etc...
    i am only interested in time/date based triggers, no motion, thermostat, x10, etc..


    I beleive the current limit for the ocelot is 2048 lines of code.
    But the new 2.0 version may have increased that I am not sure.
    But that should more than enough for your events.

    Why oh why didn't I just leave things alone, they had been working.


      The new limit with C-Max 2.0 is 4096 lines. With that, you could program hundreds of scheduled events no problem.

      If you don't know what you're doing... do it neatly.


        is there anyway to upload a program to ocelot without the use of cmax


          Right now CMAX is really the only way to upload a program.

          However, the RS232 command set is somewhat documented, you might be able to write your own upload. Since its not fully documented, you would probably need to "sniff" the serial port to see what CMAX is actually doing.

          If you want to try your hand at this, you get get the PortMon utility from that will do this for you.


            You could write a shell program in the Ocelot and have your program update the Variables with the schedule times. The Ocelot allows comparing time of day to a variable. If the I/O remains the same, this is the simplest way to go.

            Imagination is more important than knowledge.

            Albert Einstein