empeg self started while in my docking station

I was thinking that it would be nice to be listening to music when my empeg started playing while in my docking station on top of my desk. Interesting

Has anyone else had this happen? The cats weren't near it so they aren't the guilty ones (this time) of the crime.

Psychokenesis maybe? Spooky

Yes, I have had it happen occasionally. No IR devices anywhere near. I thought it was a power spike or noisy environment, but never really traced it out.

It's not related to the dock -- others have been reporting this for many many months now. Dunno what causes it yet.

Cheers

I have no IR devices nearby either. I have to turn my TV on with a pen, no remote and the on button fell off. It would have scared me if it had happened in the middle of the night since it's in my bedroom

I am running the latest version of software with no hijack (sorry Mark, I just haven't gotten around to it).

I am running the latest version of software with no hijack (sorry Mark, I just haven't gotten around to it).

Music to my eyes! This is the first definite report of it happening WITHOUT hijack installed! And it's in Car-Mode (right?), just like all of the others! Put this thread into the Bug Reports forum, please!

Cheers ...

Gee, and I thought you would be mad but instead you're happy I'm not running it.

(decides that Mark doesn't like her any more )

>decides that Mark doesn't like her any more

Naw.. you're just snuggly as ever to me! Mostly I'm happy cuz my ADSL link just came back on-line two minutes ago!

Cheers

Mostly I'm happy cuz my ADSL link just came back on-line two minutes ago!

That would make me happy too if mine went down.

Paul, when yours did this did you notice the volume keeps showing on the screen every 30 seconds or so by itself? I just posted this to the bug forum.

Greetings!

Not volume, no. When it does happen, it seems to just be a poweron. It can happen in both car and AC modes, though. Before I had the dock, I had this happen in AC mode too.

There is another thread where Tony mentions that it could be a noisy IR input. I think I agree with that. I have had other symptoms of phantom pushes, but mine are always alternating source (aux/player) very quickly. It stops on a button press.

There are a few threads about this one too - but they all seem to be the same general symptom: spurious IR or control signals. Maybe even the player waking in the car might be tied to this as well...

I suspect either some debounce logic, or the IR input is picking up / generating noise. One of these days (it happens too rarely for me to test with any consistancy), I will put the IR debug up, to see if it is "seeing" any coherent (or incoherent) signals.

Is there any good way to test if the IR receiver is starting to deteriorate somehow?

Last night I ended up pulling it out of the dock because it started playing 10 mintues after I powered it off. This morning I pushed it back into the docking station and it started right up. I don't think this has anything to do with IR signals.

I stuck it back in and powered it off and it took 4 minutes for it to start playing again. I'm going to have to test it in the van, as soon as the rain ever stops, to see if this behavior is going to happen in the sled also. This could be a big problem if it won't stay turned off now for some reason.

Has anyone else had this happen? The cats weren't near it so they aren't the guilty ones (this time) of the crime.

I still suspect the cats. This happens to a friend of mine, too (1.03, no Hijack), and cats are the only common factor that I can see. I reckon it's their invisible infra-red mind control rays... you know, the thing where they walk into the room and suddenly, without anything Shannon would recognise as information transfer, it's "Oooh, Lottie's hungry"...

Peter

cats are the only common factor that I can see. I reckon it's their invisible infra-red mind control rays...

Maybe that is it because they were in the room everytime, just not near the empeg controls

I don't think this has anything to do with IR signals.

If it is related to IR signals, I don't think it would be "stray IR" like you're thinking. It would be more like: Something wrong the circuitry causes the IR sensor to behave as though it's getting stray signals even when there are none.

Question about the Mk2a volume control: It's optical, right? Is it infrared? Maybe the casing of the encoder leaks a bit...

Unless I'm mistaken, sometimes my encoder seems to rest at the point where even the slightest touch causes the volume bar to display. Perhaps it's something as simple as this?

Ya know, Laura, if you'd only break down and install Hijack, this behaviour should cease, at least while docked.

If I recall correctly, people only observe this when the player is running in DC/Car mode.. (at this point, seven people churp in with reports of it on AC/Home, right?).

Cheers

Well, one...

I would have it sitting in the cube at work (before the docking station), so it was fully in AC mode, and it would suddenly power-up.

At this point, seven people churp in with reports of it on AC/Home right?

The friend of mine that this happens to, has it happen on AC power.

If we assume, for the sake of argument, that domestic cats do not, in fact, spontaneously emit valid consumer IR pulse-trains, then my money is on some kind of capacitative glitching on the display board, building up very slowly but eventually causing the PIC to register an instantaneous top-button press. Perhaps if front-panel buttons were debounced a bit more it could be fixed in software?

Peter

It's happening in AC power on mine also. I guess I'm going to have to keep it unplugged or pull it slightly out of the sled unless I want to listen to it. It's not random on mine now, it's happening constantly. Took a little over an hour this time to come back on but it won't stay off.

building up very slowly but eventually causing the PIC to register an instantaneous top-button press

Or, in Laura's case, a volume-knob turn. Remeber that any IR command or button press will wake up the player.

Here's an idea. Not a solution to the hardware problem, but a band-aid that might be useful: An option in Hijack (perhaps in config.ini) which says that only a specified set of button presses or events can wake up the player from standby, it ignores all other commands. For instance, tell it that only a top-button press can wake up the player, or only a knob press, or a press of the power button on the Rio remote, etc.

That way, if it's random commands (for whatever reason) causing the wake-ups, you'd eliminate 99 percent of them.

Is that even possible to do?

I don't see why it shouldn't be possible. The kernel knows when the display is off and it can just swallow all IR commands apart from say the power button one. And once it gets that one then it will do the normal thing and allow everything to pass.

- Trevor

How would I go about doing that? Or in other words exactly what would I need to put in config.ini?

How would I go about doing that? Or in other words exactly what would I need to put in config.ini?

Something like this might work:

[Dear Mark]
Please=Add this feature for me.
I'd be=eternally grateful.

[Dear Mark]
Please=Add this feature for me.
I'd be=eternally grateful.

Then I'd even put hijack back on it

Naw, let's find/fix the bug instead.

Since Laura can reproduce this bug very easily, and she's more than competent technically, this oughta be a breeze!

Could you hook up a notebook computer to the serial port, install Hijack, and set "ir_debug=1" in the [hijack] section of config.ini ?

Then just put it in standby, and wait for it to wake up again.
The serial log will tell the story for us. Post it.

Thanks!

Cheap Way to see if its an IR signel or something else... Cover the IR sensor with a Piece of Electrical Tape , if it still turns it self back on then its not a IR signel :0

Can I do it using my desktop computer?

Can I do it using my desktop computer?

Any computer that'll connect with hyperterminal, as detailed here, will do.

Ok, now that I am done painting for the night I'll give it a go and report back.

I installed Hijack, had to read how to edit config.ini again (been so long I forgot) and I have hyperterminal open and waiting.

And as I was writing this it woke up and started so here is what happened. So what does this mean?

Poll wait
Poll fail
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x4086d000
Poll wait
Poll fail
16743: IA1:0000000b,dk=00ffffff,dr=0,lk=0
16743: IA2:0000000b.P,dk=00ffffff,dr=0,lk=0
16743: ENQ.I: @c0124cc8: 0000000b.0
16744: DEQ.I: @c0124cc8: 0000000b.0
16744: ENQ.P: @c0124e54: 0000000b.0
Wakeup
Wakeup
Poll ok
16745: DEQ.P: @c0124e54: 0000000b.0
Poll wait
Poll fail
16748: IA1:00fffffe,dk=00ffffff,dr=0,lk=0
16748: IA2:00fffffe.P,dk=00ffffff,dr=0,lk=0
16748: ENQ.I: @c0124cd0: 00fffffe.0
16749: IA1:00ffffff,dk=00ffffff,dr=0,lk=0
16749: IA2:00ffffff.P,dk=00ffffff,dr=0,lk=0
16750: DEQ.I: @c0124cd0: 00fffffe.0
16750: ENQ.P: @c0124e5c: 00fffffe.0
Wakeup
Wakeup
Wakeup
Poll ok
16752: DEQ.P: @c0124e5c: 00fffffe.0
Poll wait
Poll fail
16860: IA1:0000000a,dk=00ffffff,dr=0,lk=0
16860: IA2:0000000a.P,dk=00ffffff,dr=0,lk=0
16860: ENQ.I: @c0124cd8: 0000000a.0
16861: DEQ.I: @c0124cd8: 0000000a.0
16861: ENQ.P: @c0124e64: 0000000a.0
Wakeup
Wakeup
Poll ok
16862: DEQ.P: @c0124e64: 0000000a.0
Poll wait
Poll fail

Did all of that happen AFTER it woke up?

I'd like to see the entire sequence from when you put the player into standby, if possible.

Cheers

Ok, will do.

Oh, and in answer to "what does it mean", here's the button presses that the player sees from the sequence you posted:

0000000b = KnobLeft
00fffffe = IR_FAKE_INITIAL <--- internally generated by hijack
0000000a = KnobRight

Cheers

Here is a bootup sequence of it now.

empeg-car bootstrap v1.02 20001106 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.17-rmk5-np17-empeg52-hijack-v334 (root@ibbm) (gcc version 2.95
.3 20010315 (release)) #2 Sat Apr 26 10:31:47 EDT 2003
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40103872)
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 14996k/16M available (996k code, 20k reserved, 368k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
IrCOMM protocol (Dag Brattli)
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 67706d65 'empg'
Tuner: loopback=0, ID=-1
Scheduling custom logo.
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0005980).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
hdb: IC25T060ATCS05-0, ATA DISK drive
hda: FUJITSU MHL2300AT, ATA DISK drive
hdb: IC25T060ATCS05-0, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: FUJITSU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/63
hdb: IC25T060ATCS05-0, 57231MB w/1768kB Cache, CHS=7296/255/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:28:0f:2
0
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Remounting first music partition read-only
Remounting second music partition read-only
Press 'q' now to go into development mode. You Have Zero Seconds To Comply...
Starting player
Hijack: intercepting config.ini

hijack: removed menu entry: "Hard Disk Detection"
khttpd: listening on port 80
kftpd: listening on port 21
player.cpp : 385:empeg-car 2.00 2003/04/01.
Poll wait
Poll fail
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x4086d000
1306: IA1:00fffffe,dk=00ffffff,dr=0,lk=0
1306: IA2:00fffffe.P,dk=00ffffff,dr=0,lk=0
1306: ENQ.I: @c0124cc8: 00fffffe.0
1307: IA1:00ffffff,dk=00ffffff,dr=0,lk=0
1307: IA2:00ffffff.P,dk=00ffffff,dr=0,lk=0
1307: DEQ.I: @c0124cc8: 00fffffe.0
1308: ENQ.P: @c0124e54: 00fffffe.0
Wakeup
Wakeup
Wakeup
Poll ok
1310: DEQ.P: @c0124e54: 00fffffe.0
Poll wait
Poll fail
2334: IA1:00000006,dk=00ffffff,dr=0,lk=0
2334: IA2:00000006.P,dk=00ffffff,dr=0,lk=0
2334: ENQ.I: @c0124cd0: 00000006.0
2335: DEQ.I: @c0124cd0: 00000006.0
2335: ENQ.P: @c0124e5c: 00000006.0
Wakeup
Wakeup
Poll ok
2336: DEQ.P: @c0124e5c: 00000006.0
Poll wait
Poll fail
2355: IA1:00000007,dk=00000006,dr=0,lk=0
2355: IA2:00000007.R,dk=00000006,dr=0,lk=0
2355: ENQ.I: @c0124cd8: 00000007.0
2356: DEQ.I: @c0124cd8: 00000007.0
2356: ENQ.P: @c0124e64: 00000007.0
Wakeup
Wakeup
Poll ok
2358: DEQ.P: @c0124e64: 00000007.0
Poll wait
Poll fail
2846: IA1:00000002,dk=00ffffff,dr=0,lk=0
2846: IA2:00000002.P,dk=00ffffff,dr=0,lk=0
2846: ENQ.I: @c0124ce0: 00000002.0
2847: DEQ.I: @c0124ce0: 00000002.0
2847: ENQ.P: @c0124e6c: 00000002.0
Wakeup
Wakeup
Poll ok
2848: DEQ.P: @c0124e6c: 00000002.0
Poll wait
Poll fail
2864: IA1:00000003,dk=00000002,dr=0,lk=0
2864: IA2:00000003.R,dk=00000002,dr=0,lk=0
2864: ENQ.I: @c0124ce8: 00000003.0
2865: DEQ.I: @c0124ce8: 00000003.0
2865: ENQ.P: @c0124e74: 00000003.0
Wakeup
Wakeup
Poll ok
2867: DEQ.P: @c0124e74: 00000003.0
Poll wait
Poll fail
2887: IA1:00000002,dk=00ffffff,dr=0,lk=0
2887: IA2:00000002.P,dk=00ffffff,dr=0,lk=0
2887: ENQ.I: @c0124cf0: 00000002.0
2888: DEQ.I: @c0124cf0: 00000002.0
2889: ENQ.P: @c0124e7c: 00000002.0
Wakeup
Wakeup
Poll ok
2890: DEQ.P: @c0124e7c: 00000002.0
Poll wait
Poll fail
2905: IA1:00000003,dk=00000002,dr=0,lk=0
2905: IA2:00000003.R,dk=00000002,dr=0,lk=0
2905: ENQ.I: @c0124cf8: 00000003.0
2907: DEQ.I: @c0124cf8: 00000003.0
2907: ENQ.P: @c0124e84: 00000003.0
Wakeup
Wakeup
Poll ok
2908: DEQ.P: @c0124e84: 00000003.0
Poll wait
Poll fail
2926: IA1:00000002,dk=00ffffff,dr=0,lk=0
2926: IA2:00000002.P,dk=00ffffff,dr=0,lk=0
2926: ENQ.I: @c0124d00: 00000002.0
2928: DEQ.I: @c0124d00: 00000002.0
2928: ENQ.P: @c0124e8c: 00000002.0
Wakeup
Wakeup
Poll ok
2930: DEQ.P: @c0124e8c: 00000002.0
Poll wait
Poll fail
2943: IA1:00000003,dk=00000002,dr=0,lk=0
2943: IA2:00000003.R,dk=00000002,dr=0,lk=0
2943: ENQ.I: @c0124d08: 00000003.0
2944: DEQ.I: @c0124d08: 00000003.0
2944: ENQ.P: @c0124e94: 00000003.0
Wakeup
Wakeup
Poll ok
2946: DEQ.P: @c0124e94: 00000003.0
Poll wait
Poll fail
2966: IA1:00000002,dk=00ffffff,dr=0,lk=0
2966: IA2:00000002.P,dk=00ffffff,dr=0,lk=0
2966: ENQ.I: @c0124d10: 00000002.0
2967: DEQ.I: @c0124d10: 00000002.0
2967: ENQ.P: @c0124e9c: 00000002.0
Wakeup
Wakeup
Poll ok
2969: DEQ.P: @c0124e9c: 00000002.0
Poll wait
Poll fail
2983: IA1:00000003,dk=00000002,dr=0,lk=0
2983: IA2:00000003.R,dk=00000002,dr=0,lk=0
2983: ENQ.I: @c0124d18: 00000003.0
2985: DEQ.I: @c0124d18: 00000003.0
2985: ENQ.P: @c0124ea4: 00000003.0
Wakeup
Wakeup
Poll ok
2987: DEQ.P: @c0124ea4: 00000003.0
Poll wait
Poll fail
3035: IA1:00000006,dk=00ffffff,dr=0,lk=0
3035: IA2:00000006.P,dk=00ffffff,dr=0,lk=0
3035: ENQ.I: @c0124d20: 00000006.0
3036: DEQ.I: @c0124d20: 00000006.0
3036: ENQ.P: @c0124eac: 00000006.0
Wakeup
Wakeup
Poll ok
3037: DEQ.P: @c0124eac: 00000006.0
Poll wait
Poll fail
3055: IA1:00000007,dk=00000006,dr=0,lk=0
3055: IA2:00000007.R,dk=00000006,dr=0,lk=0
3055: ENQ.I: @c0124d28: 00000007.0
3056: DEQ.I: @c0124d28: 00000007.0
3056: ENQ.P: @c0124eb4: 00000007.0
Wakeup
Wakeup
Poll ok
3057: DEQ.P: @c0124eb4: 00000007.0
Poll wait
Poll fail
Poll wait
Poll fail


I have it in standby now and will post when it wakes up which won't take it long.

Good.

Note that those ever-increasing numbers that prefix most lines are timestamps, in 100ths of a second.

When it wakes up again, you may note a huge gap in timestamps between earlier messages and the ones after it woke up.

I need to see all of the messages spanning that gap -- the two or three immediately beforehand, and everything afterwards.

Thanks

Oh, I'm heading out for a long hike to a remote geocache.. might not be back for a while, but please post away!

Neat. I've only been geocaching twice but it was a good laugh each time. Luckily it was a nice day on both times.

You going to leave anything cool?

- Trevor

Usually it wakes right back up but it has decided that it is tired. Have fun and I'll post whatever it says

>You going to leave anything cool?

Well, I picked up an E.T. toy, that probably has a tiny camera hidden inside, and left a hunting knife & scabbard that I found near another local cache last fall.

Cheers

You're back and my empeg is still sleeping on the job. It figures that before I couldn't get it 'not' to turn itself on. I'm leaving it hooked up until he awakens even though I'd like to have it play right now.

Greetings!

A thought - could having an open, well behaved connection on the serial port change the results of the test?

Since we know that the player watches for serial commands as well as the remote / IR control, maybe the serial port (if there is a stray signal) would wake the player as well??? Perhaps it is not the IR control pathway that is in question, but the serial port?

Since this test involves having an active, well behaved serial connection active, maybe it is either changing the circumstances of the bug or the bug is in the serial port sending the signal instead of the IR, as originally thought.

One possible way to check this would be to disconnect the display board from the main board completely, and see if it still happens with nothing on the serial port. That would take the IR signal path out of the loop completely...

A thought.

Edit - reread the whole thread and saw that the bug happened with a serial link connected. So that is not it.

It's toying with me. Since I said I could easily recreate the bug, it's going to prove me wrong. Don't you hate when that happens

Greetings!

The only way to get a bug to perform on command is to say "watch this"...

I left it on hyperterminal over night but it never turned itself on. Maybe the problem went away as fast as it appeared. If it starts happening again I'll post a log, in the meantime, I'm going to listen to it