PDA

View Full Version : slimp3 remote control acting up



rgduarte
2006-03-11, 02:35
Hi. I've got an early model of the first slimp3 that I've been happily using for the last couple of years. A few days ago, the slimp3 stopped responding to the remote control. Out of frustration I just sat their pressing buttons at random and it suddenly came to life - for a few minutes. Then it died again. It did this a few times but now I can't seem to get it going any longer no matter what I do.
The slimp3 works fine controlled with the web interface - absolutely no problems. I've tried replacing the batteries, cleaning the IR receiver/case, and doing a clear install. I know the remote is 'alive' because I can see light it's emitting using my video camera.
Any ideas? This is driving me nuts!
Thanks.

Mark Lanctot
2006-03-11, 08:40
Given that the IR is actually decoded in the server, I'd focus attention there. It looks like the SLIMP3 uses a file called jvc_dvd.ir in SlimServer\Server\IR\ because the file starts with these lines:


# The default mapping is that of the JVC DVD remote for the Sony
# universal remote supplied with the SLIMP3

Is this file present in your install? If not, I can send you a copy of mine.

Other than that, perhaps you could try reinstalling SlimServer?

rgduarte
2006-04-30, 06:11
I still haven't figured out why my first generation slimp3 won't respond to the remote control.
Does anyone know how I could confirm that the signals are in fact being received by slimserver? That way I could narrow down the problem somehow.
-rgduarte

GrepZen
2006-04-30, 06:47
1) dodgy remote performance is often...overlooked but simple... check the batteries in the remote.

2) You can confirm that the remote is SENDING IR. Every CCD camera picks up IR. You might have a camera/phone. If so, point the remote to the camera's lense in a dark room and press buttons. On the camera's display, you should see the LED of your remote lighting up.

--I don't know if log entries are made when IR is recieved but that's a start.. turn on verbose logging and start checking.

home | server settings | debugging | d_ir ; [x] [Change]

rgduarte
2006-04-30, 07:24
Thanks, Micke.

I've already put in fresh batteries and, with a camcorder, confirmed the remote is emitting something.

And now as you and another poster suggested (http://forums.slimdevices.com/showthread.php?t=11685), I've turned on d_ir debugging and get absolutely nothing in log. I've tried using the slimp3 remote and some other non-slimp3 remote and nothing at all comes out in the log.

So...

1. I therefore conclude it's the IR receiver. If it is the receiver can it be fixed?

2. Am I rushing to conclusions here? The other post I read says ANY IR remote should register in the log with d_ir on. Is that correct?

Thanks for any help.

-rgduarte

Mark Lanctot
2006-04-30, 07:52
Check that SlimServer - Player Settings - Remote - jvc_dvd is checked.

disputin
2007-05-01, 07:14
I have the exact same situation. I have an older slimp3 player with the Sony remote. It is mostly unresponsive to the remote.

I have

1) tested the remote with the CCD of a digital camera and found that it works
2) replaced the batteries in the remote
3) validated that the jvc_dvd is selected in the player settings. I have actually tried all setting options in frustration.
4) tested it against an older version of the slimserver software.
5) reinstalled the latest firmware 2.3

What it does do:
1) If I hold down the power button as it boots it will show the MAC address
2) d_ir does show output for example, this output was received in the logfile.

2007-05-01 07:01:55.3205 IRTM starting profiler
2007-05-01 07:01:55.3209 0000c078 703.7183712 1178028115.32094
2007-05-01 07:01:55.3212 found button volup for 0000c078
2007-05-01 07:01:55.3215 found function dead for button volup in mode class off from map Default.map
2007-05-01 07:01:55.3216 irCode = [dead] timer = [703.7183712] timediff = [703.7183712] last = []
2007-05-01 07:01:55.3217 irCode: dead, 00:04:20:04:1a:33
2007-05-01 07:01:55.3219 irCode not defined: dead
2007-05-01 07:01:55.3220 trying to execute button: dead
2007-05-01 07:01:55.3221 executing button: dead
2007-05-01 07:01:55.3659 0000c078 703.7635776 1178028115.3659
2007-05-01 07:01:55.3661 found button volup for 0000c078
2007-05-01 07:01:55.3663 found function dead for button volup.repeat in mode class off from map Default.map
2007-05-01 07:01:55.3665 irCode = [dead] timer = [703.7635776] timediff = [0.0452063999999837] last = [dead]
2007-05-01 07:01:55.3665 irCode: dead, 00:04:20:04:1a:33
2007-05-01 07:01:55.3667 irCode not defined: dead
2007-05-01 07:01:55.3668 trying to execute button: dead
2007-05-01 07:01:55.3671 executing button: dead
2007-05-01 07:01:55.5803 found button volup for 0000c078
2007-05-01 07:01:55.5805 found function dead for button volup.single in mode class off from map Default.map
2007-05-01 07:01:55.5806 irCode: dead, 00:04:20:04:1a:33
2007-05-01 07:01:55.5807 irCode not defined: dead
2007-05-01 07:01:55.5808 trying to execute button: dead
2007-05-01 07:01:55.5809 executing button: dead
2007-05-01 07:01:57.8824 00000000 706.2790896 1178028117.88248
2007-05-01 07:01:57.8826 Ignoring spurious null repeat code.
2007-05-01 07:01:57.8868 Received 00000000 while expecting 0000c078, dropping code
2007-05-01 07:01:57.8907 Received 00000000 while expecting 0000c078, dropping code
2007-05-01 07:01:57.8947 Received 00000000 while expecting 0000c078, dropping code
2007-05-01 07:01:57.8987 Received 00000000 while expecting 0000c078, dropping code

I am running the slimserver on debian (lenny) using the latest debian package.

Anyone have any idea's what to do next?

ert
2008-02-14, 09:59
I just had almost this exact thing happen to me, too. Sony remote with very old (circa 2003) SlimP3, worked fine for years, suddenly stopped working.

- Remote didn't work with either old SlimP3 or newer Squeezebox v2
- Other remote worked fine with both old SlimP3 and Squeezebox v2 (wasn't the IR receiver)
- Volume up/down was still fine (wasn't the IR transmitter)
- Put in fresh batteries, problem still there.
- Turned on d_ir debugging setting, watched slimserver.log. Lots of IR activity, all unknown ("IR: 0000c091 -> unknown")

So I remembered this was originally a multi-purpose remote. I tried each of the TV, VCR, CBL/SAT, DVD buttons, and found that pressing the DVD butting fixed the problem. It was just stuck in the wrong mode.

Good luck.