CVTz50 will report ECM error codes.

Torque Pro should work fine for your gen 1 Murano too for ECM engine codes. It's also great for lots of other engine data, graphing and displays. Having both apps is good.

Both apps would display an ECM error code if a cylinder wasn't firing. However, Torque Pro would show a lot more data associated with it...

You would something else to read body, airbag, and antilock brakes etc. error codes

 

CVTz50 will report ECM error codes.

Torque Pro should work fine for your gen 1 Murano too for ECM engine codes. It's also great for lots of other engine data, graphing and displays. Having both apps is good.

Both apps would display an ECM error code if a cylinder wasn't firing. However, Torque Pro would show a lot more data associated with it...

You would something else to read body, airbag, and antilock brakes etc. error codes

Torque pro doesnt work for me, even tho i paid for it. Maybe its my ELM adaptor? I will take screenshot later.
Also regarding CVTz50... It did not show any error when 2 of my coils were out. I felt engine is about to die. my mechanic said your car is workign with 4 cylinder. 2 coils need to be replaced.

 

Torque pro doesnt work for me, even tho i paid for it. Maybe its my ELM adaptor? I will take screenshot later.
Also regarding CVTz50... It did not show any error when 2 of my coils were out. I felt engine is about to die. my mechanic said your car is workign with 4 cylinder. 2 coils need to be replaced.

 

Also regarding CVTz50... It did not show any error when 2 of my coils were out. I felt engine is about to die. my mechanic said your car is workign with 4 cylinder. 2 coils need to be replaced.

I can't imagine it would matter, but in the CVTz50 app do you have the box checked to monitor the engine, or just the CVT? By default, I believe the app is set to monitor engine and CVT, but I if the engine box was unchecked, I wonder if that would override the app's ability to grab trouble codes from the ECM, so it's only grabbing DTCs from the TCM that pertain to the transmission. However, are you sure your mechanic pulled codes that pertain to bad coils? Or were you were told you need two new coils and assumed he arrived at that conclusion by pulling related codes from the ECM? What I'm getting at is, if your mechanic was able to determine you had some bad coils using other troubleshooting methods, it's possible there were never any engine trouble codes stored for you to view via CVTz50.

CVT codes appear as a red box around the clock in the lower-right of the app's screen, and engine codes appear as a yellow box.

 

Lets say i want to find out if all 6 coils for cylinders work... Because i sometimes suspect vehicle is workign with 5 cylynders...
How do i find out all 6 Cylinders work?

Do a power balance test, which can be done with CVTz50: CVTz50 - CVT diagnostics with ELM327

 

Do a power balance test, which can be done with CVTz50: CVTz50 - CVT diagnostics with ELM327

Thank you coffee as always for answers.
ive seen this option in the app. But problem was i think when u turn off one cylinder u cant tell the difference. unless you turn off 2 so u can feel engine starts to stall abit and sound changes.
manual says "Dialog title shows current engine RPM and minimum RPM observed after last switching of cylinders"
i guess i havent noticed that part in the app...
I will go ahead and do a test and come back with results... In case someone else wanted to do the same. so it will be good for archive

 

I remember I had an issue getting Torque Pro to connect to the ELM dongle in my 2003, but that was nearly two years ago. Unfortunately, I don't recall exactly what I did to get it to work, but it did work without having to use a different dongle. I have a vague memory of having to start the app first, then start the car. I also recall there was some issue at first about the type of car and configuration being wrong that I'd chosen.

 

Those who want bit more for engine and other subsystems can try updating cvtz50 to latest beta version http://cvtz50.info/test/ , enable Experimental Features in Menu--Settings--System, then open Service Functions from the menu. There is also BCM section sometimes allowing to change body configuration settings (be careful there and avoid changing things like type of rain sensors).

 

Nice to know the app developer is still tweaking/updating things, but I don't know if I'd want to risk using a beta version that might somehow send junk to the ECU/TCM of my 2021 and render the system inoperable. Though the original version is lacking certain correct specs for the 3rd Gen Muranos, I don't really have a need to monitor the CVT like I did with my 2003, so I can wait until any and all bugs are worked out...

 

Are you sure that's a safe link? Shouldn't "download" appear AFTER the app's site name of "cvtz50.info" with a forward slash, instead of it appearing before the site with a period? Seems odd that the "offfical" site doesn't make any mention of a beta, only the most recent release from November 2021 of version 1.54. The only beta version I see is linked to a different site (a2zapk.com) , which could mean the original developer didn't create this app beta, and that someone else has tried to modify and improve the app.

 

My take is the developer is treating us to an early beta...

It looks legit to me, it downloads from their secure cvtz.info domain now, the site of the official CVTz5 app.

Of course beta software can cause unforeseen issues, so proceed with caution...

 

@Cryogenix1, I think you mentioned in the past that you would like to disable your daytime running lights. The beta app now allows access to the BCM, disabling the daytime running lights is mentioned in the release notes...

 

Yes, I saw that. But since the app is still being tested, the possible risks to my car's brain aren't worth some random benefits.

I still don't see anywhere on the legit cvtz50 site or at googleplay's cvtz50 download page any mention of the beta and anywhere to download it. However, I seem to recall when I had my own dot.com site I could place any "word." before the "dot.com" and it would work to load that page of HTML. e.g. word.dot.com

Perhaps the poster of the link was contacted to be a beta tester, and he's passed the secret link onto us.

 

I believe vovexe is the maker of the app or related.

CVTz50: Murano CVT/Engine diagnostics for Android with...

Nissanmurano.org members (joined before 3 Jan 2018) can get CVT diagnostic software CVTz50 free of charge till Jan 31. Just send a PM to me and you will receive promocode that can be redeemed at google play store https://play.google.com/store/apps/details?id=com.cvtz50.cvtz50 allowing to...

www.nissanmurano.org

 

I believe vovexe is the maker of the app

Correct.

App page in Google Play lists cvtz50.info as official website; cvtz50.info/test links to https://download.cvtz50.info/CVTz50_test_latest.apk . There is no link to beta version on main cvtz50.info page since beta version is not advertised widely.
Don't download it from any other sites like a2zapk, cz or public file sharing services.

hard reset (removing the negative battery terminal cable for a period of time) would set many (maybe all?) things back to their default values

For majority of BCM settings that would not work. Particularly mentioned DTRL configuration is resistant to long power cuts.
For Engine Active Tests, hard reset is not needed - here nothing is written to persistent storage and ECM cancels Active Test automatically shortly after Active Test signal stops arriving from CVTz50. Algorithms of Idle Rpm and Ignition Timing adjustments are the same as in old version, but it recently got better prerequisite checks which can give a hint why adjustment is not working.

Playing Devil's Advocate, let's assume that the beta uses a two-step process to change the DRL settings from ON to OFF, and that's all the app developer was able to figure out (or maybe that's all the intel he was able to dig up) that pertains to that function. But let's say that Nissan actually has a three-step process for changing the DRL setting in a way that won't potentially harm or corrupt another aspect of the BCM system. Perhaps by only using two steps you can get the DRL setting to change, but perhaps in doing so it leaves a pathway open for some other feature to try to utilize since DRLs are no longer seen as on, and maybe that could create conflicts or glitches elsewhere.

Cannot disagree, everything possible.
Good thing is that it is possible to switch everything back (remember which values were initially selected before applying the changes!).

when the beta version will be updated through google play

Tough question. There are reasons to keep it in beta version outside of google play for some time (at least several months)

• Service Functions are not yet working on old Android versions (older than 5.0); weird bugs in user interface of Engine Active Tests (e.g. more than one BACK press sometimes needed to exit Active Test) which are not blocking the usage but should be fixed before it can be officially released
• Very limited list of already supported models. Different BCM revisions require a bit different handling from the app side. Even if running on z51-z52, there is a chance that after opening BCM section in cvtz50 you will get only message "configuration storage not found, please send diagnostic data" instead of list of settings. Effort for making changes in cvtz50 for additional BCM revisions is not big, and APK package can be updated on cvtz50.info/test quickly (and test version is being updated there quite often). But delivering updates via google play means several days delay due to long review time from google AND all cvtz50 users will be continuously getting cvtz50 updates with definitions for new BCMs which are irrelevant to more than 99% of these users.

is it possible to make this app for Iphone as well?

It's in the plan. As usual, hard to say when it can be ready for release

 

I'm thinking that if something odd occurred, I would think a hard reset (removing the negative battery terminal cable for a period of time) would set many (maybe all?) things back to their default values...but I sure don't know for sure...

 

But if the app is writing instructions to the ECM, TCM or BCM and those changes are allowed, accepted and finalized by the system, I don't see how what you're suggesting would have any ability to override or clear those finalized instructions set in the modules.

Playing Devil's Advocate, let's assume that the beta uses a two-step process to change the DRL settings from ON to OFF, and that's all the app developer was able to figure out (or maybe that's all the intel he was able to dig up) that pertains to that function. But let's say that Nissan actually has a three-step process for changing the DRL setting in a way that won't potentially harm or corrupt another aspect of the BCM system. Perhaps by only using two steps you can get the DRL setting to change, but perhaps in doing so it leaves a pathway open for some other feature to try to utilize since DRLs are no longer seen as on, and maybe that could create conflicts or glitches elsewhere.

I'm not suggesting the app developers aren't bring careful and doing they're homework and research, but Nissan stands to make more money from customers by forcing them to return to the dealer to have certain things reprogrammed, so maybe they're not giving away trade secrets...or giving away the full or correct secrets.

 

Im excited to try out the new updated cvtz50 app i guess i will just wait abit til more of you guys try it.
Thanks to developer @vovexe for this app, Would you please say when the beta version will be updated through google play?
BTW is it possible to make this app for Iphone as well?

 

I decided to begin to investigate the CVTz50 Service Functions. I REALLY like having access to these other modules for troubleshooting, etc.

So far I have done a scan of all the modules. I think many are ghost codes, perhaps triggered when I changed my battery may be one possible cause. There are some codes are for the rear hatch and sonar sensors. I have had minor issues with both that have since been resolved. These codes are most likely old and can be cleared.

I'm currently a little wary, but I am tempted to try clearing the codes and seeing if they return...

Screenshots of the all modules scan results. the last two screenshots overlap:

 

I decided to begin to investigate the CVTz50 Service Functions. I REALLY like having access to these other modules for troubleshooting, etc.

So far I have done a scan of all the modules. I think many are ghost codes, perhaps triggered when I changed my battery may be one possible cause. There are some codes are for the rear hatch and sonar sensors. I have had minor issues with both that have since been resolved. These codes are most likely old and can be cleared.

I'm currently a little wary, but I am tempted to try clearing the codes and seeing if they return...

Screenshots of the all modules scan results. the last two screenshots overlap:

View attachment 55835

View attachment 55836
View attachment 55837

I also started using it the other day. seems stable and works fine. i could even close and open VIAS valve with it to see if its working. and i found out vacuum is working, but my power valve acuator is faulty.
Something else i tried was to scan all modules and sub modules. ( nissan 2008+) Mine is late 2007...
The scan stucks at 5%.
Ive used other functions which are for Nissan 2008+ too some of them work so i wonder if scanning for the all sub modules that get stuck is a bug in the app or maybe my ELM device is bad. I tried 2. Both got stuck. or maybe its not for first gen Mos.
@vovexe Thanks for the support.

 

I installed it earlier to see what it offered, but the prompt indicating "ongoing data exchange happening" (or something like that) for more than a 40 seconds turned me off, so I closed the program and uninstalled it. I'm assuming the "data exchange" has to do with info sent back to the software developer to provide vehicle info on which the beta is being used.

 

My samsung phone is offline always. Only additional permission it wanted was to access to my local files. you can always go to an app setting and uncheck the permissions u dont feel comfortable with

 

Well, in the CVTz50 app the only thing I really saw related to sending info pertained to a logfile or something. I looked and didn't see any additonal options to prevent data exchange beyond the OBD2-to-phone/app relation. My phone's Internet and wifi are always off until I need them. However, I reinstalled it and tried the CVT Service Options, and that "ongoing data exchange" prompt cleared within a few seconds. When trying to do the BCM option, it showed the data exchange prompt for about two minutes before indicating that the "storage could not be found," so I could not access those features. I'm now guessing the data exchange is simply the app trying to reconcile with the module, and it may not be trying to send any info to the outside world.

However...something really odd happened after about the last five minutes of driving with the dongle in and CVTz50 fixed on the failed BCM attempt screen (I drove for a total of ten minutes)... A persistent whirring noise suddenly appeared on the driver-front area, and it hadn't made any noise at any speed all day long until after accessing the CVT Service Options and then the BCM failed attempt. Also, for the first time since owning this car, when I parked in the garage and shut the car off the exhaust was flexing/ticking like crazy for about ten minutes, when typically there is zero exhaust noise on cool down. Seemed to be coming from the part of the exhaust circled in red on the below pic. Is that a collector or resonator? It's positioned under the front seat area. Could the failed access from the app to the BCM have triggered some exhaust sensor to behave differently which made the exhaust behave differently?

 

Were you performing the BCM scan while driving? I would think that it would be best to only access module scanning or any of the other service functions while parked...

 

No, I stayed parked in the driveway with the engine on as the app tried to access the BCM. Once it failed, I just left it on that failed screen as I drove to the store and back. But I decided mid-way not to go, so I turned around and that's when the whirring started (after about five minutes) ... The car was never turned off and then restarted. I'll be curious to see how things act tomorrow.

 

You mentioned it was stuck on the BCM scan. That would mean it may still have been in the process of doing 'something', so it may have been still actively attempting the scan...

 

It had completed the BCM access attempt and failed, and the screen just acknowledged that and requested that I send the logfile to the app developers. It didn't ask a question or in any way lead me to believe that it was going to attempt another access. I'd be surprised if it tried to acess the BCM again after requesting me to send the logfile. But who knows... during those following minutes after the failed attempt, the screen remained unchanged and the wording unchanged. No more prompts. However, I didn't back out to the main screen, so who knows. Maybe "something" was still active and probing around.

If you recall, last year I mentioned my car started idling roughly in Park after plugging in the dongle and using the CVTz50 app (with the 2021 MO). After removing the dongle and restarting the car, everything was normal again. Possibly just coincidence. I don't think I'm going to use it again. Maybe Nissan wised up and did something to the 2020 and later models where accessing the modules with anything other than a Consult device may create temporary or permanent glitches. I say that because your 2019 BCM was able to be accessed.

EDIT: Damned...it just hit me that I had a problem with the dongle and/or CVTz50 a few months back, after slowing quickly down a hill and then accelerating fast to swerve around a tractor. After the incident, I used CVTz50 on the drive home to see if anything looked strange, and the torque lock light was acting up, and I also think there were some issues with engine sluggishness. Once I stopped somewhere and removed the dongle, then restarted the car and drove off, things were fine. Three strikes... that's it for me. EIther my car doesn't like the dongle or the app being active while driving is having adverse effects on things. I hope to hell that whirring noise isn't still there in the morning, and that the exhaust is again silent.

 

Thanks for the insight, vovexe. I didn't actually think the O2 sensors were tied into the BCM, but I was looking for something electrical that tied into the exhaust to explain it. What would make the engine produce greater heat than normal that would heat up the exhaust more than usual in a short period of time? Or maybe the question night be what would prevent something from cooling as it normally should to prevent extra heat from being pumped into the exhaust system? Seems very coincidental that after accessing (but not changing) the Service Features of the CVT that I have whirring within ten minutes, particularely since I'd driven about 400 miles today without any such sounds. It's always possible the dongle has a loose pin or soldering point that's causing some kind of random thing.when the engine is running and there are vibrations. It does seem rather strange that a 2019 can connect to its BCM, but my 2021 can't. How different can they be? Your app worked beautifully with my 2003. With the 2021, there seems to be a problem either with the hardware or the software or both. Or, as I said, maybe Nissan made some subtle changes to the circuitry or firmware (or whatever) in more recent models that renders certain non-proprietary things unable to wholly work, forcing customers to turn to dealerships for help.

The exhaust flexing could possibly be a result of freezing temps last night that kept the garage cooler during the day, so that when I arrived later on the typically warmer climate in the garage was no more, causing the metal parts to cool more rapidly and produce louder sounds. However, when I first arrived and parked, the exhaust didn't make any noise. It happened immediately after using the dongle w/app. There have been many crazy coincidences in life, so maybe that's all this is.

 

What would make the engine produce greater heat than normal that would heat up the exhaust more than usual in a short period of time? Or maybe the question night be what would prevent something from cooling as it normally should to prevent extra heat from being pumped into the exhaust system?

I can imagine that it can be caused by injecting more fuel by increasing fuel corrections or decreasing cooling fan speed (and both these can be done by engine-related service functions in cvtz50), but i see no reason which can cause car or app to do that during or after BCM reading. Just checked - these are not mixed in cvtz50.

It does seem rather strange that a 2019 can connect to its BCM, but my 2021 can't. How different can they be?

I'd suggest running BCM reading again (just in case, turn ignition off-on before driving after that), then enable internet connection and send diagnostic data by Menu->Settings->DataLogging->Send as the app suggests. Most likely minor changes are needed in the app so it can recognize your BCM revision.

Your app worked beautifully with my 2003. With the 2021, there seems to be a problem either with the hardware or the software or both.
maybe Nissan made some subtle changes to the circuitry or firmware (or whatever) in more recent models that renders certain non-proprietary things unable to wholly work, forcing customers to turn to dealerships for help.

Yes things are changing there. E.g. in z52 they removed possibility to adjust idle rpm, removed list of past CVT DTCs, made CVT monitoring working much slower than on z50-z51. Though for BCMs, I have not seen these protected from modifications yet.

 

I have another possible cause of @Cryogenix1's flexing/ticking exhaust. Scanning the module(s) is a very intensive task, either on the phone's processing speed part, or the speed the modules can process the request. A full scan using CVTz50 took around 10-15 minutes. So, it may be grabbing undue attention of a module(s), as well as putting additional traffic on the CAN (Controller Area Network). This additional traffic alone may possibly cause OBD2 events to be processed more slowly if the scan is perform while driving.

My speculation is the fuel trims may not have been as efficiently monitored/applied as normal. An either a too rich or too lean condition would possibly heat up an exhaust component and/or catalytic converter, and may have resulted in the flexing/ticking sound... Just trying to rationalize why CVTz50 would cause a hot exhaust...

You first mentioned the scan was 'stuck', then mentioned later that it had ended with a notice to send an error log or something. If it was 'stuck', and may have still been putting a load on the CAN retrying the module probe... The developer can let us know what may still be occurring after it requests to send the error log due to a failed scan...

 

My speculation is the fuel trims may not have been as efficiently monitored/applied as normal. An either a too rich or too lean condition would possibly heat up an exhaust component and/or catalytic converter, and may have resulted in the flexing/ticking sound... Just trying to rationalize why CVTz50 would cause a hot exhaust...

You first mentioned the scan was 'stuck', then mentioned later that it had ended with a notice to send an error log or something. If it was 'stuck', and may have still been putting a load on the CAN retrying the module probe... The developer can let us know what may still be occurring after it requests to send the error log due to a failed scan...

Interesting theory. It was "stuck" in hindsight after taking so long for the BCM data exchange to resolve in comparison to the CVT data exchange which lasted only a few seconds. The very first BCM attempt made I gave up after about 40 seconds and uninstalled the app, thinking it needed an Internet connection. The second attempt later that day was "stuck" (or lingering) at the data exchange prompt for about two minutes until finally indicating that attempt failed.

But are you saying that on the very first attempt on the "stuck" data exchange prompt, that it may have created problems because I closed the app prior to it resolving on its own? Or are you saying on the second attempt, where the data exchange prompt lasted about two minutes, that remaining on that failed (but completed) screen may have caused things to be processed more slowly since the app was still in communication with he system?

 

Note: these are the settings I used (under Settings/Connection) to successfully scan all modules in my '19. I'm using a BAFX OBD2 dongle.

 

I didn't read your post prior to making another attempt a few minutes ago but I don't think it matters in my case, since the app appears to be connecting correctly to other aspects of the car's systems.

With the ignition on but engine off every service function can be accessed except for the BCM. Most take less than a few seconds to reconcile. BCM failed after 58 seconds and an additional attempt failed after about the same amount of time.

After driving for about 30 minutes this morning and turning off the car there's no noise from the exhaust and there is no whirring sound. Checked the dongle and all pins are tight. I think it's looking more like Nissan has altered something that relates to accessing the BCM in newer models. Based on my three last experiences using ELM327 w/CVTz50, I thibk connecting any dongle and using any app that accesses the car's modules might create some issues on newer models.

UPDATE: After driving around a lot today to complete some errands and returning home, the exhaust has been quiet once the car's turned off, and the whirring noise has not returned. I really don't think this is mere coincidence that all three times I had the dongle plugged in and running CVTz50 I had problems. At the very least, I won't ever drive around for any significant time (if at all) with the dongle and app engaged.

 

I tried the ignition on engine off first it, it didn't work for a scan. But it did work once I turned the engine on.

Maybe try again using the same Connection settings as mine, and with the engine on.

 

The only difference between our settings is the manual bluetooth thing, and since the app is connecting successfully to other modules, that setting shouldn't make a difference.

First time I tried with the engine running. Second time was with the engine running. Third time was with engine off but ignition on. Fourth time was with engine running. Same results. Everything but the BCM is able to make a successful link to the app/phone.

It's possible Nissan put in a "back door" to the BCM that its Consult device must utilize in order to access it If someone doesn't know to use it, access is denied. And that back door could simply be a series of pressing this button "X' number of times when trying to connect to the BCM. Who knows... Maybe I've watched WarGames too many times.

 

Yeah, I selected my OBD dongle manually, it's not required if it finds it itself.

Another thought came to mind, try restarting your phone for a fresh start.

There are other Connection settings worth experimenting with if you still feel motivated. There are various quirks with the OBD2 dongles out there... I would try the ELM327 Compat:Slow for instance...

The BCM scan is a fairly long and intensive process, it may be too much for your particular dongle without tweaking it with a setting...

Also consider sending a diagnostics file of the failure to the developer to see what is causing the BCM scan failure.

 

Just by happenstance the phone had been restarted prior to the first attempt because I'd let my phone service lapse that requires rebooting after refilling. I'm really not motivated to screw around with the electronics just yet when I don't really need to. Not worth the risk.

Again all day yesterday and so far all of today, no exhaust flexing/ticking or whirring noises.

 

@vovexe, does the beta version automatically update, or should I always download the beta prior to using it to have the latest version? Are release notes available for each version?

 

does the beta version automatically update, or should I always download the beta prior to using it to have the latest version? Are release notes available for each version?

There are no automatic updates to fresh beta versions (but google play will update beta version to new official version when it released). Generally it is good to always have latest beta, but right now don't expect a lot of new functionality for a car where service functions already work. Currently main changes are in adding support for more BCM variants. No changelogs available for each version, but since we have this thread I can post here when something new noticeable appears.

As u can see the app tags the time on each 50km
Cryogenix1 MuranoSL2003 can yall do the same with your 19 mo's to compare?

Z52 and Z51 are 1s faster than Z50 in 0-100kmh acceleration according to the specs.
And on Z52, cvtz50 monitoring data refresh is slower so measurement is not so precise as for Z50 and Z51.

 

I did a 0 to 150 kmph test with the app. I didnt do the best. road was thin and kinda uphills and i manually changed gears. ... As u can see the app tags the time on each 50km
@Cryogenix1 @MuranoSL2003 can yall do the same with your 19 mo's to compare?