Here is a sample of my data:
Code:
000001: ?
000002: 
000003: >ATWS
000004: 
000005: 
000006: ELM327 v1.5
000007: 
000008: >ATE0
000009: ATE0
000010: OK
000011: 
000012: >ATL0
000013: OK
000014: 
000015: >ATS0
000016: OK
000017: 
000018: >01001
000019: 410080000001
000020: 
000021: >01201
000022: 412080018001
000023: 
000024: >01401
000025: 414040000000
000026: 
000027: >01041
000028: 410400
000029: 
000030: >01001  (Bad command should be 0105, I fixed it!)
000031: 4100BFBFB993
000032: 
000033: >01061
000034: 410680
000035: 
000036: >01071
000037: 41077F
000038: 
000039: >01081
000040: 410880
000041: 
000042: >01091
000043: 41097B
000044: 
000045: >010A1
000046: NO DATA
definition seems to be getting what I'm asking for, but...
I'm getting "ghost data" on the vehicle speed that seems to be the same as the RPM level.
I've checked the commands and response setups and am wondering if I'm displaying the right values at all. (the 1's at the end of the commands are not in my sent string)
The response is set for 1 in all the payload boxes except for the 16 bit (set to 2) or binary 4 byte values that request PID status (set 4).
Code:
000036: >01071   Mode 1, 07 PID request, 1 is added by plug in?
000037: 41077F    41 indicates mode 1, 07 is PID#, 7F is data (8 bit)
Seeing how the response also includes the command, should I be using a 2 byte offset or possibly entering the command into the "Header" field as hex characters?

Just thinking that may be another part I'm missing.
TIA