Well, I'm using 4800 baud right now because its what the ADX file is defining. Maybe I should try 160 baud and see what happen...
I will read that page as well.
Well, I'm using 4800 baud right now because its what the ADX file is defining. Maybe I should try 160 baud and see what happen...
I will read that page as well.
First off.... have you tested the ECU with a known working 160 baud software package and a "real" PC serial port to verify that some jack-wagon didn't send you a busted ECU (that works as far as he remembers but hasn't been used in years)?
If it passes that test, will it work with the same software and your USB to serial cable?
It's been a long time but I recall that the 160 baud software had some timing parameters that had to be tweaked to get it to work reliably and the serial port isn't actually set to 160 baud, it was something like 1600. I don't believe the 160 stream is a true serial protocol, it's just 160 bits per second.
I have never worked with 160 "baud" but from reading the material at the link on the prior page, it seems obvious that 1) the bits are sent in the opposite order from the 8192 system (msb first, instead of lsb first), 2) each bit has its own start and stop bit, and 3) the baud rate might be simulated by using a higher rate (1600) and testing each bit as a full 8-bit byte received. Note the reference to the result of "FE" just like your results. See the section titled: RS232 1600 baud Serial and ALDL 160 baud data.
Are you using 1600 baud?
Last edited by GaryDoug; 10-30-2013 at 10:08 PM.
I've been thinking about 160 baud.....
I assume that the bluetooth ALDL adapter you have is the one from Red Devil River and it says it supports 160 baud, so should work with your Android software as-is.
In order for theRed Devil River adapter to transmit the 160 baud data stream via bluetooth, the adapter has to convert the non-standard 160 baud stream to a standard UART style stream at whatever baud rate the bluetooth transmitter is running at.
So, if all the above is true, you only have an issue with your serial to USB adapter. The folks at Red Devil River have already figured out how to do this conversion inside their adapter (it has to have some sort of micro-controler inside it), maybe they can give you some insight as to what is needed to read the 160 baud data stream directly. I think you're gonna have to write your own library.
Mike, I did test the ECM with TunerPro, it works great. Looks like that jack-wagon sent me a good one :P
Robert, this is VERY useful! The annoying part is that java byte are obviously 8 bits. The FTDI drivers for USB only allow me to read a byte array. So, I'm thinking of doing something like this:
- Convert the byte array to binary
- Find the sync element
- Read all bits in chunk of 9 bits after the sync element
- Make sure the first bit of each chunk of 9 bits is 0.
- Extract the 8 bits (starting from second bits of each chunk) and build a new data array with all those 8 bits byte.
- Then I got my data array that I can forward to the other stuff just like I'm doing with the 8192 baud ECM
Gary, I'm curious where do you see the reference to FE ? I don't see it... I'm using 4800 baud, which is what is defined in the ADX. I think its fine... maybe ?!
Mike, yes, it's in the Red Devil River's instructions that 160 baud is supported. Currently I just need to move a jumper to make it work. I'm pretty sure I'm going to have to write my own thing, this app is over 10k lines of code of my own thing really :) I will start with what I mentioned above and I will email Timm (Red Devil River) if I'm really stuck. Timm really seems to be a nice guy from what I've seen so far but I don't want to be too annoying just yet. I will try a few things on my side.
You guys are awesome, we will figure this out :)
Hummm but thinking about this, I'm only getting "FE" or "0" back. 0 is obviously 00000000 and FE is 11111110 so with this in mind, it mean I'm somehow never getting the sync character (9 consecutive "1").
I'm stuck :/
Sorry, that was found in a link within the posted link document: Further, and more recently written, 160 baud information can be be found here.
I wouldn't assume that the interface adapter does anything fancy with any decoding. It's probably just a Serial-to-Bluetooth type. I would be very surprised to find anything more sophisticated inside, like anything along the line of an ELM327 (OBD2 multi-protocol decoder) or something.
Last edited by GaryDoug; 10-31-2013 at 03:34 AM.
Yeah, I'm leaving the Bluetooth adapter out of the equation for now. I'm getting the same thing over both Bluetooth and USB right now tho. The most consecutive "1" I'm getting is 7 and I need 9 for the sync character :|
Do I assume correctly that you don't have access to a scope to view these signals? For what it's worth, and just for kicks, I just ordered an 86 Z28 PCM for cheap and will take a look at its data output.
Correct, I don't have access to a scope :P Cool, let me know what you found!
Here is the data at different baud rate. The thing is, there is something else then the baud rate that is wrong because I'm always getting only two different byte values for some reason...
At 160 baud:
ff 80 80 80 80 80 80 80 80 80 80 ff ff ff ff ff ff 80 ff ff
80 80 ff 80 ff ff ff ff ff ff ff ff 80 80 ff 80 80 ff ff ff
At 1600 baud:
ff ff c0 c0 c0 ff c0 c0 c0 ff c0 ff ff ff ff ff ff ff ff c0
c0 ff c0 c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff c0 ff ff c0 ff c0 ff ff ff ff ff ff ff ff ff c0 ff ff ff
At 1800 baud:
80 80 ff 80 ff ff ff ff ff ff ff ff 80 80 ff 80 80 ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff 80 ff ff 80 ff 80
ff ff ff ff ff ff ff ff ff 80 ff ff ff ff ff ff ff ff 80 80
At 4800 baud:
fe 00 fe fe fe fe fe fe fe fe 00 00 00 00 fe fe fe fe 00 fe
fe fe fe fe fe fe 00 00 00 fe 00 fe fe 00 fe 00 fe fe fe fe
fe fe fe fe fe fe fe fe fe fe 00 00 00 00 00 00 00 00 00 00
I'm sure this will all become evident once the solution is found. Now you have my curiosity piqued.
Yes, I hope it will be soon, I'm really confused by this right now :/
Do we need to add any other apps or drivers of sorts for ftdi support on android? Also are there any decent serial port apps? I just want to see I'd my tablet will listen on the serial bus to to verify my cable will work with my tablet
Bookmarks