pXius
New member
Hi guys,
I've got a bit of a unique problem and I'm starting to think I might have a faulty JB unit.
So here it goes:
I've got a weird problem where JB4 Mobile does not work properly when using the CANbus setup, I'm tapped into the blue and gray wires behind the OBD port for a more stealthy setup. I have full CANbus control when doing so (Flap opening and closing, map switching etc).
Problem:
With JB4 Mobile running, certain data like REV and AFR is delayed and only updates every now and then. Sometimes it stays stuck at 0. I'm using an OTG cable with android device (Dell Venue 7 Tablet). Its the same when logging with a laptop using the JB4 interface.
Also when JB4 mobile is "connected" CANbus controls no longer function, not sure if that's normal though.
No other devices on CANbus.
Things I've tried:
-2 other OTG cables,
-Reflashing firmware and older firmwares,
-Another Android device (Galaxy Note 3)
-Wires from CAT7 Lan cable from engine bay to keep wire resistance to a minimum.
-Checked USB serial connection on JB4 unit. Seems fine to me.
Vehicle is a 2013 PWG M135i Right hand Drive.
Here's a video of the behavior on JB4 Mobile, followed by a video of the behavior via the JB4 interface on a laptop.
[video=youtube]
[video=youtube]
Posi Tap Method.
Posi-Tap Setup works fine, or better at least...
So when using the posi taps logging is much better. Things like throttle, and Revs are now at least live. I have found AFR and Trim to sometimes freeze for a few seconds but disconnecting and reconnecting solves the problem.
Here's a video of logging behaviour via positap method on a laptop.
[video=youtube]
The only thing I haven't tried is the original Burger OBD cable but I don't see how that will benefit over tapping into the wires behind the OBD port as they also use the stealth method on some cars from what I have read.
I have posted on N54tech but it seems that even Terry has not encountered the problem before. Obviously they don't have access to right hand drive PWG M135i's, so I'm hoping someone here might have an idea as to where the problem lies. :smashScreen:
New theory.
The TTL 232R chip in the BMS USB cable might be faulty. From what I understand the JB4 uses 3 wires from the chip, Ground, Data up(Tx) and Data down (Rx). Considering I have no problem with uploading new maps or switching maps via Tablet or laptop I think the problem might be with Rx. Maybe the chip is struggling to process received data?
Only way I can test that is with another cable -_-
I've got a bit of a unique problem and I'm starting to think I might have a faulty JB unit.
So here it goes:
I've got a weird problem where JB4 Mobile does not work properly when using the CANbus setup, I'm tapped into the blue and gray wires behind the OBD port for a more stealthy setup. I have full CANbus control when doing so (Flap opening and closing, map switching etc).
Problem:
With JB4 Mobile running, certain data like REV and AFR is delayed and only updates every now and then. Sometimes it stays stuck at 0. I'm using an OTG cable with android device (Dell Venue 7 Tablet). Its the same when logging with a laptop using the JB4 interface.
Also when JB4 mobile is "connected" CANbus controls no longer function, not sure if that's normal though.
No other devices on CANbus.
Things I've tried:
-2 other OTG cables,
-Reflashing firmware and older firmwares,
-Another Android device (Galaxy Note 3)
-Wires from CAT7 Lan cable from engine bay to keep wire resistance to a minimum.
-Checked USB serial connection on JB4 unit. Seems fine to me.
Vehicle is a 2013 PWG M135i Right hand Drive.
Here's a video of the behavior on JB4 Mobile, followed by a video of the behavior via the JB4 interface on a laptop.
[video=youtube]
Posi Tap Method.
Posi-Tap Setup works fine, or better at least...
So when using the posi taps logging is much better. Things like throttle, and Revs are now at least live. I have found AFR and Trim to sometimes freeze for a few seconds but disconnecting and reconnecting solves the problem.
Here's a video of logging behaviour via positap method on a laptop.
[video=youtube]
The only thing I haven't tried is the original Burger OBD cable but I don't see how that will benefit over tapping into the wires behind the OBD port as they also use the stealth method on some cars from what I have read.
I have posted on N54tech but it seems that even Terry has not encountered the problem before. Obviously they don't have access to right hand drive PWG M135i's, so I'm hoping someone here might have an idea as to where the problem lies. :smashScreen:
New theory.
The TTL 232R chip in the BMS USB cable might be faulty. From what I understand the JB4 uses 3 wires from the chip, Ground, Data up(Tx) and Data down (Rx). Considering I have no problem with uploading new maps or switching maps via Tablet or laptop I think the problem might be with Rx. Maybe the chip is struggling to process received data?
Only way I can test that is with another cable -_-