When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
If so, how are you doing it? Jet is less than helpful. They don't have much interest in supporting this anymore and their tech line people only speak LS.
I just got my new 383 running. I went into the constants and adjusted the engine size from 350 to 383 and adjusted the idle speed up to ~900 rpm as my cam is a little rowdy at idle.
Runs pretty good but at very small throttle openings and light load/low rpm it is a little herky jerky. Would like to be able to datalog from the DST and my Innovate wide band to see what to adjust next, and for when I bolt the vortech on....doing the impossible!
I see from your post history that you have a '96 (at least, you posted about having one, my apologies if I'm wrong). That being the case, you can datalog using any off-the-shelf OBDII software. It's not unique to the LT4. Even something as simple as the OBDLink would be able to datalog for you. Best of luck!
Thanks for the reply, and sorry for making so many assumptions (Jet DST = must be a '96) in my post. I guess I am interested in the actual physical interface. The DST box has a four pin connector on the side that is casually mentioned in their literature as being available for datalogging. But they offer no pinout or clue as to what protocol the data port might use. I was hoping to datalog with a smaller device than a laptop, like maybe ab iPad or phone without purchasing another device.
My setup is:
383 all forged, port matched stock LT4 top end, custom Comp cam, Racetronix 255 lph fuel pump, Aeromotive FP regulator. I have a Blowerworks bracket and dedicated 8 rib drive already installed and plumbed and as soon as the engine is broken in a bit will install the Vortech V2. Water/Meth injection.
Seems like it would be proprietary; I can't find any information on 14005 having datalogging capabilities, so if JET themselves won't tell you, you're out of luck.
As for your wanting to datalog with a small device, that's really not a problem; again, any off-the-shelf OBDII solution will work. OBDLink, for example, has versions of their hardware that work with Android devices. Sadly due to how Apple implemented their Bluetooth protocol they don't work with iPad. Anyway, the OBDLink LX Bluetooth is $60. No need to go searching for the more expensive versions since your '96 doesn't use GMCAN or any of the newer protocols. Your PCM speaks regular OBDII, and the rest of the computers in the car speak 8192 ALDL (the old OBDI protocol).
Last edited by Nomake Wan; May 19, 2020 at 09:46 AM.
Agree, I've never heard of any data-logging add-on or capability with Jet DST. I just don't think they ever implemented it. I have used OBDLink successfully on my 96. Mine is the WiFi version.
Agree, I've never heard of any data-logging add-on or capability with Jet DST. I just don't think they ever implemented it. I have used OBDLink successfully on my 96. Mine is the WiFi version.
By Wifi, you mean you are using the Bluetooth version? How is the lag?
By Wifi, you mean you are using the Bluetooth version? How is the lag?
No, he means the wifi version. OBDLink MX Wifi. It's no longer for sale, but it used to be, and for those platforms which supported it it was an amazing tool. Here is a benchmark from Harry of Harry's Laptimer of various devices, including the OBDLink MX Wifi:
For the OP, Harry's Laptimer is actually a decent resource for OBDII adapters capable of datalogging in general. Here's their list for iOS: http://www.gps-laptimer.de/compatibility/ios
Last edited by Nomake Wan; May 19, 2020 at 01:10 PM.
No, he means the wifi version. OBDLink MX Wifi. It's no longer for sale, but it used to be, and for those platforms which supported it it was an amazing tool.
Yep, that's the one. I didn't know I had such a unicorn! FWIW, the WiFi connection was a little flaky in my C4 - it would connect sometimes, but not at others. I think I read somewhere that the power lead on that ALDL connector may not be quite to modern specs, even though it's fully OBD2 compliant. It has always worked perfectly in every newer car. So the Bluetooth version may actually be the better bet for a 96 C4.
Last edited by MatthewMiller; May 19, 2020 at 02:14 PM.
The OBDLink MX+ supposedly uses Bluetooth Low Power, which iOS does actually support, and it's supposedly just as fast as the old Wifi version. However, it's also out of stock with no ETA on restock. So for now, the LX and an Android tablet/phone would work.