AEM wideband not logging

dschultz · **Posted:** Sat Apr 09, 2022 9:30 am

Delete the rr_system.log and then reproduce the problem. The log will be smaller.
If it is still >2MB, zip it.

BlastinBlanks · **Joined:** Mon Jul 19, 2021 2:41 pm **Posts:** 101

dschultz wrote:

Delete the rr_system.log and then reproduce the problem. The log will be smaller.
If it is still >2MB, zip it.

gotcha

Attachment:

rr_system.log

dschultz · **Posted:** Sat Apr 09, 2022 8:15 pm

From the log, the important lines I see are:

Code:

56:52,886 INFO  [Query Manager] - Connected to: COM1
56:55,011 INFO  [Query Manager] - ECU ID = 1406464
56:55,011 INFO  [AWT-EventQueue-0] - CAL ID: 12, Car: 1996-1999 USDM BMW E36 M3 MS41.2 (256KB) MT/AT
java.io.FileNotFoundException: C:\Users\Husle\Documents\RomRaider.xml (The system cannot find the file specified)
57:41,665 DEBUG [AWT-EventQueue-0] - Adding logger:   [X_AEM_UEGO_Wideband_[9600_baud]] AEM UEGO Wideband [9600 baud]
57:41,674 INFO  [Thread-218] - AEM UEGO AFR [9600 baud]: connecting...
57:41,742 INFO  [AEM UEGO AFR [9600 baud]] - Connected to: COM3
57:41,746 INFO  [AEM UEGO AFR [9600 baud]] - Serial connection initialised: AemConnectionProperties[baudRate=9600, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=500]
57:41,751 INFO  [AEM UEGO AFR [9600 baud]] - AEM UEGO AFR [9600 baud]: connected.

Even though COM3 is open I don't see any data coming in. This is where you need to confirm that COM3 is correct and that data from the AEM controller is connected correctly to your serial->USB adapter.

If you just want to test the AEM in the Logger, uncheck ECU on the toolbar. This way you don't need to connect to the ECU to see the AEM logging results on the screen.

BlastinBlanks · **Joined:** Mon Jul 19, 2021 2:41 pm **Posts:** 101

dschultz wrote:

From the log, the important lines I see are:

Code:

56:52,886 INFO  [Query Manager] - Connected to: COM1
56:55,011 INFO  [Query Manager] - ECU ID = 1406464
56:55,011 INFO  [AWT-EventQueue-0] - CAL ID: 12, Car: 1996-1999 USDM BMW E36 M3 MS41.2 (256KB) MT/AT
java.io.FileNotFoundException: C:\Users\Husle\Documents\RomRaider.xml (The system cannot find the file specified)
57:41,665 DEBUG [AWT-EventQueue-0] - Adding logger:   [X_AEM_UEGO_Wideband_[9600_baud]] AEM UEGO Wideband [9600 baud]
57:41,674 INFO  [Thread-218] - AEM UEGO AFR [9600 baud]: connecting...
57:41,742 INFO  [AEM UEGO AFR [9600 baud]] - Connected to: COM3
57:41,746 INFO  [AEM UEGO AFR [9600 baud]] - Serial connection initialised: AemConnectionProperties[baudRate=9600, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=500]
57:41,751 INFO  [AEM UEGO AFR [9600 baud]] - AEM UEGO AFR [9600 baud]: connected.

Even though COM3 is open I don't see any data coming in. This is where you need to confirm that COM3 is correct and that data from the AEM controller is connected correctly to your serial->USB adapter.

If you just want to test the AEM in the Logger, uncheck ECU on the toolbar. This way you don't need to connect to the ECU to see the AEM logging results on the screen.

Wow man i just took a look at the db9 connector i bought off amazon and noticed one of the prongs was snapped. Took some solder to it and im logging like a lumber jack. Its been a journey. Nevertheless thanks again for the help schultz

Sent from my iPhone using Tapatalk

dschultz · **Posted:** Sun Apr 10, 2022 9:50 am

Thanks for the update. Happy logging.

ohnelader · **Joined:** Wed Apr 03, 2024 2:37 pm **Posts:** 10

dschultz wrote:

Thanks for the update. Happy logging.

Hi there! I have a similar issue with wideband logging. I read all threads here and everywhere, but I only found partial solutions. Hardware details:
-AEM UEGO X-series WBo2
-latest Romraider versions, definitions, etc (BMW MS42 ECU)

According to the AEM manual, I wired up the DB9 male connector. I have a USB-DB9 female adaptor. Installed the driver of the adaptor cable (Windows 10), and the connection check was successful on COM5. Checked with Putty, no incoming data.
Flipped the AEM serial wire (blue) from pin 2 to pin 3, ground still in pin 5, and Putty can read the data flowlessly. Out of curiousity, I put the ground in pin 1, same nice readings. If i disconnect the ground cable, no reading of course. Baud rate is 9600, with 19200 its not working.
So in theory, the signal reaches the PC. But still no readings in RR logger. I picked the correct port (COM5), the correct (and only) plugin, but nothing. I also made a short rr_system log file, attached. The only things I understand from it are: "AEM UEGO AFR [9600 baud]: connect error" & "Failed to open port: COM5"

I ran out of ideas, could anyone help me? I appreciate it.

dschultz · **Posted:** Sat Apr 27, 2024 8:31 pm

It appears you have told the Logger that the DME is on COM5 too.

Code:

35:45,749 DEBUG [Query Manager] - QueryManager started.
35:45,756 INFO  [Query Manager] - J2534 Library names loaded from file: ./customize/j2534Libraries.properties
35:46,248 INFO  [Query Manager] - Trying serial connection...
35:47,192 INFO  [Query Manager] - Connected to: COM5
35:47,196 INFO  [Query Manager] - Serial connection initialised: SerialConnectionProperties[baudRate=9600, dataBits=8, stopBits=1, parity=2, connectTimeout=2000, sendTimeout=55]
35:47,223 DEBUG [Query Manager] - ECU Init Request  ---> 12040016
35:47,224 TRACE [Query Manager] - Reading stale data
35:47,225 DEBUG [Query Manager] - Stale data read: 31302E380D0A31302E380D0A31302E380D0A31302E390D0A31302E380D0A31302E380D0A31302E380D0A


36:02,669 ERROR [AEM UEGO AFR [9600 baud]] - AEM UEGO AFR [9600 baud]: connect error
com.romraider.logger.ecu.exception.SerialCommunicationException: Failed to open port: COM5
36:03,870 INFO  [AEM UEGO AFR [9600 baud]] - Connection closed.

That stale data looks like your WBO2 data:
10.8
10.8
10.8
10.9
10.8
10.8
10.8

It's not the best error description, but it should say port is busy or in use.

Select a different port for ECU logging and set the AEM plugin to COM5.

ohnelader · **Joined:** Wed Apr 03, 2024 2:37 pm **Posts:** 10

ECU logging was on COM1, WBO2 on COM5. And ECU logging was working fine. As you told, I changed ECU logging to COM2, WBO2 still on COM5, and it started to log! So thank you very much for your help!

As you saw in the stale data, it reads like 10,8. Also Putty sees these numbers. As the gauge is switched to display Lambda value, it's actually 1,08. So it is one decimal away. When I switch the gauge to show AFR, the output is correct, 14,7 and around. Do you have an idea, what could be the reason for it? If not, it is still something I can handle in the data aquisition software.

Thank you very much again for your help!

dschultz · **Posted:** Thu May 02, 2024 8:25 pm

You can select different units to log the data in, but the Logger assumes the WBO2 is sending AFR values, not lambda.
A code modification would be needed to read lambda values natively.

RomRaider

Forum rules

AEM wideband not logging

Who is online