| Author |
|
nadler
Super User
Joined: February 25 2006
Location: United States
Online Status: Offline
Posts: 354
|
| Posted: July 25 2006 at 17:13 | IP Logged
|
|
|
I haven't had this issue with PH before, but today I added several IR Triggers. When executing those triggers in rapid succession, the third time PH locks up and pins the CPU at 100%. I then get a coutdown auto message "Smarthome Dev Manager does not appear to be running..command could not be sent." The countdown stops at 1 and freezes. I have to go into Task Manager and shut PH and Dev Manager down. The trigger is not only receiving IR but sending it as well. Could there be some sort of conflict with the USB UIRT driver? In addition I am wondering why I get a device manager message as it should only be accessing the USB UIRT not the PLC.
On a similar note, after this started I then tried a similar trigger with a keypadlinc. Big mistake on my part. I messed up the keypadlinc, had to reset it and right now am trying to rebuild its links through PH. I should mention that I am watching the Performance Monitor in the task manager as I type this and it is peaking at 100% every couple of seconds and then coming down to 5%-19%. It looks like the top of a square wave. Should it be doing that?
|
| Back to Top |
|
| |
nadler
Super User
Joined: February 25 2006
Location: United States
Online Status: Offline
Posts: 354
|
| Posted: July 26 2006 at 08:05 | IP Logged
|
|
|
More Information.
I downloaded a program called IR Learner from the USB-UIRT site. This program has nothing to do with PH. When I opened the program and tried to use it, it crashed PH which was running in the background.
There is definitely some conflict between the two.
Anyone have ANY ideas?
|
| Back to Top |
|
| |
nadler
Super User
Joined: February 25 2006
Location: United States
Online Status: Offline
Posts: 354
|
| Posted: July 26 2006 at 13:20 | IP Logged
|
|
|
More info:
The above described crash happens when I send a ph_ir formula (or a macro that contains the same formula or ir command) AFTER receiving an IR command which triggered the macro.
So it goes like this:
USB UIRT Receives IR command
PH executes Trigger (which either is a formula or macro)
USB UIRT Sends IR command
PH crashes (2 out of 3 times) by pinning CPU at 100% and has to be shutdown using task manager.
This is absolutely repeatable.
If I just run the macro over and over without having first triggered it with an IR input the macro runs with no problem. Conversely if I use the IR command to trigger a formula or macro which does a task but does NOT include an IR send, PH works well.
So it seems that the sequence of receiving an IR command and then transmitting an IR command is the problem.
I hope someone has an idea or a fix.
Thanks!
Edited by nadler - July 26 2006 at 13:21
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: July 26 2006 at 13:28 | IP Logged
|
|
|
You mentioned a USB-UIRT driver; none is needed for PH. If you installed one, try uninstalling it.
|
| Back to Top |
|
| |
nadler
Super User
Joined: February 25 2006
Location: United States
Online Status: Offline
Posts: 354
|
| Posted: July 26 2006 at 13:58 | IP Logged
|
|
|
Good suggestion, but it didnt work. I uninstalled the driver and rebooted my pc. When it booted up again it asked for a driver. I exited out without a driver and loaded PH. PH said it couldnt find the USB UIRT. So I downloaded a new driver and reinstalled. It now works as before...PH crashes with an incoming IR and outgoing IR. I fooled around with the USB UIRT controller settings in PH but I think I only made it worse. Now PH seems to crash upon receiving an IR signal. I think I uninstalled the driver correctly but if you have any suggestion on that score, please let me know - maybe I missed something.
Thanks!
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: July 26 2006 at 16:48 | IP Logged
|
|
|
Noel,
It sounds as if the action type of your triggers are set to "Immediate" instead of "Queued". Reference this post for further information on this: http://power-home.com/forum/forum_posts.asp?TID=613.
Let me know if this solves your problem or not.
Dave.
|
| Back to Top |
|
| |
nadler
Super User
Joined: February 25 2006
Location: United States
Online Status: Offline
Posts: 354
|
| Posted: July 26 2006 at 17:14 | IP Logged
|
|
|
Dave,
All the triggers are Queued. I tried setting up another controller as a USB UIRT type and deleted the first controller. That didn't help. Same problem. The driver is ver 1.4 which I downloaded from the USB-UIRT site. I saw PH has a PHUIRT.dll but I didn't know how to load that as a device driver instead. Am I supposed to do that?
I am now noticing that PH sometimes freezes and pins the CPU when I send an IR command to the USB UIRT multiple times and it doesn't execute a macro or formula which sends IR. This either didn't happen before and I made something worse or I just didn't notice it before.
Since I'm planning on doing a lot of this type of IR, should I get rid of the USB-UIRT and try something else?
|
| Back to Top |
|
| |
nadler
Super User
Joined: February 25 2006
Location: United States
Online Status: Offline
Posts: 354
|
| Posted: July 26 2006 at 18:27 | IP Logged
|
|
|
What a puzzle. Here's another piece.
The crash I described happens with a particular IR remote. The codes for this remote were easily learned by PH. When I switched the trigger to take the codes of another remote, the trigger worked fine with absolutely no lock up no matter how many times I transmitted. I then tried other buttons on this particular 'bad' remote and each button repeated the lockup. I then tried other buttons as a trigger on the 'good' remote and the trigger did not lock up (limited testing). So here is the code for one button of the bad remote. I'd appreciate it if someone with a USB UIRT could try it and see if it locks up their PH. I bet it does!
Incoming code: 170000AD00CA
Outgoing code: <Pronto>0000 0071 0000 000C 0020 0020 0020 0020 0041 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0020 0041 0020 0020 0041 0020 0020 0CED<Repeat>3
Edited by nadler - July 26 2006 at 18:28
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: July 26 2006 at 19:30 | IP Logged
|
|
|
This code is played without issue on my system.
|
| Back to Top |
|
| |
nadler
Super User
Joined: February 25 2006
Location: United States
Online Status: Offline
Posts: 354
|
| Posted: July 26 2006 at 20:40 | IP Logged
|
|
|
Puzzled solved.
Tony,thanks. You gave me a clue.
It turns out that if you pressed the 'bad' remote button just for an instant the trigger worked. You could do this repeatedly. If you held down that button (like you would for a volume up or down for example) it overwhelmed PH (or the USB UIRT) and PH froze and crashed.
I thought I could get around it by setting flags and building in waits in a macro but that didn't work reliably. If PH got multiple IR INs quickly and had to execute a trigger with a formula or macro it would crash. If the flag was set quickly enough then the macro would only execute the first line and end. Then PH won't crash.
So the bottom line is that I can't use the 'bad' remote (which is too bad since I have several of them). But the good news is that I figured this out (took me long enough). The reason the 'good' remote worked is that it only sent the ir stream once, even if you held down the button.
Dave and Tony, thanks for the help.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: July 26 2006 at 21:13 | IP Logged
|
|
|
Glad you have it worked out. 
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: August 02 2006 at 23:29 | IP Logged
|
|
|
Noel,
You could probably get this working reliably with the flags you're talking about. What I would try is create a macro where the first line sets the flags you're talking about (I assume to keep the macro from re-executing within a certain time frame). After you're set the flag, do a Wait 0.01 and then follow with the rest of the required macro commands. Then set the trigger that calls this macro to "Immediate".
The immediate should cause the macro to fire immediately before it can overwhelm PowerHome and then set the flag appropriately. The "Wait" command then inserts the rest of the macro into the execution queue for processing in order.
Before giving up on the remote I would give this a try and if it still gives you problem, post the code you're using for the "flag" setting, etc. as there may be a logic problem there.
HTH,
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome Bug Reports
Topic: PH Pinning CPU at 100%
