News:

I have updated the spam detection on registrations, and as such I am enabling new users.  If we have spam, I will change it back to by approval.

Main Menu

Caught in the act? "CD-X" with Level10 diag logfile...

Started by jtnfoley, July 08, 2008, 02:17:05 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jtnfoley

Only took a night to reproduce the 'CD-X' failure this time... Generated a 3.5MB logfile in the process.
There are about 225 lines of output between the last successful song play and the bottom of the file. Below is the last page or so of lines in case they prove interesting.

VW PB, 7.02, recently hacked (this has been happening for years before tho) with a Monsoon HU. Red and Green LEDs on solid, disk spinning, 'CD-X' on the HU upon starting the car. My only recourse is to power cycle the HU.


23.46:51d  :rw_packet : ********************************************************
23.46:51d  :processpac: uC DEBUG: 0a 0c 04 03 80 7f 4d c3
23.46:51d  :rw_packet :        ce (206) ------------->
23.46:51d  :rw_packet : ********************************************************
23.46:51d  :processpac: Got Stop
23.46:phatd:stop_mp3pl: Stopping player
23.47:phatd:wait_child: Start child=14
23.58:phatd:wait_child: player exited normally (return code 1), sig 0 14
23.80:51d  :rw_packet : ********************************************************
23.80:51d  :rw_packet :              <============ e2 (226)
23.80:51d  :rw_packet :              <============ 8b (139)
23.80:51d  :rw_packet :              <============ 41 (65)
23.80:51d  :rw_packet :              <============ 27 (39)
23.80:51d  :rw_packet :              <============ 01 (1)
23.80:51d  :rw_packet :              <============ 52 (82)
23.80:51d  :rw_packet :              <============ 00 (0)
23.80:51d  :rw_packet :              <============ 70 (112)
23.80:51d  :rw_packet :              <============ 83 (131)
23.80:51d  :rw_packet :              <============ e5 (229)
23.80:51d  :rw_packet :        ce (206) ------------->
23.80:51d  :rw_packet : ********************************************************
23.81:51d  :processpac: uC DEBUG: 8b 41 27 01 52 00 70 83
28.81:51d  :main      : Auto PONG
28.81:51d  :rw_packet : Buffering 70 at 0
28.81:51d  :rw_packet : ########################################################
28.81:51d  :rw_packet :        70 (112) ------------->
28.81:51d  :rw_packet : Expecting HACK
28.82:51d  :rw_packet :              <============ ac (172)
28.82:51d  :rw_packet :        90 (144) ------------->
28.82:51d  :rw_packet : Expecting PACK
28.83:51d  :rw_packet :              <============ ce (206)
28.83:51d  :rw_packet : ########################################################
33.83:51d  :main      : Auto PONG
33.83:51d  :rw_packet : Buffering 70 at 0
33.83:51d  :rw_packet : ########################################################
33.83:51d  :rw_packet :        70 (112) ------------->
33.83:51d  :rw_packet : Expecting HACK
33.84:51d  :rw_packet :              <============ ac (172)
33.84:51d  :rw_packet :        90 (144) ------------->
33.84:51d  :rw_packet : Expecting PACK
33.85:51d  :rw_packet :              <============ ce (206)
33.85:51d  :rw_packet : ########################################################
34.38:51d  :rw_packet : ********************************************************
34.38:51d  :rw_packet :              <============ 61 (97)
34.38:51d  :rw_packet :              <============ 9f (159)
34.38:51d  :rw_packet :        ce (206) ------------->
34.38:51d  :rw_packet : ********************************************************
34.38:51d  :processpac: Got Shutdown

VorTechS

The last lines won't prove a lot, because these messages are fired in rapid succession until the box is shut down. 
Attach the entire log file.
Kenwood KDC-W7031 | Kenwood KHD-CX910 | 250GB DMS | PhatHack Media Manager v1.1.4 (Alpha) | VIOT

Catch me weekdays 8am-4pm GMT on IRC @ irc.freenode.net on channel #phathack (aka the chat link!!)

jtnfoley

Trying to wrap my mind around the upload restrictions...


jtnfoley


jtnfoley

Three of three.

I'm also going tolook at the logfile for a normal shutdown...

jtnfoley

Oh.. and I have VAG-COM (unlicensed) and can check stored codes in the HU... if it helps.

jtnfoley

Quote from: jtnfoley on July 09, 2008, 12:50:40 PM
Oh.. and I have VAG-COM (unlicensed) and can check stored codes in the HU... if it helps.

Needed to register VAG-COM (was going to do this anyway...) in order to get into the HU. Waiting on activation from them.
Interesting that when the dealership replaced the HU on warranty three years ago that they neglected to re-code it to be a Monsoon. I'll be fixing that shortly!

sbingner

I thought I fixed the upload size restrictions... but I'll make sure they're fixed again ;)

jtnfoley

OK... curiouser and curiouser...

I used VAG-COM to convince the radio that it has an attached CD changer by 'recoding.'  I could not convince the HU that it should be a monsoon... it refused to accept that bit.

After a few days I got a CD-X again and immediately plugged in VAG-COM. The radio had a stored code:
"00857 - CD Changer Unit (R41)"
"            49-00 No Communications"

I power cycled the PB and turned the HU back on, and then drove to work listening to the PB most of the way. With the PB still playing, I killed the engine and switched back to run, then fired up VAG-COM again to find:
"00857 - CD Changer Unix (R41)"
"            49-10 - No Communications - Intermittent"

I had no means of reading or setting codes before acquiring VAG-COM, so I don't know whether these codes existed every time I experienced CD-X or if this level of diag only became active when I re-coded the HU.

This CD-X problem has been going on pretty much since day one, with my initial thoughts along the lines of a thermal problem (did not seem to happen in winter here in the northeast US, but happens lots in the summertime.) Venting the disk cart and adding a heatsink to the bottom of the PB in the area of the power supply FET did not resolve...
Unplugging the PB so many times led to a broken connector, and the poor quality of the VW OEM connector led me to replace that connection with Molex. The problem is still repeating.

Firefox

If you can beg/steal/borrow another Phatbox i would bet your problem will be solved. Sounds more and more like a bad connection/bad component somewhere inside the Phatbox.

jtnfoley

Well, I really can't afford it right now but I DID bid on one on the 'bay... auction closes in about six days. We'll see if it helps.

jtnfoley

I took the time to rebuild the PB side of the cable... it was dropping a channel due to forever unplugging to hardboot the PB. While I was in there I improved the signal and power pins. I also put a momentary NC switch in the cable hoping to never use the thing. I had to use it this morning  :'(

We'll see what the future holds. For now I just will have to go into my trunk two or three times a week and reboot the PB.