InDashPC.org

[boone711]

I have a question about how the COM port data is being encoded/decoded. When I received an updated chip for my Car2PC adapter, it was left in debug mode (DB1) instead of default (DB0; see Car2PC API on the forums).

In my 2004 Acura TSX w/Nav the interesting thing was that I could see all sorts of traffic even if unrelated directly to the stereo. The first thing I noticed was that user interaction with any of the devices in the car would show up. I could decode a line that updates the volume number and current AC mode (which get sent to the nav screen when either is changed).

The best part was that I could read touchscreen coordinates when pressing the touchscreen. I identified sets of numbers that would go up or down depending on where i pressed on the screen (more to the right would be higher in one set, lower on the screen would be higher in another set, etc).

If I could interpret these lines as they occur I could have basic touchscreen interaction my Car PC. Unfortunately I cannot get the data to show in the same format that it appears in the grom console program. Any time I try to read the data in homebrewed programs, serial port loggers, or hyper terminal, it shows random characters and does not locate the line return characters (etc). I am familiar with ASCII/Hex and have tried all types of methods of reading the COM port data and different encoding but to no avail.

If anybody knows much about the stuff any info would be appreciated. I dont know where to go at this point.

Thanks,

Travis

[jbors]

Basically the RAW data from the bus come in binary form.
You will need to switch hyperterm into Binary mode to get it.
The format as follows:
FF <LEN> 0x43 0x4D <binary data>

[Louk]

[jbors]

Yes, you have to switch device into PS1 mode.
The CDC emulation will turn off.
Here is the CDC emulation script (may not work work for your car though)

[Louk]