Recent Posts

Pages: 1 ... 8 9 [10]
91
ECUsim / Re: Programming ECU SIM 5100 CAN 29/500
« Last post by STN-Brian on April 22, 2016, 02:47:24 PM »
This does seem to be a bug, I have escalated this to the project's firmware engineer.
92
OBDLink SX / OBDLink SX Not Connecting
« Last post by dan-youd on April 22, 2016, 01:51:44 PM »
I received a OBDLink SX yesterday but unfortunately I can't get it to connect to my car.

The car is a UK Ford Focus MK2 2.0TDCI 2007
The laptop is running Windows 10 Pro X64

Device driver is up to date:



Tests done with stnterm:





OBDwiz:


Scan Tool Finder:


EasyOBD2:


I have also tried this with Torque Pro on Android Kitkat with a device that supports OTG and it gets detected by Torque but doesn't make contact with the vehicle.

It's also worth mentioning that I have a cheap Bluetooth ELM327 (fake) which works flawlessly on this vehicle on both Torque Pro and many other apps on my laptop via Bluetooth.

Any Ideas?

Regards
93
OBDLink MX Bluetooth / Re: OBDLink no longer connects to car
« Last post by avary on April 22, 2016, 01:24:32 PM »
Hello,

We have sent you a message through our help desk.

Thank you,
Avary
94
OBDwiz/TouchScan / Add PID
« Last post by klingon on April 22, 2016, 01:06:57 PM »
Hello,

Is there anyway to add custom PID's?
95
OBDLink MX Bluetooth / Re: Ford f250 Pid read speed
« Last post by Bkemp on April 22, 2016, 11:33:03 AM »
It's an 03 and above

I tried to attach a screen shot but it was too large. Looks like ISO15765-4CAN11/500

Thanks!
96
OBDLink SX / Re: Desperate for help - ATMA command doesn't work
« Last post by MARCO1981 on April 22, 2016, 11:32:14 AM »
Hi Brian,
sorry to bother you but i'm not totally sure that the "issue" is the modernity of my car.
I've also tried the same set of commands also on a 2002 BMW Z3 and i got no answer both using ATMA and STMA
Here is the log:
******
atz


ELM327 v1.3a

>atsp0
OK

>0100
SEARCHING...
41 00 BE 1F F8 10

>stdix
Device:       OBDLink SX r4.2
Firmware:     STN1130 v4.0.1 [2014.05.02]
Mfr:          ScanTool.net LLC
Serial #:     113010781876
BL Ver:       2.16
IC ID/Rev:    0x0110, 0x067D, 0x3004
Init Date:    2015.07.17
POR Count:    27
POR Time:     0 days 00:14:22
Tot Run Time: 0 days 05:37
Eng Cranks:   2
Eng Starts:   2

>atsp3        NOTE: The protocol seems to be ISO 9141-2
OK

>0100
41 00 BE 1F F8 10

>atsp0
OK

>0100
SEARCHING...
41 00 BE 1F F8 10

>atma         NOTE: no answer

>stp22       
OK

>stcmm 1
OK

>stma   NOTE: No answer

>0100           NOTE: the protocol seems to be the correct one since it answers to 0100
BUS INIT: ...OK
41 00 BE 1F F8 10   

>atdp
ISO 9141 (5 BAUD) [ST]

>

Any clue? Do you still think is a car problem

Regards,
m.

97
OBDLink MX Bluetooth / Re: Ford f250 Pid read speed
« Last post by STN-Brian on April 22, 2016, 10:14:09 AM »
What year is it?  Most modern vehicles use CAN protocol, which is fast.  Also, can you use the bafx to look up your protocol?
98
OBDLink MX Bluetooth / Re: OBDLink no longer connects to car
« Last post by STN-Brian on April 22, 2016, 09:55:12 AM »
You can start the RMA process yourself if you wish.  Go to the support center -> Support Center
Select Sales and include a link to this forum topic.
99
Developer Forum / Re: Developing Software to comunicate with ELM327 USB
« Last post by Ziggy on April 22, 2016, 09:00:28 AM »
   As mentioned above you don't communicate with the USB. When you install the drivers for the ELM327 it creates a virtual comport (VCP) and you communicate with that comport just like before.
100
Developer Forum / Re: Multiple Devices Querying BUS
« Last post by Ziggy on April 22, 2016, 08:55:49 AM »
   So since we don't know what third party devices our customers are putting on the bus along with our OBDLink S, and we really don't even know the make and model of the vehicles, is there any guaranteed way of setting up the OBDLink S so we will always get a response to the 010D query no matter what devices our customers have on the OBD Bus?
Pages: 1 ... 8 9 [10]