Monday, July 10, 2017

OBD2 interface issues.


I wasn't sure if this was the right place to post this, or if it should be on one of the more mechanic focused subs.I bought 2 different obd2 adapters and I can't get either of them to connect. The first one was a super cheap Bluetooth elm327 off Amazon, so I'm willing to believe that it's just doa. The second one though is the Foseal wifi adapter. It seems to have gotten a bunch of good reviews, so either I got supremely unlucky, or I'm doing something wrong.This is all on my 03 civic.Once the Foseal (a wifi obd2 adapter) showed up today I plugged the Foseal into my obd2 and connected to the wifi network that showed up. I went into Torque pro and selected wifi for the adapter type. I set my static ip to 192.168.0.5 and set the gateway to 192.168.0.10. I tried both .10 and .11 in Torque pro with a port of 35000, but Torque pro just keeps saying it's waiting to connect.I've tried this both with the car on and the car off and it seems to make no difference. I also tried using Dash Command with no luck. Finally tried it in my mom's 13 corolla, but no dice.Before I give up and return this interface, anyone want to prove how dumb I am by having missed something obvious? Thanks. via /r/cars http://ift.tt/2uKXxy0

No comments:

Post a Comment

Popular Posts