STN1110 Bluetooth OBD-II Adapter

Update:  The STN1110 readers have been “discontinued” in favor of my new  STN1170-based Bluetooth OBDII Reader!  “Discontinued” really only means that I’m not actively producing the STN1110 based reader anymore.  Parts are still available and software updates will probably continue to be released by Scantool.net.  I will of course link to those updates as I have in the past.  The only reason I’m discontinuing the STN1110 reader is that I don’t have the time to support producing two different units that pretty much do the same thing (the STN1170 does more in fact).

This page contains all the information for all the legacy Bluetooth OBD-II modules I’ve designed.  These are by far the smallest modules of their kind that I’ve seen.  I have an agreement with Scantool.net to open-source my designs.  The majority of my adapters are based on their STN1110 chip (ELM327 compatible).  All of my Bluetooth OBD-II modules work very well with Scantool.net‘s ScanXL OBD-II diagnostic software for Windows.  Check it out!

For Android users, my Bluetooth OBD-II adapters are an excellent companion for the Torque app ($5 on the Android Market), which is easily the best OBD-II software available for any Android smart phone or tablet.

Palm Pilot and PocketPC users can use OBDGauge, although both of these configurations are untested with my adapters.  Essentially as long as you can pair your Palm Pilot or PocketPC device to my adapter via Bluetooth, OBDGauge should be able to communicate with my adapter.

IPhone/IPod/IPad owners will not be able to use my Bluetooth adapters with their Apple products due to the lack of an Apple authentication chip in my BT module (the BT module also doesn’t support Apple’s authentication protocol).  If you have an Apple device, you will have to purchase a wifi ad-hoc OBD-II adapter if you want a wireless link to your vehicle.  Apple also makes it prohibitively expensive and complicated for hobby type people wanting to connect something via Bluetooth to their iOS device.  I’m not sure if this is also the case with OSX.

Right now I have 5 different modules to choose from, although since Sparkfun discontinued the one Bluetooth module I was using, there are really only 3 modules that have parts available to build.   PCBs and assembled units are available for purchase below (and kits too, but post a message for kit purchase details as they may or may not be in stock at any given time).  The modules aren’t too hard to build yourself, but there are small parts on the unit, which enable this module to be the smallest OBD-II Bluetooth modules on the market today.  It is smaller than the OBDLink MX, which claims to be the smallest adapter in the world.  The smallest passive parts are 0603 and the smallest pin pitch for an IC is 0.5mm.  There aren’t any QFN/DFN/BGA…etc kind of crap on my modules.

Here’s a quick and dirty manual I created that explains how to connect up my modules (or any OBD-II module really) to your vehicle and pair it to your Android phone.  For other operating systems, the process is essentially the same, but not covered in the manual.  Download the manual here:  Bluetooth OBD-II Adapter Manual

To make a complete module, two boards are needed: a driver board and a Bluetooth board.  A STN1110 based Bluetooth board requires the STN1110 universal driver board and likewise, an ELM327 based Bluetooth board requires an ELM327 universal driver board.

Please note that for shipping destinations outside of the USA I am not responsible for any extra customs/duty fees that may be encountered when importing happens, and I am not responsible for lost packages outside of the USA.  A tracking number will be provided if there is one available (depends on shipping method).  If you don’t receive your package within say 4 weeks of me informing you that I shipped your item, I can provide customs form numbers so that you can check with your country’s customs office to see if they have your package. The untracked international shipping method should arrive somewhere between 2-4 weeks of when I tell you the item has shipped. You will not see tracking updates once the package leaves the USA. The tracked international shipping option will get your adapter to you within 1-2 weeks, and the package is tracked the entire trip.

Kits:

RN-42 (FCC Certified) STN1110 Bluetooth Module Kit
Unassembled Kit w/ All Parts
A kit will contain a minimally assembled driver PCB and Bluetooth PCB.  You’ll be responsible for soldering down pretty much all the parts.  Assembly drawings and a page of directions to assemble the kit is included.  All this stuff are available to download via links above. Please read through the kit directions before ordering the kit so that you have some idea of the task you are going to undertake. I can provide some help, but as this is a kit, it is your responsibility to properly assemble, test, and program the unit to your liking. The only assembled/tested piece of the module is the 12V to 5V supply in the kit.  Please leave a comment to purchase a kit as they may or may not be in stock.
Kit: $60 Shipped (USA), $95 Shipped (International, tracked)

Genuine STN1110 Bluetooth OBDII PCBs:

Genuine STN1110 very low-power consumption FCC certified Bluetooth board STN1110 Universal Driver Board Genuine STN1110 non-FCC certified Bluetooth board

RN-42 TopRN-42 Bottom

STN1110 Driver TopSTN1110 Driver Bottom

Bare PCB Only: $13 shipped (USA)
$23 shipped to other countries

Shipping Destination

Bare PCB Only: $13 shipped (USA)
$23 shipped to other countries

Shipping Destination

Out of stock

 

Genuine ELM327 OBDII Bluetooth PCBs:

ELM327 Universal Driver Board Genuine ELM327 non-FCC certified Bluetooth board

Just for completeness, the following modules were also designed, but cannot be built anymore because the BTM-182 Bluetooth module is no longer obtainable:

Genuine STN1110 Bluetooth board (BTM-182 not available) Genuine ELM327 Bluetooth board (BTM-182 not available)

If there is some interest, I could also create a ELM327 based module with the FCC certified Bluetooth module.  I use only genuine STN1110/ELM327 chips in my designs, not ripped-off versions of the ELM327 like the blue Chinese modules on Ebay.

All the designs were created in Altium Designer.  Each zip file contains the Altium source binaries, gerbers, a BOM, a PDF of the schematics, and an assembly drawing showing where all the parts go.

You’ll also need the information in this text file to set up the STN1110/ELM327 chips and their corresponding Bluetooth module on the board:  OBD-II Adapter Setup Commands.  Essentially what needs to be done is both the Bluetooth module’s UART and STN1110/ELM327 UART need to be at the same baud rate to communicate.  On all Bluetooth modules except the RN-42, you have to connect up to the UART side of the Bluetooth module (the side the OBD-II interpreter chip connects to) and enter the module’s command mode and send it commands to get it to match the baud rate of the OBD-II interpreter chip.  On my modules, I have the OBD-II interpreter chips configured to run at 115.2kbps (although they can go higher…I just haven’t tested them higher).

 


The Bluetooth OBD-II adapter is copyrighted under the Creative Commons Attribution 3.0 license.  If you use these sources for creating your own module that you post online, please attribute my module as the original source (as the license states).


 

Creative Commons License
OBDII Bluetooth Module by Andrew Honecker is licensed under a Creative Commons Attribution 3.0 Unported License.

129 Responses to STN1110 Bluetooth OBD-II Adapter

  1. Shaukat Ali says:

    Dear Andy.
    I need OBD-2 Scan Tool Based on STN1110 IC. How many days will it take and what will be the total price for shipment to Pakistan???
    Thanks
    Regard

  2. DIEGO URDA says:

    Hi Andy

    I would like know if you can supply me the OBDII connector with the STN1100 chip, without the bluetooth board.

    Otherwise you can send me the OBDII device with the bluetooth board solderless.

    I’m testing with my Ducati Monster board and I need check RS232 in first.

    Same question for the OBDII with the new STN1170 chip.

    Regards

    • Andy says:

      Diego,

      I am out of stock of STN1170 and STN1110 based units now and probably will be for a long time. If you just want a OBDII connector, I can get you one of those, but if you want a nearly complete unit to use, I don’t really have anything.

      – Andy

  3. Gilson says:

    Hi Andy,

    What care I need to have to modify the drivers for 24V vehicles?

    Gilson

    • Andy says:

      Gilson,

      Assuming you’re referring to my reader, you shouldn’t need to modify anything to work w/ 24V vehicles. The power supply works up to 42V. The only problem w/ 24V vehicles compared to 12V vehicles is that under load dump scenarios from the alternator, the 24V vehicle could produce a higher load dump voltage than a 12V vehicle would, which could damage the power supply on the reader. Adding some sort of voltage clamp to keep voltage peaks below 42V would be nice. Also, as long as the OBDII interfaces you’re looking to use are standard interfaces, you should be fine at 12V or 24V as all the interfaces (except ISO/KWP) are independent of the main car voltage (again, as long as standards are being followed).

      The only exception may be ISO/KWP as the resistors used to pull the bus high are sized for 12V operation not 24V (thresholds should scale, but who knows, strange things may happen). Hopefully your 24V vehicle uses something nicer like CAN.

      – Andy

  4. pat says:

    Where can I get the plastic case that these units are housed in?

  5. S.Khan says:

    Dear Mr. Andy We are doing our Final year project on OBD2. We will explain our Project summary shortly. As every vehicle used its own specific OBD-II company protocols which only compatible with specific vehicles. Now our objective is to put all OBD-II protocols in OBD using STN1110 IC and make such type of algorithm that search a specific protocol which is compatible for every type of vehicle. In short our research is based OBD2 to make it General. Is it Possible?? Please take us in the right direction. I shall be very thankfull to you. Regard..

    • Andy says:

      I’m not 100% sure what you’re intending to do, but yes, if you want to be compatible w/ every OBDII compliant car out in the world, it’s best to stick w/ the standardized set of OBDII PIDs for requesting data. The manufacturer specific PIDs are useful for getting more detailed information, and getting “deeper” into your vehicle, but not all cars even within a manufacturer will support all the manufacturer specific PIDs you find.

      – Andy

  6. Stuart says:

    Where do you buy the J1962 connector and housing ?

  7. Andreas says:

    Hi Andy,

    thanks for the great information you provide on this website.

    I am working on a new startup in Berlin, Germany and we are currently looking for a OBDII Bluetooth 4.0 device. Did you work on such a product in the meantime?
    Or do you know any products available on the market?

    Would BT 4.0 guarantee the pairing with an Apple device? Or is this only possible via the Apple authentication chip?

    Kind Regards from Germany,
    Andreas

    • Andy says:

      Hi,

      Bluetooth 4 supposedly isn’t under strict control by Apple like previous versions of Bluetooth. As such, you won’t need the authentication chip. I don’t know of BT4 devices on the market at the moment, but I’m fairly certain there are ones being designed. I’m not going to make one at this point in time for a number of reasons.

      Hope this helps!

      – Andy

  8. JohnBallhanger says:

    STPBR max baud rate for K-Line is at 78125. Is it possible to increase to 115200?

    Also the stn1100-frpm.pdf is dated 2009. Where can I find a current with all ST commands and explanations. For example STPBR, STPBRR, STPTO commands are not in the pdf.

    • Andy says:

      John,

      I really don’t know the answers to your questions as all I have to go from is the same dated reference manual and datasheet for the parts. I agree that it’s not good if there are commands supported by the STN11xx parts that isn’t in the family reference manual.

      Your questions are probably better directed at the Scantool.net people.

      – Andy

  9. Vincent says:

    Hi, Do you have the information about the max ISO_K baudrate could be set and really achieved with this device? I heard the command is “STPBR” or “STIBR”, but I couldn’t find this in the datasheet, thank you!

    Regards

    Vincent Qin

  10. Neil Carle says:

    Are these adapters universal?
    I have a 1996 Toyota 4 Runner and a 2005 Renault Megane.
    Would your adapters work on those cars?

    • Andy says:

      Neil,

      Generally speaking, the adapters will work on any car that supports the OBDII standard. However, some have oddball connectors and you end up needing an adapter to use a standard OBDII unit like mine w/ those cars (BWM and Audi do this). There are also cases of older vehicles like 1995/1996 that have what looks like a OBDII connector, but don’t actually talk OBDII. I’ve seen this first hand w/ a 1995 mercury cougar and a 1996 oldsmobile silhouette.

      Your Toyota is borderline as to whether or not it supports OBDII based on the year. See chapter/section 2 in the manual for the adapter for details on how to check if your Toyota is OBDII compliant (would apply to the renault too, but it’s new enough to be OBDII compliant):
      http://ahdesign.us/blog/obdii/Bluetooth_OBDII_Manual.pdf

      For the renault, it does support OBDII. You just need to find out where the connector is located.

      -Andy

  11. Jürgen says:

    Hi

    Ist is possible to use this adapter with Mistsubishi I-miev and the tool from priusfan to view battry data and so on…?

    • Andy says:

      Jurgen,

      It’s possible to connect to that vehicle as long as it supports the OBDII standard (probably does, but check to make sure). I’m not familiar w/ the tool from Priusfan you’re referring to, but it would probably work if it supports ELM327/STN11xx based readers.

      -Andy

  12. Mana says:

    Hi Andy,

    I am building an embedded Android board for vehicle positioning application. I need vehicle speed and your adapter looks like something I need. I will be writing the firmware on the Android board myself. Can I assumed that it won’t be too hard to connect to your adapter via the Bluetooth? Please give me some pointer on this. Also, how do I and what message format do I need to send to your adapter to be connected to the ECU so I can request the vehicle speed? Thanks for your helps. Oh, yes, I will need a few of your adapters fully assembled and tested.

    • Andy says:

      Mana,

      Pairing to my device doesn’t require anything special to be done (unlike the OBDLink MX) and is similar to pairing with pretty much any other Bluetooth device. My adapter is constantly searching for something sending a pairing request, and when it receives one, the pairing process is started, and the only thing you need to enter is a PIN number (which is changeable to whatever you want, or that can be disabled). After you’re paired, reconnecting to the device is automatic as my unit stores I think the last 8 pairings to the unit.

      My module passes all serial data from the Bluetooth module untouched to the STN1110 onboard. You’ll want to look into the datasheets and reference manuals for the STN1110 here: http://www.obdsol.com/stn1110/

      and look at ELM327 command sets/datasheets as those will also apply to the STN1110. Using all that, you’ll find what you need to access the speed parameter you’re looking for, along with many others. Unfortunately I don’t know off the top of my head what you’d need to do for a particular vehicle, but documentation and examples for the ELM327 are pretty widely available.

      You’re welcome to buy as many units as you’d like from the site. If you want, I can give you a price for saving shipping/possibly quantity discount on whatever number of units you want.

      -Andy

    • PaJa says:

      By my opinion and 2cents advise. When you are building the specialized board, it will be more useful to place STN chip directly to the android board and communicate with CAN bus directly w/o playing with OBDII adapters.

  13. Chris says:

    I know that the Bluetooth module used here has a low current consumption sleep mode. Does your design support this?

    -Chris

    • Andy says:

      Chris,

      Yes, the RN-42 low power mode is utilized along w/ the STN1110’s low power mode to achieve ~100mW power consumption when Bluetooth isn’t connected.

      – Andy

  14. Joshua says:

    I was about to purchase your plug n play kit when I read your last message pertaining to SW-MS-CAN. What benefit would that be for me (hobbyist)? I have 8 vehicles, so your more than welcome to use one of mine if your in Ohio.
    I need the ability to scan vehicle codes quickly as I also buy and sell vehicles, frequently. I recently used a very expensive snap-on scanner for a 2011 Jeep Wrangler. The scanner is snap-on’s latest and greatest… however, because the 2011 Jeep has unique ECU/PCM programming I was not able to do anything with the jeep other than clear codes. So the Jeep is now at the stealership…
    Any help or recomendations in regards to the benefits of your new project versus buying the plug/play kit you have currently would help me make the choice.
    Thanks and keep up the good work!
    Joshua

    • Andy says:

      Joshua,

      Well, the main benefit is the ability to access other “ECU’s” on those buses in addition to the normal high-speed CAN that the newer vehicles support. It sounds like people can access some interesting information relating to infotainment, climate control…etc via MS CAN or SW CAN. Keep in mind that as far as I know, only Ford uses MS CAN and only GM uses SW CAN. This is implemented on fairly new vehicles, I kinda want to say 2008 onward, but I’m not completely sure.

      For general purpose reading of information from vehicles, either the STN1110 or STN1170 based adapters would suit your needs (the STN1110 adapter will be cheaper). Really the only thing the STN1170 gets you is the MS CAN and SW CAN support. Everything else remains the same as the STN1110.

      – Andy

  15. Mike Crowe says:

    Hi Andy,

    I have a motorcycle that uses the kline protocol, will this be able to pull basic data like rpm temp etc? If not what could i do to make this work. It is OBD2

    Could you also contact me about bulk pricing?

    • Andy says:

      Mike,

      From what I’ve seen online for motorcycles, they can choose to implement ECU communications over the OBDII connector however they want (generally speaking). Even though the hardware interface should work, you’d probably need to do some digging on the internet to see if you can use “standard” software with an ELM327 compatible interface (like mine hehe) for getting data off your bike. More likely though, you’d need to figure out what non-standard ECU parameters your bike uses and add those into Torque for getting the data you want.

      The K-Line protocol uses 1/2 of the ISO/KWP interface on my reader, so electrically, you can connect to your bike. Hopefully it actually supports KWP as far as initializing and communicating goes. I guess my best answer is I don’t know for sure, but you can always try it and see what happens =).

      I’ll send you an email about bulk pricing.

      – Andy

  16. Mathew says:

    Hi Andy,

    your adapter looks really good and i’m considering buying a kit. Do you have any in stock?

    -Mathew

  17. Chris Frey says:

    Hi Andy,
    I am a college student working on the beginning stages of an OBD-II project for my Senior Design class. I need a module with Bluetooth connectivity that is compatible with my own original Android application (also, part of the project). I believe that the unassembled kit would work well with my project. Could you possibly provide a parts list for the kit?

  18. Monower Sohel says:

    I suggest you design a LCD board to use with this project and we get a fantastic professional grade product.

    Thanks.

    • Andy says:

      Thanks for the comment, but you’re completely missing the point of all this. The module paired w/ Torque on an android phone or ScanXL on a computer turns this into a much more cost effective, much more powerful diagnostic/performance tool than you can get from a handheld, cabled tool w/ a text or if you’re lucky, graphic LCD screen.

      – Andy

  19. CEIF2001 says:

    Hi Andy,

    What will you charge for 4 Fully Assembled and Tested units, international tracked ?

    Regards

  20. Chris Daniels says:

    Hi Andy,

    Do you have any in stock??

    How does the STN1110 compare to the now available MCP2515.

    Why can’t this be used during driving operations of the car ??

    Kind Regards

    • Andy says:

      Chris,

      I’m not sure what item you’re wondering if I have stock of or not, but if Paypal lets you place an order, I have units in stock of whatever you’re trying to order. If you’re asking about a kit, yes I have those in stock too, but you need to specifically ask to place a kit order. I don’t have an easy way to order kits as the stock changes on those all the time as they’re not terribly popular. Sometimes if I’m in a pinch, I’ll steal parts from the kit for the assembled units…etc.

      So there’s really no way to compare the STN1110 to the MCP2515 as they each serve very different purposes. The STN1110 is an OBDII interpreter chip, which handles all the software specific stuff in a whole variety of OBDII protocols. The MCP2515 is simply a CAN controller, which handles the electrical interface (MAC layer in communications) between a CAN bus and a non-CAN enabled microcontroller. The STN1110 is a CAN enabled micro, so it only needs a a small piece of what the MCP2515 offers to communicate on a CAN bus. However, the STN1110 also knows how to “speak” OBDII with your vehicle, whereas the MCP2515 needs a microcontroller/processor/whatever to do those communications. I guess long story short, there’s no way you can drop the MCP2515 in place of the STN1110 and expect similar functionality w/o a ton of software work on your end.

      There’s no reason why my OBDII module (or anyone’s really) CAN’T be used while the vehicle is in motion. Rather, you SHOULDN’T be messing around with your phone/laptop/whatever while driving. I get data from my vehicles all the time, but only if I’m not the one driving. The only thing that you really should avoid doing while the vehicle is in motion (you’re not driving) is resetting the ECU (clearing trouble codes). Most likely nothing bad would happen, but why would you want to take the risk? So yeah my “don’t mess w/ this thing while driving” warning in my manual (assuming that’s where you saw this) is a safety “don’t be an idiot and endanger yourself and others on the road” kinda warning. The most practical use of the OBDII module is in fact when the vehicle is running and/or moving.

      – Andy

  21. Ajish S says:

    Dear Andy,

    Can you please give me the commands for changing the baud rate of STN1110 to 38400bps? I am planning to change the baud rate with connecting the STN1110 through serial port of PC with Hyper terminal application?

    • Andy says:

      Ajish,

      I’m assuming you’re using a hardwired serial/USB interface to connect to the STN1110 and you’re not using one of my adapters. The process differs slightly if you’re using my adapter. Just wanted to clear that up for you and others that may read this comment.

      To change the baud rate of the STN1110, I’ve only had success using the ELM327 baud rate commands. I haven’t found the trick to get the STN1110 baud rate commands to work (or stay applied after reboots), and quite frankly, since the ELM327 commands work just fine, I don’t see a need to mess w/ the STN1110 baud rate commands. So anyway, you use the following command to change the baud rate to 38400: AT PP 0C SV 68 The 0x68 (hexadecimal) is what sets the divisor for 38400bps. To get that divisor, you divide 4000 by your desired baud rate (in kbps) and then convert that decimal number to hexidecimal. So in this case, 4000/38.4 = 104.17, so we’ll round down to 104. And then 104 in hex is 0x68.

      Now to enable the baud rate change, you then have to send the command: AT PP 0C ON This will apply the new baud rate on subsequent power cycles of the STN1110.

      Hope this helps!

      -Andy

  22. Nick M says:

    Andy,

    Thanks for providing such great info on the obdii interface. I’m interested in building that that connects via USB. I know this limits to just PC but my intention is to build a reliable CAN BUS scanner/interface for testing purposes. My plans are to have two USB interfaces on the device. One for pure monitoring/filtering the bus (atma) and one for sending data (since my understanding is that you cannot do both simultaneously with the STN1110 or ELM IC’s). I can follow your schematics for the driver board and simply replace the Bluetooth to UART board with a USB to UART chip?) Since the device will be connected to a computer, would it be possible to draw the 5V from the USB port so a 12v to 5v converter would no longer be needed? I’d appreciate it if you could lead me in the right direction, product numbers for the usb->uart would be appreciated. Thanks again

    • Andy says:

      Nick,

      I think what you’re trying to do would require two STN1110/ELM327’s units, both connected to the same vehicle CAN bus, and each would have it’s own dedicated USB port. Even then, you’d have to be sure that both aren’t communicating on the CAN bus at the same time.

      So back to your original question, yes, you can simply replace the Bluetooth module w/ a FT232RL (or similar, but that chip is very easy to use) and that’ll give you your USB->UART interface. You can use this on phones/tablets that have USB OTG ports as Torque pro (Android) supports a USB connection. For either Android, PC, or whatever else you could use the USB interface with, you have to set the virtual serial port’s baud rate to match the baud rate of the STN1110/ELM327.

      Thanks,
      Andy

  23. AmitN says:

    Hi Andy,

    First – You are super cool and this is pure awesomeness.

    Second, I want to buy the assembled kit so I can plug and play, but I just realized that it comes as a naked PCB? Is there no way some sort of a cover could be devised to make it look more like a product ready for use? If not do you have any suggestions on a DIY cover, like say just covering it with duct tape, hot melt glue etc.?

    What is the idle power draw, is it 1mA? I drive about 1-2 times weekly normally and occasionally go out of town for about 2 months, so I was wondering if I have to worry about removing this module frequently or does my driving pattern fall below the safe threshold of your excellent low power design.

    Is the bluetooth version 2.1? Is it possible to upgrade to v3 or v4? Not for higher speed of course, but for the lower energy features I mean. Not a big deal since we are already pretty low power, plus newer chips are going to be more expensive for little gain, but just wondering.

    I assume you will update the kit to the latest v3 firmware that was released before shipping?

    Thanks a lot!

    • Andy says:

      Amit,

      Unfortunately I can’t get back to you about the kit as you left a bogus email address. I would be sending kit purchase instructions to you via email so….yeah

      Anyway, for a cover for the thing, conformal coating is acceptable, or if you wanted to, potting the whole thing in epoxy would be fine too. I’ve not tried potting in epoxy, but the only downside I could see is trapping all the heat in. The module really doesn’t even get warm, so I don’t think that’ll be an issue. I wouldn’t recommend duct tape or hot glue as both would look hideous and neither are durable, long term solutions =).

      The power draw is roughly 1/10W when in the idle state. The manual is outdated, and the current consumptions in there are for an older module. Having the vehicle sit for 2 months may be pushing things, depending on your battery capacity. It’s really hard to say that “yes you’ll be fine” or “no you won’t” because every car’s battery is different in the sense of the available capacity of the battery. If your battery is pretty old, like 5 yrs old, it could be on its way out and maybe the car can only sit 2 weeks before some small current draw will bring the battery down far enough to where it can’t start the car. I guess if you had a brand new battery, you should be able to go several months before that thing is dead. But again, “dead” is a different battery state than being “low enough that it can’t start the car”…..

      The Bluetooth version is 2.1. It’s pretty meaningless though as it’s not like the SPP profile makes use of any of the features 2.1 has to offer. There are no drop in replacements for BT4 for the RN-42. I may switch to a different module at some point, but I have yet to find a newer module that has a nice command interface like the RN-42, isn’t impossible to solder, and doesn’t cost a fortune.

      The kit as if right now cannot be updated to v3 firmware as it needs to be assembled to update the firmware =). I still have a small stock of the chips from my last Scantool order, so obviously those’ll be used up before I order some more. The completed units will ship w/ updated firmware. The kits will probably ship w/ the latest firmware, assuming future batches of chips have the latest firmware already loaded.

      -Amdy

  24. Jeff says:

    nice unit i have the vgate scan bluetooth unit it’s a nice unit as well but i have notice that the response time is kinda slow, what software for pc can i use that has more of a smooth respones, i have torque(free) version for my android phone and it seems to work great and fast response, i’ve tried touchscan for pc and it seems to leg by a secand or two ,what shareware/freeware software with gauges would you say would be best for a laptop, odbii software that i have searched for seems to be not cheap from 80 bux and up kinda much for personal use i don’t drive but my girlfriend does and shes always worried about sounds and stuff with her truck so i got a unit to keep an eye on things and what is the response of your unit with pc software or should i go with a hardwired unit or what kind of bluetooth dongle should i use for faster response. thanks

    • Andy says:

      Jeff,

      Ok so there’s quite a bit there, but what I think you’re asking for is recommendations on what PC software gives quick, responsive updates, and you’re also wondering if you need a new reader or not.

      For the PC software, I’m probably not the best to ask as I myself have yet to find a piece of software that I really like. Scantool’s ScanXL Pro is nice, but I only use that for stuff that Torque doesn’t really do, like communicate w/ ABS and stuff besides the ECU. I wasn’t terribly impressed w/ the gauge stuff in this software. They do also have OBDWiz, which is their cheaper software that comes for free w/ their adapter purchases. I’m not sure how great that software is as I’ve never used it. All the free OBD software I’ve tried in the past have been absolutely awful. Hopefully this has changed since I’ve last sought out the free OBD stuff for the PC. But if things work great w/ Torque on your phone, what would using some other program on the PC get you that Torque wouldn’t? Seriously, pay the $5 and see what Torque pro is all about. There’s soooo much more Torque Pro does compared to the free version.

      As for the adapter, if your Bluetooth adapter gives you the quickness you desire w/ Torque, it’s probably not the adapter that’s pokey on the PC side of things, but rather sucky software or maybe your PC’s Bluetooth adapter is crappy. It’s hard to say. But if you want the fastest updates possible, the OBDLink MX is the fastest via Bluetooth, and the OBDLink SX is supposedly quite fast hardwired. My adapter was aimed at being the smallest adapter out there, and being cheaper than most other quality adapters out there, and being open-source. So while my adapter gives plenty fast updates for me, the two OBDLinks are faster, but you pay 2x as much as mine for the MX and you’re stuck w/ a wire with the SX.

      -Andy

  25. Jeff says:

    When did you start creating these? I designed a similar bluetooth diagnostics module for a school project in 2004. iPhone wasn’t available, so it went to PC.

    • Andy says:

      Jeff,

      This all started back in 2000 w/ an ELM327 and a large home-etched and drilled PCB. The OBDII reader connected to an ancient palmpilot via RS232 and ran Dana Peters’ OBDGauge software. That adapter was way too large to use all the time, and once the STN1110 came out, it finally made sense to try and make something that was more affordable and better than the ELM327. Bluetooth was everywhere, modules readily available, quickturn cheap PCB houses are everywhere as well, so the time was right for making a really small module. My first prototype was built in I dunno, probably 2010 now. There were several flavors of the modules, and I finally ended up with one “flavor” that was superior to the others, which is what is for sale/download on the site now.

      I’m now working on a similar module w/ single-wire CAN and medium speed CAN support and hope to have that ready to go in a month or two.

      -Andy

      • Colt says:

        “I’m now working on a similar module w/ single-wire CAN and medium speed CAN support and hope to have that ready to go in a month or two.”

        What ever came of this? I assume development was/is with the STN1170?

        • Andy says:

          Colt,

          Well the module is developed and as far as I know it works well and is a little shorter than my current module, but I don’t have a vehicle to test MS or SW CAN on so I can’t really call this complete at the moment. Plus I’m having time issues at home w/ everything going on for the holidays, so it’s tough to allocate time for trying to find someone local that has a vehicle I could test with. Once I verify that MS and SW CAN works on my design (which is different from the reference design provided by Scantool.net), then I’ll post it for sale and all that. This is taking longer than I had hoped for though :-/

          – Andy

    • cameleven says:

      Does this work with the Iphone4?

      • Andy says:

        Hi,

        The main thing that prevents this module from working w/ any of the Apple products is the lack of any software support for ELM327 (or compatible) units operating via Bluetooth. The other thing that is lacking is the Apple authentication chip on my module, but if your Iphone/whatever was jailbroken, you could pair to the module that way. But still, w/o software support, it doesn’t really matter if you can pair to the device or not =).

        -Andy

Leave a Reply to pat Cancel reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.