Bluetooth OBDLink MX+ issue

I have a 1996 Nissan Maxima, an OBDLink MX+ and currently an iPhone. I can pair to the adapter just fine, it reads protocols, but once I go into RealDash it just keeps trying to connect over and over again. Adapter works fine on other apps. This is now my second adapter thinking maybe that was the problem. I have sent logs to the developers twice now with no response. I would really like to get this working if possible. I’m totally new at this but will try my best to help. Thanks

atd
OK

atz
atz


ELM327 v1.4b

atl0
atl0
OK

ate0
ate0
OK

ats0
OK

atsp1
OK

atdpn
1

0100
NO DATA

0900
NO DATA

atpc
OK

atsp2
OK

atdpn
2

0100
NO DATA

0900
NO DATA

atpc
OK

atsp3
OK

atdpn
3

0100
BUS INIT: …OK
4100BFBFB910

0120
NO DATA

0140
NO DATA

0160
NO DATA

0180
NO DATA

01a0
NO DATA

01c0
NO DATA

0900
NO DATA

atpc
OK

DETECTION COMPLETE
SUPPORTED PROTOCOL: 3, ISO 9141-2 (5 baud init, 10.
4 kbaud)
0100: 0xBFBFB910
SUPPORTED PIDS (HEX)
01: Monitor status since DTCs cleared. (Includes ma
lfunction indicator lamp (MIL) status and number of
DTCs.)
03: Fuel system status
04: Calculated engine load
05: Engine coolant temperature
06: Short term fuel trim - Bank 1
07: Long term fuel trim - Bank 1
08: Short term fuel trim - Bank 2
09: Long term fuel trim - Bank 2
0B: Intake manifold absolute pressure
0C: Engine RPM
0D: Vehicle speed
0E: Timing advance
0F: Intake air temperature
10: MAF air flow rate
11: Throttle position
13: Oxygen sensors present (in 2 banks)
14: Oxygen Sensor 1 (voltage and trim)
15: Oxygen Sensor 2 (voltage and trim)
18: Oxygen Sensor 5 (voltage and trim)
1C: OBD standards this vehicle conforms to

Per that, the protocol 3 is supported. Did you try to activate that protocol in OBD2 monitor and then run the dashboard?

I did get your messages about log files but did not find time to take a look at them yet. Sorry about that, but we do get about 100 emails per day and we have to prioritize :frowning:

Yes, I let it scan and then agreed to let it set to that protocol. Same result.
3DA86DA9-7F3D-4A64-AFE8-CA3DFA3CFF71.jpg

So I know that my Snap On scanner does not plug into the OBD2 port, it actually uses an adapter to plug into the consult port and read data that way. Figured I would try using it that way, but it comes up saying protocol not supposed. Argh!

I was wondering that 1996 car is a bit old to support OBD2 (though its possible). I will try to take a look at the logs as soon as I’m able.

Thank you for your time on this. I didn’t think it would either until I tried a friends OBD2 adapter and one of the many apps for it. Also, all Maximas from 1995-2002 use basically the same engine and ECM. In fact many swap the the 1995 ECM because it has less emission codes but runs the engines just like other years. Every other OBD2 app I have downloaded works fine, just not RealDash🤷

I was finally able to check your log file. Unfortunately its not very helpful. For every command sent by RealDash, car responds with ‘NO DATA’, couple of examples:

20.9.2021, 10:50:47.983: OBD2: Send: 010c
20.9.2021, 10:50:48.552: OBD2: Receive(570ms): NO DATA
20.9.2021, 10:50:48.552: OBD2: Send: 010b
20.9.2021, 10:50:49.122: OBD2: Receive(570ms): NO DATA
20.9.2021, 10:50:49.122: OBD2: Send: 010d
20.9.2021, 10:50:49.692: OBD2: Receive(570ms): NO DATA
20.9.2021, 10:50:49.693: OBD2: Send: 010e
20.9.2021, 10:50:50.263: OBD2: Receive(571ms): NO DATA
20.9.2021, 10:50:50.263: OBD2: Send: 0110
20.9.2021, 10:50:50.832: OBD2: Receive(569ms): NO DATA
...

The 0100 command (support request) works and your car reports supported pids. Your vehicle probably requires some kind of custom header to be set before it responds to the standard pid requests. Other app makers seem to be aware of that, but we are unfortunately not.

I don’t know if switching to ‘Nissan->Generic’ profile in connection settings will help. It will set the header:

ATSH8110FC

At the initialization. Give it a go.

Still no luck. What are the options at this point? Is the Dash Box still available? I was thinking of buying one so there wouldn’t be any lag one things like tech and also for turn signals and things like that. Can you use it to run all the features of Real Bash? Wiring isn’t an issue, that’s kind of my specialty. Any help on options would be greatly appreciated and thank you for taking the time to help

Rick

DashBox is one option, though its official support has ended, so we are unable to help on its setup.

Is there any other option beside the Dashbox then. I’m trying to make a complete “glass” interior in this car. The goal is to have a 10.5” tablet for gauges and a 18.5” in the center console to control the whole car, control and monitor the audio system as well as charging and battery monitoring. I will be using Phidget modules for all the controlling and monitoring. I already have most of it laid out, design of the app for the main tablet is in progress as we speak. Getting this to work is my last main hurdle.

There are some options but I don’t want to endorse one over another. Hopefully other RealDash users can chime in with their experiences. Maybe you could consider starting a new thread about hardware solutions.