IIRC a splitter is hit or miss when trying to run two monitors. I'm pretty sure @Qholic did it for a while, but I think he had a special startup procedure to get them to work. I don't think he has been on in a while, but maybe he'll see the tag.

 

Haven't seen/heard from him for some time - miss his input. He showed me/us how to custom PID the Delta T.

Oh yeah, does any one know if the CTS can display Fan Speed????

 

agreed it is probably not the splitter just conflict between devices

 

I'm still around :grin: I have been extremely busy and considering I write for a living and just finished an MBA; I'm all typed out by the end of the night.

I still use the splitter but, what I found is that I had to start the SCT first before starting the Torque app. It seems that the SCT wants priority and will not connect to the OBD bus if another device is already connected to the port. That said, I have had a couple of times in the multiple years that I have run this configuration where the two monitors (I'm guessing) tried to connect at the same time; they did, but it threw an engine light when the truck was started. The fix was to shut down and let them connect one at a time.

I like my setup, it's not the fanciest but, it allows me to have EGT monitoring and monitor another 18 PIDs or so.

 

Gonna try that - THANKS!!!!!

:yourock:

 

Yea I tried to run the sct as well as tmobile's vehicle tracker (Speed, location, wifi, ect) but couldn't get them to work at all together. From what I read it's because when retrieving information you have to send data to the ecu/pcm in order to get a response and when another device sees that request it freaks out. I haven't tried the sct and torque because it seems kind of pointless because you can have whatever PIDs you want running on torque.

 

I haven't tried the sct and torque because it seems kind of pointless because you can have whatever PIDs you want running on torque.

Not exactly pointless; you cannot monitor EGT with Torque.

 

I've used a splitter in my truck for almost a year now. I had to replace it once due to a wonky connection. I generally buy off of Amazon, that way I can read reviews and hopefully get a slightly better one.

I split mine, one for the HP Tuners Ngauge with tuning and PID scanning, and the other one for an AT&T hotspot. (I have an Android replacement head unit, and it used the hotspot for maps and streaming)

Whenever I flash a new tune from the Ngauge, I unplug the splitter. One time the truck wouldn't start after a flash, so I unplugged the splitter, bypassed it, reflashed the tune, then it worked. But I can generally leave both plugged in without it causing issues. Due to how many times I flash new tunes though, I expect the $8 splitters to wear out on me sooner rather then later, so I do have a spare in hand.

 

I didn't like the extra "stuff" down there so I ditched my splitter and hard wired a stub of ethernet cable wired for my Scangauge 2. I use an ethernet coupler and any length ethernet cable I want. Connecting the Scangauge and Torque at the same time is hit and miss. Sometimes they just don't like to play nice.

I always disconnect everything when I am changing my tune. I have no desire to find out if it will cause a problem or not.

 

Where did you splice into the OBD wires? In the truck wire harness close to he OBD port?

 

Scangauge II Hardwire Information

This mod requires decent soldering skills and the ability to extract pins from the OBD II connector without damaging anything. If you are not sure you can do that, you can still use the pinout information below to directly splice wires into the OBD II wiring.

While I was away, my wife cleaned my desk and organized my papers. Now I cannot find my original diagram on how I hardwired my Scangauge. Fortunately I still had my test rig so it wasn't too hard to reproduce. I went out to the truck and confirmed the connections so as long as you have my truck it will work. (That's my disclaimer. This has only been confirmed to work on my truck. If you break anything on yours it's all on you.) Though it should work for you too.

I compared the pinout for the Scangauge cable (top part of connector image) and the OBD II connector (bottom part of connector image) to determine which pins are being used. I narrowed it down to pins 4, 6, 7, 14, 16 of the OBD II connector. From the Scangauge pinout I matched those up to pins 1, 2, 6, 3, 8 of the RJ-45 connector.

Then I took an ethernet cable and determined the wire colors for the RJ-45 pins using a TIA/EIA 568B wired cable. (There is a 568A wiring spec but they are not ac common as the B spec. Regardless, check your cable type. It should be printed along the length of the cable.)

Here are the ethernet wire colors and pin number aligned with the OBD II pin numbers. (I didn't record the wire colors.)

Ethernet (pin) ---------- OBD II (pin)
White/Orange (1) ------ (4)
Orange (2) ------------- (6)
White/Green (3) ------- (14)
Green (6) -------------- (7)
Brown (8) -------------- (16)

(This part is optional if you trust me.) Next I built a test rig (see attached image) to confirm the wiring before I pulled the tuck OBD II connector apart. I cut a short piece of ethernet cable and soldered nails to wires 1, 2, 6, 3, 8. Be sure to use nails that are approximately the same size as the OBD II connector pins. After inserting the nails into the proper connector holes I plugged the Scangauge in and ran some tests. Everything worked fine.

Next I pulled out the OBD II connector and used a pin removal tool to extract pins 4, 6, 7, 14, 16. Then I soldered the corresponding wire from a short piece of ethernet cable with an RJ-45 connector on the other end. (This is critical because otherwise you would have to crimp an RJ-45 on the stub. Too hard.) When you are soldering you must be very careful to keep everything small enough for the pin to fit back into the OBD II connector.

Once everything was all back together, I used an RJ-45 to RJ-45 coupler (ethernet coupler) and an ethernet cable (568B spec) to connect my Scangauge. I have been running it like this for over a year without any issue. (See attached image. Red cable is hardwired. Couple is beige and ethernet cable to Scangauge is black.)

Even though the factory OBD II connector is open, I cannot guarantee that other devices will work correctly with the Scangauge connected at the same time. I would also caution you to disconnect the hardwired Scangauge any time a tune or update may be flashed to your vehicle by you or another technician.

 

I run the SCT and ScanGauge via a splitter. The initial power up requires the SCT to go first so I unplug the back of the ScanGauge. The SCT will not program the truck thru the splitter so I have to reach under the dash and swap cables. Thankfully I don't change too often