VW Phatbox -> Alpine M-BUS(BMW) -> Honda'06 problem ("PW Auth failed - wrong PWi

[shoora]

I have Honda Odyssey'06 and want to hookup PhatBox to my factory head unit. Previously I thought of Sony adapter. But PB on SONY does not have SSA.
BMW interface is a M-Bus with pullup resistor to +5V instead of +12V (in opposite to Alpine HU). Is there any other difference?
I bought PAC AAI-HON (same as Peripheral HONASX ) M-Bus/AUX adapters.
On first start it blinks green light for minute or two. Then it restarts and then it only ocasionally blinks green light. Looks like it just writes log file and nothing more.
In get error message "PW Auth failed - wrong PWid" in my logfile.txt. What does it mean?
Here is some parts of my log:

Code: [Select]

05.94:phatd:main      : Media Daemon (phatd) $Revision: 1.217 $
05.96:phatd:main      : Debug level = 10
Selected profile is: Default
06.28:phatd:main      : Using /dos/exec.ini for exec.ini
06.39:phatd:fork_if_in: Spawning /dos/51d
06.40:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
07.16:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

07.16:51d  :main      : Debug level = 10
07.16:51d  :main      : Force update file found
could not open drive id file
could not get pw header
08.47:phatd:match_enc_: Find PWid: 1
 in
08.47:phatd:match_enc_: PW Auth failed - wrong PWid
08.47:phatd:match_enc_: 08.47:phatd:match_enc_: PWid: 1
08.47:phatd:check_inst: PW Auth failed - will not install
08.58:phatd:check_inst: Added PWid 2, value 0
08.59:phatd:main      : Entering Main loop
08.59:phatd:wait_child: Start child=0
08.69:phatd:wait_child: PID 0 ended
08.69:phatd:check_dead: sync process done
08.70:phatd:main      : Socket 2 has MSG_ID 2
08.95:51d  :openserpor: /dev/ttyS1 open fd=11
08.95:51d  :main      : Old ISP timeout value set to 50000 uSec
08.96:51d  :main      : Rollins timeout value set to 100000 uSec
08.96:51d  :test_uC_ve: f9 (249) ------------>
08.97:51d  :test_uC_ve: <============ 53 (83)
08.97:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
08.97:51d  :parse_pac : opening /dos/firmware.pac
08.97:51d  :parse_pac : PAC file summary
08.97:51d  :parse_pac : firmware name h: 22
08.97:51d  :parse_pac : firmware name l: 00
08.97:51d  :parse_pac : firmware ver   : 08
08.97:51d  :parse_pac : firmware base h: 0f
08.97:51d  :parse_pac : firmware base l: fd
08.97:51d  :parse_pac : firmware size h: 15
08.97:51d  :parse_pac : firmware size l: 60
08.98:51d  :send_arm_s: firmware_modification=2
could not get pw header
09.76:phatd:match_enc_: Find PWid: 1
 in
09.76:phatd:match_enc_: PW Auth failed - wrong PWid
09.76:phatd:match_enc_: 09.76:phatd:match_enc_: PWid: 1
09.76:phatd:check_inst: PW Auth failed - will not install
09.85:phatd:check_inst: Added PWid 2, value 0
09.85:51d  :rw_packet : Buffering 10 at 0
09.85:51d  :rw_packet : ########################################################
09.85:phatd:wait_child: Start child=0
09.85:phatd:wait_child: PID 0 ended
09.85:phatd:check_dead: sync process done
09.85:51d  :rw_packet : 10 (16) ------------->
09.85:51d  :rw_packet : Expecting HACK
09.86:51d  :rw_packet : <============ ac (172)
09.86:51d  :rw_packet : 08 (8) ------------->
09.86:51d  :rw_packet : Expecting BACK
09.87:51d  :rw_packet : <============ bd (189)
09.87:51d  :rw_packet : 22 (34) ------------->
09.87:51d  :rw_packet : Expecting BACK
09.88:51d  :rw_packet : <============ bd (189)
09.88:51d  :rw_packet : 00 (0) ------------->
09.88:51d  :rw_packet : Expecting BACK
09.89:51d  :rw_packet : <============ bd (189)
09.89:51d  :rw_packet : 01 (1) ------------->
09.89:51d  :rw_packet : Expecting BACK
09.90:51d  :rw_packet : <============ bd (189)
09.90:51d  :rw_packet : 02 (2) ------------->
09.90:51d  :rw_packet : Expecting BACK
09.91:51d  :rw_packet : <============ bd (189)
09.91:51d  :rw_packet : 07 (7) ------------->
09.91:51d  :rw_packet : Expecting BACK
09.92:51d  :rw_packet : <============ bd (189)
09.92:51d  :rw_packet : bc (188) ------------->
09.92:51d  :rw_packet : Expecting PACK
09.93:51d  :rw_packet : <============ ce (206)
09.93:51d  :rw_packet : <============ 11 (17)
09.93:51d  :rw_packet : <============ 00 (0)
09.93:51d  :rw_packet : <============ 00 (0)
09.93:51d  :rw_packet : <============ 32 (50)
09.93:51d  :rw_packet : <============ 01 (1)
09.93:51d  :rw_packet : <============ bc (188)
09.93:51d  :rw_packet : ########################################################
09.93:51d  :rw_packet : ce (206) ------------->
09.93:51d  :rw_packet : ********************************************************
09.93:51d  :processpac: Got Session: mode 0, run type 0, lot 32 01
09.94:phatd:log_bc    : CPUid info:
Unique ID: 0xcc0a1690
Random ID: 0xcc0a1690b1b18dcf7fb505bab3379528
CPU: EP73xx, ver 0x02
Lot Code: 0x3201
09.95:phatd:log_bc    : Writing CPUid MRU
10.18:phatd:log_bc    : Adding to CPUid log
10.27:51d  :processpac: Initializing 1.2 DAC
10.36:51d  :processpac: Non-text head unit - will not load text



[shoora]

Here is my logfiles.

[sbingner]

That is in reference to a plugin... but it doesn't look like it's causing any problems.  If you want it to go away, rename your plugins directory on PHTSYS

[shoora]

That is in reference to a plugin... but it doesn't look like it's causing any problems.  If you want it to go away, rename your plugins directory on PHTSYS

Thanks.
I don't see other problems reports in my logfile. What else could be wrong? Looks like BMW M-bus interface just does not work with HONASX (AAI-HON) adapter
By the way, do you know how big current from Phatbox takes from ACC? Inside of adapter they have only small surface mounted transistor to control ACC and too big current will kill it.
Temporarily I just solder ACC wire to +12V -don't think it make a problem for protocol?

[S80_UK]

By the way, do you know how big current from Phatbox takes from ACC? Inside of adapter they have only small surface mounted transistor to control ACC and too big current will kill it.
Temporarily I just solder ACC wire to +12V -don't think it make a problem for protocol?

The ACC current into the Phatbox is very low - it is just used to enable other things to work.  All the real power comes through the regular power lines, so don't worry about the size of the components.  (Actually, you'ld be amazed just how much current some small surface mount parts can carry if they are correctly designed, so long as they are switched fully on or fully off.  They only get hot when they are not correctly used.)

Also, rather than solder the ACC to +12V, it's not essential, but I would generally recommend connecting it through a resistor to limit the current (helps prevent things going bang in case of mistakes).   I'd recommend a resistor of maybe a few hundred ohms or so.  That will still give a very good "power on"  signal to the box.

[sbingner]

You should try listening to the raw audio output to see if the phatbox actually plays and it's just not getting to your head unit...

That is, if you see anything in the logfile beyond what you posted... you should see it PLAY a file, if you don't... odds are it's never getting a play signal from the HU

[shoora]

FYI.
Seems like PhatNoise does not work with PAC AAI-HON adapter.
Basically what I did.
I've used multimeter to test voltage on M-Bus. And don't see anything.
It's open collector line, so I pulled it up to +5V with 2KOhm resistor and signal diode. In addition to that I solder 5V zener diode directly to connector pin.
Strangely, I could not find where signal ground goes on PCB, but it's not directly connected to the ground. But it is connected to the ground on PhatNoise.
Unfortunately I don't have any M-bus device to verify that this adapter actually works.

--Alex

P.S. I am now considering Sony or Kenwood(if I can find one) adapter.

[shoora]

You should try listening to the raw audio output to see if the phatbox actually plays and it's just not getting to your head unit...

That is, if you see anything in the logfile beyond what you posted... you should see it PLAY a file, if you don't... odds are it's never getting a play signal from the HU

Exactly! I don't see any PLAY of SEEK or STOP or anything like that in my log files. What make me think that PhatNoise is not fully compatible with M-bus. May be it is some kind of protection.

[az1324]

I have gotten BMW firmware to work with a Blitzsafe Honda to Alpine adapter with one problem:  because of the way the cd changer communication was designed in M-bus the Blitzsafe BMW to Alpine adapter sends random-next and random-previous commands for track changes instead of goto song xx commands.  unfortunately the other adapters do not use the same commands and are not processed by the phatbox.  so you can never use the next,prev commands which is a slight problem.  Other than that you should be able to get it to play on an Mbus adapter.

[shoora]

Unfortunately Blitzsafe does not have adapters for new hondas And they not going to. I have confirmation from support department.
Though I will try PIE HON03/PC-ALP. If this will not work, we may consider this question closed.

[sbingner]

I have a HON03-PC/ALP that I didn't manage to get working... although I may have done something wrong.

If you want to buy it from me you can have it for say... $40 + shipping?

[az1324]

Unfortunately Blitzsafe does not have adapters for new hondas And they not going to. I have confirmation from support department.
Though I will try PIE HON03/PC-ALP. If this will not work, we may consider this question closed.

Ok but just know that if there isn't a way to put it into random mode you aren't going to be able to use the track next/prev functions.

[shoora]

I have a HON03-PC/ALP that I didn't manage to get working... although I may have done something wrong.

If you want to buy it from me you can have it for say... $40 + shipping?

HON03-PC/ALP does not work either