Utility: STBKeepAlive - scheduled commands for USB-UIRT

[shadeblue.com]

Originally Posted by bmellesmoen

STBKeepAlive Install (1.0.5) getting the following error when installing. Is there a resolution to this?

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2869.

Thanks, Bob

Hi Bob, can you please try downloading from this link:
http://download.shadeblue.com/stbkee...%20Install.exe

Maybe something got corrupted when I uploaded to the forums.

Thanks,
SB

[korben_dallas]

Shadeblue,

This is a very neat-looking add-on. I don't need it right now, but may in the future.

You should post an announcement about the new version in the Customization Announcements forum section.

[AFinch]

I'm getting an error on Windows 7 x64 when I try to use this with my U-Verse VIP1200 STB. The USB-UIRT looks fine in Device Manager, but when I run STBKeepAlive in Console mode and hit F3, I get an error saying the USB-UIRT STPKeepAlive has stopped working and the console tells me that the System Type Initialization failed and says it can't read the driver.

Help?

[dvd_maniac]

Will this work with Win7 64Bit?

[AFinch]

Turns out this doesn't work with Windows x64.

[dvd_maniac]

Does anybody have a remedy for 64 bit?

[timg11]

Shadeblue,

I've seen some failures of STBkeepalive since I have moved to Window 7 32-bit. I'm using 1.0.5 with exe dated 11/11/2009.

I'm seeing messages like this in the log:

2010-08-08 14:57:00,191 [14] ERROR STBKeepAlive.Service [(null)] - IR COMMAND TRANSMISSION FAILED @ 2:57:00 PM
2010-08-08 14:57:00,192 [14] INFO  STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STOPPED.
2010-08-08 15:58:15,343 [13] INFO  STBKeepAlive.Service [(null)] - SYSTEM POWER EVENT: 'ResumeAutomatic'; EXECUTE JOB: 8300HDC STB Wake Up
2010-08-08 15:58:15,343 [13] INFO  STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STARTED.
2010-08-08 15:58:15,432 [13] INFO  STBKeepAlive.Service [(null)] - SYSTEM POWER EVENT: 'ResumeSuspend'; EXECUTE JOB: 8300HDC STB Wake Up
2010-08-08 15:58:15,444 [13] INFO  STBKeepAlive.Service [(null)] - EXECUTE CMD: Name=[Button - Select] Delay=[100] RepeatCount=[2]
2010-08-08 15:58:15,444 [13] INFO  STBKeepAlive.Service [(null)] - EXECUTE PROGRAM: [STBKeepAlive.Transmit.exe]
2010-08-08 15:58:15,570 [13] ERROR STBKeepAlive.Service [(null)] - [STBKeepAlive.Transmit] TRANSMISSION TO USBUIRT FAILED.
[STBKeepAlive.Transmit] ERROR: 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.Transmit.Program.Main(String[] args)

The USB-UIRT is working normally in SageTV both for receiving IR commands and IR blasting to change channels on the cable box.

What could cause these errors? How do I debug it further?

[dvd_maniac]

Has anybody gotten this to work using WIN7 64bit yet?

[timg11]

Originally Posted by dvd_maniac

Has anybody gotten this to work using WIN7 64bit yet?

dvd_maniac, I don't run a 64 bit OS, but Jon at USB-UIRT support has been helpful and responsive. He provided me updates that fixed the standby-wake issue and the USB-UIRT sharing issue. (see this thread). I suggest you contact him to see what he has for 64 bit drivers.

[dvd_maniac]

Looks like Sage will make this problem go away in the next Beta.
I sent a request to add a delay between the prefix code and the channel change and below is the email response they sent me.
WHAT A GREAT PRODUCT AND SUPPORT TEAM!!!

irtune_prefix_extra_delay

which you can set to whatever kind of delay you want to be sent after the prefix command (but you will need to have a prefix command setup for it to work). The value is in milliseconds and will default to zero for no delay.
We'll probably add a UI option for it later as well, but for now you'll need to edit the Sage.properties file for it. It'll be in 7.0.16.

[Savage1701]

I installed the STB Keep Alive.

I can learn my 612 "Select" code easily and test transmit it and it works from the learn IR module.

I don't understand how to make the console or the service transmit it, though. It just keeps sending the default U-Verse code.

Where is the config file or how do I edit it? I have my Dish "Select" code that needs a repeat rate of 10.

I don't know what file to alter, and I can't find the one everyone is talking about. I can see the console is sending the U-Verse code only, not mine. But, again, the IR learn module sends it successfully.

Thanks for any help.

[shadeblue.com]

Originally Posted by Savage1701

I installed the STB Keep Alive.

I can learn my 612 "Select" code easily and test transmit it and it works from the learn IR module.

I don't understand how to make the console or the service transmit it, though. It just keeps sending the default U-Verse code.

Where is the config file or how do I edit it? I have my Dish "Select" code that needs a repeat rate of 10.

I don't know what file to alter, and I can't find the one everyone is talking about. I can see the console is sending the U-Verse code only, not mine. But, again, the IR learn module sends it successfully.

Thanks for any help.

Hi Savage,

The Learn utility just provides the RAW data for the IR command ... it does not save it as part of the configuration data .. that step is manual. So after learning, copy the IR command data to the clipboard.

Next, you will need to navigate to the program installation folder ... typically located here : "C:\Program Files\shadeBlue\STBKeepAlive" . In this folder you should find the file "STBKeepAlive.exe.config". Make sure the STBKeepAlive service is stopped and then edit this file with a text editor software like Notepad. (or Notepad++ my favorite free text editor). In this file you will see several job XML nodes, only the first one named "Uverse STB Wake Up" is active , the others are commented out and just provided as an example. Inside this JOB, there is a <Command> element with the "IF" attribute. Replace the IR="xxxx xxxx ...x" with the IR command data that you learned and copied into your clipboard. Save this file and then start STBKeepAlive. (You can also rename the JOB with a more friendly name based on your equipment if you want to.)

Good Luck!
SB

[Savage1701]

Originally Posted by shadeblue.com

Hi Savage,

The Learn utility just provides the RAW data for the IR command ... it does not save it as part of the configuration data .. that step is manual. So after learning, copy the IR command data to the clipboard.

Next, you will need to navigate to the program installation folder ... typically located here : "C:\Program Files\shadeBlue\STBKeepAlive" . In this folder you should find the file "STBKeepAlive.exe.config". Make sure the STBKeepAlive service is stopped and then edit this file with a text editor software like Notepad. (or Notepad++ my favorite free text editor). In this file you will see several job XML nodes, only the first one named "Uverse STB Wake Up" is active , the others are commented out and just provided as an example. Inside this JOB, there is a <Command> element with the "IF" attribute. Replace the IR="xxxx xxxx ...x" with the IR command data that you learned and copied into your clipboard. Save this file and then start STBKeepAlive. (You can also rename the JOB with a more friendly name based on your equipment if you want to.)

Good Luck!
SB

Thank you; I knew I had to copy the raw data from the IR Learn, but I was not sure where to paste it. Now it looks like, when running under the DOS box, it is sending the correct code as the Dish channel info banner pops up. I must have failed to stop/restart the service correctly.

I'll see what happens tonight/early tomorrow morning when Dish does its update thing and KeepAlive is running as a service. I have shutdown disabled, but I'm guessing it's going to show a sleep screen at it's 3:00 AM update. Hopefully this will prevent that. Obviously, your program works very well.

Thanks again for taking the time to help me.

FWIW, I changed the repeat rate to "10" from "1".

[shadeblue.com]

Originally Posted by Savage1701

FWIW, I changed the repeat rate to "10" from "1".

You are welcome. As for the "repeat rate", I have not done any testing with this settings, this value gets directly passed into the USB-UIRT driver. If you have any problems getting it to transmit ten times, you can also try to to simply copy the IR command node for ten instances .. see example:

<Commands>
        <Command Name="Button - OK #1"
                 IR="0000 0070 0000 0024 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C87 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C86"
                 RepeatCount="1" />

        <Command Name="Button - OK #2"
                 IR="0000 0070 0000 0024 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C87 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C86"
                 RepeatCount="1" />

        <Command Name="Button - OK #3"
                 IR="0000 0070 0000 0024 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C87 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C86"
                 RepeatCount="1" />

        <Command Name="Button - OK #4"
                 IR="0000 0070 0000 0024 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C87 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C86"
                 RepeatCount="1" />

        <Command Name="Button - OK #5"
                 IR="0000 0070 0000 0024 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C87 000F 000B 0006 000B 0006 0017 0006 000B 0006 001D 0006 0011 0006 000B 0006 000B 0006 000B 0006 000B 0006 0017 0006 0011 0006 0017 0006 0011 0006 0011 0006 001D 0006 000B 0006 0C86"
                 RepeatCount="1" />

</Commands>

[bialio]

I have Sage set to use my USB-UIRT to change channels on my motorola set top box - will this utility work along side that to let me do a "power cycle" each night?

IT looks like the commands necessary for discreet power on / power off is a combination of commands - 'Info' + 'Power' + 'Power' for ON, 'Info' + 'Power' for OFF.....

btl.

[shadeblue.com]

Originally Posted by bialio

I have Sage set to use my USB-UIRT to change channels on my motorola set top box - will this utility work along side that to let me do a "power cycle" each night?

IT looks like the commands necessary for discreet power on / power off is a combination of commands - 'Info' + 'Power' + 'Power' for ON, 'Info' + 'Power' for OFF.....

btl.

Yes it will work alongside SageTV.

For sequential IR commands (Info+Power+Power), you will have to include multiple <Command> nodes under the <Commands> section.

If you need a delay between the POWER OFF and the POWER ON, you may have to create two scheduled "Jobs" with time "Triggers" that effectively create the delay.

[bialio]

I get the error below when I the command tries to run - seems like it can't connect to the USB-UIRT. What am I doing wrong?

[2011-02-09 16:15:00,150] (INFO ) EXECUTE CMD: Name=[Button - Info] Delay=[100]
RepeatCount=[1]
[2011-02-09 16:15:00,150] (INFO ) EXECUTE PROGRAM: [STBKeepAlive.Transmit.exe]
[2011-02-09 16:15:00,259] (ERROR) [STBKeepAlive.Transmit] TRANSMISSION TO USBUIR
T FAILED.
[STBKeepAlive.Transmit] ERROR: 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.Transmit.Program.Main(String[] args)

[2011-02-09 16:15:00,290] (ERROR) IR COMMAND TRANSMISSION FAILED @ 4:15:00 PM
[2011-02-09 16:15:00,290] (INFO ) IR PROCESSING TIMER will process the next comm
and in [100] ms.
[2011-02-09 16:15:00,400] (INFO ) EXECUTE CMD: Name=[Button - Power] Delay=[100]
 RepeatCount=[1]
[2011-02-09 16:15:00,400] (INFO ) EXECUTE PROGRAM: [STBKeepAlive.Transmit.exe]
[2011-02-09 16:15:00,462] (ERROR) [STBKeepAlive.Transmit] TRANSMISSION TO USBUIR
T FAILED.
[STBKeepAlive.Transmit] ERROR: 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.Transmit.Program.Main(String[] args)

[2011-02-09 16:15:00,462] (ERROR) IR COMMAND TRANSMISSION FAILED @ 4:15:00 PM
[2011-02-09 16:15:00,462] (INFO ) IR PROCESSING TIMER STOPPED.

[bialio]

To answer my own question - when STBKeepAlive is running in Service mode it can share the USB-UIRT driver with SageTV IN SERVICE MODE. When STBKeepAlive is in console mode, it can share with SageTV NOT in service mode.

In other words, either both or neither has to be in Service mode for it to work.

Thanks for the awesome tool shadeblue.
btl.

[bialio]

OK - now that I'm working with an x64 system, I'm running into some issues:

2011-02-26 12:22:00,398 [4] ERROR STBKeepAlive.Service [(null)] - [STBKeepAlive.Transmit] TRANSMISSION TO USBUIRT FAILED.
[STBKeepAlive.Transmit] ERROR: System.TypeInitializationException: The type initializer for 'UsbUirt.Controller' threw an exception. ---> System.ApplicationException: Unable to read UsbUirt driver version ---> System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
   at UsbUirt.Controller.UUIRTGetDrvInfo(UInt32& drvVersion)
   at UsbUirt.Controller..cctor()
   --- End of inner exception stack trace ---
   at UsbUirt.Controller..cctor()
   --- End of inner exception stack trace ---
   at UsbUirt.Controller..ctor()
   at STBKeepAlive.Transmit.Program.Main(String[] args)

Any ideas?

[bialio]

OK - I haven't had any luck getting this working on x64 windows. HOWEVER.

I have found a way to get things working more or less.

There is a command line utility for USB-UIRT that will send commands called 'uutx.exe'. I downloaded it here.

So with that, I created a couple of batch files that fire off the commands I had STBKeepAlive running :

uutx.exe "0034 0022 0953 ...."

That's not the real code, but the same code you would use in the STBKeepAlive config file works with uutx.exe.

Then, the good old Task Scheduler in Windows has a few tasks defined that fire off at the required times. Note that since I run Sage in Service mode, to get it to work I had to specify in the task to run the batch file as "NT Authority\SYSTEM" user. While testing I took Sage out of service mode, and it worked fine as my normal login user.

So now I'm back in business!

btl.