STN1170 Bluetooth OBDII Adapter

This page contains all the information for all the STN1170 Bluetooth OBD-II module I’ve designed.  This is even smaller than my STN1110 based reader (files, comments, and other info still available here:  STN1110 OBDII Reader) and is the smallest module of its kind that I’ve seen to date.


All of my Bluetooth OBD-II modules work very well with‘s ScanXL OBD-II diagnostic software for Windows.  FORScan (for Ford vehciles) and CANIon are other apps that are popular with the STN1170/STN1110 based readers fro Windows.

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.  If Bluetooth 4 Low-Energy based OBDII adapters catch on and iOS OBDII software is available, I’ll most likely design a reader for Bluetooth Low Energy.  At this point, it doesn’t make sense to create one without software support.

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:  STN1170 Bluetooth OBD-II Adapter Manual

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 you don’t receive your package within say 4 weeks of me informing you that I shipped your item, contact your customs office as it is probably held up.  The amount of tracking provided unfortunately depends on the country being shipped to.  For most countries, you’ll receive your package in 2-3 weeks.

At the moment, enclosures are not available for the reader.  Depending on interest in the readers, their sale may end up funding a custom enclosure design.

Assembled Modules:

STN1170 Bluetooth Adapter – Fully Assembled and Tested (Out of Stock)
 STN1110 RN-42 Top ViewSTN1110 RN-42 Bottom View
$85 shipped (USA)
$125 shipped (international, tracked)

Download open hardware Altium sources and gerbers for STN1170 Bluetooth and STN1170 Driver

The STN1170 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
STN1170 OBDII Bluetooth Module by Andrew Honecker is licensed under a Creative Commons Attribution 3.0 Unported License.

78 Responses to STN1170 Bluetooth OBDII Adapter

  1. lee bright says:

    Hello Andy,
    In seeing your work and answers, obviously you are an expert on HW/SW and vehicle interfaces. I also heard the STN1170 chipset is the one to get and it is also considered for embedded systems where developers can create custom interfaces with reliable data transfer. I am NOT at a level you are, but would like to have an oppurtunity to use a module like you have created. I work as the blunt knife among surgeons. I need a reliabe way to access specific data sets that may be available on a myriad of vehicle types and the STN1170 was highly reccomended by my coworkers that are more on your level.
    Currently for CAN, I have been using GridConnect and their CanExplorer5 software, However through peer direction. Problem with that is other ISO types are not supported. i.e. KWP,KLine,VPW etc.

    Sorry for long prelude, but noticing that it is out of stock and many of the posts are around 2013 is there a chance of getting one of your units you designed, noted below? The closest match I found was at this site.

    Assembled Modules
    STN1170 Bluetooth Adapter – Fully Assembled and Tested (Out of Stock)
    $85 shipped (USA)



    • Andy says:

      Your best bet would be the OBDLink MX I think if you’re on anything other than Apple devices. I don’t have plans to make new readers or run another batch of old.

      – Andy

  2. Rich Pasco says:

    I come to you recommended by this post.

    My 2012 Prius Advance Plug-In is now in “Fail Safe Mode” (FSM) following a communications failure with this cheap Chinese ELM327 Bluetooth adapter.

    My most urgent question is, how do I get my Prius out of FSM to re-enable normal driving? The thought of having it towed 15 miles to the nearest dealer is daunting.

    My second question is, how do I get one of your STN1170 adapters, since above it says “STN1170 Bluetooth Adapter – Fully Assembled and Tested (Out of Stock)”?

    • Rich Pasco says:

      Update: I got my car out of Fail Safe Mode by starting and stopping it a few times as described here. But I would still like to get an STN1170, since the Chinese ELM327 is not satisfactory.

    • Andy says:

      I have no idea how to get your car out of fail safe mode. Glad you figured it out though. As far as selling any OBDII adapters goes, I don’t have them for sale anymore due to extremely low interest with the last batch I made. It just didn’t make sense to continue on and sit on inventory for 3 years. All I can recommend doing is buying an OBDLink MX. They’ve come down in price significantly to the point where I’d imagine people would buy that reader vs mine.

      – Andy

  3. Steve says:


    Does the STN1170 input OBD-2 ISO 9141-2 and convert it to CAN protocol? There is an in-car device that I want to use with my 1999 Mitsu, but it (the device) uses CAN High/Low output not the older ISO 9141-2.


    • Andy says:

      Steve, I’m not really sure what you’re asking. CAN is an electrical interface and ISO9141-2 is a protocol. There’s no cross-protocol conversion done if that’s what you’re asking….

      – Andy

  4. LUIS says:

    Do you sell schematics for USB based STN1170? I get STN1170 from ScanTool friends, but I have a ELM327 so my plan is to convert it (or just build a STN1170 adapter from the scratch)

    Thanks for the reply!

    • Andy says:

      No, I don’t sell schematics. It’s simple though, you just need a USB to UART chip (FTDI has a number of them) and connect that to the serial UART of the STN1170.

      – Andy

  5. Anthony says:

    I’m wondering if the stn1170’s firmware is updatable I have tried from but it says the bootloader is not supported but the version of update utility.

    I have come across a problem with leaving it attached to my car so wanted to update hopeful that it would fix it.

    • Andy says:

      Yes you can update the module firmware, but the STN1170 firmware has not been updated since I made units based on that chip. What problem are you having when leaving it attached to the car? I’m assuming you’re using a STN1170 unit you bought from me. I don’t seem to have a record of you buying a unit from me (using the provided email address).

      – Andy

  6. Tosh says:

    Alex, wondering if you have thought about repairing/selling the few STN1170 test modules you have. Or perhaps making available the design. Apparently, other than the OBDLink MX, there are no products with the STN1170 chip.

    • Andy says:

      Dunno if you’re asking me a question or not, but no, I’m not going to bother with repairing and selling the STN1170 units I have. They are likely damaged due to electrical abuse, so while I can certainly repair them, my confidence that other parts aren’t damaged in some manner too isn’t good. The STN1170 design is freely available on my site, and the OBDLink MX does not use a STN1170 chip in it. It’s similar and probably runs similar code, but it’s not the same chip.

      – Andy

      • Tosh says:

        My apologies Andy, I was writing quickly. Yes I was talking to you. Thanks for keeping this page open. If I can get some free time, I’ll try to make a few modules for my own use, based on your design.

  7. Nishanth says:


    I’m interested in developing the software for a BTLE variant of your device (with a Nordic BTLE chipset). Would you be interested in building one together?


  8. Steve says:

    What an awesome job.
    Since the STN1170 is a canned solution, how is the RN42 configured?
    Does the RN42 just power up in SPP mode and is transparent to the STN 1170?

    • Andy says:

      The RN-42 that I use is preconfigured for SPP, but I do set up a number of parameters over the air before setting up the STN1170. The STN1170 requires configuration as well to get the most out of it.

      – Andy

  9. ressaunt says:

    Your STN1170 for my i-Miev/Peugeot Ion appears to be out of stock.
    Could you estimate when it will be available for purchase again, please?
    Could you ship to the UK by USPS?
    Many thanks.

    • Andy says:


      Yes it is out of stock most likely forever. There just isn’t enough interest to warrant making another batch. Even when I made the first batch, there wasn’t a lot of interest, but I made them anyway. Then I sat on inventory for about 1.5 years before running out =). It just a lot of money to tie up for that amount of time.

      Anyway, I am looking to open source the design sometime before 2015. Maybe that’ll help you? Also, I do have a few units that have died, so I may repair those and offer those for sale at a reduced price.

      Yes I only ship USPS overseas as they are by far the cheapest option. If you can do without tracking and don’t mind a 2-3 week wait, that shipping option is $20 USD. Normally I ship using the $40 option which includes tracking.

      – Andy

      • ressaunt says:

        Apologies for the delayed reply. We have had a great summer for a change and time flashes by. Thank you very much for letting me know your position on production of the STN1170 for my Peugeot Ion. How disappointing for you. I would be interested in a repaired unit and look forward to hearing from you about their availability – or not. I do hope others will add their interest in a unit too. Post by USPS, tracked, would be fine in the event. Please let me know what you decide.
        Best wishes, Tony in East Devon, GB.

  10. Gilson Roizman says:

    Hi Andy,

    I was taking a look at the picture of your STN1170 Bluetooth Adapter and found that although the power supply is up to 40VDC, it is not using the J1962 type B connector for 24V vehicles (with a split slot designed to prevent the J1962 12V male connector of the adapter from being plugged into a 24V vehicle).


    Could you verify?


    • Andy says:


      I don’t know much of anything about the J1962-B versions of connectors so…if you think it won’t fit, it probably won’t =). It also makes sense that you wouldn’t want to accidentally plug a 12V device into a 24V system. I’m also not claiming that you can use the reader on a 24V system w/o issue. As far as I can tell, it should work, but there could be other electrical changes that I wouldn’t know about that could cause issue. I’d say proceed at your own risk.


  11. Michael Luscher says:

    We actually spoke before about FORScan, I’m glad to see that it’s been more widely accepted. I know this question has been beaten to death, But how does the performance on this compare to a OBDLink MX/SX that are STN1110?
    I would assume anything would be better then my ELM327 clone, Just curious before I buy.

    • Andy says:


      For FORScan, I don’t really know. If you’re using FORScan, I’m assuming the primary reason is to sit on the MSCAN bus, which if I remember right, the OBDLink SX can’t do. The OBDLink MX can get on the MSCAN bus. The OBDLink adapters aren’t STN1110 based per se, but I wouldn’t be surprised if the codebase running in the chips is nearly identical to the code in the STN1170/STN1110. I have not compared MSCAN access rates, but based on the high speed CAN performance, the OBDLink MX is faster than my adapter (aka more PIDs/sec).

      – Andy

      • Michael Luscher says:

        I hate to be a bother again, But do you have any comparative numbers against the MX?
        How much slower or faster would we be talking? I’d much rather give the purchase to you, and I would assume anything’s going to perform better then my current ELM327,
        But what are we talking about in terms of performance?

        • Andy says:


          Somewhere either in the comments or on the STN1110 page I talk about performance differences. Roughly speaking, the real throughput will be determined by how quickly your car and your host device can respond, but assuming those aren’t the bottlenecks, the MX is about 2-4x faster in terms of PIDs read per second (obviously this is very dependent on the PIDs requested).

          It may or may not be faster than your ELM327 adapter, especially if your current adapter is USB based. Bluetooth is rather pokey for lots of small transfers due to protocol overhead. I’d doubt you’d see a huge performance difference of a STN11xx device over a ELM327 device that’s USB based (comparing OBDLink SX with some ELM327 device).

          – Andy

  12. Vic says:

    1) Does the actual device ship with schematics?
    2) How is Blutooth pairing security implemented?

    • Andy says:


      No, schematics are not provided as this is not an open-source device and it’s not really all that easy to pull the thing apart to do anything with it. I have not released schematics of this unit like I have w/ my STN1110 unit as there have been a number of people contacting me with questions about blatantly ripping off the design for their own products. As such, I don’t know if I will ever release the STN1170 reader schematics. Anyway, you can get the gist of what’s going on w/ this reader from the STN1110 schematics on my site.

      The Bluetooth pairing is implemented via the RN-42 module. It’s probably not terribly secure even though encryption is enabled. The OBDLink MX does a better job w/ Bluetooth pairing security, but at the expense of end user annoyance w/ their pushbutton pairing.

      Hope this helps!

      – Andy

  13. David says:

    Hi, Andy.

    Your dongle worked perfectly for 2 months with CanIon app for Mitsubishi I-miev. Few weeks ago I tried to use it with Torque on ICE car. No problems at all. Then I reconnected it to I-miev. No data shown any more on phone. It pairs OK I guess but no data transmission. Now it works OK on ICE car and not on I-miev.

    Is there a way to update it or something to make it work again?


    • Andy says:


      I’m not sure what you’re referring to when you say “ICE car”. Things should work fine w/ the iMiev regardless of what other vehicles you connect to. However, if CanION doesn’t explicitly set the protocol (if for some reason this ICE car has a different protocol in use), CanION may be trying to connect w/ an incompatible protocol for the iMiev. Or something went wrong w/ this ICE car and it blew out the CAN transceiver….

      – Andy

  14. Oliver says:


    Why it doesn’t make sense to create a bluetooth 4 Low-Energy based OBDII adapter without available iOS OBDII software?
    Probably the software will be made, if an adapter exists?
    (And for Androide useres etc. would be no difference!)

    I would like to have one and then test to write my own iOS Software!
    (But without hardware, this is not possible!)


    • Andy says:

      It would not be the same on Android without some piece of software involved to convert whatever Bluetooth 4.0 profile is chosen into the serial port profile (SPP) of bluetooth 2. OBD apps on android are expecting to talk with a serial stream, not some other profile hijacked to transfer the necessary data (bluetooth 4). Bluetooth 4 OBDII readers exist, but does some common software exist? Nope. So as I’ve said a number of times in the comments, until some general purpose app like Torque arrives and some sorta-standard way to transfer OBDII data via Bluetooth 4 exists, I’m not going to spend time designing a Bluetooth 4 adapter that maybe one or 2 people might possibly use.

      – Andy

      • Matt says:

        I haven’t been able to find any Bluetooth LE OBD-II readers (other than the custom one from Automatic). Since you’re not making them, would you mind posting where we could find one? I am planning to develop software for iOS to read from a 4.0 LE adapter. I also plan to mass produce and sell them to customers. Would love to hear who is making them so I can purchase some.

        • Andy says:


          At the moment, I don’t know of anyone that’s making a BTLE adapter that also isn’t creating custom software for the hardware (in other words, closed source on both ends). You could certainly obtain one of those adapters, but you’d probably have to reverse engineer what’d going to and from the adapter to make it useful for you. There are a few other BTLE adapters out there. I’ve run across them here and there. I just don’t remember the names of them unfortunately. I even forgot about Automatic lol.


          • Matt says:

            I bought an “Automatic” to see if I can pull any useful data from it. Will know in the coming week or so whether I can connect to it. Going through a little learning curve on iOS development at the same time. Fun stuff.

  15. Matt Starbuck says:

    What’s your general delivery time on STN1170 units right now? (continental U.S.). I’m sure I’m missing it here somewhere, but I don’t see where it says whether stuff is in stock or not, or what the order-filling time is at the moment.
    Not complaining; I know you are a small operation, and I appreciate that.
    I do see all the detail about “out-of-country” delivery times, etc.
    Regards, Andy.

    • Andy says:

      Delivery time is about 2-3 days from when I ship. I normally ship the next day. Paypal will prevent you from ordering if there aren’t units in stock.

      – Andy

  16. MikeInDetroit says:

    What would be involved in creating a GSM version of this, instead of Bluetooth, and packaging the request/replies in SMS?

    • Andy says:


      You’d need a GSM modem and possibly an external microcontroller, depending on what the modem has onboard. I think this would be slow as molasses to use SMS to send/receive PID requests and responses, but I also don’t know your application. It could definitely be done w/ some messing around in hardware and software.

      – Andy

      • Michael says:

        You’re correct about the speed. But first, if you check the new DL 7-Series – Hybrid Bluetooth you’ll see that some devices are being created with both. Now, as you are aware, the STN1170 can access MS CAN protocol. The data available via this access is most useful remotely. Having said that, what would really be require for a production version would be packaging communication in the form of SMS messages. This is how it’s done with other products such as the MT3050 or xirgotech 2000. None of them, however, provide STN1170 type access.

      • Michael says:

        Oh, BTW, I have the MX and it does everything I need it to do. We have a working mini-app that’s verified the required functionality. Except I need it to do it over GSM/CDMA.

  17. Keith says:

    Is schematics and drawings available? Can I buy your kit without the BT module?

    • Andy says:


      Yes you can buy the module w/o Bluetooth installed if you’d like for $10 less.

      Schematics are not available for the STN1170 unit at this time. See the STN1110 based unit for a full, open-source design.

      – Andy

  18. Kethav says:

    Hello, I would like to know if this OBD interface support the MS-CAN bus (Ford proprietary).

    I plan to use it with Forscan software which already is compatible with STN1170 chip or ELM327.
    In case of ELM327 is required to add a switch and select manually which protocol to use HS-CAN (standard pins @ 500kbaud) or MS-CAN (ford specifications pins @ 250kbaud).
    In case of STN1170 it should automatically switch on correct pins and baud rate without the need of any hardware modifications.
    More info here:

    So, is your OBD interface compatible with MS-CAN protocol and so Forscan software?

    • Andy says:


      Yes, the reader supports MSCAN and FORScan. I have used FORScan successfully on my MSCAN-enabled Ford Edge. Keep in mind though that a quirk of the STN1170 and the MSCAN/SWCAN interfaces is that it does not keep the connection alive. After a period of inactivity, it disconnects from the bus (or the vehicle “kicks” it off the bus) and the connection needs to be re-established to start communicating on the MSCAN interface again.

      You probably already know this, but the STN1170 cannot communicate on HSCAN and MS/SWCAN simultaneously. You can communicate on one or the other, but not both at the same time. This is a limitation imposed by the STN1170 (or rather to be more exact, the PIC they’re using for the STN1170).

      – Andy

  19. Sam says:

    Andy, great project! Very interested in buying one at some point in the future.

    Quick questions!

    Will this work with a Mac? Specifically I use a 2011 MacBook Air and MacBook Pro? I will be using primarily FORScan, Scan XL, and OBDWiz in a virtual machine on my computers. If it can connect to mac it will connect to the VM.


    • Andy says:


      That’s a good question. I haven’t tried the reader in this kind of a configuration. My gut feel is no, it wouldn’t work, but in reality, whether or not this works will depend on a lot of nitty gritty details surrounding Bluetooth and how your virtual machine handles things. Your best bet to have this run on a “mac” is probably to use bootcamp or whatever they call it now to dualboot OSX and some version of windows.

      Anyway, the virtual machine *may* work if the following are true:
      – OSX supports the serial port profile (SPP) portion of Bluetooth
      – The virtual machine can see your paired Bluetooth OBDII reader and do something w/ it to show up as a virtual COM port or something to that effect to windows running on the virtual machine.
      – The virtual machine doesn’t mess w/ the Bluetooth traffic

      Unfortunately I don’t have a solid answer to your question other than give it a shot and see what happens. I’ll send you an email to discuss this further.

      – Andy

  20. Mitch says:

    Hi Andy,

    Great design! Do you know if the battery state of charge data can be extracted over OBDII from an electric vehicle such as the Toyota Prius? I have been looking everywhere for SOC codes but have not come across anything.

    Thanks, Mitch

    • Andy says:


      Most likely if the ECU uses that data for something, you *could* access it w/ an OBDII reader. You just need to know the manufacturer specific code to do so. Unfortunately I don’t know what this would be. You might try talking w/ someone in the service/parts dept. at a Toyota dealer and see if you can get them to let you look at a book or something that lists out the specific codes.

      – Andy

    • priusfan says:

      hello Mitch
      Yes, definitely it is possible to get the SoC from a Prius using this device.
      Have a look on priuschat.
      You can try to write your own program (quite a difficult job) or use Torque.
      I confirm Andy’s device works perfectly with Torque on android phones or tablets.

    • paja says:

      Download the customized CSV from’s thread –

  21. Lee says:

    I’m interested in your adapter Andy, but I have a few questions/concerns:

    Has this been tested with FORScan to see if it supports MS CAN bus functions?

    How does your adapter compare with the OBDLink MX in terms of speed? Can it reliably produce 60+ PIDs/sec?

    Are the boards physically robust enough to handle being pushed or pulled on to insert/remove the adapter? A lot of sockets have a tight fit in a tight location, so I’m concerned whether this will hold up to anything other than extremely light use? You said an enclosure may be forthcoming, but I’d be happy with something like a puller tool that would temporarily hook around onto the connector?

    IC ships with latest 3.3.1 firmware, right? Can the firmware be updated over Bluetooth in the future or do you need some kind of wired interface?

    Could you possibly provide a depth dimension from the bottom of the DLC socket to the top of the Bluetooth IC (AKA estimated stick-out amount)? I have a door over my OBD port and I’d like to roughly determine if your adapter will fit in there with the door closed.

    Any future plans to create a version with built-in automatic data logging or a cabled version?

    Thanks for the cool projects,

    • Andy says:


      I’ve never heard of FORScan, but it appears that it added support for STN1170 MSCAN functionality so I don’t see any reason why this wouldn’t work. The adapter has been manually tested on a MSCAN bus and it worked (really not much different from Scantool’s MSCAN ref schematic).

      For speed compared to the OBDLink MX, this has been mentioned numerous times, but no, the RN-42 limits throughput and the adapter can sustain probably 30 PIDs/sec max.

      If you grab the board stack by the short edges where the board to board connectors are, you won’t stress the boards at all. The unit is really meant to stay installed all the time, but it isn’t fragile either. Even if you pulled/pushed along the long edges of the PCB, if you’re grabbing onto both PCBs at the same time, that shouldn’t be a problem either.

      Yes, the units ship w/ the latest firmware that has put out (3.3.1 currently). Yes, you can update the STN firmware over bluetooth.

      I don’t have a ruler handy at the moment, but I believe the height above the OBDII connector is roughly 13-15mm. Dimensions of the whole unit are 40mm x 19mm x 32mm (LxWxH). You can see the STN1170 module (on the far left) compared to OBDLink MX height here:

      A datalogger is more of a specific flavor of OBDII reader and I really don’t think it would be useful for the vast majority of people. I really don’t have the time to write software, and while the processor/memory combo I’d choose might be good for some, there’d probably be an equal or greater number of people that it wouldn’t be sufficient for. A design that people could write software for would be better time-wise, but still, making a generic OBDII logger that can satisfy the masses unfortunately doesn’t seem realistic to me. Most people as it is think my reader is too expensive and a datalogger would just add to that price. Plus, OBDII dataloggers are already out there for sale now =).

      I doubt I’ll do anything on the wired front either as I don’t have any advantage over any other wired reader. I suppose mine could be open source, but since all the cheapo readers out there are based on ELM327 or STN11xx reference designs, there’s not much point for investing that time. When I made my 1st readers, no one had a good, stable STN11xx based reader that was power efficient and very tiny. Now other tiny readers are out there, but last I knew they still lack the power efficiency and stability.

      – Andy

  22. John Adcock says:


    My 2012 Chevrolet Cruze eco DLC pinout populates pins 1, 4, 5, 6, 7, 12, 13, 14 and 16. I’d love to be able to monitor the Cruze eco air-shutter position, but I’m unsure which bus the shutter stepper motor is or whether the STN1170 would be able to access this information.

    Any comments?

    Thank you in advance for your interest,

    John Adcock

    • Andy says:


      Your Cruze supports SWCAN and HSCAN interfaces, although it is odd that the K-Line of ISO/KWP also seems to be present too. I’m not familiar w/ what the air-shutter is on your vehicle, but if it has something to do w/ the engine in any way, it’ll be accessible on the HSCAN bus (although you might need manufacturer specific codes to access something like this). Otherwise if this is a cabin air thing, or something not really engine, drivetrain, or safety related, it’ll be on the non-critical SWCAN bus. The SWCAN bus will need manufacturer specific codes to access whatever is present on that bus.

      The STN1170 can access either of those 2 interfaces, or even the K-Line, but I’d be surprised if anything is really sitting on that bus.

      The other weird thing is that 12 and 13 are populated too. I don’t know what those are used for, and as such, if there is some unknown interface on those pins, the STN1170 can’t access that.

      – Andy

    • Mikayo says:

      I have a little information about the GMLAN CAN Bus.
      As far i know, the DLC PIN on a Cruze is .
      1 Single Wire GMLAN
      4,5 Ground
      6 GMLAN Primary (+)
      14 GMLAN Primary(-)
      12 GMLAN (+) Chassis Expansion Bus
      13 GMLAN(-) Chassis Expansion Bus
      16 +Batt

      PIN 7 is not used …

      Kind Regards

  23. Mantene says:

    Any ETA and final price on this product?

    • Andy says:

      Apparently you missed the section above where you can buy the STN1170 units. They’re available and the price is shown above.

      – Andy

  24. Sam says:

    How much for a parts kit?

  25. Mauricio Saldarriaga says:

    Hello Andrew . i saw your module , i am interested to buy it but before i want to be sure that this will work with J1939 protocol in big vehices as Buses os Truck. have you ever tested it with a big vehicle , maybe a cummis engine or something similar.

    i hope it will work . i will wait your answer asap




    • Andy says:


      No, I have not tried the unit w/ any of the heavy-class of vehicles. The STN11xx chips support J1939. I’d suspect you’ll easily be able to get on the J1939 CAN bus just fine, but you’ll need software that knows how to communicate via the J1939 protocol. Scantool’s ScanXL might support J1939. Otherwise, you’d need to write your own software/scripts to be able to communicate via J1939.

      – Andy

Leave a Reply

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

Time limit is exhausted. Please reload the CAPTCHA.