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+.