Author Topic: Problem with home made Music Keg cable  (Read 12703 times)

0 Members and 3 Guests are viewing this topic.

Offline busvol

  • Newbie
  • Posts: 12
Problem with home made Music Keg cable
« on: July 14, 2005, 06:58:52 pm »
Hi everyone,
I have (had) a converted Phatbox running with a Kenwood HU for a week. At first everthing was fine with the homemade cable, only the right audio channel was dead ( bad solder connection). So I thought no big deal to fix, but ever since I tried to reconnected the cable the unit will do the short boot sequence - the red solid and green light flickering and both go off. I also tried reloading the firmware and start over gain. I measured each strand of the cable for conductivity and it seems fine. The HU just does not recognize the Phatbox anymore.
Any ideas what might be wrong? Is the problem in the Phatbox, the Hu or the cable. I hope I didn't fry the HU or the phatbox.
Cheers

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Problem with home made Music Keg cable
« Reply #1 on: July 14, 2005, 07:11:35 pm »
You mean it will do that when you first connect it?  That's just an initial powerup sequence to initialize things.   Does it power up at all when you turn on your head unit?

If not, you could have an issue with your ACC line (is it a Kenwood head unit?)

Offline busvol

  • Newbie
  • Posts: 12
Re: Problem with home made Music Keg cable
« Reply #2 on: July 14, 2005, 07:19:34 pm »
It's a KDC-MP225 HU. When I connect the cable to the HU (still powered off) the the red light will go on solid and the green starts flashing, after 15sec or so both go off. Seems like no power issue?
When I try to select the phatbox from the HU after switching it on it will not show up.
The strange thing is that I already had it working fine (except the right audio channel) but now it will not be recognized by the HU.

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Problem with home made Music Keg cable
« Reply #3 on: July 14, 2005, 07:50:25 pm »
er, I forgot that the kenwood setup doesn't USE an acc line... check pin 10 on headunit side to pin 24 on the phatbox, thats what kenwood uses to turn it on

Offline busvol

  • Newbie
  • Posts: 12
Re: Problem with home made Music Keg cable
« Reply #4 on: July 15, 2005, 04:01:05 pm »
Hi Sbingner,
thanks for the advice, but I couldn't get it working. The pin 10 to pin 24 strand seems to be in perfect order.
Now I am ready to try a more directed approach to troubleshoot the 3 components. Is there a way to create an error log of what's going on when you try to connect the phatbox and go from there? Somehow I suspect either the connection to the HU or the phatbox faulty since I measured all strands of the cable and that gives me no dead or high resistance wire.
Unfortunately I only have a standard digital Voltmeter to do any testing.
At some point I probably give in and order the keg cable for $50.

I just don't want to give up yet.

I'd appreciate any advice.
« Last Edit: July 15, 2005, 04:01:37 pm by busvol »

Offline Firefox

  • Needs to get outside.
  • ***
  • Posts: 124
  • Kenwood 710 Keg 80GB ;-)
Re: Problem with home made Music Keg cable
« Reply #5 on: July 15, 2005, 04:31:10 pm »
Sounds similar to my failed Keg a few months back -
pity the old forums have gone, there was a great thread describing lots of tests that you could try (from Ryan at PN) including making sure the hex nuts on the keg connector are tight in (or removed for the test) - but the best way to 100% prove it is to locate another Keg user near you and try your keg on their cable and H/U. I was lucky I got help from a guy 10 miles from me - one quick test and the old Keg went in the skip.

Seriously, you could waste a lot of time otherwise!
Hope you get it sorted.

Offline busvol

  • Newbie
  • Posts: 12
Re: Problem with home made Music Keg cable
« Reply #6 on: July 15, 2005, 05:33:21 pm »
Good idea.
Is there any Phatbox/Music keg owner to help me out in the San Diego area?
Cheers

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Problem with home made Music Keg cable
« Reply #7 on: July 15, 2005, 10:30:46 pm »
You could put the debug 10 rc.sh on it, and boot it up... see if that tells you anything

Offline busvol

  • Newbie
  • Posts: 12
Re: Problem with home made Music Keg cable
« Reply #8 on: July 15, 2005, 10:50:35 pm »
Could you please specify, where I can get the file and what to do?
I am lost here.
Thanks

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Problem with home made Music Keg cable
« Reply #9 on: July 15, 2005, 11:37:15 pm »
http://downloads.phathack.com/bushing/rc_pairs.zip

replace your rc.sh and rc.sig then delete your logfile.txt and try to boot it up... hopefully you get some info in logfile.txt on PHATSYS

Offline busvol

  • Newbie
  • Posts: 12
Re: Problem with home made Music Keg cable
« Reply #10 on: July 26, 2005, 05:21:58 am »
That's what I get in error_log.txt:
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null
CORRUPT_FILE: /dev/null

Any clues?
Peter

Offline busvol

  • Newbie
  • Posts: 12
Re: Problem with home made Music Keg cable
« Reply #11 on: July 26, 2005, 05:41:12 am »
This is the logfile.txt content after booting:

06.66:phatd:main      : Media Daemon (phatd) $Revision: 1.226 $
06.69:phatd:main      : Debug level = 10
06.69:phatd:dac_clock_: Set DAC clock mode to 0
Selected profile is: Default
06.96:phatd:main      : Using /dos/exec.ini for exec.ini
07.05:phatd:fork_if_in: Spawning /dos/51d
07.06:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
07.59:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

07.59:51d  :main      : Debug level = 10
could not open drive id file
could not get pw header
08.52:phatd:match_enc_: Find PWid: 1
in
08.52:phatd:match_enc_: PW Auth failed - wrong PWid
08.52:phatd:match_enc_: 08.52:phatd:match_enc_: PWid: 1
08.52:phatd:check_inst: PW Auth failed - will not install
08.52:phatd:main      : Entering Main loop
08.53:phatd:wait_child: Start child=0
08.55:phatd:wait_child: PID 0 ended
08.55:phatd:check_dead: sync process done
08.56:phatd:main      : Socket 2 has MSG_ID 2
08.82:51d  :openserpor: /dev/ttyS1 open fd=11
08.82:51d  :main      : Old ISP timeout value set to 50000 uSec
08.82:51d  :main      : Rollins timeout value set to 100000 uSec
08.82:51d  :test_uC_ve:

f9 (249) ------------>
08.83:51d  :test_uC_ve:



<============ 53 (83)
08.83:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
08.83:51d  :parse_pac : opening /dos/firmware.pac
08.83:51d  :parse_pac : PAC file summary
08.83:51d  :parse_pac :
firmware name h: 02
08.83:51d  :parse_pac :
firmware name l: ff
08.83:51d  :parse_pac :
firmware ver   : 0c
08.83:51d  :parse_pac :
firmware base h: 0f
08.83:51d  :parse_pac :
firmware base l: fd
08.83:51d  :parse_pac :
firmware size h: 26
08.83:51d  :parse_pac :
firmware size l: f0
08.84:51d  :send_arm_s: firmware_modification=21
06.65:phatd:main      : Media Daemon (phatd) $Revision: 1.226 $
06.65:phatd:main      : Debug level = 10
06.65:phatd:dac_clock_: Set DAC clock mode to 0
Selected profile is: Default
06.92:phatd:main      : Using /dos/exec.ini for exec.ini
07.01:phatd:fork_if_in: Spawning /dos/51d
07.02:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
07.55:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

07.55:51d  :main      : Debug level = 10
could not open drive id file
could not get pw header
08.49:phatd:match_enc_: Find PWid: 1
in
08.49:phatd:match_enc_: PW Auth failed - wrong PWid
08.49:phatd:match_enc_: 08.49:phatd:match_enc_: PWid: 1
08.49:phatd:check_inst: PW Auth failed - will not install
08.49:phatd:main      : Entering Main loop
08.49:phatd:wait_child: Start child=0
08.52:phatd:wait_child: PID 0 ended
08.52:phatd:check_dead: sync process done
08.53:phatd:main      : Socket 2 has MSG_ID 2
08.79:51d  :openserpor: /dev/ttyS1 open fd=11
08.79:51d  :main      : Old ISP timeout value set to 50000 uSec
08.79:51d  :main      : Rollins timeout value set to 100000 uSec
08.79:51d  :test_uC_ve:

f9 (249) ------------>
08.80:51d  :test_uC_ve:



<============ 53 (83)
08.80:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
08.80:51d  :parse_pac : opening /dos/firmware.pac
08.80:51d  :parse_pac : PAC file summary
08.80:51d  :parse_pac :
firmware name h: 02
08.80:51d  :parse_pac :
firmware name l: ff
08.80:51d  :parse_pac :
firmware ver   : 0c
08.80:51d  :parse_pac :
firmware base h: 0f
08.80:51d  :parse_pac :
firmware base l: fd
08.80:51d  :parse_pac :
firmware size h: 26
08.80:51d  :parse_pac :
firmware size l: f0
08.81:51d  :send_arm_s: firmware_modification=21
06.65:phatd:main      : Media Daemon (phatd) $Revision: 1.226 $
06.65:phatd:main      : Debug level = 10
06.65:phatd:dac_clock_: Set DAC clock mode to 0
Selected profile is: Default
06.92:phatd:main      : Using /dos/exec.ini for exec.ini
07.01:phatd:fork_if_in: Spawning /dos/51d
07.02:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
07.56:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

07.56:51d  :main      : Debug level = 10
could not open drive id file
could not get pw header
08.49:phatd:match_enc_: Find PWid: 1
in
08.49:phatd:match_enc_: PW Auth failed - wrong PWid
08.51:phatd:match_enc_: 08.51:phatd:match_enc_: PWid: 1
08.51:phatd:check_inst: PW Auth failed - will not install
08.51:phatd:main      : Entering Main loop
08.51:phatd:wait_child: Start child=0
08.54:phatd:wait_child: PID 0 ended
08.54:phatd:check_dead: sync process done
08.55:phatd:main      : Socket 2 has MSG_ID 2
08.81:51d  :openserpor: /dev/ttyS1 open fd=11
08.82:51d  :main      : Old ISP timeout value set to 50000 uSec
08.82:51d  :main      : Rollins timeout value set to 100000 uSec
08.82:51d  :test_uC_ve:

f9 (249) ------------>
08.83:51d  :test_uC_ve:



<============ 53 (83)
08.83:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
08.83:51d  :parse_pac : opening /dos/firmware.pac
08.83:51d  :parse_pac : PAC file summary
08.83:51d  :parse_pac :
firmware name h: 02
08.83:51d  :parse_pac :
firmware name l: ff
08.83:51d  :parse_pac :
firmware ver   : 0c
08.83:51d  :parse_pac :
firmware base h: 0f
08.83:51d  :parse_pac :
firmware base l: fd
08.83:51d  :parse_pac :
firmware size h: 26
08.83:51d  :parse_pac :
firmware size l: f0
08.84:51d  :send_arm_s: firmware_modification=21

Any clue what is wrong?
Cheers
Peter