Page 1 of 1

Re: How Internal Memory Works

Posted: Wed Dec 23, 2015 12:21 pm
by KCReefer
I'm assuming that it is okay to use both internal memory and code?

Example:

I want to use internal memory for my daylights, actinic, moonlight, heaters, and dosers, but I want a special 2 hour daily timer for a solenoid valve, which would require the parameters to be set in code. (Since there is no way to have a specialized time schedule that is not daylight, actinic, or moonlight in the internal memory.)

I am going to try it tonight, but I figured I'd ask anyway

Re: How Internal Memory Works

Posted: Wed Dec 23, 2015 12:51 pm
by lnevo
You can totally mix. You could also use variable locations 100-199 for custom variables. You just have to set through the http API or through the android app

Re: How Internal Memory Works

Posted: Wed Dec 23, 2015 2:24 pm
by KCReefer
Could you explain a little more about using the variable locations? perhaps give a simple example of the variable, how it can relate to the port, and how it would be accessed through the API?

I'm a software engineer II if that helps you decide how to explain this to me. I'm used to Java and front end development, although I do have some building automation background. I'm not too familiar with arduino at all

Re: How Internal Memory Works

Posted: Wed Dec 23, 2015 3:06 pm
by lnevo
Look at my INO I have declarations up top of all the custom memory locations I use.

You basically do an InternalMemory.read() and InternalMemory.write() to grab and set those variables. It's pretty basic. As a software engineer, I think you'll get it pretty quick.

You may want to peek at the library docs http://www.easte.net/ra/html