how "stalk" works?

i found this:


but how do i use the "stalk" to navigate? i dont see a menu option etc...

i ask this because i have thoughts about getting a sony "stalk"

i got the stalk... but cant even access the menu.... do i have to set up ir_ translate first?

No, but you do have to enable the stalk in the player configuration. It's one of the options in the "Configure Player" screen in emplode if I recall correctly. Make sure to synch after changing the setting.

i tried that... still no go... but i have tried the ir_translate.. just have to test it in the car....

When you select the Hijack "Button Codes Display" feature on the player's screen, do you see anything when pressing the stalk buttons?

Just checking the basics here.. but, *exactly* how have you connected the stalk ?

(it does NOT plug into the sled wiring harness microphone jack!).

of course not... connected via the tuner, only that do work is that seek/ams ring can change visuals...

yeah.. all buttons give me the right codes

So let me be clear about what you're asking? As I understand it now, you're saying:

- The stalk seems to work.
- Using buttons on the stalk does all the right things, from what you can tell (can you change tracks?).
- You want to know which button on the stalk brings up the player's main menu, so that you can navigate the menu and make selections by twisting the stalk controls.

I've never used the stalk, so I don't know the answer to that question. I don't know if that's even implemented; I was under the impression that the stalk was mostly for volume and track changing and such, so it might be that this isn't implented at all, and that it was a design decision to implement it that way. Does anyone know the answer to this?

-I get the right codes in hijack
-No it does not
-Yes

back to the car

The answer is in the top post of this very thread: none of the buttons has "Menu" assigned to it by default.

If one is willing to give up an existing button/function in favour of a "menu button", then do so in this manner in config.ini:

[ir_translate]
Kxxxxx.L=Kxxxxx.L
Kxxxxx=Menu

Or possibly like this, so that a short press of the same button still has the original functionality, but a long press now brings up the menu:

[ir_translate]
Kxxxxx.L=Menu
Kxxxxx=Kxxxxx

Or even like this, so that a long press of that same button brings up the Hijack menu (same as on the IR remote control):

[ir_translate]
Kxxxxx=Menu

(all three completely untested, of course: that's your job).

Replace the Kxxxxx part by the name of the button you are modifying, from this list:

KOff, KSource, KAtt, KFront, KNext, KPrev, KVolUp, KVolDown, KRear, KBottom, or by one of the "shifted" button combinations (same as before, but with KS instead of K at the start of each button name (eg. KSSource).

-ml

no problem... no wonder why my ir_translate does not work:

[ir_translate]
;Sony Stalk
;
; Source
80000016=20df03
;
; volume up / down
80000013=VolUp
80000017=VolDown
;
;seek-ams
80000031.LT=B9460A.L,null ; In tuner, long press of left scans back
80000031.T=20DF10 ; In tuner, left seeks back
80000031.M=PrevTrack.N,Left.U ; In player, track-. In menu, left
80000013.LT=B9460B.L,null ; In tuner, long press of right scans forward
80000013.T=20DF11 ; In tuner, right seeks forward
80000013.M=NextTrack.N ,Right.U ; In player, track+. In menu, right
;
;off
80000030=20df03.L
;
;Mute
80000016=20df16
;
;menu
80000033=20df12
;
;
; Pioneer steeringheel remote
;
; The shift key
AD520C.L=20df03.L,null ; press and hold "ATT" = standby
AD520C=null.S ; "ATT" = Shift Key
;
; These are needed to ignore the "Func" button sending out a bogus code
AF5067=null
80AF5067=null
;
; Search macros
; used when shift-lock is active and long press
AD5212.LS=20df0e ; "1" PIN
AD5243.LS=20df0e,20df0e ; "6" year
AD520A.LS=20df0e,20df0e,20df0e ; "9" title
AD521A.LS=20df0e,20df0e,20df0e,20df0e ; "2" artist
AD5241.LS=20df0e,20df0e,20df0e,20df0e,20df0e ; "5" genre
AD5242.LS=20df0e,20df0e,20df0e,20df0e,20df0e,20df0e ; "3" source
;
; Numbers
; Shift lock active, short press
AD5212.S=20df00 ; 1
AD521A.S=20df01 ; 2
AD5242.S=20df02 ; 3
AD5240.S=20df04 ; 4
AD5243.S=20df05 ; 5
AD5241.S=20df06 ; 6
AD5219.S=20df08 ; 7
AD520D.S=20df09 ; 8
AD520A.S=20df0a ; 9
AD520B.S=20df0d ; 0
;
; volume up / down
; ??? AD520A.B
; ??? AD520B.A
AD520A=20df13,20df13,20df13,20df13,20df13
AD520B=20df17,20df17,20df17,20df17,20df17
;
; The "source button"
AD520D.LT=20df07,null ; AM/FM in tuner
AD520D.LM=20df0B,null ; select mode in player
AD520D.T=b9461e ; switch to player from tuner
AD520D.A=b9461e ; switch to player from Aux
AD520D.M=b9461c ; switch to tuner from player
;
; Setting the Prev/Next buttons to emulate front-panel allows
; press-and-hold to do manual tuning in tuner mode
AD5242.T=4;
AD5243.T=2;
AD5242.LM=b9460c.L ;Prev Track / Rewind
AD5243.LM=b9460d.L ; Next Track / Fast Forward
AD5242.M=20df10 ; Prev Track
AD5243.M=20df11 ; Next Track ;
;
; Normal functions
AD5212.L=20df15,null ; press and hold cancel = visual (makes no sense)
AD5212=20df0c ; cancel
AD521A.L=20df12.L ; menu/OK
AD521A=20df12 ; menu/OK
AD5240.L=20df16.L ; play
AD5240=20df16 ; play
AD5241.L=20df14.L ; info
AD5241=20df14 ; info
AD5219=FidEntry.N ; search
; ???

the part for the stalk corrected to:

Sony Stalk
;
; Source
KSource=20df03
;
; volume up / down
KVolUp=VolUp
KVolDown=VolDown
;
;seek-ams
KPrev.LT=B9460A.L,null ; In tuner, long press of left scans back
KPrev.T=20DF10 ; In tuner, left seeks back
KPrev.M=PrevTrack.N,Left.U ; In player, track-. In menu, left
KNext.LT=B9460B.L,null ; In tuner, long press of right scans forward
KNext.T=20DF11 ; In tuner, right seeks forward
KNext.M=NextTrack.N ,Right.U ; In player, track+. In menu, right
;
;off
KOff=20df03.L
;
;Mute
KAtt=20df16
;
;menu
KFront=20df12


testing i a few min (have to do a sync first)

Why are you (still) using hex values for most stuff??

was the fastest way

but the new ir_translate did not work...

only thing that do work is that the seek/ams ring can change visuals

Well, you could start by deleting everything from there, and using the built-in (defaults). Then start modifying anything you want to change, one button at a time.

And I'm still not sure what you are trying to accomplish with all of that complexity -- and no mention of a Menu button anywhere.

-ml

i tried with just hte built ins.... still only able to change the visuals with the seek/ams..

remember that if my ir_translate looks big it contains the pioneer steeringwhel remote (plan to take it out later)

btw... how should it work with the built in? if any know this i would have a point to start

but at least i can read the codes (in hijack) when i push'n'twist the darn thing

Most functions should "just work" if you nuke your entire "[ir_translate]" section (try it.. including getting rid of the Pioneer stuff temporarily).

The buttons mostly do what their names suggest: on/off, Source, Attenuate, Next/Prev (like the left/right front panel buttons), volume up/down, ..

Note that a reboot is required for any changes there to take effect.

hehe... the reboot comes by itself when i take it to the car

but right now i have removed the ir_translate complete and waiting for the sync to complete

btw... another funny thing is that when i set the boot logo in hijack to the "stock" logo where "tux" waves at you.. it always gives me the hijack verson... i have tried to set it both at home and in the car... same result

i have now nuked the entire ir_translate.. still only the seek/ams responds with a change in the visuals

and still if i look at the display button codes in hijack all buttons have a different code. so i know that it works.. partly

Try posting the entire config.ini file here for us.. probably something somewhere in there is interfering.

Cheers

[Network]
Gateway=192.168.1.1
Netmask=255.255.255.0
IPAddress=192.168.1.11
DHCP=0
[synchronise]
seq_num=40
[wendy]
flag_amount=0
[custom]
wendy=
[searches]
amount=0
[VisualFavourites_AM]
count=0
[VisualFavourites_AUX]
count=0
[VisualFavourites_DSP]
count=0
[VisualFavourites_FM]
count=0
[Options]
Name=Empeg
[controls]
stalk_side=right
[User Info]
Email=
Phone=
Name=Tina Andersen & Bo Herrmannsen
[display]
play_count=1
visual_names=1
caching=1
[kenwood]
disabled=0
[menu]
quit=0
sort_playlist=1
[shuffle]
deduplicate=1
[sense]
muteaction=0
mute=-1
[power]
off_timeout=60000
[hush]
hushpercent=20
[volumecap]
enabled=0
[ramp]
disabled=0
[tuner]
region=europe
[aux]
source=
title=
artist=
[hijack]
decimal_fidentry=1
;@MENUEXEC Set_Date_Time /rdate -s 192.168.1.1 &>/dev/null
temperature_correction=0 ;; default is -4
fan_control=1
fan_low=16
fan_high=21

my "farmers" logic say that this ini should work.... but i might be wrong

have i said something wrong?

Not at all. The config.ini you posted should work, the stalk should be doing more than just changing visuals.

Just for grins, when you press, say, the "Next Track" button on the stalk, what does the button codes display tell you?

(Just verifying that the stalk is sending the right signals to begin with.)

0x5b

but i have tried everything that comes to mind... but with the ini i just posted.. the only thing that do work is that seek/ams ring changes the visual... none of the other buttons make the player react...

Okay, according to the developer info page, 5b is the correct code for "next track" (actually seek+).

Why in blue blazes is it not working?

don't ask me.... has it anything to do with what software i run? i use the 3alpha11 developer... from time to time i need to be able to get to bash to perform drive test etc.

Do you have a specific need to run the alpha software? Perhaps it has a previously unreported bug in the Stalk code.

I'd be curious to know if the stalk worked OK with the 2.0 final software.

need the auto eq at some point.... but need to get a very good mic

So you'd be OK to run 2.0 final for a while, then? I'd say try that and see if the stalk works. Remember that when switching back and forth between 3.0 Alpha and 2.0 Final, you might have to rebuild the databases manually. At least I remember having that problem.

what about bens fan controller... do that run under 2.0 ?

I don't know for sure, but I'd hope that anyone designing an add-on for the player would intend for it to work under the most common configuration.

but i will try the 2.01 final first and then hit the car... which is covered in a heavy layer of snow

one way could be to use the alpha ver. to get the values for EQ.. and then go back to 2.01

at least it did the rebuild in less than 1 min. so one step saved

just opened emplode to check that stalk was enabled... but i want to do a disk check....

while i wait i was remembering one of the new features of hijack... to select boot logo... i selected the original one where the penguin waves at you... but i always displays the hijack default one...

2.01 without hijack did not do the trick....

2.01 with newest hijack same thing... stil only the seek/ams ring that changes the visuals... but a display codes it gives different codes for each button

Your post of the config.ini contents showed the stalk as correctly enabled.

Thank you for going to all the trouble of installing the 2.0 firmware. I am stumped as to why it's not working. Anyone else have any ideas?

i did an extra check... would be rather stupid to get to the car and back to discover i had it disabled again

could it be the model of the stalk? i have read that there is 2 models...

also i cant get out of my mind that i cant select boot logo.. i can in hijack but it does not "remember" what i select

As long as it's an RM-X4S or an RM-X2S, you should be fine. Even so, your Button Codes Display seemed to show the correct value, meaning that the stalk is sending the correct signal to the player, so I'm wondering what's up.



You can put any boot logo you want into place with Jemplode. The original 2.0 software boot logo is here and can be installed to the player via Jemplode.:

http://empeg.miniinfo.net/anilogo/515.raw

it said that animation upload failed.... do it upload via network or serial?

regarding the stalk i'm 100% sure it,s one of the 2... i will get the model number in 1 sec

Sony RM-X2S Stalk

I'm pretty sure that Jemplode uses ethernet to install custom boot animations.

it had a password set for ftp.. so now it works

but i think i better get to bed... have to get up in around 6 hours... but backagain in something like 10-11 hours

Hopefully when you wake up someone will have figured out the stalk problem and posted a solution for you. I'm stumped: the thing should just be working.

We have yet to see the entire config.ini in one post, so far we've seen it broken into two sections.

Bo, post the entire config.ini here just to be certain.

I thought the most recent post of config.ini *was* the entire file. He removed all ir_translate data and reposted the whole file. It looks fine to me. I might be missing something though.

No, he actually has never shown us the real config.ini file, and I really cannot help any further until he does.

As evidence, he recently said he had an FTP password set -- no sign of that in the config.ini's that were posted.

Cheers

ftp was in jemplode.. not in the ini

the last ini was the COMPLETE ini

[Network]
Gateway=192.168.1.1
Netmask=255.255.255.0
IPAddress=192.168.1.11
DHCP=0
[synchronise]
seq_num=40
[wendy]
flag_amount=0
[custom]
wendy=
[searches]
amount=0
[VisualFavourites_AM]
count=0
[VisualFavourites_AUX]
count=0
[VisualFavourites_DSP]
count=0
[VisualFavourites_FM]
count=0
[Options]
Name=Empeg
[controls]
stalk_side=right
[User Info]
Email=
Phone=
Name=Tina Andersen & Bo Herrmannsen
[display]
play_count=1
visual_names=1
caching=1
[kenwood]
disabled=0
[menu]
quit=0
sort_playlist=1
[shuffle]
deduplicate=1
[sense]
muteaction=0
mute=-1
[power]
off_timeout=60000
[hush]
hushpercent=20
[volumecap]
enabled=0
[ramp]
disabled=0
[tuner]
region=europe
[aux]
source=
title=
artist=
[hijack]
decimal_fidentry=1
;@MENUEXEC Set_Date_Time /rdate -s 192.168.1.1 &>/dev/null
temperature_correction=0 ;; default is -4
fan_control=1
fan_low=16
fan_high=21

Okay, that config.ini works fine in a player here, thanks.

So, the very obvious thing to do next is (always) to post a serial port trace from while trying to use the stalk. If anything is ever wrong with an empeg, there is almost always some useful information there.

In this case, I am betting that some components somewhere are slowly aging, and the A->D conversions of stalk values are showing up as out of range ("Stalk: no match for value=0xXX").

So you may need to fine tune the conversion scale, by adding/modifying these lines in config.ini:

Code:

[hijack]
;; Min/max A/D pairs for all ten buttons on a Right mounted Stalk
;; Button order is:
;;KOff,KSource,KAtt,KFront,KNext,KPrev,KVolUp,KVolDown,KRear,KBottom
;;
;; Here are the built-in factory defaults for a Right-Hand-Side stalk:
stalk_rhs=0x00,0x07,0x10,0x1c,0x24,0x30,0x34,0x40,0x42,0x4e,0x54,0x60,0x68,0x74,0x7e,0x8a,0x94,0xa0,0xa0,0xb5

More info available here.

Cheers

how do i do a serial port trace? might as well get it done

Connect with hyperterminal or some other terminal program. This part is going to be tricky because, since we want the serial traces from actual stalk activity, and the stalk hooks to the tuner module, and the tuner module can only connect to the car docking sled, then it will require the car docking sled and the computer to be in the same room.

Select "Transfer, Capture Text" in Hyperterminal to begin creating the log file.

Apply power to the player. Allow it to boot. Try some stalk commands.

Select "Transfer, Capture Text, Stop" when you have captured the desired activity.

Always do the capture-to-file thing. Do not try to do a cut-and-paste from the hyperterminal main window, it's got a bug that messes up the order of lines and characters when you copy from its main window.

Another way to check things, not involving us here, would be to just use the Hijack Button Code Display screen. Press each stalk button in turn, and compare the reported stalk value (from the display) with the min/max pairs for that button in the config.

The bet here is that some of them are "out of range", and the min/max ranges will require adjustment to compensate.

But if they show up as "in range", then we'll need serial port traces to help you further.

Cheers

I had him do that for the "next track" button (i.e., the "seek +" button) up above, and it came out as "5b" which according to the developer info section, is the correct value for seek+.

For example, the button on the end of the stalk is the KSource button.
It should always be generating codes within the range 0x10 - 0x1c,
preferably 0x16 (mid-range).

If not, then add the config.ini lines shown earlier,
and modify the range to match what the button is really doing.

Cheers

Yeah, I saw that. Part of the problem here is that we have a
guy who has never used a working stalk before, so things will
be very confusing for him. And he may not notice when things
actually work or not.

So, perhaps he could also report here exactly what each button
generates on the display, going through all of the buttons 2-3 times
to get an average.

Cheers

damn... i only have the cable that came with the player

i can do that, in an hour or so, it's dinner time here

I *think* the hole in the bottom rear of the sled makes enough room to use the regular serial port that's built in to the player. Check and see.

not in an peogeot 106. like max 5mm space around the sled

source=0x16
vol+=0x88
vol-=0x71
seek+=0x5c
seek-0x4a
off=0x02
mute=0x2b

and the 3 buttons seen from above with the stalk standing flat on a table.. and the two that side next to each other closeest to you..

single button= 0xb0
left one=0x9b
right one=0x3b

Looks like it is all working normally.

yeah.. i cant get it either. the next problem is serial port trace.. it will take some days before i can do it since i have to route a flat cable from the sled's db9 connector.. only way i can do a trace right now is to get the sled out of the dash

.. or get an ethernet connection into the dash, if that's any easier. The serial port messages could then be retrieved via FTP, I believe.

-ml

no, it's the same trouble.. but i think i can get some connectors and cable by sunday...

is there any further test's i can do?

was there no other chioce than serial or network to do the serial trace? or other test that i can do?

Nothing worthwhile.

ok... so i will aim for a serial port

how should i wire the 2 db9 connectors.. from my pc to the sled connector?

like this?

1+6 ------------ 4 (1 and 6 to 4)
2 -------------- 3 (2 connected to 3)
3 -------------- 2 (3 connected to 2)
4 -------------- 1+6 (4 connected to 1 and 6)
5 -------------- 5 (5 connected to 5)
7 -------------- 8 (7 connected to 8)
8 -------------- 7 (8 connected to 7)

Connect *only* the Tx, Rx, and GND pins (3-wires). Ignore the rest of them.

-ml

ok... but i will report back some time this sunday.... around 20:00 CET i guess

i just soldered a cable... but will the sleds serial work along with the players serial when in the car?

The sled serial port and the serial port on the back of the empeg unit are the same port. One is wired DCE and one is wired DTE.

so if i use the serial on the player while it's docked in the car I just have to cross the wires from pin 2 and 3 ?

just aksing to make sure i dont blow anything up

done the serial trace... but nothing happens in putty when i use the stalk... nor when i use the front panel.. log attached

Okay, add this to the [hijack] section in config.ini, and then get another serial port trace. This time it *will* have stuff in it:

stalk_debug=1

No problem... will be around the same time.. have to "steal" the power at an outdoor outlet...

new log...

and when pressing any button on the stalk the sound is stuttering and ful of clicks...

but strange that the end of the log is just one big space.. but nothing happend on screen

btw.. my config.ini... just to make sure

[Network]
Gateway=192.168.1.1
Netmask=255.255.255.0
IPAddress=192.168.1.11
DHCP=0
[synchronise]
seq_num=41
[wendy]
flag_amount=0
[custom]
wendy=
[searches]
amount=0
[VisualFavourites_AM]
count=0
[VisualFavourites_AUX]
count=0
[VisualFavourites_DSP]
count=0
[VisualFavourites_FM]
count=0
[Options]
Name=Empeg
[controls]
stalk_side=right
[User Info]
Email=
Phone=
Name=Tina Andersen & Bo Herrmannsen
[display]
play_count=1
visual_names=1
caching=1
[kenwood]
disabled=0
[menu]
quit=0
sort_playlist=1
[shuffle]
deduplicate=1
[sense]
muteaction=0
mute=-1
[power]
off_timeout=60000
[hush]
hushpercent=20
[volumecap]
enabled=0
[ramp]
disabled=0
[tuner]
region=europe
[aux]
source=
title=
artist=
[hijack]
stalk_debug=1
decimal_fidentry=1
;@MENUEXEC Set_Date_Time /rdate -s 192.168.1.1 &>/dev/null
temperature_correction=0 ;; default is -4
fan_control=1
fan_low=16
fan_high=21

Your player is doing the "change the baud rate midway through startup"
thing that they do by default when in a car.

Fix it with this, in config.ini, then try again.
This might even fix the stalk, too, now that ya mention it..

[serial]
car_rate=115200 ; Set default rate when on DC to 115kbps

no special place to but this?

i added it just before hijack... now the click/stutter is away... but it's too late to start the car just to drive and do the serial trace...

The stalk itself has not changed

now here it is.. i startede by pressing source.. then vol+,vol-,track+,track-

then the buttons.. off first, the 3 when seen from above and lastly mute...

It still all looks normal.

Code:

Stalk: in=02 01 ff 00 == no button
Stalk: in=02 01 16 17 == 00000031
Stalk: out=02 01 16 17 == 00000031
Stalk: in=02 01 ff 00 == 80000031
..

Can you use the Radio with this player (eg. does the radio work?)?

For some reason, the player software is ignoring the stalk buttons.
This generally happens only if the radio is not detected,
or if the config.ini file says to disable the stalk.

Does this make the button on the end of the stalk work?

[ir_translate]
KSource=Source


??

Radio works fine... crystal clear sound

just testing the ir_translate you wrote.. be back in 15 min

Well, not quite normal, I suppose.
That sequence above is clearly the "KSource" button,
but for some reason it is being translated into 00000031
instead of the expected value of 00000011.

Is this a kernel you built yourself ??

-ml

nope... the alpa kernel... i'm not smart enough to build such things myself

i use this one: http://www.empeg.com/v3alpha/car-v3-alpha11/car2-developer-v3.00-alpha11.upgrade

i have also tried this one: http://www.empeg.com/v3alpha/car-v2.01/car2-developer-v2.01-final.upgrade

but no luck with that either

did not do the trick...

could 00000031 be used in ir_translate ?

Sure, like this:

[ir_translate]
00000031=Source

now i only have to do that for the rest..

and test it out... but i bet there is a more correct way to do it?

hmm...

could i do like this also:

[ir_translate]
00000031=KSource

Oh.. wait a sec.. 00000031 is the KSource+Shift button (KSSource).

I think you are either (1) pushing in the outer part of the end of the stalk (the "shift" collar), or perhaps it is *stuck* in.

The button on the end of the stalk (the KSource button) should be flush with the end of the stalk, not protruding.

But when the "shift collar" is pushed/stuck in, then the Ksource button will stick out by 2-3mm.

Check that on your stalk.

i guees it's stuck... because when i twist the wolume the seek/ams do not follow....

if i push the vol collar.. it jumps back.... i guees you use the vol collar as shift also....

Yes, that is the "Shift collar". The collar has no function when simply pushed, but pushing causes all of the other buttons/twists to have new/different meanings. Just like a "shift" key on a computer keyboard.

-ml

yeah but when i let go of the shift collar.. then it jumps back to normal....

so i guess the switch inside is stuck... can i take the stalk apart ?

Maybe.

I wonder what happens when you *do* SHIFT it and press source. Does it still send 00000031 then?

Because, if then it sends 00000011 instead, the switch is okay, just backwards.

i could try to have a look at the button code display... dont want to disturb the all the fol around us by starting the car...

but hang on and i will grab the codes from the display

Yes. I just took mine apart here to find out.

Be *very* careful not to drop any pieces. Do this at a table in the house, not in the car.

Remove the rubber mounting pads, and undo the three small pozidrive (phillips) screws. Keep the stalk upside down during all of this (KSource button at the bottom!!).

The switches are all on the removeable plate, and the "shift" switch is the larger yellow one:

anyway... do the player make use of all combinations? i mean is there any meaning for the shift function to work like it should?

Note that second photo above: there is a clear plastic plate just sitting there, only gravity holding it in place. I think this is what may be wrong in your stalk: that plate may be in the wrong location or something.

The player does use all of the codes, but if you are happy without them, then just remap the working ones only:

[ir_translate]
KSOff=KOff
KSSource=KSource
KSAtt=KAtt
KSFront=KFront
KSNext=KNext
KSPrev=KPrev
KSVolUp=KVolUp
KSVolDown=KVolDown
KSRear=KRear
KSBottom=KBottom

I'm going out to play ice-hockey in the park now.

Ciao!

looking at the button code display.. it does not matter if i shift or not... it gives me that same code for source and off ... so i guees the shift is stuck....

just want to tell about my stalk.... looks just like yours... but somehow the shift is still stuck...

well.. it's 01:28am... think i will sleep on this one

mark thanks a lot for the help... if you get an idea of what i could do to narrow this one let me know..

and you are right... dont shake on your hands while takeing those small screws out.... i dropped one between the seats... so have to take the seats out to get it... but have to take them out anyway... the electrical heat is dead so have to do some testing on the seats also

cheers :-D

If you don't think you need the shifted buttons, then just ignore the problem and use it as-is. That's not such a bad solution.

But to fix it, you'll have to dismantle it, and test the shift-switch to see if the switch itself is stuck, or simply worn-out or dead.

Cheers

Can he re-define the actions to the 'as-shifted' values?

but it would be nice to have them all

but it's like the shit does not work... it tried to take apart the stalk and push the buttons on the rubber mat...still the same...

and from juding the sound i dont think the mechanic part ever touch the shift button on the small pcb...

but testing the shift should be simple with a ohm meter?

did at test with the ohm meter... when i do pres shift there is a short between the 2 contacts on the jack... so the stalk works 100% as it should... now wonder what it could be... maybe a short somewhere in the tuner? it's one of those from PCA

Ahh.. good point. Yeah, the fault could be in there. I suppose it *must* be in the tuner, even.

The obvious thing to do is to ensure that there are no shorts between the three pins of the stalk jack in the tuner. There should be lots of resistance measured between (any two of) the three pins when the stalk is not connected.

Most likely pins 1,2 are shorted, which would make it appear that the shift button is being pressed.

Also, when the tuner is powered ON, pin 1 of the jack should measure close to +5V at no load. Measure that between pin 1 and pin 2 (GND). Alternatively, with power OFF, check for about 4-5Kohms resistance between pin 1 and the +5V pins in the tuner.

-ml

Actually, I suppose it's probably a short in the wiring of the actual stalk jack -- on a PCATS tuner this is an external jack, at the end of a small cable, right? (Factory tuners have the jack built-in).

For reference, on a properly wired PCATs stalk cable, BLUE is pin-1.

yep... i have yet to do the testing you said...

hmm... there is 3 colors... blue, red, orange... but in the big white box they do not tell where orange goes at the jack end

It goes to the only pin that doesn't already have a wire (blue or red) on it.

it says twin core screened wire... so i guess there should only be 2 wires, hence only 2 colours... and then the screen...

the screen goes to the pin in the middle....

just getting confused here

Ah, yeah, one wire leftover then.

just did a check up... there is no orange on my cable... but instead of orange the screen is used....

just have to messure the voltage

here it goes... useing the picture above as reference...

there is 5 volt between orange and red...

Check for shorts first, between any two of the three contacts.

oki.. back in 5 min or so... damn dark outside.. and no flaslight

well .... a short between the screen and the blue... just got it in for a better check

Good. Fix that, and your shift function will work correctly.

yepp.. you are right... works like a champ... but i thing the pins that connects the 2 boards has come loose... it cant lock to any station...

well... if i use the seek function it does not lock to anything... but if i take a preset it's ok... cant remember how to store the best stations automaticly tho

but thanks for alle the help mark... what would the empegs be without your support

Good. My apologies for taking so long to sort this one out.
As soon as you said "PCATS tuner" I should have remembered
the external stalk jack and directed you to check that first.

Getting rusty, I guess.

My favourite way to "tune" the tuner, is to use Hijack's knobseek magic "button". It's normally available from the Hijack PopUp0 menu: go into the main hijack menu, and assign PopUp0 to the (short) Knob Press Definition.

Then, tap (short press) the knob, and rotate it until KnobSeek appears, and tap it again to select. Now, the knob is a manual tuning dial, just like on a normal radio.

If you like it, you can use ir_translate to assign KnobSeek to one of the stalk buttons. This way, a press of that button will activate it, and twisting the stalk will tune forward/backward.

Cheers

no problem mate...

i read the manual for the player.. no section for the tuner

but is there a way to store all stations automatic?

and way cant it "scan" from one station to the next? it just scans forever.... because the stalk debug etc. is stil in the ini ?

I think the tuner scan function is broken in some versions of the firmware -- not sure which, though.

But you can manually tune to the stations you like, and save them as "tuner presets" through the menu system: Menu -> Radio -> Store .... After that, the Prev/Next buttons (or Left/Right on the front panel, will jump between the saved presets.

-ml

Scan doesn't work in 2.0 Final and 2.01 Final. The last 2.x release that tuner scan works in is 2 beta 13. As far as I can remember, tuner scan works in all v3 releases.

yeah it must be broken

i use the latest alpha... delevoper version

but i can live with it... and the stalk is awesome compared to the remote and steeringwhell remotes

the stalk it not just awesome.... it's freaking awesome when you have just spend 5 min with it... a shame that they did not get some oem's with the empeg logo

Yup, that's a known issue (with a workaround), and everything is now working as expected.

well.. doing it manually is ok... but sometimes it's more handy that it's true auto scan to the next station.. and rolling back just for that would be rather stupid from my point of wiev...

could i roll back... store the stations.. and then go to 3alpha11 without loosing presets?

never mind.... i just found a complete list of stations within 80 km... more than plenty

I've always found the manufacturer-supplied steering wheel controls much easier to get on with. The Sony stalk looks like an unsightly afterthought in most cars.

whell.. sadly peugeot did not think that far when they made the 106 in 1994... so i have placed the stalk at the right side just´between the arm for the windscren wiper and the dash... not much room but just enough to make it practical

at first it ver wierd to use.. but when you first get the hang of it there are no problems....

i have a pioneer steeringwheel remote... but it will go in a week... only keeping it as a backup until the Girlfriend has learned the stalk