Utility: STBKeepAlive - scheduled commands for USB-UIRT

[shadeblue.com]

Hi Jim

Looks like a problem in the UsbUirtManagedWrapper.dll

This part is not my code, but I can provide the source that I have for it. PM me your email address and I'll send it along.

Thanks, SB

[shodge]

Running under Server 2K3. Was running both sage service and STBKeepalive under the local System account. Running the default commands for U-Verse.

After 3 days I got this...
2009-03-17 18:55:00,025 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-17 18:55:00,025 [STBKeepAliveQuartzScheduler_Worker-4] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-17 18:55:00,025 [STBKeepAliveQuartzScheduler_Worker-4] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 06:55 PM]
2009-03-17 18:55:00,025 [STBKeepAliveQuartzScheduler_Worker-4] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STARTED.
2009-03-17 18:55:00,025 [STBKeepAliveQuartzScheduler_Worker-4] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-17 18:55:00,285 [33] INFO STBKeepAlive.Service [(null)] - EXECUTE CMD: Name=[Button - OK] Delay=[100] RepeatCount=[1]
2009-03-17 18:55:00,285 [33] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STOPPED.
2009-03-17 21:55:03,443 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-17 21:55:03,453 [STBKeepAliveQuartzScheduler_Worker-5] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-17 21:55:03,453 [STBKeepAliveQuartzScheduler_Worker-5] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 09:55 PM]
2009-03-17 21:55:03,453 [STBKeepAliveQuartzScheduler_Worker-5] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STARTED.
2009-03-17 21:55:03,453 [STBKeepAliveQuartzScheduler_Worker-5] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-17 21:55:03,633 [34] INFO STBKeepAlive.Service [(null)] - EXECUTE CMD: Name=[Button - OK] Delay=[100] RepeatCount=[1]
2009-03-17 21:55:03,633 [34] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STOPPED.
2009-03-18 00:55:00,070 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-18 00:55:00,070 [STBKeepAliveQuartzScheduler_Worker-1] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-18 00:55:00,070 [STBKeepAliveQuartzScheduler_Worker-1] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 12:55 AM]
2009-03-18 00:55:00,070 [STBKeepAliveQuartzScheduler_Worker-1] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STARTED.
2009-03-18 00:55:00,070 [STBKeepAliveQuartzScheduler_Worker-1] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-18 03:55:00,026 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-18 03:55:00,026 [STBKeepAliveQuartzScheduler_Worker-2] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-18 03:55:00,026 [STBKeepAliveQuartzScheduler_Worker-2] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 03:55 AM]
2009-03-18 03:55:00,026 [STBKeepAliveQuartzScheduler_Worker-2] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-18 06:55:00,026 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-18 06:55:00,026 [STBKeepAliveQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-18 06:55:00,026 [STBKeepAliveQuartzScheduler_Worker-3] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 06:55 AM]
2009-03-18 06:55:00,026 [STBKeepAliveQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-18 09:55:00,047 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-18 09:55:00,047 [STBKeepAliveQuartzScheduler_Worker-4] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-18 09:55:00,047 [STBKeepAliveQuartzScheduler_Worker-4] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 09:55 AM]
2009-03-18 09:55:00,047 [STBKeepAliveQuartzScheduler_Worker-4] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction

I had to kill the service through the task manager. When I re-started in console mode I got this:

[2009-03-20 22:02:51,799] (DEBUG) START SERVICE
[2009-03-20 22:02:51,849] (INFO ) STBKeepAlive version: 1.0.2.0
[2009-03-20 22:02:52,020] (INFO ) Initialized Scheduler Signaller of type: Quart
z.Core.SchedulerSignalerImpl
[2009-03-20 22:02:52,020] (INFO ) Quartz Scheduler v.1.0.0.2 created.
[2009-03-20 22:02:52,020] (INFO ) RAMJobStore initialized.
[2009-03-20 22:02:52,020] (INFO ) Quartz scheduler 'STBKeepAliveQuartzScheduler'
initialized
[2009-03-20 22:02:52,030] (INFO ) Quartz scheduler version: 1.0.0.2
[2009-03-20 22:02:52,110] (FATAL) STBKeepAlive encountered a fatal exception in
'STBKeepAlive::Program::Main()'
System.ApplicationException: Unable to connect to USB-UIRT device! Please ensure
device is connected to the computer
at UsbUirt.Controller.OpenDriver()
at UsbUirt.Controller..ctor()
at STBKeepAlive.Service.StartService()
[2009-03-20 22:02:52,520] (DEBUG) STOPPING SERVICE

After stopping Sage, the STBKeep live started fine. So I restarted Sage. However, Sage would NOT tune the STB. Stopping STBKeep live and restarted sage restored sages tuning capibility. So it would appear somehow the driver has an issue.

I'm going to re-boot and verify that the symptom goes away. Then I am going to move to a non-local system account for both. BTW I did try this as well to get the sympton to go away - it did not. I am assuming a re-boot of the server will fix it - if not I'll post back quickly.

Any ideas?

-Stan

[shodge]

Again win2K3...
If I run in the console mode [both Sage and STBKeepAlive] they trade having control of USBIRT. The first on to starts owns it.

If I run both as a SYSTEM task they both work for about 3 days untill STBKeepalive is unable to run the key stroke...
2009-03-25 03:55:00,554 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-25 03:55:00,554 [STBKeepAliveQuartzScheduler_Worker-5] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-25 03:55:00,554 [STBKeepAliveQuartzScheduler_Worker-5] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 03:55 AM]
2009-03-25 03:55:00,554 [STBKeepAliveQuartzScheduler_Worker-5] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STARTED.
2009-03-25 03:55:00,554 [STBKeepAliveQuartzScheduler_Worker-5] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-25 03:55:00,714 [34] INFO STBKeepAlive.Service [(null)] - EXECUTE CMD: Name=[Button - OK] Delay=[100] RepeatCount=[1]
2009-03-25 03:55:00,714 [34] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STOPPED.
2009-03-25 06:55:00,023 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-25 06:55:00,023 [STBKeepAliveQuartzScheduler_Worker-1] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-25 06:55:00,023 [STBKeepAliveQuartzScheduler_Worker-1] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 06:55 AM]
2009-03-25 06:55:00,023 [STBKeepAliveQuartzScheduler_Worker-1] INFO STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STARTED.
2009-03-25 06:55:00,023 [STBKeepAliveQuartzScheduler_Worker-1] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-25 09:55:00,022 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-25 09:55:00,022 [STBKeepAliveQuartzScheduler_Worker-2] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-25 09:55:00,022 [STBKeepAliveQuartzScheduler_Worker-2] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 09:55 AM]
2009-03-25 09:55:00,022 [STBKeepAliveQuartzScheduler_Worker-2] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction
2009-03-25 12:55:00,022 [STBKeepAliveQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Simpl.SimpleJobFactory [(null)] - Producing instance of Job 'IRJobs.Uverse STB Wake Up', class=STBKeepAlive.IREventJob
2009-03-25 12:55:00,022 [STBKeepAliveQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job IRJobs.Uverse STB Wake Up
2009-03-25 12:55:00,022 [STBKeepAliveQuartzScheduler_Worker-3] INFO STBKeepAlive.Service [(null)] - TRIGGER EXECUTE: [Uverse STB Wake Up-Daily @ 12:55 PM]
2009-03-25 12:55:00,022 [STBKeepAliveQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction

I'm going to try administrator as a USER for both to see if that works. I am not holding any hope it will. Any other ideas?

-Stan

[shadeblue.com]

Hi Stan,

I have seen some random issues like this in my system as well. I am not experiencing it at the same frequency, but about once a month it may lock up. I typically reboot my SageTV server once every week or two so maybe that is why I see less lock ups.

Stéphane warned me of getting into this situation here:
http://forums.sagetv.com/forums/show...8&postcount=11

But since it seemed to be working at first, I just continued with my program running independent from the SageTV process.

After thinking on the subject for some time and becoming more familiar with the SageTV API, I think I know another method to accomplish this task but that may mean rewriting the software and possible making it a SageTV plugin rather than an independent NT service.

Please let us know if your alternate configuration attempts provide a successful workaround, I would much prefer to find a working solution than a rewrite :-)

Thanks,
SB

[shodge]

Changed both to .\administrator account. Nothing higher security wise on the server. Its been running for 3 days. It is at the point now I would expect it to fail based upon experience. We will see what happens over the next day's events.

Since I am not using Sage Server as a client, might it be possible to take one of the unused keys and assign a IR command through USBIRT it? Then we could use sendevent through the windows scheduler to do the scheduleing....

Just some thoughts... I really like your program if I could get it to work consistantly. Bouncing the server every week is not an option as there are several other apps on the system which would not be very happy.... Do you have to do this because of your HD-PVR's? I'thinking seriously about getting one...

-Stan

Will post status in 1 day.

[shadeblue.com]

Originally Posted by shodge

Just some thoughts... I really like your program if I could get it to work consistantly. Bouncing the server every week is not an option as there are several other apps on the system which would not be very happy.... Do you have to do this because of your HD-PVR's? I'thinking seriously about getting one...

-Stan

Will post status in 1 day.

In part, yes, I have had to reboot because sometimes my HD-PVRs would lock up. I have the some of the earliest units so that may be one reason they are not so stable. I have some replacement units on the way and I am hoping they will take care of these stability issues.

The HD-PVRs can be a pain, but if you want to record HD from a STB and do not use a R5000, then this is the only option. Even with the troubles I have had, I am still happy to have them.

Cheers, SB

[shodge]

Ok after 25 events (this is consistant over 3 failures now [3 days +1]) it stops sending the 'OK'. It looks like it is going to then does not do it. If I go to the service panel to stop it - it will not susceed in performing a stop. I have to to open task manager and kill the task. Then it will re-start again....

Do you have just a simple program which will open usbirt and send the 'OK' then close usbirt? If so I can try and use windows scheduler to run it.

-Stan

[shadeblue.com]

Originally Posted by shodge

Ok after 25 events (this is consistant over 3 failures now [3 days +1]) it stops sending the 'OK'. It looks like it is going to then does not do it. If I go to the service panel to stop it - it will not susceed in performing a stop. I have to to open task manager and kill the task. Then it will re-start again....

Do you have just a simple program which will open usbirt and send the 'OK' then close usbirt? If so I can try and use windows scheduler to run it.

-Stan

Hi Stan, I have added a command line option to the existing program that allows you to load up the program and execute a single job by name, then terminate.

Just replace the current STBKeepAlive.EXE in the program directory with the updated version in the attached ZIP file.

Next, use the syntax:

STBKeepAlive.exe -run "Uverse STB Wake Up"

where "Uverse STB Wake Up" is the name of the job you want to run.


If this works for you, please let me know, because I could refactor the scheduler part of this program to shell out to a separate send IR process and then users would not have to use the windows task scheduler to schedule the jobs.

Thanks! SB

[shodge]

Thanks SB. I will not get to install it until 3/31 PM but I will try it and advise.

-Stan

[shodge]

SB,

Installed new version. Added event in schedular for 12:55AM repeating every 3 hrs for 22 hrs. The event occurs daily. So far - 7 wakups. I'll post again on Friday if its still working. So far so good....

-Stan

[shodge]

26 events past.

All looks good. No issues. The log is clean. Sage is up - along with the box.

I Just ordered my HD-PVR box.

-Stan

[shadeblue.com]

Originally Posted by shodge

26 events past.

All looks good. No issues. The log is clean. Sage is up - along with the box.

I Just ordered my HD-PVR box.

-Stan

Hi Stan,

I went ahead and converted the core program to shell out to a separate executable to transmit the IR command via USBUIRT. The core scheduler now has no reference to the USBUIRT driver. I am running it here for a week or so before releasing it to the main downloads section, but if you want to try it out, feel free to download it from this post.

Make sure to backup your existing config file, installing the updated version will force you to uninstall the existing version which may delete your existing config file.

Let me know if you run into any trouble or bugs!

Thanks SB.


EDIT:

Version 1.0.3 is now released,
You can get it from the DOWNLOADS page

[shodge]

SB,

I DL'd, deinstalled, reinstalled. I do not see a version difference (1.0.3, 1.0.0.2). I still cannot run in the console [same result with the previous version]. If Sage is running the console will not send the event to the IRBLASTER. I even created a dos box in the same user context as Sage - no go...

So I am running as a service. Running as the default 'System' level. I will report more tomarrow.

-Stan

[shadeblue.com]

Originally Posted by shodge

SB,

I DL'd, deinstalled, reinstalled. I do not see a version difference (1.0.3, 1.0.0.2). I still cannot run in the console [same result with the previous version]. If Sage is running the console will not send the event to the IRBLASTER. I even created a dos box in the same user context as Sage - no go...

So I am running as a service. Running as the default 'System' level. I will report more tomarrow.

-Stan

Hi Stan,

When I first deployed this to my SageTV server, I had some similar issues where in the console mode, it was not sending the IR. I rebooted my server and that seemed to clear it up for me. What should happen in version 1.0.3 is when the scheduled event time occurs, the service should call out to a new EXE (STBKeepAlive.Transmit.exe) to send the IR command out to the USBUIRT. My thought is that moving all the USBUIRT logic out to a separate process should interfere less with Sage since there is not an active program holding some reference to the USBUIRT driver. Conflicts could still occur if both SageTV and STBKeepAlive tried to access the URBUIRT at the same time. So I schedule all my STBKeepAlive event to occur at odd times that do not likely conflict with channel tuning.

My STB's are still up today. I have been running the new version since my last post so it seems to be working here on my end. Time will tell if it improves the lock up issues, but you were getting them much more frequently than I ever was so your results may be a better indicator.

Thanks - SB

[shodge]

Well as a service, its running. So far 7 events and yes I can tell that its the new version. It shows the IR data when transmitting. Sage is still in control as well. So my system always died at event 25 so we should know something Friday night. I'll repost then.

So far so good.... and thanks for the effort....
-Stan

[shodge]

Well I am at 32 events straight. No issues. Box is still up. I think we are ready for prine time. Way to go!!!!

I just got my HDPVR as well. Almost ready to replace my old server with the new one.

Thanks again for all you hard work!

-Stan

[shadeblue.com]

Originally Posted by shodge

Well I am at 32 events straight. No issues. Box is still up. I think we are ready for prine time. Way to go!!!!

I just got my HDPVR as well. Almost ready to replace my old server with the new one.

Thanks again for all you hard work!

-Stan

Hi Stan,

If you don't mind, I will hit you up again for a status update in about a week. I like to let the software run stable for a couple of weeks before publishing a new version for all users. Mine here has also been running without any lock-ups, so I am really hopeful that this change fixes this issue for good.

Thanks for your help with this, your input and feedback has been a big help!

Good luck with the HD-PVR and new server. I have has 2 of these units and they have run stable about 90% of the time. I just received two new replacement units that are supposed to address the locks ups and some AC3 audio issues I was having. What server OS are you planning on going with? I want to rebuild mine but am waiting for Window7 release.

Cheers!
SB

[shodge]

I just made the server switch. I have a developers copy of Server2K3. I really like it and it is very stable. I just got the PVR to work on U-Verse. I see that the latest driver beta is to address the optical input. I'm going to install that tonight. I do not have STBKeepalive re-hosted yet. Sometime this week I think. I'll let you know when I start the next timer.

-Stan

[shodge]

Well, I have my PVR running with U-Verse for a full week - no lockups and no box turning off. Nothing in the error log. All looks great on my end! Once again - thanks for the great program!

-Stan

[shadeblue.com]

Originally Posted by shodge

Well, I have my PVR running with U-Verse for a full week - no lockups and no box turning off. Nothing in the error log. All looks great on my end! Once again - thanks for the great program!

-Stan

Hi Stan, Thanks for the update! Same here all running fine with no lock-ups. I'll try to post the release this week.

Cheers - SB