Printable View
Hello
I am having problems with the red devil blue tooth adapter.
I can get data when I have my devices hard wired so my ADX file works.
blue tooth pairs with no problem.
Using the red devil blue tooth i get no communications with ecm.
I also changed the default baud rate in the adx file to 9600 and the same thing, no communications with ecm.
I don't know what else i can try so I am stuck. No word from the red devil web sight.
Any ideas would be great. Thanks
Dom
If you have no communication with the ECM it wont work period. What programme are you using? I'm just starting with this and my whole system is custom and I had some problems getting it going.
I'm using the red devil with ALDL droid blue toothed to a tablet or android phone. My first problem was the socket was wired wrong, my mistake. I had 160 baud going to the 8192 pin E and M reversed. Corrected this and got communication. Now my problem is the ADX file.
You need to look at the flashing led to determine the status of the unit. I'm not sure but your ADX file that worked with the other set up may not be right for this.
I'm getting data in but it wrong. I changed the same setting you did as well to 9600.
The other thing also is you may have to put a 10K resistor between pin A and B. This may be taken care of when you hard wire it, but I have to have the Resistor.
MQQN28 Thanks for the reply
The program i am using, ALDLdroid and Turner pro RT, the same adx file works for both devices and programs just not over the red devil. Green blinking light when the blue tooth connects.
I could try the 10k resistor easily.
I tried the 10k resistor between pin A and B. with engine running, blue tooth paired ALDLdroid not connected and the light on the red devil blinks red and when connected the red blinking turns solid blue and the service engine light turns on.
No resistor, Red devil light with no connection blinking green and turns solid blue when connected.
Blue light must be a bad thing. Still no data, not communicating with ECM.
thinking adx file,
Have you not heard back from Red Devil? I have heard their cust service is very lacking. I got my bluetooth device from John at 1320 electronics. Excellent customer service and he is on this forum as well.
Nothing from red devil. Wasted $80
Not giving up, Samsung Phone S8 and Samsung tablet E could also be the prob. just grasping at this point.
Dom
been away for a few days.
This seems to be where I was at one stage. The red devil is not seeing the data stream. My problem was I reversed the 160 and 8192 terminals when I wired up the ALDL socket my ECM an 808 160 baud. But this should not be your problem. The other thing I have just read is that the RED Devil does not like a pin on both E (160) and M (8192) of the socket. I'm not familiar with your ecm I take it is 8192.
On my system I know the data stream is running because the CEL light flashes, this seems to be what you get with the 10K resistor. The 10K resistor will start the data and can be removed. With 8192 it would appear to be full on.
I'm looking for some information I have on the red devil showing the led status, I have missed placed it.
I'm at the stage where I am receiving data but its not going where it should, I'm playing with the adx file.
Are you able to check if the data stream is getting to the right pin?
The other thing I'm using a Samsung S8 also and it seems to be working.
MQQN28
The pin that is sending data is M at 8192, if I use a wire adapter every thing works good , I would rather not have wires. No pin E.
Timm Becker got back to me asking for tuck info, and he said that there is already a 10k resistor built into it.
I looked at the info on the disk that came with it and 8192 would be a blue light with some other color blinking every few seconds, I get that just no data.
ALDLdroid after pressing the connect button i get a red bar on the bottom of the screen with no response from ecm.
DOM
I started mine up last night.
First you are right about the 10k resistor it will start with the built in one, I don't have to kick start it. When it connects the led is blue. Then it flashes green and red when the data starts.
At this point it should start for you. One other thing you could check is if you have an XDF file in the XDF directory. ALDL Droid checks this at start up. I know this seems strange as you only want to see it connect at the moment. But I just remembered that I had to put an XDF file into that directory. When mine starts I get a comment that the XDF file it could not be parsed properly. This could be why I'm still getting wrong data.
Next you could try this.
Try ALDL Scan app. Its easily obtained from play store.
It connects to the RED devil ok. From the menu select Vehicle protocol (ALDL file) pick one of the pre installed ones that suits you. Then select Adapter. Then press view data.
It should start when you touch the arrows icon.
This programme uses less baggage but at least you can see if the red devil is working.
What ever my problem is it is the same with both programs. Next step is to check my wiring again.
Dom
Another thing to try is check if the RS232 box is checked. When connecting with a cable this is checked, you may not need it with the box.
Look in the ADX file at the Header for <flags>0x10001</flags> or <flags>0x01</flags>. If its like this then the RS232 box is checked. When unchecked it will look like this <flags>0x10000</flags>.
Its probably better to edit this in tuner pro, when you uncheck it you can save the file with a different name.
MQQN28
Thanks , RS232 Echo box was checked, I unchecked it, I will give that a try and let you know.
Still nothing from red devil.
Edit
I tried with the Echo box unchecked and still the same, I might just have to cut my loss and buy the other one and hope I don't have the same problem, that would bite
Dom
My Red devil is finally working, but not without fixing some faults.
Your comment about the 10k resistor got me moving. I had it wired to a switch near the ALDL plug which was mounted behind the seat in the model A because this was close to the ECM, not a good place for the aldl. I have moved it to the equivalent of under the dash, which is under the tank in the model A. I got rid of the switch. If I left it on it was putting 2 10k resistors in parallel when the red devil switched, this wasn't sending the right mode wrong adx file also. The other problem was in extending the cables I damaged the data wire and had to find that little error. I am now getting data on Samsung S8 with ALDL Droid, so that works.
I just recently found an ADX file on the forum ($42-1228062-V1) that with modification will suit my $5D 160 baud.
Your problems may just be some editing in the ADX file for the red devil. When you connect the app you press connect to ECU this makes the red devil connect the 10K resistor to start the data stream.
In the ADX file you are using for the cable it has other commands to start the data stream, you may not need these commands.
<ADXCLISTENPACKET id="160BAUD" idhash="0xD05BBA9A" title="Data Transfer" flags="0x00000009">
<desc>Command to hook up to ECM and get data!</desc>
<listentimeout>400</listentimeout>
<packetbodylength>0</packetbodylength>
<packetoffsetinbody>0</packetoffsetinbody>
<packetsize>20</packetsize>
</ADXCLISTENPACKET>
This is a the only send command. As you are 8192 the packet info will be different. You could try a few edits. I think you only have to get the ADX right.
I also found a good description of the data stream for 160 baud $5D and will now edit up the adx. I just got the RPM parameter going first and starting to add the rest.
Don't give up keep going. At least you have a stock system, mine is all modified.
MOC
MQQN28
I don't know where to fine that string of code. This is a little over my head.
Have a go at putting up your ADX file.
Ill have a look. I'm not an expert but I may be able to come up with something.
Is any one else running 16168625 BDJZ to red devil and have an ADX file for this.
edit Found one right where it should be let me have a look and get back post yours any way. just for a look
Dom
Try this adx file and see if it works.
With ALDL Droid when you press connect ECU button it switches the 10k resistor and the data stream should start. The blue led will be flashing and then change to green yel/red.
If ALDL droid indicates no data stream check if the CEL light is flashing , probably look like it is full on. This will tell you if the data stream has at least started.
If this works your data may be a bit off due to this file, but we just want to see if the data stream starts.
If this doesn't work it may be another problem other than the ADX file or both.
Dom
sorry I put up the wrong file. I will change it and put the right one up in the morning.
MOC
Dom
try this one. Sorry about that busy day
MOC
I tried the 2nd file witch has the correct ECM number and I get a [connected waiting for ECM data] message. Never gets data.
Dom
Maybe back to basics
It's either the sensor state is not sending the message or the unit is not seeing the data.
Check pins A eth, B sensor, M 8192 data, G the blue tooth powers from this. This tag is fuel pump power
Is pin M actually in the right spot in the ALDL socket. When you get the message not seeing data is the CEL light flashing. If no the data has not started, if yes the data pin M is a problem.
I did read some where in the instructions from red devil that you may have to start the data by manually putting the 10k resistor in. This is a nuisance but if the data starts and works you know where you are. When working properly you connect the leds flash, press connect ECU the blue flashes then the other colors flash it connects and the data starts.
MOC
just tried and now not even Tuner Pro RT is not working.
Are you using the original ADX file for tuner pro?
Thank You MQQN28
I am giving up. I need to install an WB O2 sensor with gauge I can monitor that plus tune.
Dom
Sorry to hear that. I know mine was a battle at times but I got it, your initial query got me going again.
I'm at adjusting the ADX file at the moment but a little transmission problem has sidelined me. I will see the transmission man on the way home today.
When that problem is fixed I will be asking questions also.
MOC