IndyUDIuser
Members
-
Joined
-
Last visited
Solutions
-
IndyUDIuser's post in Can UDM show the current time on my EISY? was marked as the answerI found an indirect way to verify the time. I have a program that sets several variables based on the system date and time, and updates them all day long. I was able to view those variables in UDM and confirm they were set correctly.
Thanks, and good luck with EISY-UI. I have peeked at it but still rely on Admin Console until the forum posts indicate EISY-UI is more ready for prime time.
-
IndyUDIuser's post in UDM Favorite needs 3 taps to run program was marked as the answerA late followup... A few weeks later, the icon started working as desired. The little circle appears every time I open Favorites, and I can click the button to turn on the fan.
I have no idea what changed, but it is working now.
-
IndyUDIuser's post in Stop reporting added device that was added weeks ago was marked as the answerTry rebooting the EISY. That seemed to help mine when I was getting those messages.
I just pulled the power cord out of the back for 10 seconds and then plugged it back in. Once it rebooted, the "added" messages stopped happening.
-
IndyUDIuser's post in System Busy dialog repeatedly after variable updated was marked as the answerActually, I changed the code to send a beep to the switch instead of flashing the backlight. That works, and no "System Busy" messages.
-
IndyUDIuser's post in INIT TO causing variable to be zeroed out was marked as the answerOK, I confess...
I found a line in one of my sub-programs (one I have not been paying attention to until now) that was setting iCurrentDayOfMonth to zero. I had accidentally used the wrong variable name in that program and didn't notice it until now. I corrected that and now all of the variables seem to be setting correctly. I added code to the beginning of the master program to initialize all variables to zeros before calling all the sub-programs (just so I can see this happening). I eliminated some of the waits, although I still wait 1 second between each sub-program call. So far so good.
I'll check this tomorrow to see if it is working in production as expected. FIngers crossed.