I mentioned this in general, but it is buried in a thread that might not get read much. Is there a @dock or similar hijack macro? I have some config.ini settings that I would only like to apply when the unit is docked. Any way to do this?

-Mike

The ;@AC macro can be used for this, if the dock is the only place you normally use the player on AC power.

Cheers

It isn't. I only have a dock at work, but I frequently use the player on AC at home. The problem is that the empeg won't work with DHCP at work for whatever reason so I wanted to be able to give it a static IP at work and let it do DHCP everywhere else. So, any chance of a macro for the dock in some future release?

-Mike

Okay, so why not just use the ;@WORK and ;@HOME macros, and use the Hijack menu HOME/WORK entry to switch between them?

-ml

Because you have to manually select those. Hijack knows when it's in the dock just like it knows if it's on AC or DC, right? Why not add another config option? If the answer is because it's technically difficult, I'm sure that's a valid answer, but if it's as trivial as it seems, then why not?

>then why not?

Easy answer: I don't have any use for it.
And unless more than one or two others NEED it, there's no real justification for the blatent waste of kernel memory, taking away from the player's very limited caching space.

That's why not.

-ml

Aw, but what about the grand tradition of feature creep?

I feel like I'm going to get slammed for asking this... but:

Could there be a "HiJack Lite" in the future that has all of the networking and advanced features stripped out? It would just have in-car stuff like VolAdjust, Bass/Treble, Screen Blank, etc. Maybe "HiJack Car" and "HiJack LAN"?

I know it would add too much to the workload, but I was thinking of the age old empeg question "To you, is the empeg an in-car Linux computer that just happens to play mp3's or is it an in-car mp3 player that just so happens to run on Linux?" Likewise, some people never connect their empeg to a computer except to upload tunes while others will never have their empeg in a car... Feature creep might bump heads with cache creep and database size creep too!

I'm not asking you to do this, I'm just tossing it out there as a "what if".

That's why not

Fair enough, but I do wonder if anybody actually uses the @home/work stuff? Seems like more trouble than it is worth to switch.

Of course the right solution would be to figure out why DHCP doesn't work in the first place. Anybody have any guesses? As far as I can tell absolutely nothing changed on the network and DHCP had been working fine for a couple years (and still works fine on my home LAN). The DHCP server is a redhat 7.2 box that wasn't updated in any way on the day this stopped working. I have used tcpdump and the server is responding to the address requests, but the empeg just keeps requesting over and over.

-Mike

I have the same problem here at home -- the empeg just plain has a bug of some kind in it's ethernet init code. Never resolved. So I use the ;@WORK/;@HOME thing to toggle between DHCP enabled and DHCP not enabled, for when I use it in a demo or something where it works.

Works fine, btw, when plugged into a 10mb/s hub; but not when on a 10/100 hub or a 10/100 switch. Just plain buggy.

Cheers

I know it's been gone over again and again, but FWIW, my empeg is attached to a 10/100 hub and has never failed to work properly.

Mine is connected to a 10/100 switch which uplinks to a 10/100 router/hub that runs its own DHCP (Netgear) and I've never had any issues.

I use the at home at work switch almost every other day. My home network is static addressed and my work is DHCP. =] So count that for one. I think i might have been the one that asked for it because of that reason, but i might just have illusions of granduer.

A ha! For the record I finally got DHCP working. In my case it was an auto-sensing 10/100 hub between me and the dhcp server that decided to stop working properly at 10mbit. Since my empeg is the only 10 megabit device on our network nobody else noticed. A power cycle of the hub fixed it.

-Mike

Okay, this is trivial.

Hijack v345 will be out shortly, with new macros based *soley* on detection of the loopback connector in a dock:

;@DOCKED
;@NOTDOCKED

Cheers

Okay, this is trivial

Uh, thanks Mark, but I don't really need it anymore.

However, as feature creep goes this does seem like it could be potentially useful at some point

-Mike

Oh.

Well, okay then. I'll delete the three lines of code and not bother with v345 then.

Cheers

Hello Mark,

mcomb may not have a need for @dock. However it would come in handy for some of the others who still use the empeg as a file taxi.

That sort feature in v344 is fantastic. Thanks very much,

I'd also be into the @dock addition. =]

Considering this further @tunerid-x would be more versatile.

Mmm.. There is already some AC/DC stuff based on tuner-ID in the Force AC/DC Powermode menu. Does that not do enough? But good idea for the macro, if it can be done cheaply enough.

Cheers

The code that you refer to seems like it is merely a fix (a kludge if you will) around a broken 'ac' switch. @tunerid would permit those various vehicles and docking stations setups a method to select unique parameters for a particular setup without user intervention. (If memory serves; Loren has two or more docking stations.)

++++++++++++++++++++++++++++++++++++

The actual tuner id could be from a pic programmed similarly to the one in pca's tuner kit.

i DO have a couple, one at work and one at home, and i wouldn't minde a different ID for each, so i could have the passwords on at work and not at home, etc...

But how would each dock have it's own ID? Are you saying each would need a PIC chip programmed with a different ID?

Yes. Unfortunately, hardware is needed.


(Much less expensive than the whole tuner kit.)

It looks like @DOCKED never got added. Still got those three lines of code lying around?

Oh, there it is. @LOOPBACK in v392.

I think I could really do with this dock detection, but first can someone explain what is meant by a dock? Car mount frame? Doesn't this mean DC power, so why not use ;@DC.

Is @dock actually there in hijack 4...? Or by another name? Is there a comprehensive list somewhere of ALL these options?

Mark made some wooden docks for use in the home (or office or whatever) that are specially wired so that the empeg can detect when it's in one.

No specific tuner ID, just the detection of the loopback wire.

But the Hijack menu can select AC/DC parameters based on Tuner-ID as well..

Cheers

I'd forgotten - I kept trying to get this to work, but no matter what I did with the loopback I couldn't get it to recognise it was in a dock. Which is a pity, because the workaround is to have servers forced on always...which includes when the empeg is in the car...wasting valuable resource.

Can someone reiterate which pins should be connected, and where just so I can try and get this sorted, please.

(apologies for being more moronic than usual today)

Okay, that helps a bit - mine is built from a car sled, so I'll need to check my pins 6 and 7 to see I have things the right way round.

I might just follow Tony's idea and go for the power plug mod.

So does Hijack still/now include the ;@DOCKED option?

I'm sure it does, but that doesn't help flash upgrades. The part of protected flash that waits on the serial port for an upgrade signal is executed before the kernel takes over. So if you are sled-docked and the AC sensor switch isn't tripped, there is no way for the player to listen for a serial port upgrade. No matter what tricks hijack does.