FORScan Lite V 1.2.3 notes

[jdcmax]

Used on an iPhone 4 IOS 7.1.2 with a 2013 Ford C-Max Energi

In the BECM module the PID BAT_TO_EMPTY_ESTIM the units are wrong. Should be Wh (Watt-hour) not Watt. Also there are no "tick marks" or a needle on the gauge even if you specify a Min and Max.

I've had trouble deleting a PID, it would crash the program. Seems like it was the last PID added, maybe a linked list management problem? Fortunately I had previously stored a PID file before added that PID so I could backup to something usable without deleting and re-installed the program.

Setting min and max is a real trial and error procedure, what you enter is rarely what ends up on the gauge. Are there some rules?

Takes a couple of minutes to Connect, even if you have saved the vehicle profile file. What is it doing and what is stored in the vehicle profile?

Would be nice if it started up on the last module displayed rather than the first one added (I think that's what it is doing)

Would be nice to be able to combine two PIDs, such as multiplying traction battery current and voltage to display watts.

Looking forward to the next version.

[FORScan]

Thanks for your feedback. Please see our comments below:

In the BECM module the PID BAT_TO_EMPTY_ESTIM the units are wrong. Should be Wh (Watt-hour) not Watt. Also there are no "tick marks" or a needle on the gauge even if you specify a Min and Max.

We will investigate and fix it.

I've had trouble deleting a PID, it would crash the program. Seems like it was the last PID added, maybe a linked list management problem? Fortunately I had previously stored a PID file before added that PID so I could backup to something usable without deleting and re-installed the program.

This bug was fixed long time ago, very odd it re-appeared. We would really appreciate if you sent the Crash report. Here is information on how to obtain it:

http://forscan.org/forum/viewtopic.php?f=5&t=19#p3047

Setting min and max is a real trial and error procedure, what you enter is rarely what ends up on the gauge. Are there some rules?

FORScan calculates gauge scale trying to make it looking like a "real" gauge. For example, if you specify min=21 degrees and max =119 degrees for ECT PID, FORScan will show a scale from 20 to 120. In fact, the algorithm is more complex as it takes into account wide of scale, size of gauge and other data. So if you look at the same PID gauge in small, normal and big size, you will see 3 different scales, and may be even with 3 different min and max values on it.

Considering the above, it would be good to get a screenshot that illustrates the problem you describe, in order to understand if it is a bug or feature.

Takes a couple of minutes to Connect, even if you have saved the vehicle profile file. What is it doing and what is stored in the vehicle profile?

Please check minimal response time of your adapter (Vehicle section). If it is greater than 20 ms, please read this thread:

http://forscan.org/forum/viewtopic.php?f=4&t=16#p19

If it is 20 ms or less, it would be great to get internal FORScan logs as described here for further investigations:

http://forscan.org/forum/viewtopic.php?f=5&t=19#p3048

Would be nice if it started up on the last module displayed rather than the first one added (I think that's what it is doing)

Do you mean, FORScan should remember the module you selected to read PIDs from?

[jdcmax]

Thanks for your feedback. Please see our comments below:

I've had trouble deleting a PID, it would crash the program. Seems like it was the last PID added, maybe a linked list management problem? Fortunately I had previously stored a PID file before added that PID so I could backup to something usable without deleting and re-installed the program.

This bug was fixed long time ago, very odd it re-appeared. We would really appreciate if you sent the Crash report. Here is information on how to obtain it:

http://forscan.org/forum/viewtopic.php?f=5&t=19#p3047

OK, sent.

Setting min and max is a real trial and error procedure, what you enter is rarely what ends up on the gauge. Are there some rules?

FORScan calculates gauge scale trying to make it looking like a "real" gauge. For example, if you specify min=21 degrees and max =119 degrees for ECT PID, FORScan will show a scale from 20 to 120. In fact, the algorithm is more complex as it takes into account wide of scale, size of gauge and other data. So if you look at the same PID gauge in small, normal and big size, you will see 3 different scales, and may be even with 3 different min and max values on it.

Considering the above, it would be good to get a screenshot that illustrates the problem you describe, in order to understand if it is a bug or feature.

Sounds like I just need to try different values until I get something I like.

Takes a couple of minutes to Connect, even if you have saved the vehicle profile file. What is it doing and what is stored in the vehicle profile?

Please check minimal response time of your adapter (Vehicle section). If it is greater than 20 ms, please read this thread:

http://forscan.org/forum/viewtopic.php?f=4&t=16#p19

If it is 20 ms or less, it would be great to get internal FORScan logs as described here for further investigations:

http://forscan.org/forum/viewtopic.php?f=5&t=19#p3048

As you can see from the screen shot it was 21ms which should be close enough. I'm just wondering if the vehicle information is not getting saved from some reason...

Would be nice if it started up on the last module displayed rather than the first one added (I think that's what it is doing)

Do you mean, FORScan should remember the module you selected to read PIDs from?

I mean when you tell it show dashboard it should show the last shown dashboard as the default. I'm not sure, but appears it also does not remember the gauge size, that would be nice.

[FORScan]

This bug was fixed long time ago, very odd it re-appeared. We would really appreciate if you sent the Crash report. Here is information on how to obtain it:

http://forscan.org/forum/viewtopic.php?f=5&t=19#p3047

OK, sent.

Thanks, answered by email.

As you can see from the screen shot it was 21ms which should be close enough. I'm just wondering if the vehicle information is not getting saved from some reason...

Yes, 21 ms is OK. When FORScan connects first time, it may ask some questions about model year, equipment installed etc, these questions are not asked after vehicle information is cached. So If these questions are asked every time, it certainly means the vehicle cache is not saved properly. Another way to check is to clear vehicle cache (Vehicle->Service (button at the right bottom) -> Clear cache). Then connect and measure the connection time. Then reconnect and measure it again. If connection time is roughly the same, it certainly means the vehicle cache is not saved .

[FORScan]

FORScan Lite version 1.2.4 is released today - but please note it has no fixes for problems mentioned in this thread. In fact this version was submitted to AppStore a week ago.

[jdcmax]

1) Connect Time: 2:12

2) Went to Vehicle page and clear debug and cache.

3) Disconnect

4) Went to IOS task manager (or whatever they call it) and terminated FORScan just to be sure.

5) Connect Time: 3:20 (Answered No to question about MSCAN support)

6) Saved Vehicle info

7) Restored PID's from their files and reset Min & Max where needed. Out of curiosity, why aren't Min & Max stored in those files? The Units are.

8) Disconnect & Terminate

9) Connect: 2:24

So that didn't do much good.

I originally tried the program on an iPad 3 (same OS version) and went back to that. Connect time: 0:32. Seems like there is something awfully strange going on.

[FORScan]

I originally tried the program on an iPad 3 (same OS version) and went back to that. Connect time: 0:32. Seems like there is something awfully strange going on.

Do you mean, it has connection time 2+ mins on your iPhone but 32 seconds on iPad? This is really odd. Performance tests on our slowest (iPhone 3GS) and fastest (iPad Air) show noticeable difference in performance, but not 4x times at all. May we ask to send us logs from you iPhone as described here: http://forscan.org/forum/viewtopic.php?f=5&t=19#p3048?

Regarding Min/Max... these values are stored in vehicle profile because they are PID-specific. Two different vehicles may have two different PIDs for the same parameter. As a result Min and Max values originally stored for one vehicle may be not applicable for another vehicle. We however agree it is not convenient (when the values are removed together with other cached data), so we will try to improve this functionality in next releases.

Also, we have fixed the crash bug in iOS 7 you mentioned, the fix will be available in next release.

[jdcmax]

Do you mean, it has connection time 2+ mins on your iPhone but 32 seconds on iPad? This is really odd. Performance tests on our slowest (iPhone 3GS) and fastest (iPad Air) show noticeable difference in performance, but not 4x times at all. May we ask to send us logs from you iPhone as described here: http://forscan.org/forum/viewtopic.php?f=5&t=19#p3048?

Seems like you might need me to send you two log files, one on the first connection (after clearing cache) and the second one doing a subsequent connection, true?

[FORScan]

The following sequence would be ok:

Clear cache, enable debug, connect, disconnect, connect again, disconnect and send us logs.

[jdcmax]

In the BECM module the PID BAT_TO_EMPTY_ESTIM the units are wrong. Should be Wh (Watt-hour) not Watt. Also there are no "tick marks" or a needle on the gauge even if you specify a Min and Max.

We will investigate and fix it.

I think scaling it to kWh would probably be the best as far as readability. At least 1 digit to the right of the decimal point, 2 if there is room