Please login or register.

Login with username, password and session length

Author Topic: GUI Tracking Failure  (Read 6303 times)

murphy

  • Sr. Member
  • ****
  • Helpful Post Rating: 1
  • Posts: 77
GUI Tracking Failure
« on: March 25, 2005, 06:48:13 PM »

Windows 2000 with SP4
AHP version 3.183 with Smart Macros
installed.  CM15A connected to computer.
CM15A is the diagnostic version.

Macro initiated events are not updating the
GUI display or the Activity Monitor.  Events
are happening at the correct time as
evidenced by looking at the lights and as
recorded in a CM11A communications log from a
CM11A that has nothing downloaded to it.
i.e. it's memory has been cleared.

The Status Report is correctly recording the
current state of the modules including the
flag that was set when the dusk triggered
macro started.  The macro has completed and
the flag has been reset.  Stopping AHP and
restarting it does not correct the GUI
display.  The status report is still correct.
Stopping AHP and disconnecting the USB cable
and then reconnecting the USB cable and
starting AHP causes the GUI to be correct.
The status report is still correct.
None of the events were recorded in the
Activity Monitor.
Logged

bob linca

  • Full Member
  • ***
  • Helpful Post Rating: 0
  • Posts: 61
Re: GUI Tracking Failure
« Reply #1 on: March 26, 2005, 01:17:21 AM »

I am seeing the same problem.

As I type, AHP is showing all my outside
lights as being ON, but they are really OFF.

This problem is not happening on all
devices. When I manually trigger a macro,
via AHP or RF remote, another module is
shown in its correct state.

--------------------------
My Configuration:
Windows 2000 with SP4
AHP version 3.183 with Smart Macros.
CM15A connected to computer.
AHP running at all times.
CM15A is the diagnostic version.
--------------------------
Logged

bob linca

  • Full Member
  • ***
  • Helpful Post Rating: 0
  • Posts: 61
Re: GUI Tracking Failure
« Reply #2 on: March 26, 2005, 02:06:40 AM »

Murphy: When this problem reoccurs, can you
check the Activity Monitor and see if it is
logging the macros.

The two problems could be connected.

Thanks,

Bob

Logged

murphy

  • Sr. Member
  • ****
  • Helpful Post Rating: 1
  • Posts: 77
Re: GUI Tracking Failure
« Reply #3 on: March 26, 2005, 07:33:05 PM »

The only events being logged by the Activity
Monitor are external RF signals from Palm
Pads and the Firecracker controlling my
camera, and power line signals from my AC
powered control box.  All events generated by
the CM15A whether directly from timers or
indirectly from macros that were triggered by
a timer (dusk for example) are not recorded
in the Activity Monitor.  They are all
correctly recorded in the Communications log
of the CM11A that I use to monitor power line
activity.  The same is true for the GUI
display of the associated modules.  Events
generated external to the CM15A are correct
in the GUI display.  Events generated in the
CM15A are never recorded in the GUI display.
The Status Report is always correct with
respect to the current state of the modules.
Logged

Noam

  • Community Organizer
  • Hero Member
  • ***
  • Helpful Post Rating: 51
  • Posts: 2818
Re: GUI Tracking Failure
« Reply #4 on: March 27, 2005, 09:45:10 AM »

I am having the same issue, since upgrading
to 3.183. I found that my Activity monitor
is no longer logging timers run from the
CM15A. It only seems to be logging "manual"
commands (those I click in the interface, or
use a handheld remote, etc).
Logged

murphy

  • Sr. Member
  • ****
  • Helpful Post Rating: 1
  • Posts: 77
Re: GUI Tracking Failure
« Reply #5 on: March 27, 2005, 11:25:31 PM »

Additional info.  I turned off a breaker to
rewire a switch and then realized it was the
breaker that feeds the CM15A.  When the
breaker was turned back on I did a download
to the CM15A and verified that the clock was
correct.  All of my dusk internal events were
recorded correctly in the GUI and the
Activity Monitor.  On a hunch I shut down AHP
and disconnected the USB cable.  I
reconnected the USB cable and started AHP.
Internal events are no longer being recorded
in the GUI and the Activity Monitor.  In all
cases the Status Report is correct.  It would
appear that the new USB driver in its attempt
to handle "surprise" disconnects is unable to
receive events from the CM15A once the USB
cable has been disconnected and then reconnected.
Logged

X10 Pro

  • Hero Member
  • *****
  • Helpful Post Rating: 23
  • Posts: 1416
Re: GUI Tracking Failure
« Reply #6 on: March 28, 2005, 02:40:43 PM »

I think the problem is probably simpler than
the new driver causing problems. Most likely
we changed how we're decoding and logging the
stored event notices from the interface, and
broke something in the process. We'll fix this.
Logged

hans

  • Newbie
  • Helpful Post Rating: 0
  • Posts: 3
Re: GUI Tracking Failure
« Reply #7 on: March 28, 2005, 10:34:22 PM »

After Updating to Version 3.183

As reported by others  --  The GUI is not
updating for Timer Events initiated by the
CM15.
Sending manual command  -  using PalmPad --
works properly -- the GUI  is Updating.

Logged
 

X10.com | About X10 | X10 Security Systems | Cameras| Package Deals
© Copyright 2014-2016 X10.com All rights reserved.