Topic: OBDWiz and STN1110

[axscan]

Hi,

I am tried connecting the STN1110 to the OBD port and wanted to check if I could see CAN bus information through the OBD port on Toyota RAV4 2006 Gasoline vehicle. When I do an AutoDetect OBDWiz fails to detect any protocol when connected to the toyota RAV4. However it does detect the COM port which it is connected to. Even commands like AT RV (ST RV) would not give any reponse.

So I tried connecting STN1110 to another car. VW Jetta 2003 Gasoline. OBDWiz detected the COM port (laptop end) and the protocol (OBD end) as ISO 9141-2. It also detected 2 ECUs 1A with 7 PIDs and 10 with 20 PIDs. When I selected any one of the ECUs, it would connect for a short period of time (2-3 sec) and automatically disconnect. In this, AT RV returned 13.3 V which is what I would expect.

I also tried it on Mercedes SLK 280 roadster Gasoline. Everything works like a charm here. The protocol detected was ISO 15765-4 (CAN 11/500) and I was able to see the entire CAN bus information (available on OBD2).

I thought it could be a OBDWiz issue and so used MyTTY (like hyper terminal) and connected to the COM port. I saw the same behavior as mentioned above on all the 3 cars. I checked the pin configurations of the OBD to DB9 connectors and they are the same. What I want is to monitor all the CAN frames (AT MA or ST MA) or anything equivalent. I do not want to poll information to get vehicle speed but be able to monitor the CAN bus information at its baud rate (eg 500 k baud).

Kindly help me figure out the problem.

Regards,
axs

[axscan]

Hi,

Previously I had bought CANUSB f7001 from EasySync. I connected one end to the OBD port and the other end to the laptop and I was able to read all the information on the OBD port (50 messages) on a 2006 Toyota RAV4 Gasoline car. I didnt have to poll or read PIDs for information.

Now I have a STN1110 and am trying to do the same. On connecting the device and selecting/ searching for the correct protocol, still I was not able to get any information from the OBD port. I have no experience in using STN and am new to this. So, I tried using OBDWiz and still was not able to read any information from the 2006 Toyota RAV4. The pin connections are connect, I have verified it. I would assume AT MA or ST MA command will help in monitoring all information on the OBD port.

Please help me get a better understand of this device and also in getting started with STN device.

Thanks,
axs

[Jason Smith]

Hi Axs,

Can you please post logs of the RAV4 and Jetta?

To create a log, go to Diagnostics->Raw Data and click "Always Collect" if there is not a green check mark next to it, then connect. Copy/paste the data into your next post.

What country were the vehicles purchased in?

Thanks,
Jason

[axscan]

Hi Jason,

Thanks for the reply. All the cars are purchased and used in the USA.

This is from VW Jetta 2003 Gasoline -

Opening communications: COM9
Port Open
Flushing communications buffer
?: [ELM327 v1.3a]
Sending Reset Command: ATZ
ATZ: [ELM327 v1.3a]
Interface connected
Sending ECHO OFF Command: ATE0
ATE0: [ATE0
OK]
Sending LINEFEEDS OFF Command: ATL0
ATL0: [OK]
STI: [STN1110 v2.1.3]
ATI: [ELM327 v1.3a]
AT@1: [SCANTOOL.NET LLC]

Trying Protocol: SAE J1850 PWM (41.6 Kbaud)
ATSP 1: [OK]
Sending request: 01 00
01 00: [NO DATA]

Trying Protocol: SAE J1850 VPW (10.4 Kbaud)
ATSP 2: [OK]
Sending request: 01 00
01 00: [NO DATA]

Trying Protocol: ISO 9141-2 (5 baud init, 10.4 Kbaud)
ATSP 3: [OK]
Sending request: 01 00
01 00: [BUS INIT: ...OK
41 00 88 18 00 10
41 00 BE 1F E8 11 ]
Protocol detected: ISO 9141-2 (5 baud init, 10.4 Kbaud)

Sending HEADERS ON Command: ATH1
ATH1: [OK]
01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]
01 20: [48 6B 10 41 20 00 00 10 00 34 ]
Detected PIDs:
    ECU: 10
        0x00 - SupportedPIDs0
        0x01 - MonitorStatus
        0x03 - FuelSystemStatus
        0x04 - EngineLoad
        0x05 - EngineCoolantTemp
        0x06 - ShortTermFuelTrimBank1
        0x07 - LongTermFuelTrimBank1
        0x0C - EngineRPM
        0x0D - VehicleSpeed
        0x0E - TimingAdvance
        0x0F - IntakeAirTemperature
        0x10 - MassAirFlowRate
        0x11 - ThrottlePosition
        0x12 - SecondaryAirStatus
        0x13 - OxygenSensorsPresent
        0x15 - OxygenSensorDataBank1Sensor2
        0x1C - OBDStandard
        0x20 - SupportedPIDs1
        0x34 - OxygenSensor1EquivalenceRatioCurrent
    ECU: 1A
        0x00 - SupportedPIDs0
        0x01 - MonitorStatus
        0x05 - EngineCoolantTemp
        0x0C - EngineRPM
        0x0D - VehicleSpeed
        0x1C - OBDStandard

01 00 1: [48 6B 1A 41 00 88 18 00 10 BE ]
01 00 1: [08 FA <DATA ERROR]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
ATSH 6C 10 F1: [OK]
01 00 1: [NO DATA]
ATSH 68 6A F1: [OK]
01 01 1: [48 6B 10 41 01 00 07 6D 00 79 ]
AT@1: [SCANTOOL.NET LLC]
STI: [STN1110 v2.1.3]
STDI: [STN1110 r1.0]
STSN: [111010106619]
01 1C 1: [48 6B 1A 41 0C 0C 3D 63 ]
01 0D 1: [48 6B 1A 41 01 00 04 00 00 13 ]
01 0C 1: [48 6B 10 41 0C 0C 3E 5A ]
01 0D 1: [48 6B 10 41 0D 00 11 ]
01 0C 1: [FB ERROR]
01 0D 1: [48 6B 10 41 0D 00 11 ]
01 0C 1: [48 6B 1A 41 0D 00 1B ]
01 0D 1: [A4 <DATA ERROR]
01 0C 1: [48 6B 10 41 0C 0C 43 5F ]
01 0D 1: [48 6B 1A 41 0D 00 1B ]
01 0C 1: [48 6B 10 41 0C 0C 3D 59 ]
01 0D 1: [48 6B 1A 41 0C 0C 35 5B ]
01 0C 1: [48 6B 10 41 0C 0C 21 3D ]
01 0D 1: [48 6B 1A 41 0C 0C 20 46 ]
01 0C 1: [48 6B 10 41 0C 0C 1F 3B ]
System.TimeoutException - The operation has timed out.
01 0D 1: [48 6B 1A 41 0C 0C 21 47 ]
System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.IO.IOException - A device attached to the system is not functioning.

System.TimeoutException - The operation has timed out.
System.TimeoutException - The operation has timed out.

some times I get this FB Error at it stop.
01 0D 1: [08 FA <DATA ERROR]
01 00 1: [48 6B 10 41 00 BE 1F E8 11 DA ]
01 00 1: [FB ERROR]
ATI: [ELM327 v1.3a]
ATI: [ELM327 v1.3a]


For the Toyota RAV4 2006 Gasoline -

The connection itself wouldn't establish. I do not have any logs from this car. OBDWiz does not even allow me to go to the log sections. I did manual connection and also Auto detect and connect options. I have checked the pin configurations and also voltages on the OBD port end. They look fine. I even connected another tool CANUSB F7001 from EasySync and checked on the hypertermial to find the below information on Toyota RAV4 (which is what I also want from STN1110) -

t2D08066E0900100000676542
t3A1800000000000000006544
t02030000076546
t0237020A02090000416547
t2C4803480021008021DB6549
t2D522E1D654B
t26080E00000000000078654B
t62081000000030400050654F
t02030000076551
t0258000A0006787878A56553
t0237020A020B0000436553
t0B0600000000110E6557
t32030000266557
t0203000007655C
t2238002000000000004D655E
t2C1808FF8BFFD4BC00EC6560
t2D522E1D6562
t0B0600000000110F6564
t224800000000000000086564
t02030000076569
t0B4800000000000000BC656A
t0237020A0208000040656A
t0B06000000001100656F
t23540000003B6570
t0B260000000011006570
t26080E00000000000078

Merc SLK 280 Roadster 2007 model Gasoline -
I only got my hands on this car for a day. I do not have the OBDWiz log for this. But using STN1110 and checking on the hyperterminal, I was able to get this (again this is what I want and I could get it with STN1110) -

>ATMA
238 00 00 88 C0 08 08 00 00
003 00 00 00 00 00 00 00 01
200 02 18 00 00 00 00 FB E0
208 00 20 00 00 02 18 00 00
300 08 08 00 00 00 00 7F DD <DATA ERROR
328 FF FF 7E 00 00 06 00 00 <DATA ERROR
3FF 2C B9 8E 32 FE FF FF 7E
238 00 11 88 C0 08 08 00 00
200 02 5C 00 00 00 00 FB E0
208 00 20 00 00 02 5C 00 00
300 88 88 80 00 80 00 7F DD <DATA ERROR
328 FF FF 7E 00 00 07 00 00 <DATA ERROR
012 00 07 4A 40 32 00
238 00 12 88 C0 88 88 80 00
200 02 60 00 00 00 00 FB E0
208 00 20 00 00 02 60 00 00
300 88 88 80 00 80 00 7F CC <DATA ERROR
328 FF FF 7E 00 00 00 00 00 <DATA ERROR
238 00 03 88 C0 88 88 80 00
404 FD 1A 3F FF FF FF FF FF <DATA ERROR
200 02 24 00 00 00 00 FB E0
208 00 20 00 00 02 24 00 00
300 08 08 00 00 00 00 7F DD <DATA ERROR
328 FF FF 7E 00 00 01 00 00 <DATA ERROR
238 00 14 88 C0 08 08 00 00
004 03 00 01 0F 00 4C 46
000 0F 00 4C 46 B2 05 <DATA ERROR
016 8E <DATA ERROR
200 02 28 00 00 00 00 FB E0
208 00 20 00 00 02 28 00 00
300 08 08 00 00 00 00 7F EE <DATA ERROR
328 FF FF 7E 00 00 02 00 00 <DATA ERROR
238 00 05 88 C0 08 08 00 00
003 00 00 00 00 00 00 00 01
200 02 6C 00 00 00 00 FB E0
208 00 20 00 00 02 6C 00 00
300 88 88 80 00 80 00 7F DD <DATA ERROR
328 FF FF 7E 00 00 03 00 00 <DATA ERROR
3FF 2C B9 8E 32 FE FF FF 7E
238 00 06 88 C0 88 88 80 00
200 02 30 00 00 00 00 FB E0
208 00 20 00 00 02 30 00 00
BUFFER FULL

==========================
With the EasySync, I get a continuous input of data without a buffer full, but with the STN1110 I get a BufferFull. This is another concern and I can take it as a new post. But my main concern is that STN1110 is not being detected on the car which I am using to test (Toyota RAV4).
For all the good reasons, we plan to opt for STN1110 and go towards bulk order but the road block currently is that we are not able to verify that we can use this device and OBDWiz on all cars.

Sorry for the long post and thanks again for your reply.

Regards,
axs

[Vitaliy]

I'm assuming you're using a homebuilt interface?

The first issue, <DATA ERROR on the 2003 VW Jetta is probably caused by dirty power (to the point where the interface disappears from the system). You can try to fix the issue by adding more capacitance, or even adding a proper power filter.

The second issue is unrelated, it has to do with how STN1110 interprets CAN messages. When you tell it to automatically detect the protocol, it tries legislated CAN first (ISO 15765), but the messages are actually raw CAN (ISO 11898). Do "ATDP" after "ATMA" in your example, and tell us what the protocol is.

Vitaliy

[axscan]

Hi Vitality,

Interesting that you said that it was a homebuilt interface. I checked all the connections and they are all fully connected. The OBD2 port also seems clean and I am able to read data using EasySync's CANUSB F7001. I have checked it for both the cars VW Jetta 2003 and Toyota RAV4 2006.

And for the second part. This is what I get from both the cars -
VW Jetta - Protocol detected: ISO 9141-2 (5 baud init, 10.4 Kbaud)

Toyota RAV4 - I am still not able to read another from the car using STN 1110 with and without OBDWiz. However as I mentioned in my previous note, I am able to read the CAN bus information using EasySync's F7001. Below is what I get with STN1110 and OBDWiz.

Version: 2.7.1.2

System.TimeoutException - The operation has timed out.
System.TimeoutException - The operation has timed out.
System.TimeoutException - The operation has timed out.
System.TimeoutException - The operation has timed out.
Opening communications: COM4
Port Open
Flushing communications buffer
System.TimeoutException - The operation has timed out.
Command timed out
Opening communications: COM4
Port Open
Flushing communications buffer
System.TimeoutException - The operation has timed out.
Command timed out

My last important part. I really what to know what this is...
Using 2 separate devices on 2 different cars I was able to get this information.
1. EasySync 7001 on Toyota RAV4 2006
t2D08066E0900100000676542
t3A1800000000000000006544
t02030000076546
t0237020A02090000416547
2. STN1110 w & w/o OBDWiz on Merc SLK 280 2007   (when I hit ATMA)
3FF 2C B9 8E 32 FE FF FF 7E
238 00 11 88 C0 08 08 00 00
200 02 5C 00 00 00 00 FB E0
208 00 20 00 00 02 5C 00 00

The first three digits (after t in the first case) are the HexIDs or MsgIDs from CAN bus. The remaining are data packet size, data bits etc etc.

What I got from VW Jetta 2003 using STN1110 was - (when I hit ATMA)
01 0C 1: [48 6B 10 41 0C 0C 3D 59 ]
01 0D 1: [48 6B 1A 41 0C 0C 35 5B ]
01 0C 1: [48 6B 10 41 0C 0C 21 3D ]

Why this difference? The data from Jetta does not seem to be like a normal CAN-bus message. It seems like a diagnostic information.
How can I get the information with the HexIDs? I actual CAN bus information?

Any answers on this will really help me understand the whole thing much better.
Thanks a lot in advance and hoping to get some information.

-axs

[Vitaliy]

axs,

You lumped a whole bunch of issues into a single post. Untangling the meaning from the mess is a challenge. Consider focusing on one problem at a time.


Interesting that you said that it was a homebuilt interface. -- so is it, or is it not?


System.TimeoutException - The operation has timed out. -- Have you tried cleaning up the power (e.g., add caps) as I suggested?


What I got from VW Jetta 2003 using STN1110 was - (when I hit ATMA)
01 0C 1: [48 6B 10 41 0C 0C 3D 59 ]
01 0D 1: [48 6B 1A 41 0C 0C 35 5B ]
01 0C 1: [48 6B 10 41 0C 0C 21 3D ]

You didn't use ATMA to generate this, it looks like part of OBDwiz log.


Why this difference? The data from Jetta does not seem to be like a normal CAN-bus message.

Because the protocol is not CAN, it's ISO 9141-2.

[axscan]

Hi Vitality,

Sorry for the any confusion caused.
Yes it is a homebuilt interface. The sockets, ports are cleaned and the required caps are added as you suggested.

I have the two cars (2003 VW Jetta and 2006 Toyota RAV4) which I am checking on, and STN1110 hasn't worked on both. So, I will be listing both the information below. I have used both OBDWiz and MTTTY (which is like hyperterminal).

I again did what you had suggested -
ATDP and then ATMA

For 2003 VW Jetta -
This is what MTTTY shows
> AT Z

ELM327 v1.3a
>AT DP
ISO 9141-2
>AT RV
13.7V
>AT MA
>AT Z

ELM327 v1.3a
>AT DP
ISO 9141-2
>AT MA
>

So when I did ATDP, it would show the protocol, but wouldn't show anything when I did ATMA. It would also show the current battery voltage reading with ATRV.

This is the raw output from OBDWiz
Version: 2.7.1.2

Opening communications: COM3
Port Open
Flushing communications buffer
?: [Sending Reset Command: ATZ
ATZ: [ATZ

ELM327 v1.3a]
Interface connected
Sending ECHO OFF Command: ATE0
ATE0: [ATE0
OK]
Sending LINEFEEDS OFF Command: ATL0
ATL0: [OK]
STI: [STN1110 v2.1.3]
ATI: [ELM327 v1.3a]
AT@1: [SCANTOOL.NET LLC]

Trying Protocol: SAE J1850 PWM (41.6 Kbaud)
ATSP 1: [OK]
Sending request: 01 00
01 00: [NO DATA]

Trying Protocol: SAE J1850 VPW (10.4 Kbaud)
ATSP 2: [OK]
Sending request: 01 00
01 00: [NO DATA]

Trying Protocol: ISO 9141-2 (5 baud init, 10.4 Kbaud)
ATSP 3: [OK]
Sending request: 01 00
01 00: [BUS INIT: ...OK
41 00 88 18 00 10
41 00 BE 1F E8 11 ]
Protocol detected: ISO 9141-2 (5 baud init, 10.4 Kbaud)

Sending HEADERS ON Command: ATH1
ATH1: [OK]
01 00: [48 6B 1A 41 00 88 18 00 10 BE
48 6B 10 41 00 BE 1F E8 11 DA ]
01 20: [48 6B 10 41 20 00 00 10 00 34 ]
Detected PIDs:
    ECU: 1A
        0x00 - SupportedPIDs0
        0x01 - MonitorStatus
        0x05 - EngineCoolantTemp
        0x0C - EngineRPM
        0x0D - VehicleSpeed
        0x1C - OBDStandard
    ECU: 10
        0x00 - SupportedPIDs0
        0x01 - MonitorStatus
        0x03 - FuelSystemStatus
        0x04 - EngineLoad
        0x05 - EngineCoolantTemp
        0x06 - ShortTermFuelTrimBank1
        0x07 - LongTermFuelTrimBank1
        0x0C - EngineRPM
        0x0D - VehicleSpeed
        0x0E - TimingAdvance
        0x0F - IntakeAirTemperature
        0x10 - MassAirFlowRate
        0x11 - ThrottlePosition
        0x12 - SecondaryAirStatus
        0x13 - OxygenSensorsPresent
        0x15 - OxygenSensorDataBank1Sensor2
        0x1C - OBDStandard
        0x20 - SupportedPIDs1
        0x34 - OxygenSensor1EquivalenceRatioCurrent

01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]
01 00: [48 6B 1A 41 00 88 18 00 10 BE
48 6B 10 41 00 BE 1F E8 11 DA ]
01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]
01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]
01 00: [48 6B 1A 41 00 88 18 00 10 BE
8 6B 1A 41 00 88 18 00 10 BE
48 6B 10 41 00 BE 1F E8 11 DA ]
01 00: [48 6B 1A 41 00 88 18 00 10 BE
48 6B 10 41 00 BE 1F E8 11 DA ]
01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]
ATSH 68 6A F1: [OK]
01 01: [48 6B 10 41 01 00 07 6D 00 79
48 6B 1A 41 01 00 04 00 00 13 ]
AT@1: [SCANTOOL.NET LLC]
STI: [STN1110 v2.1.3]
STDI: [STN1110 r1.0]
STSN: [111010106619]
01 1C: [48 6B 10 41 1C 03 23
48 6B 1A 41 1C 01 2B ]
01 0D: [48 6B 10 41 0D 00 11
48 6B 1A 41 0D 00 1B ]
03: [48 6B 10 43 00 00 00 00 00 00 06 ]
01 10: [48 6B 10 41 10 00 C8 DC ]
01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]
AT DP: [ISO 9141-2]
01 0C: [48 6B 10 41 0C 0C 7C 98
48 6B 1A 41 0C 0C 7B A1 ]
01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]
01 0D: [48 6B 10 41 0D 00 11
48 6B 1A 41 0D 00 1B ]
System.TimeoutException - The operation has timed out.
01 00: [48 6B 10 41 00 BE 1F E8 11 DA
48 6B 1A 41 00 88 18 00 10 BE ]

and this is the output from the console in OBDWiz

AT DP:
ISO 9141-2
AT RV:
13.6V

Attachments Untitled1.png, Untitled4.png, Untitled6.png are related to VW Jetta

From the Toyota RAV4, I do not get anything atall, no information either on MTTTY nor OBDWiz.

Attachment Untitled8.png is related to Toyota RAV4.

Thanks a lot for your help,
axs

[Vitaliy]

Post your schematics, please. My suspicion is that you are powering STN1110 from the OBD port, and the RAV4 has a blown fuse. Check the voltage on pins 5 & 16 of the DLC, it should be roughly 12V. If you read zero, check the cigarette lighter fuse.

[axscan]

Hi Vitality,

Thanks for your help. Actually we are using the SparkFun board http://www.sparkfun.com/products/9555
The voltage on Pin5 & 16 of DLC was reading a 0, but the cigarette lighter was reading 12+ V.
Toyota RAV4 has a separate fuse for OBD port and a separate one for the cigarette lighter. We checked the fuses to fine, so went tracing the pin16 wire and somewhere inside we found that the wire was cut, we replaced that wire and were able to see data on Toyota RAV4 also (data at the end of post).
I also checked and found that the other portable device we were using was powered by the USB port rather than the OBD port and thats why we had no problems with the RAV4 and that device till now.

Thanks for all your help. Now the first step is over, we are able to read CAN-bus data using STN1110 which in itself is a good news for us.
As you will notice from the data, there are 2 big concerns which I still have -
1. Buffer Full
2. Data Error

I will post this concern as a new post, and this post can be closed.

Thanks once again for your help,
axs

Data from a single read
========================
>
624 1A 00 41 49 49 40 00 00
0B0 00 00 00 00 11 07
0BA 15 F7 C9
0B2 00 00 00 00 11 07
224 20 00 00 00 02 FC 00 28
2C1 08 FF 4F FF 8E BA 00 68 <DATA ERROR
2C6 00 00 00 10 00 00 00 E0
2D0 06 66 09 00 10 00 00 5F
020 20 00 07
0B4 00 00 00 00 74 00 00 30
630 17 00 00 00 00 00 00 00
2C4 03 3C 00 1B 00 80 21 C9
2D5 2E 1D
260 0E 00 00 00 00 00 00 78 <DATA ERROR
0B0 00 00 00 00 11 08
235 00 00 00 3B
0B2 00 00 00 00 11 08
638 13 00 18 00 00 00 00 00
3A1 00 00 00 00 00 00 00 00
020 20 00 07
223 07 28 00 00 00 10 00 6C
0B4 00 00 00 00 74 00 00 30
0B0 00 00 00 00 11 09
0BA 15 F7 C9
0B2 00 00 00 00 11 09
224 20 00 00 00 02 FA 00 28
260 0E 00 00 00 00 00 00 78 <DATA ERROR
020 20 00 07
0B4 00 00 00 00 74 00 00 30
2C4 03 3A 00 1B 00 80 21 C7
BUFFER FULL