Another question about this...
If I have an Analog RAM with Store, Recall, and Select1 all set to "1" for constant store, can I route these same signals to another analog RAM (or several different ones) for the secondary ones to handle zone presets??
---In Crestron@..., <nick@...> wrote:
Thanks for the info.
Is this constantly storing ARAM even useful if I did do an init that set values at each program restart? I almost always so the init in all other programs. ?
---In crestron@..., <hvolmer@...> wrote:
Nothing should clear them. ??When the program runs for the first time, they may have seemingly random values - depending on the control systems. ?I think 3-series will default to 0.
Now, if that ARAM is modified or moved in the program, its values will get out of whack. ?Whenever you define an ARAM like this, it should stay put forever and only have things added after it.
If you *want* to clear them, you can put an init in the program with all the analogs set how you want, and fire it off. ?You can also hit them all individually in debugger.
On Nov 11, 2013, at 4:01 PM, <
nick@...> wrote:
?
Oh Ok. That makes sense.. What would clear those values out??
---In
crestron@..., <hvolmer@...> wrote:
It keeps those analog values loaded over program restarts. ?The processor always store the value of a given analog, and at startup, recalls it as it's initial value. ?
On Nov 11, 2013, at 3:17 PM,
nick@... wrote:
?
Hi all,
I am looking at an older program that used a real early version of D3. Not sure how much of it was tech-modified.
The code has an ARAM at the top of the program with ALL lighting ins routed to itself (input=output) and the store, recall, and select1 values are all set to "1".?
What is the purpose of this? Is this just setting up the RAM space for these analog values for OTHER ARAMs in the program, which actually handle presets?
Processor was a PAC2.?
