home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Input / Output interfaces
Remotes
Blaster Setup Question
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1180940" data-attributes="member: 82144"><p>Okay, I understand. In that context a "time out" generally means that IRSS is receiving zero or invalid input from the receiver.</p><p></p><p></p><p>These are all sensible things to try/check. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up (y)" loading="lazy" data-shortname="(y)" /></p><p></p><p>For learning, my understanding is that you should only have to press the remote button once. There should be no need to hold it down longer than you normally would, and no need to repeatedly tap/press it. Also, the remote needs to be quite close to the receiver. Between 2 (0.75") and 5 cm (2") is the guideline from Microsoft, though this may vary a little (maybe up to 10cm/4"???) depending on the actual receiver vendor/design. 1" may not be close enough; 36" is certainly much too far away.</p><p></p><p></p><p>It means nothing. Windows 10 should work as well as any other version.</p><p></p><p></p><p>I have to admit that I've personally never used IRSS or a blaster, so it's a little tricky when things go wrong like this. However I do have some recommendations.</p><p></p><p>1. Attempt to use the process/config that was successful in the past.</p><p>In your previous reply you said you were successful in learning 0 and 1 before deciding to have dinner. From this we can deduce that the process/config you were using at that time - 10 second time-out, receiver distance, button press pattern etc. - must have been okay, and IRSS <em>can</em> learn. I'd recommend you stick to that without too much variation.</p><p></p><p>2. Ensure that only IRSS is using the transceiver.</p><p>Only one application can use/control the transceiver at any given time. You want that application to be IRSS. Any other process that attempts to use the transceiver for either blasting or receiving remote control input may mess up IRSS and the learning process.</p><p></p><p>3. Reboot.</p><p>It's clichéd I know, but it can be effective. When all else fails, try rebooting the PC.</p><p></p><p>4. Provide log files.</p><p>Log files will give me the detail I need to understand exactly what's going on.</p><p>First we need to make sure the IRSS and TV Server log levels are set to debug so that I get the required level of detail:</p><ul> <li data-xf-list-type="ul">Open IRSS Input Service Configuration.</li> <li data-xf-list-type="ul">Click "advanced" (top left).</li> <li data-xf-list-type="ul">Set log level to debug.</li> <li data-xf-list-type="ul">Click OK.</li> <li data-xf-list-type="ul">Restart the IRSS service.</li> <li data-xf-list-type="ul">Close IRSS Input Service Configuration and open TV Server Configuration.</li> <li data-xf-list-type="ul">Go to the "general" section.</li> <li data-xf-list-type="ul">Set log level to debug.</li> <li data-xf-list-type="ul">Go to the "manual control" section.</li> <li data-xf-list-type="ul">Click "stop service"... then "start service".</li> </ul><p>Now try learning buttons again at least 5 times so I can clearly see the situation/problem.</p><p></p><p>Finally, collect the log files:</p><ul> <li data-xf-list-type="ul">Open Windows Explorer.</li> <li data-xf-list-type="ul">Copy and paste <strong>c:\ProgramData\Team MediaPortal\MediaPortal TV Server\log</strong> into the address bar/field (up the top).</li> <li data-xf-list-type="ul">Compress/zip all the files in that folder.<br /> </li> <li data-xf-list-type="ul">Copy and paste <strong>c:\ProgramData\IR Server Suite\Logs</strong> into the address bar/field.<br /> </li> <li data-xf-list-type="ul">Compress/zip all the files in that folder.</li> </ul><p>You can attach the two zip files to a forum post using the "upload a file" button/function.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1180940, member: 82144"] Okay, I understand. In that context a "time out" generally means that IRSS is receiving zero or invalid input from the receiver. These are all sensible things to try/check. (y) For learning, my understanding is that you should only have to press the remote button once. There should be no need to hold it down longer than you normally would, and no need to repeatedly tap/press it. Also, the remote needs to be quite close to the receiver. Between 2 (0.75") and 5 cm (2") is the guideline from Microsoft, though this may vary a little (maybe up to 10cm/4"???) depending on the actual receiver vendor/design. 1" may not be close enough; 36" is certainly much too far away. It means nothing. Windows 10 should work as well as any other version. I have to admit that I've personally never used IRSS or a blaster, so it's a little tricky when things go wrong like this. However I do have some recommendations. 1. Attempt to use the process/config that was successful in the past. In your previous reply you said you were successful in learning 0 and 1 before deciding to have dinner. From this we can deduce that the process/config you were using at that time - 10 second time-out, receiver distance, button press pattern etc. - must have been okay, and IRSS [I]can[/I] learn. I'd recommend you stick to that without too much variation. 2. Ensure that only IRSS is using the transceiver. Only one application can use/control the transceiver at any given time. You want that application to be IRSS. Any other process that attempts to use the transceiver for either blasting or receiving remote control input may mess up IRSS and the learning process. 3. Reboot. It's clichéd I know, but it can be effective. When all else fails, try rebooting the PC. 4. Provide log files. Log files will give me the detail I need to understand exactly what's going on. First we need to make sure the IRSS and TV Server log levels are set to debug so that I get the required level of detail: [LIST] [*]Open IRSS Input Service Configuration. [*]Click "advanced" (top left). [*]Set log level to debug. [*]Click OK. [*]Restart the IRSS service. [*]Close IRSS Input Service Configuration and open TV Server Configuration. [*]Go to the "general" section. [*]Set log level to debug. [*]Go to the "manual control" section. [*]Click "stop service"... then "start service". [/LIST] Now try learning buttons again at least 5 times so I can clearly see the situation/problem. Finally, collect the log files: [LIST] [*]Open Windows Explorer. [*]Copy and paste [B]c:\ProgramData\Team MediaPortal\MediaPortal TV Server\log[/B] into the address bar/field (up the top). [*]Compress/zip all the files in that folder. [*]Copy and paste [B]c:\ProgramData\IR Server Suite\Logs[/B] into the address bar/field. [*]Compress/zip all the files in that folder. [/LIST] You can attach the two zip files to a forum post using the "upload a file" button/function. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Input / Output interfaces
Remotes
Blaster Setup Question
Contact us
RSS
Top
Bottom
