ELM327 cable sends different response payload that is not treated on elmobd

[AramisHM]

While trying a cheap chinese ELM327 cable, I got: "Failed to get rpm Expected at least 3 OBD literals: SEARCHING..."

This is happens because parseOBDResponse on device.go is receiving 2 arguments, the first is "SEARCHING..." and the other are the OBD literals. So, when it calls NewResult(payload), it passes only the first argument wich, in this case, is "SEARCHING...".

This is the call sequence I got while testing in a car:

runs command to get engine RPM

• :processResult: `dev.outputs = [ELM327 v1.5]`
• :processResult: `dev.outputs = [OK]`
• :processResult: `dev.outputs = [SEARCHING... 41 0C 0B F4]`
• :RunOBDCommand: `outputs len = 2` `outputs content = [SEARCHING... 41 0C 0B F4]`
• :NewResult: ` Failed to get rpm Expected at least 3 OBD literals: SEARCHING...`

I made a pull request (b6e3ddf) with a workaround that solved my problem

[rzetterberg]

Oi, @AramisHM! Muito obrigado! :+1:

I'll have a look at your PR and see if it works well with my device and car. Hopefully no special cases are needed for different devices.