| Author |
|
krommetje
Super User
Joined: December 29 2004
Location: Netherlands
Online Status: Offline
Posts: 695
|
| Posted: January 15 2015 at 12:13 | IP Logged
|
|
|
Dave!
what is going on here?????????
Here is part of the eventlog:
Edited by krommetje - January 15 2015 at 12:19
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 15 2015 at 21:03 | IP Logged
|
|
|
Peter,
Not sure what you're asking about. I can see the two screenshots of the eventlog but they don't look related. Is there a specific problem within one or the other?
In the second screenshot, I can see a critical error that occurred as the result of a double click in the PowerHome Explorer (I'll do some research and see what this is and try to make sure it doesnt happen again).
I also see a second critical error for the K8000. Cant really count this one as any critical errors that occur after the first critical error are invalid as memory is already corrupt (PowerHome needs to be restarted after any critical error to recover the memory).
I don't see any issues with the first screenshot.
Let me know some more details concerning what you're asking.
Thanks,
Dave.
|
| Back to Top |
|
| |
krommetje
Super User
Joined: December 29 2004
Location: Netherlands
Online Status: Offline
Posts: 695
|
| Posted: January 15 2015 at 22:39 | IP Logged
|
|
|
In the topmost screenshot you see macro K9on executed and under that you see
L1=I|L2=I| and so forth... PH never did that before, it started with that just after the crirtical error. There was a red band in PH that said "Powerhome needs to be restarded" and stopped working all of a sudden. It has to do with X10 because it does that with all x10 macros and commands... I Think
The so called criatical errorm with the K8000 is there all the time when exiting PH or a reinit.
I was working on my weathermacro to import the forecast cumulus gives on the webpage by importing a code in the file realtime.txt
I imported all 26 forecasts into PH as a global to subsitute the numeric code in realtime.txt by a text-forecast.
Edited by krommetje - January 15 2015 at 22:43
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 15 2015 at 22:47 | IP Logged
|
|
|
Peter,
The L1=|L2=|... is the verbose macro logging. It would have been introduced with version 2.1.5. To turn it off, open the PH Explorer and navigate to PowerHome|Setup|Logs and uncheck the "Verbose Macro" option. You'll have to restart or reinit in order for the changes to take effect.
The verbose macro option shows the values of the LOCAL and TEMP variables when the macro is launched.
Whenever there is a critical error, PowerHome now shows the red band and the notice to restart. This was added in PowerHome 2.1.5b I believe.
So all this is normal for the new version (except for the critical errors...I'll look into those).
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: what the ....
