OBDII Module doesn't work in streetdeck

**Lok** · 02-21-2008, 01:21 PM

I just purchased a full version of streetdeck and also an ELM Scan 5 OBDII scanner from webstore a couple weeks ago and I have been having trouble getting the OBDII Module working with Streetdeck. I used ELMScan's software and it works fine and I can read all the sensors and the error codes however when I use it in streetdeck doesn't work. I have the right plugin selected. I also checked and made sure I have the right com port as well. Is When I go to the module in SD after a short time it says cannot query OBDII please see Log for details. I have no idea where this log or how I can go about troubleshooting this. Please help!

**vinzer** · 02-21-2008, 04:16 PM

Same here. I have OBDII interface ELM-323. With its original (free) software it works fine always. With SD it works sometimes, but most of the time immideately after start or in couple of minutes saying that can not connect to ELM interface. If I go right away to other software and try it - it's gonna work with no problems. That is strange, may be SD does not reset ELM contorller properly, or loosing communication for some reason.

**S4Per** · 02-22-2008, 12:05 AM

check the "Where is the log?" thread in the Streetdeck F.A.Q. section.

i would close streetdeck...restart it with the -verbose command line switch (there's also a FAQ on the different command line switches), and go to the obdII module and reproduce the error. then close SD, then find the right log (timestamp should be from when you last started SD, I believe).

post the log and have chuck take a look.

**maxxell** · 02-26-2008, 12:28 PM

I have the same problem, having just rec'd my ELMscan in the mail last night.

Any updates?

S4Per... how do I 'find the right log'?? I've never had to do any advanced troubleshooting with streetdeck, but am willing to help with this if someone will explain.

**Lok** · 02-26-2008, 01:15 PM

Maxxell its located in C:\Documents and Settings\YOURUSERNAME\My Documents\Streetdeck\Log. The logs are listed by date and time, respectively. Once you run the program and exit out you should see a log created for that specific date and time (looks something like 2008-02-26 12_23.txt). I have already taken the liberty to submit my log to chuck in the new streetdeck bug reporting thread ID # 76. http://www.mp3car.com/vbulletin/tracker.php?projectid=4

**maxxell** · 02-26-2008, 01:33 PM

Lok, thanks for the info. Since you've already done it, should I not waste time doing the same or is there benefit to seeing the log from more than one machine?

**Lok** · 02-26-2008, 01:39 PM

I am not sure if it will help, but I guess if Chuck has info from multiple machines it may help him troubleshoot the issue. Make sure you type in "-verbose" at the end of the command line parameter so you get the extended log info. You can also reference my bug ID (#76) so that way he knows its the same issue.

**Fiberoptic** · 02-27-2008, 10:58 AM

Thanks for taking the time to submit this to the bug reporting system. Please follow this post for updates.

http://www.mp3car.com/vbulletin/tracker.php?itemid=76

**maxxell** · 03-23-2008, 11:17 AM

How are those updates going? Looks like a lot of people are having this issue. Does Streetdeck work with the OBD module for ANYBODY? Is this a systemic problem?

I find it very disingenuous for Streetdeck to continue offering the Elmscan hardware and advertise it as compatible with the software when it's clear there is a big problem and nobody seems to be doing anything about it.

**tek818** · 03-24-2008, 01:20 PM

Originally Posted by maxxell

I find it very disingenuous for Streetdeck to continue offering the Elmscan hardware and advertise it as compatible with the software when it's clear there is a big problem and nobody seems to be doing anything about it.

get used to it... it's the way they work. This company is an absolute joke. I am filing a BBB complaint shortly.