[AZJeeper]

I got the opportunity to get the Vlinker MC+ for free (can't beat the price). Everything works great including JeepAA, but I have a problem. I can converse between metric and imperial fluently, but not quickly! Is there an option to display in Imperial in the near future?

I love the app! Works great. It just takes me a second or two to do the conversion. Something about old dogs and new tricks comes to mind.

 

[Gary Kline]

I got the opportunity to get the Vlinker MC+ for free (can't beat the price). Everything works great including JeepAA, but I have a problem. I can converse between metric and imperial fluently, but not quickly! Is there an option to display in Imperial in the near future?

I love the app! Works great. It just takes me a second or two to do the conversion. Something about old dogs and new tricks comes to mind.

Great news @AZJeeper! Both the vLinker MC+ and ODBLink MX+ are solid choices but there's a big price benefit on the MC+ !!

Regarding the units conversion, this is usually a function of the software application, not the OBD Adapter. Which app are you using that it's only displaying in metric?

 

[mariuslt]

I got the opportunity to get the Vlinker MC+ for free (can't beat the price). Everything works great including JeepAA, but I have a problem. I can converse between metric and imperial fluently, but not quickly! Is there an option to display in Imperial in the near future?

I love the app! Works great. It just takes me a second or two to do the conversion. Something about old dogs and new tricks comes to mind.

Hi, nice to hear that you like application. I will try to add option button in the settings to select display units. Btw do you use play store version or old one from github ?

 

[AZJeeper]

Great news @AZJeeper! Both the vLinker MC+ and ODBLink MX+ are solid choices but there's a big price benefit on the MC+ !!

The MC+ is especially sweet if you can score one for free! I now have both the MC+ and MX+. I think the MX+ has an edge only because it works with the OBDLink App, and it may be a bit faster though I couldn't tell for sure. I read your detailed review and that was another factor in getting the MC+. I was disappointed that I couldn't get Torque (Lite) to work with the MC+ until I realized that the app is no longer supported on my relatively new Galaxy S23. It was copied over from my old phone during the switchover. I spent WAY too much time figuring that out!

Regarding the units conversion, this is usually a function of the software application, not the OBD Adapter. Which app are you using that it's only displaying in metric?

Hi, nice to hear that you like application. I will try to add option button in the settings to select display units. Btw do you use play store version or old one from github ?

Yes, the conversion is an app issue. I got the Play Store version of JeepAA. Quite impressed!

 

[mariuslt]

1.0.9 new version with units display option is available now

 

[AZJeeper]

1.0.9 new version with units display option is available now

Thank you!

Here are some observations from your beta tester (i.e. me).

First, I found a really strange bug. When selecting Group: Engine, the page that comes up seems somewhat random. If I select another group and go back to Group: Engine, the title and data appear to be whatever the selection was prior to the last selection before Group: Engine. Confusing? Here is an example:

Select Group: Battery. Group: Battery is displayed correctly. Select Group: Performance. Group: Performance is displayed correctly. Select Group: Engine, Group: Battery is displayed!! That wasn't 100% consistent but that particular scenario did happen. The issue only seems to occur when selecting Group: Engine.

The other strange issue with Group: Engine...

Select Group: Driveline, then select "Start". "Off-road page" comes up. Then when I select Group: Engine, I get a page labeled Group: Driveline with gauges displayed and all data is in metric! That particular scenario happens 100% of the time.

Other Metric/Imperial observations:

Under Group: Driveline: Torque listed in Nm (ft-lb please).

Under Group: Performance: Boost listed in BAR (PSI please). X force and Y force are listed in m/sec2 (g-units please).

Under Group: Acceleration: listed in Km/h (MPH please).

Don't know if this is a comprehensive list, but I tried.

Appreciate your time and effort in making JeepAA!!!

 

[mariuslt]

Hi, yep refactoring for imperial values didn't go well . Added 1.1.0 version for google review. Review can take from 1h up to 2days or so. I hope i have fixed all issues now.

 

[AZJeeper]

Much better! Thank you!

One little nitpick... Group: Performance engine torque still in Nm.

The other thing I noticed is there seems to be fewer groups than before, but I didn't keep track of prior groups so I don't know which ones they might be. Guages in 1.0.9 not in 1.0.10 include X force, Y force, Front to Rear - Actual, Front to Rear - Desired, Pitch-Lateral, Roll-Longitudinal, Gear, and Steering value. I know those were duplicates to data in Group: Driveline so maybe that's the reason?

This version is much better overall, so I wouldn't change a thing! OK, maybe that torque in Nm thing.

Bravo! Great job! Off-road pages for the masses!!

 

[mariuslt]

Much better! Thank you!

One little nitpick... Group: Performance engine torque still in Nm.

The other thing I noticed is there seems to be fewer groups than before, but I didn't keep track of prior groups so I don't know which ones they might be. Guages in 1.0.9 not in 1.0.10 include X force, Y force, Front to Rear - Actual, Front to Rear - Desired, Pitch-Lateral, Roll-Longitudinal, Gear, and Steering value. I know those were duplicates to data in Group: Driveline so maybe that's the reason?

This version is much better overall, so I wouldn't change a thing! OK, maybe that torque in Nm thing.

Bravo! Great job! Off-road pages for the masses!!

yep, in 1.0.9 version, gouges were messed up, now is as it should be. Btw I see that you have TH version. I have simples one with DRIVEI if I am correct. So I could not test/confirm 3 more parameters from drivetrain unit. e-locker coupling, front/rear axle coupling torque and Rear Coupling Torque. In near future will add maybe new test group page with those parameters. You could test if something happening on those values when locking diff's, rear and center I think exists in TH version?

 

[AZJeeper]

yep, in 1.0.9 version, gouges were messed up, now is as it should be. Btw I see that you have TH version. I have simples one with DRIVEI if I am correct. So I could not test/confirm 3 more parameters from drivetrain unit. e-locker coupling, front/rear axle coupling torque and Rear Coupling Torque. In near future will add maybe new test group page with those parameters. You could test if something happening on those values when locking diff's, rear and center I think exists in TH version?

Be glad to!

"E-locker Coupling" would be when Rear Lock is selected. The torque values I get. So the data would essentially be confirming 4X4 Low performance. Right?

Now for some "feature creep" ideas...

On the Driveline page, it might be helpful to see each wheel's braking force. That way it would be obvious when Brake Lock Differential is active. It applies to all Active Drive (but not in ADII 4X4 LOW) so it might be helpful for anyone with 4X4 to see when the system is providing traction control braking. Also might be helpful so see if ABS is kicking in.

Is there a parameter for what mode the Selec-Terrain switch is in? I didn't notice but maybe I didn't look in the right place. Would be nice (not necessary, but nice) to see something to confirm the Selec-Terrain setting. Would also make screenshots of the Driveline group make more sense as it would give a complete picture of the switch setting, gear selected, torque splits, and (assuming implemented) the braking force for each wheel.

There are two other features available with ADII in 4x4 Low mode - Hill Descent Control (HDC) and Selec Speed Control (SSC). HDC uses the brakes to control speeds when going downhill. This parameter probably wouldn't be necessary if you added the braking force for each wheel as in the suggestion above. SSC uses the shifter to set predetermined crawling speeds. Again, probably not necessary since the Driveline group shows what gear you are in. So I guess I'm really just putting in another vote for getting the braking force added to the driveline page.

I'm also getting a cheap ELM mini (also for free) to evaluate. I'll test it with JeepAA, but doubt I would use it as the go-to ELM device since it is so cheap it doesn't have an automatic sleep mode. Don't want to drain the battery! But it would be interesting to see if everything works with a very low-end device.

Feel free to PM me if you'd rather not use this thread.

Thanks again!

 

[Flybynightcru]

You guys need to make a video on this app, and show exactly what it does. That would be helpful, and help others who might be interested in having it...😁😉😎

 

[Gary Kline]

Be glad to!

"E-locker Coupling" would be when Rear Lock is selected. The torque values I get. So the data would essentially be confirming 4X4 Low performance. Right?

Now for some "feature creep" ideas...

On the Driveline page, it might be helpful to see each wheel's braking force. That way it would be obvious when Brake Lock Differential is active. It applies to all Active Drive (but not in ADII 4X4 LOW) so it might be helpful for anyone with 4X4 to see when the system is providing traction control braking. Also might be helpful so see if ABS is kicking in.

Is there a parameter for what mode the Selec-Terrain switch is in? I didn't notice but maybe I didn't look in the right place. Would be nice (not necessary, but nice) to see something to confirm the Selec-Terrain setting. Would also make screenshots of the Driveline group make more sense as it would give a complete picture of the switch setting, gear selected, torque splits, and (assuming implemented) the braking force for each wheel.

There are two other features available with ADII in 4x4 Low mode - Hill Descent Control (HDC) and Selec Speed Control (SSC). HDC uses the brakes to control speeds when going downhill. This parameter probably wouldn't be necessary if you added the braking force for each wheel as in the suggestion above. SSC uses the shifter to set predetermined crawling speeds. Again, probably not necessary since the Driveline group shows what gear you are in. So I guess I'm really just putting in another vote for getting the braking force added to the driveline page.

I'm also getting a cheap ELM mini (also for free) to evaluate. I'll test it with JeepAA, but doubt I would use it as the go-to ELM device since it is so cheap it doesn't have an automatic sleep mode. Don't want to drain the battery! But it would be interesting to see if everything works with a very low-end device.

Feel free to PM me if you'd rather not use this thread.

Thanks again!

I like those suggestions. One thing I might differ on though is perhaps only focus on supporting the vLinker MC+ adapter which is more of less the standard used here among Cherokee enthusiasts (along with the OBDLink MX+). It's relatively inexpensive and can be used for quite a few apps (including AlfaOBD and DiagFCA) but the main reason is that we should do all we can to lighten the testing/compatibility load on @mariuslt as he's doing this on his free time. It could be quite time consuming for him tracking down potential issues in the future from someone who bought a $3 supposedly ELM327-compatible (but not always 100% compatible), adapter on AliExpress and eBay etc. This way, if he tests on an MC+, it should work the same for everyone downloading the app. Just my $.02.

 

[AZJeeper]

I like those suggestions. One thing I might differ on though is perhaps only focus on supporting the vLinker MC+ adapter which is more of less the standard used here among Cherokee enthusiasts (along with the OBDLink MX+). It's relatively inexpensive and can be used for quite a few apps (including AlfaOBD and DiagFCA) but the main reason is that we should do all we can to lighten the testing/compatibility load on @mariuslt as he's doing this on his free time. It could be quite time consuming for him tracking down potential issues in the future from someone who bought a $3 supposedly ELM327-compatible (but not always 100% compatible), adapter on AliExpress and eBay etc. This way, if he tests on an MC+, it should work the same for everyone downloading the app. Just my $.02.

I was going to respond by saying that the JeepAA Google Play site said it was compatible with most ELM327 devices so I thought I would test it. That way if not compatible with a generic device, @mariuslt could decide how to limit his audience. Besides, I'm also investing a bit of free time to test and provide feedback. I don't mind. It's similar to my pre-retirement job!

It's up to @mariuslt to 1) say "Enough is ENOUGH!" (free time appreciated, but I understand limits), or - if not completely fed up with the feedback, 2) what devices the app is compatible with.

But I thought of another great reason to show the braking forces... Let's say you are using Cruise Control and are towing (I know, not recommended). Wouldn't it be great to see when the brakes are being applied so you could get a sense of what engine compression was doing vs the heat-inducing brakes?

HOWEVER (a really BIG "however"), I can no longer find JeepAA on Google Play (as of 7/22/2024 3:54 MST). Maybe that "enough" bridge has already been crossed?

 

[Gary Kline]

I was going to respond by saying that the JeepAA Google Play site said it was compatible with most ELM327 devices so I thought I would test it. That way if not compatible with a generic device, @mariuslt could decide how to limit his audience. Besides, I'm also investing a bit of free time to test and provide feedback. I don't mind. It's similar to my pre-retirement job!

It's up to @mariuslt to 1) say "Enough is ENOUGH!" (free time appreciated, but I understand limits), or - if not completely fed up with the feedback, 2) what devices the app is compatible with.

But I thought of another great reason to show the braking forces... Let's say you are using Cruise Control and are towing (I know, not recommended). Wouldn't it be great to see when the brakes are being applied so you could get a sense of what engine compression was doing vs the heat-inducing brakes?

HOWEVER (a really BIG "however"), I can no longer find JeepAA on Google Play (as of 7/22/2024 3:54 MST). Maybe that "enough" bridge has already been crossed?

Re: finding JeepAA: Are you using the link? It doesn't show up doing a regular search in the Play store. (see post #20)

 

[Gary Kline]

Hi @mariuslt,

There's a bunch of us who are using the T'EYES CC3 Android Auto head. Since your app is a regular .apk I figured I'd try installing and testing it on the T'EYES. It downloads fine from the Play store and installs. It asks for permissions (but I think only location, not BT or BTE) but then it hangs on the following page saying, "All permissions are granted" with no way forward. I tried for testing purposes download onto my Google Pixel phone and the same thing happened. It installed fine but right after the permissions granting, it went to the same screen.

Is the app coded using something unique to the uConnect or should it work on any Android Auto /Android device?

 

[mariuslt]

Hi @mariuslt,

There's a bunch of us who are using the T'EYES CC3 Android Auto head. Since your app is a regular .apk I figured I'd try installing and testing it on the T'EYES. It downloads fine from the Play store and installs. It asks for permissions (but I think only location, not BT or BTE) but then it hangs on the following page saying, "All permissions are granted" with no way forward. I tried for testing purposes download onto my Google Pixel phone and the same thing happened. It installed fine but right after the permissions granting, it went to the same screen.

Is the app coded using something unique to the uConnect or should it work on any Android Auto /Android device?

View attachment 233807

Should work on any android auto headunit. But yours is android tablet itself and thats the problem I guess. My app is coded specifically for "android auto car screen", screen what you see is just normal application screen to grant bluetooth permissions (and yes shows up as location). After you plug device to usb cable, you should see android auto screen started. Double check if Google Pixel has android auto installed.

 

[mariuslt]

I was going to respond by saying that the JeepAA Google Play site said it was compatible with most ELM327 devices so I thought I would test it. That way if not compatible with a generic device, @mariuslt could decide how to limit his audience. Besides, I'm also investing a bit of free time to test and provide feedback. I don't mind. It's similar to my pre-retirement job!

It's up to @mariuslt to 1) say "Enough is ENOUGH!" (free time appreciated, but I understand limits), or - if not completely fed up with the feedback, 2) what devices the app is compatible with.

But I thought of another great reason to show the braking forces... Let's say you are using Cruise Control and are towing (I know, not recommended). Wouldn't it be great to see when the brakes are being applied so you could get a sense of what engine compression was doing vs the heat-inducing brakes?

HOWEVER (a really BIG "however"), I can no longer find JeepAA on Google Play (as of 7/22/2024 3:54 MST). Maybe that "enough" bridge has already been crossed?

I could add all data if I knew formulas how to calculate this is the problem. For instance yesterday I have managed to get what terrain mode is selected. Auto/snow/sport/mud I know how to map because I see in my car what is going on. Somebody will need to tell what number shows when rock mode is selected (will be some integer number)

Regarding ELM327 it should work. Vlinker,elm and others similar BT devices use AT commands, just speeds and other params differs also supported commands.
Regarding braking power- not sure if this data easily available. ABS module has for sure. But just connecting to abs module lights abs and other errors on dash.

And thanks for feedback

 

[Dodgeboy 1969]

I can not seem to download it.

 

[mariuslt]

I can not seem to download it.

Have you joined the google group? if so, make sure that play store account is on the same email. What is the problem?

 

[AZJeeper]

Re: finding JeepAA: Are you using the link? It doesn't show up doing a regular search in the Play store. (see post #20)

Oh. Duh. My bad.

I could add all data if I knew formulas how to calculate this is the problem. For instance yesterday I have managed to get what terrain mode is selected. Auto/snow/sport/mud I know how to map because I see in my car what is going on. Somebody will need to tell what number shows when rock mode is selected (will be some integer number)

Regarding ELM327 it should work. Vlinker,elm and others similar BT devices use AT commands, just speeds and other params differs also supported commands.
Regarding braking power- not sure if this data easily available. ABS module has for sure. But just connecting to abs module lights abs and other errors on dash.

And thanks for feedback

I poked around with AlfaOBD and can see all of the Selec-Terrian mode selections, 4x4 Low range, locker status, and more. BUT, I thought there was a way to get raw data from AlfaOBD. I couldn't. Sorry.

I'm familiar with the ELM327 AT command structure so if there is something specifically you need for me to query I'll see what I can do that way if you can give me the PIDs.

I tried the cheap ELM327 mini. It connected to JeepAA, but I was only able to get data on groups Engine and Performance. Everything else was blank. The mini really a POS (Piece Of, umm... Stuff). I can say without hesitation that you need something better than the cheapest ELM327 mini (or maxi or whatever) to connect with anything, including JeepAA. It was free. I got to evaluate it. It won't get 5 stars!!

Thanks again!