News:

Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Venom986

#31
Users / Re: USB-UIRT Learning
February 17, 2008, 10:09:51 PM
Excellent, glad it worked out for you!  I seem to have things to the point now where I can make use of both my satellite boxes (one attached to the core, one to my MD int he living room) from either the core or MD (PiP working too).
#32
Users / Viewing Satellite TV on another MD
February 16, 2008, 05:15:35 AM
I don't seem to be capable of formulating decent search criteria for this quesiton, as I keep drawing a blank.  I have one PVR-150 installed on my core and the other on my MD.  As of yet, I haven't been able to get things working such that I can watch TV through the satellite box attached to my Core through its PVR on my MD in the living room and vice versa.  I suppose tis not a huge deal atm, but I thought this was one of the main features and its something I will definately want to know how to get to work when I add another MD.
#34
Users / Re: USB-UIRT Learning
February 15, 2008, 04:39:21 PM
In the web admin:

*Go to Advanced > Configuration > Device Templates
*In the "Do you know the ID of the device template" box enter 275 (assuming you are using the SAT_3100 template) and click Pick Device Template
*In the template page that opens, scroll down to Device Data section
*You need to copy and paste your lircd.conf file into the text area for Default Value (I first cut the existing out and saved it to a file just in case, then pasted the other one in).
*Save the changes to the template and then force a reload of the router.

Assuming you've also followed the other instructions for creating a channel changing script and adding a remote that uses that device template to your media director it should work.
#35
Also of possible interest, this is the channel changing script that I found for working with lirc


#!/bin/sh
REMOTE_NAME=DISH_1  # Define my remote name here
for digit in $(echo $1 | sed -e 's/./& /g'); do # Accept input from MythTV
irsend --device=/dev/lircd1 SEND_ONCE $REMOTE_NAME $digit # Send the output to Lirc
sleep 0.4 # note, you may have to tweak the interdigit delay up a bit # Wait for next digit
done # got last digit from MythTV
irsend --device=/dev/lircd1 SEND_ONCE $REMOTE_NAME select # Add a select to speed up channel changing.
sleep 0.4
irsend --device=/dev/lircd1 SEND_ONCE $REMOTE_NAME cancel # Get the Dish OSD off the screen, it annoys me and I don't want it on my recordings.
#36
actually, for that matter, you could just grab it directly off the link i provided to the lirc sourceforge page in my first post.
#37
#38
Developers / Device Template for SAT_3100 (LIRC Remote)
February 15, 2008, 02:20:25 PM
This device template already existed in my 0710b3 DVD install.  I have made some modifications to it that I consider substantial improvements.  I'm not sure if my local changes sync back or not.  Here is the lirc.conf file I changed to. It is not my original work, but I got it from http://lirc.sourceforge.net/remotes/dishnet/Dish_Network.  This lircd.conf file supports ALL 16 remote addresses on the 3.1IR remote that comes with MANY DishNetwork, Echostar and ExpressVu satellite receivers.

Or at least, here it would be if it didn't exceed the character limit and if the website would let me upload a file (get the error that it can't access the upload path).
#39
Users / Re: Changing Channels On MythTV
February 15, 2008, 02:11:43 PM
You will have to run mythsetup (on your orbiter go to Computing>MythSetup).  From there go to your Input Sources, select the appropriate one and in its config point it at a suitable channel changing script.

Now, LinuxMCE provides one by default in /usr/pluto/bin/TuneToChannel.sh, however I have had trouble with that these past couple of days (look at my USB-UIRT learning thread).  With a couple of modifications to the script itself to remove DOS carriage returns I could get it to blast channel change requests, but every button press was repeated 4 times, making it ineffective.

Sadly, I can't help much further with getting the channel changing script to work with the USB-UIRT.  The script just calls SendMessage which is a binary and I'm not familiar with how it works.  As yet, no gurus have responded to my thread with further info.  I was hoping I could pass a parameter to it from the channel change script to have it not repeat button "presses", but no luck so far.

In the interim, I returned to working on getting lirc to control the irblaster built into my MCE receiver; and I have been successful.  I will post with links to wiki pages once I get them updated.
#40
Users / Re: USB-UIRT Learning
February 15, 2008, 02:06:49 PM
I went back to using the receiver/transmitter that came with the PVR-150, and setting up lirc for it.  I have learned a lot, and have it working.  I will be updating a bunch of wiki pages and forum posts with the results and instructions for others.

I have updated the SAT_3100 remote device template (does this sync back to the servers?) with the following lircd.conf: http://lirc.sourceforge.net/remotes/dishnet/Dish_Network which is an EXCELLENT piece of work and contains entries for all 16 remote addresses supported by the slew of receivers from DishNetwork, Echostar, Expressvu (the 3.1IR, which has the blue buttons).  Having that entered in the device template, and copying a very simple channel change script I now have the MCE IRBlaster changing channels on my ExpressVu 4100 receiver.  I even changed the remote address to 6 and its working (I'll be using a second one after I get my config finalized using just one).

oh happy happy day!
#41
Users / Re: USB-UIRT Learning
February 15, 2008, 07:04:39 AM
Looking at the USB-UIRT log I see the following differences (trying to send the key '3').

If I use the Test Code button in the A/V properties page for the satellite box, the log shows


10      02/15/08 1:01:20.798            Receive string: MESSAGE 451            <0x42003950>
10      02/15/08 1:01:20.798            Received MESSAGE 451            0x651940 device: 54 <0x42003950>
10      02/15/08 1:01:20.799            Received Message type 1 ID 191 from 0 to 54 (device: 54) resp 0 <0x42003950>
10      02/15/08 1:01:20.799            UsbUirt Sending with repeat 1: 0000 0048 0000 0024 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 176E <0x42003950>


If I instead use the TuneToChannel.sh script:

10      02/15/08 1:02:06.042            Receive string: MESSAGE 78             <0x42003950>
10      02/15/08 1:02:06.042            Received MESSAGE 78             0x651940 device: 54 <0x42003950>
10      02/15/08 1:02:06.042            Received Message type 1 ID 187 from 0 to 57 (device: 54) resp 0 <0x42003950>
10      02/15/08 1:02:06.051            AVMessageTranslator::Translate begin <0x42003950>
10      02/15/08 1:02:06.054                Status : CMD=187, TP=0, TI=0 last input 0 last power 0 <0x42003950>
05      02/15/08 1:02:06.054            Device id 57 has no number digits parameter. Sending as is with an enter.
<0x42003950>
10      02/15/08 1:02:06.054            Sending digit 3... <0x42003950>
10      02/15/08 1:02:06.054            Sending <enter>... <0x42003950>
10      02/15/08 1:02:06.054            AVMessageTranslator::Translate begin <0x42003950>
10      02/15/08 1:02:06.054                Status : CMD=207, TP=0, TI=0 last input 0 last power 0 <0x42003950>
10      02/15/08 1:02:06.054            AVMessageTranslator::Translate end <0x42003950>
10      02/15/08 1:02:06.054            AVMessageTranslator::Translate begin <0x42003950>
10      02/15/08 1:02:06.054                Status : CMD=190, TP=0, TI=0 last input 0 last power 0 <0x42003950>
10      02/15/08 1:02:06.054            AVMessageTranslator::Translate end <0x42003950>
05      02/15/08 1:02:06.054            #### Pre-Process Queue = 2 <0x42003950>
05      02/15/08 1:02:06.068            _QueueProc Pre - 207 : 0 <0x42804950>
10      02/15/08 1:02:06.068            _QueueProc ------- 207 <0x42804950>
05      02/15/08 1:02:06.069            GSD-Sleep Pre 207 : 0 <0x42804950>
10      02/15/08 1:02:06.069            In IRBase::DispatchMessage <0x42804950>
10      02/15/08 1:02:06.069            Sending Infrared Code for dev <57> cmd <207>, channel <>, repeat <4> code <0000 0048 0000 0024 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 176E> <0x42804950>
10      02/15/08 1:02:06.069            pos 380 size 379 Checking 0000 0048 0000 0024 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 176E
for multiple codes, got: 0000 0048 0000 0024 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 176E <0x42804950>
10      02/15/08 1:02:06.069            UsbUirt Sending with repeat 4: 0000 0048 0000 0024 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 00A2 0017 00A2 0017 0062 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 176E <0x42804950>
05      02/15/08 1:02:07.264            GSD-Sleep Post 207 : 250 <0x42804950>
05      02/15/08 1:02:07.265            _QueueProc Post - 207 : 250 <0x42804950>
05      02/15/08 1:02:07.265            _QueueProc Pre - 190 : 0 <0x42804950>
10      02/15/08 1:02:07.265            _QueueProc ------- 190 <0x42804950>
05      02/15/08 1:02:07.265            GSD-Sleep Pre 190 : 0 <0x42804950>
10      02/15/08 1:02:07.265            In IRBase::DispatchMessage <0x42804950>
10      02/15/08 1:02:07.265            Sending Infrared Code for dev <57> cmd <190>, channel <>, repeat <4> code <0000 0048 0000 0046 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0164 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 1774> <0x42804950>
10      02/15/08 1:02:07.265            pos 720 size 719 Checking 0000 0048 0000 0046 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0164 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 1774
for multiple codes, got: 0000 0048 0000 0046 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0164 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 1774 <0x42804950>
10      02/15/08 1:02:07.265            UsbUirt Sending with repeat 4: 0000 0048 0000 0046 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0164 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 00A2 0017 0062 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 00A2 0017 0163 0017 1774 <0x42804950>
Return code: 139
3       02/15/08 01:02:07       54 (spawning-device)    Device died... count=8/50 dev=54


Now, ignoring for the fact that everytime it gives that device died message....the channel changing script seems to forcing a repeat of 4.  Why would it do that?  that means its going to fire 4 of each button press for the channel I request and that is, I assume, what is causing the issues here.
#42
Users / Re: USB-UIRT Learning
February 15, 2008, 06:20:41 AM
Status update.

I have the codes input into my device in the web admin.  If I hit the Test Code button there for the digit buttons, I properly get a single press of that digit registered on the receiver.

Now, I went on to trying to use /usr/pluto/bin/TuneToChannel.sh script.  Running this from the commandline I got a lot of errors.  A few things were wrong:


  • There were ^M characters terminating lines.  Someone obviously edited this in a non-text editor.  I removed the control characters in my copy.
  • It was very unclear on the wiki what you had to pass as the Source ID.  I started trying to pass /dev/video0.  It turns out this is simply the numeric source id of the Source associated with the channel in mythtv.  In my case I have one tuner card, set up one source for it and that source got id 1.
  • So, now the TuneToChannel.sh script runs, but it is sending unexpected codes (looks like repeating codes of the first digit in the channel number I ask for?)

anyone with more experience want to step in with suggestions?
#43
Users / Re: USB-UIRT Learning
February 15, 2008, 04:35:28 AM
So, I think the fresh batteries helped some, but moreso, it helped to double check that my changes to the database through the web admin tool had actually stuck as far as having moved my USB-UIRT from the MD to the core for learning codes.  Turns out it still thought it was attached to the MD so wasn't being set to learning mode when I hit new code.

I now have codes for all the pertinent buttons.  Just have to figure out how to set up to use the channel changing script in mythtv (and then see if I can swap over to using the mce transmitter now that i know the codes since i need the USB-UIRT back on the MD)
#44
Users / Re: USB-UIRT Learning
February 15, 2008, 01:33:38 AM
In case others are having issues, this looks like a promising list of helpful hints: http://www.remotecentral.com/features/irtips.htm
#45
Users / Re: USB-UIRT Learning
February 15, 2008, 01:07:33 AM
well, was within inches.  maybe the batteries are old though, i'll try new ones.  so it SHOULD work the way i described then?