View Single Post
Posts: 208 | Thanked: 31 times | Joined on Aug 2007 @ PQU
#35
Originally Posted by rotoflex View Post
I think this is one of those things where it's hardly fair to dislike something just because it is not something else.

pyOBD is what was adapted to the N900 in this case, (and more successfully than any previous BT OBD package). It is diagnostic-oriented, not dashboard/driving oriented & works well. If Carman had already been ported successfully to the N900, pyOBD would still be a great application because its objective is different.

Just to show that tastes can differ even as far as the packaging of a particular application, I think that Carman becomes less effective by its slant toward heavily stylized graphics - its information would be better conveyed with larger, simpler windowed digital readouts which would make not only for faster perception, but allow more outputs to be displayed simultaneously. At the size of the N900 screen, two pseudo-analog gauges eat up a lot of real estate costing reduced readability that could have been more effectively used with even four or six simplified digital readouts.

There is already a Carman thread, if you would like to attempt to resurrect interest in Carman. But pyOBD is dstinct & not inferior to Carman's objective - which is still unachieved on the N900, also.
Another opinion without knowing what carman for OS2006 is.
I repeat more clearly. the oldest version of carman, yes it had graphics AND it could read hundreds of sensors in comparison to pyOBD which reads only a few of them.
What I am trying to do here is to help the author of pyOBD get some more information in order to improve pyOBD if he can look into the source code of the OLD carman.