Android CAN Monitoring App

Mitsubishi i-MiEV Forum

Help Support Mitsubishi i-MiEV Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
hello
thx for the feedback.

about the long time when closing, it is due to a copy of 2 tables from the database to text files.
as the db is growing, it takes more & more time.
I made a change to solve this: I make a copy of the logs of the day only. it is much faster.

today, I tested also a variant with a very good approximation for distance (with autoadaptative coef).
it will be easier when somebody find this info in the CAN frames; it should be there as we have it with odo A & odo B.

I will test another variant without logging every second to see the effect on the stability.
when analysing the android log, I saw the GC (garbage collector) is quite busy.....
 
What is the GC?

The fps at the bottom of the screen has the number written
right over the fps characters, with a transparent background.

Tap the graph, and I get a transparent overlay of the table,
but it was not transparent before - maybe when I tried it
on another tablet (I have more than one).

Than, a tap of the table went back to the bar graph before,
but does not seem to work correctly now (or on this tablet).

Testing with CAN-Do v202, I get somewhat irratic results.
But I think that the Send Selected MsgIDs is working.

Also, try the new function in the Main Window, select related
MsgIDs like 6Ex and then list them, then it is easy to see the
relationship between these commands.
 
hello
here is another release for android.

some cosmetic changes: position for some labels.

for John: click on GPS panel will alternate between SoC & Alt.

accurate distance calcs.

much faster closing.

I will test this evening cando.

some details about the GC here
 
Testing this latest App, without a BT connection, it seems
much improved, and much better behaved. Thanks.

Suggestion:
If if if your App turns On BT, then maybe it should turn
BT back Off when the App exits?

I will test with CAN-Do v202 a little later this morning.

Right now I have fed and medicated my two "puppies"
(actually 11 years old this month) and they are snuggled
up with me in the easy chair, so it is "impossible" for
me to move at the moment. :D So, I am web-surfing
the forums with my Android tablet.
 
Having a link to a zip file to get the next version of your
App is a GREAT way to get the App installed.

It takes just a few seconds to download, then open with
the downloader, send the zip file to ES Zip Viewer, open the
zipped archive, open the Object folder, and tap the
application file to install it. VERY nice indeed :p :D :mrgreen:
 
Latest Version:
Seems to work well with CAN-Do v202.

However, I really do not understand what determines
the "fps" rate over the BT link. It seems like I could
be sending them much faster, but something slows
down the transfer rate. Any Ideas?

Sugestions:
1. It would be nice to have a way to see the App name,
or version number when the app is running, maybe on the GPS bar?

2. Tap the GPS bar and Alt changes to SoC, but the
Soc Value is displayed in the same field as the SoC label.

3. kM/H at the top left, and WH/KM at the bottom left
have their values displayed as Centered, the rest are
Right Adjusted. Maybe Centered would liik nicer for
all of these left-side values?

4. The label WH/KM is a smaller font size, matching all the
other larger labels would be better?

5. In the GPS bar, the values could be Right Adjusted, or
Centered perhaps?

6. The kMh value in the GPS bar is shown as ".0" instead of "0.0".
Is that intentional?

7. What MsgID values is this version wanting?

8. It seems to not hurt to send other MsgIDs as well, right?

9. When you say "Connected successfully", it would be nice to
include the name of the device that you connected to, since you
conect automatically if BT is already ON when starting.

10. If BT is Off when starting, you turn it On, and very briefly show
the "Enabling Bluetooth Adapter" message, perhaps for a half second.
Perhaps keeping the message up for a slightly longer time would
be better?

11. If BT is Off, and you turn it On, it appears that you do not
automatically connect, and one must know to press the START
button.

12. The STOP button does not just disconnect the BT, but it
EXITs the appliaction, so it is not really the inverse of START.
Maybe the STOP button could disconnect, after being connected,
but be labeled EXIT when there is no connection?

VERY Nice progress.
Please forgive me if I make too many suggestions.
Cheers, Gary
 
hello
I like suggestions...
but I can not promise I can do everything (I work also sometimes).

@gary: could you make printscreens & annotate them.
with android, it is a bit tricky to adjust the font's size to any screen size & resolution,
it will be easier to react on printscreens

just some partial answers:
9. When you say "Connected successfully", it would be nice to
include the name of the device that you connected to, since you
conect automatically if BT is already ON when starting.
10. If BT is Off when starting, you turn it On, and very briefly show
the "Enabling Bluetooth Adapter" message, perhaps for a half second.
Perhaps keeping the message up for a slightly longer time would
be better?
Click to expand...
the app tries to connect to the last device used (by this app)...
these msg are managed by the system, not by me ...
it was a PIA to have this BT link operational as it is now,
I will reluctantly change something there ..
icon_velo.gif



11. If BT is Off, and you turn it On, it appears that you do not
automatically connect, and one must know to press the START
button.
Click to expand...
I will check that one
 
I understand that some things are much more difficult
to change than others, and some things are out of your
control.

If something is difficult, but it is working, it is best
to NOT change it, most times.

I am just trying to bring some of these to your attention,
just in case you want to make small changes.

With the font size or Centering, you have code that works
for some of the variables, and must be a slight bit different
for other variables (or labels) that are displayed differently.
Hopefully, those that display the way you like can be "copied"
to those that are not quite the way you want.

I also understand, even with B4A, programmig for the Android
is not perfectly easy!!!! :D

Is there a way to make a "snapshot" of the screen in Andriod?

The only way I knw right now, is to get out my camera and
take a picture.
 
priusfan said:
hello
here is another release for android.

some cosmetic changes: position for some labels.

for John: click on GPS panel will alternate between SoC & Alt.

accurate distance calcs.

much faster closing.

I will test this evening cando.

some details about the GC here
Click to expand...


Yes, I tried it this morning and it worked much better. what does the small 57.750 in yellow mean?

Log files:
https://www.dropbox.com/s/zve7h8e40nlhcgj/odolog_121105.txt
https://www.dropbox.com/s/6xglozakwf84kir/seclog_121105.txt

I should have taken a picture before stopping it. I'll do that on the way home.


2012-11-05 06.13.41 by JJLINK, on Flickr


2012-11-05 06.13.27 by JJLINK, on Flickr
 
hello

the small yellow number is a coefficient to convert M_RPM to distance...
it is adjusted automatically every km after the second km in a trip.
the initial value is 57.75 , it should not move too much.
it is interesting for tests only.

here is another release.
the only diff with the previous one is:
when taping the left green panel, it will silently make a screen capture. (no message, no feedback)
it will create a file, in the BT_Can folder , named pict_YYMMDD_HHMMSS.png

I mixed up 2 labels for the SoC in the blue panel; correction soon....
 
The distance looks close, I checked it with my trip meter which said 19.3 (31.44 Km = 19.5359 miles).
The Odometer on the car says 9210 miles and the display here 14820 KM (which should be 9208.72 miles). Not too far off.

I'm guessing the average speed (58.7) is MPH? That looks about right, if its KMH then its off.


2012-11-05 14.51.17 by JJLINK, on Flickr


2012-11-05 14.51.22 by JJLINK, on Flickr

Log files:
https://www.dropbox.com/s/jl7eunf00cvo1fy/BT_CAN.zip

It worked very well on the drive to and back from work today.

Thanks
 
@John
yes some figures are totally wrong
some of my formulae are wrong: essentially in the graph WH/KM (integration is not good)


also, what is the tyre's size? I find the value 65.42 very far from mine.

the avg speed 58.7km/h is ok for a distance of 31.44km and a time of 32:08,


sending the zipped BT_CAN folder is really efficient; and if you make screen capt, they will be included.
 
I believe that the final gear ratio is different on the US model.

US/CA model: 7.065:1
Rest of the world: 6.066:1
 
US wheel / Tire size:

145/65 R15 low rolling resistant front tires
175/60 R15 low rolling resistant rear tires

I read that the Ion has this size:

Front : 145 / 65 R15
Rear : 175 / 55 R15
 
thx for infos...

I have seen on a log from John something strange (for me):
the speed from the CAN had a value LOWER than the GPS...
this could not happen in europe
maybe the diff has for origin the tyre size...

so it seems some calibration is necessary for NA's iMiev...
 
hereis rel 46
changes:
correction of calcs WH/KM
right align for some labels:
ion46.png

to switch between Alt & SoC, now it s necessary to click on the label Alt/SoC
 

Similar threads

R
Canion
35 36 37
Replies
727
Views
574K
MickeyS70
M

Latest posts

Back
Top