Logging PLX SM-AFR wideband

flinkly · **Posted:** Wed Jul 24, 2013 6:35 pm

so I'm having the exact same problem (I can get romraider to read a single datapoint of reasonable AFR data, but no more) ...

first off, I can't plug in my 3.5mm jack all the way into the PLX sensor module or I just get "10"s and not real AFR data. so I figured out that issue (just don't seat the jack all the way in) and I can read "real" data thru putty. I did collect a bunch of that data and converted it to hex and all my packets start and stop with 80 and 40 respectively. so I don't seem to be having that issue. I have the com port selected correctly in romraider, and I have my usb to COM port driver setup to the PLX specs (19200 8n1 ) that are given in their development PDF.

I'm at a loss as to how I can get romraider to take my plx data for more than the first millisecond. :cry:

EDIT: I do also have a PLX boost guage/sensor that i'm going to attempt to read thru romraider and/or putty and see what I get from that.

dschultz · **Posted:** Wed Jul 24, 2013 6:38 pm

Can you also send the rr_systm.log?
http://www.romraider.com/RomRaider/HowToDebug

flinkly · **Posted:** Wed Jul 24, 2013 6:47 pm

I believe i'm getting the 4032 error, PLX device not recognized. I also attempted to turn on all the PLX devices in romraider to see if my AFR data was coming in as another device, but to no avail.

EDIT: sorry, I didn't delete my log file and recreate it with my issue. it's there near the end, but there's all sorts of other crap in there, like me trying to change com ports and baud rates.

Code:

371803 INFO  [Thread-116707] - PLX SM-AFR: connecting...
371833 INFO  [Thread-116707] - Connected to: COM4
371833 INFO  [Thread-116707] - Serial connection initialised: PlxConnectionProperties[baudRate=19200, dataBits=8, stopBits=1, parity=0, connectTimeout=2000, sendTimeout=500]
371833 INFO  [Thread-116707] - PLX SM-AFR: connected.
371943 ERROR [Thread-116717] - Error occurred
java.lang.IllegalArgumentException: Unknown PLX Sensor Type: 4032
   at com.romraider.logger.external.plx.plugin.PlxSensorType.valueOf(Unknown Source)
   at com.romraider.logger.external.plx.io.PlxParserImpl.pushByte(Unknown Source)
   at com.romraider.logger.external.plx.io.PlxRunner.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
372085 INFO  [Thread-116717] - Connection closed.

dschultz · **Posted:** Wed Jul 24, 2013 7:05 pm

It would be much more helpful if you can delete the rr_system.log to create a new clean one and log at DEBUG level. The log you posted does not have enough detail.

BTW: If you un-check both ECU and TCU in the Logger toolbar you can log the PLX data item all by itself with no active ECU connection. This would provide the cleanest DEBUG log.

flinkly · **Posted:** Wed Jul 24, 2013 7:33 pm

Done.

it comes on, gives me a single value and never updates (to the next/current value). turned it off and on and it gives me a new value, but stops with that one value. tried some different menu settings (as you can see in the debug file).

dschultz · **Posted:** Thu Jul 25, 2013 3:47 am

There's an odd sensor type value in your data stream.

Code:

80 00 00 00 01 2f 3f 00 00 00 00 40

80 is the Start of the packet
The next two bytes (00 00) make up the sensor address or Type in RomRaider
The next byte (00) is the instance
The next two bytes (01 2f) is the sensor raw value
The next byte (3f), because it is not the end of packet (40), it should be the next sensor address (or type) but there is no definition for that value in the PLX app notes.

What is in your PLX chain? Can you provide the part/model numbers?
Thanks

flinkly · **Posted:** Thu Jul 25, 2013 2:55 pm

well, i'll get more exact numbers when I get to the paperwork, but the items I have from PLX are the SM AFR sensor module, SM AFR DM-5 gauge (don't seem to sell DM-5's anymore), a boost sensor module and a boost DM-5 gauge.

Now I am only hooking my FTDI cable (TTL-232R-3V3-AJ) into the AFR DM-5 gauge output, and the DM-5 is plugged into the SM-AFR sensor module output. I didn't get the boost gauge to log it really, but I was thinking about hooking it up into a chain after I got the wideband working.

I also do have a D-link 4 port usb hub in the dash that my tactrix 2.0 and FTDI cable are plugged into before coming out in a single usb cable to my laptop. now that we're talking about it, i'll remove the hub from the system, see if it starts working, and then plug straight into the sensor module to see if it starts working. after that, I guess it's talking to PLX about my sensor not sending good signals.

just to note it, my guage reads just fine, but I guess it's probably just ignoring the extra info in the packet. and when I was looking into this myself and converted the packet to hex, I was surprised by it's length compared to PLX's example. didn't notice that the data spanned 3 "bits" though, just surprised there was so much blank before the stop bit.

dschultz · **Posted:** Thu Jul 25, 2013 4:01 pm

I don't think the USB hub will cause any issues as this data is from the PLX stream and has nothing to do with USB. It's all before your serial to USB converter.

Since you own these PLX devices maybe you can open a support ticket with them to ask about the 3f 00 00 00 00 byte sequence. Maybe they defined a new sensor address but never updated the APP note on their support web site.

In the meantime I can code in a check and drop that sensor data when it's seen so the valid sensor data can still be logged. This will be in the next release.

discojon · **Joined:** Sat Nov 30, 2013 4:45 pm **Posts:** 17

Bumping this because i'm having the exact same freezing issue. I am getting an unknown device error as well. I recently had this exact issue with an innovative LC-2 and went with the PLX to try and remedy it but now I'm getting the same issue again. I have attached a debug level log. Please take a look at it and let me know what i need to do to get this car finished.

dschultz · **Posted:** Fri Mar 07, 2014 3:10 am

I see this:

Code:

java.lang.IllegalArgumentException: Unknown PLX Sensor Type: 25

But there's not enough log info to see the packet the device sent. You need to log at TRACE level for that.

discojon · **Joined:** Sat Nov 30, 2013 4:45 pm **Posts:** 17

I'll go log at trace level and update this post. Give me a few

discojon · **Joined:** Sat Nov 30, 2013 4:45 pm **Posts:** 17

Heres the trace level log file. The SM-AFR is the newest V3 if that matters. If there is anything we can do to get this working it would be greatly appreciated. The AFR reads just fine on my VBG-1 using the plx trs cable connection btw. It's just RR that wont read. Let me know if you need anything else.

discojon · **Joined:** Sat Nov 30, 2013 4:45 pm **Posts:** 17

and the putty log file

discojon · **Joined:** Sat Nov 30, 2013 4:45 pm **Posts:** 17

Is there a way to. Log to SD on the open port 2 with the plx? If I have to I can do that just to get on with tuning.

dschultz · **Posted:** Fri Mar 07, 2014 1:58 pm

I don't think the Openport2 understands the PLX protocol.

RomRaider

Forum rules

Logging PLX SM-AFR wideband

Who is online