Hi Vitaliy,

I guess seeing how I recommended OBDPro I will now have to clear my
reputation at least...

I am not sure what you are talking about re PWM & CAN on the OBDPro I
have been using it for J1930 & SW CAN and it works just fine, I also
had a ford vehicle for testing and I can successfully connect to and
it is using PWM.

I ran into an issue with SW CAN, but OBDPro has the ability to reflash
firmware so I was able to get a fix within 24 hours, so in my book
they did all right.

Like you mentioned I guess you cannot be as objective when you have a
competing product,

On Wed, Nov 12, 2008 at 9:24 PM, Vitaliy <spam@maksimov.org> wrote:
> microsoftwarecontrol wrote:
> just changed egr P sensor and fix engine light on of my car.
>
> Also find out, to read OBD II code, you can know all working condition of
> all sensors.
>
> Any body worked out to read it, by PIC rs232?
>
> -----------------
>
> I guess it's time for my shameless plug. :)
>
> Our company (ScanTool.net) has been manufacturing PC-based OBD-II scan tools
> since 2002. Initially, we also offered the scan tools in kit form,
> unfortunately we couldn't justify the support costs (since we couldn't
> differentiate b/w customers who bought complete scan tools or kits), so we
> dropped the kits. You can still buy the ELM327 chips from our website,
> though:
>
> http://www.scantool.net/products/index.php?cPath=4
>
> OBDPros is probably the best quality clone of ElmScan 5 out there, but it
> has some serious connection issues. We bought their unit recently, and it
> would not connect on 250kbit CAN, it would not connect to our PWM simulator
> (when every other scan tool we tried, connected just fine), and it would
> quite repeatably under certain circuimstances insert random whitespaces in
> its PC-side response. Now, obviously I can't be objective in this case, but
> I can definitely provide a list of equipment and a detailed description of
> the test conditions, in case anyone is interested.
>
> However, my biggest beef with OBDPros is that they quite shamelessly
> violated copyrights of at least three companies: Elm Electronics,
> Obd2AllInOne, and ours. Paul Smith (the guy behing OBDPros) initially ripped
> E.E.'s datasheets word-for-word, and also ripped Obd2AllInOne's website.
> Some of the stuff OBDPros do is not technically a copyright violation, but
> it's obvious that a lot of it is pure imitation. For example:
>
> http://www.scantool.net/clones/obdpros_bt/obdpros_comparison-1.jpg
> http://www.scantool.net/clones/obdpros_bt/obdpros_comparison-2.jpg
>
> Other ELM327 clones that we purchased, either don't work at all, or only
> work on CAN and/or ISO. Just for the fun of it, we swapped out their PIC
> clone with a real ELM327 chip, and found that it wouldn't connect on VPW and
> PWM -- the board doesn't have provisions for those protocols.
>
> Autoenginuity is a good tool for manufacturer-specific diagnostics, but
> their tools are priced outside the range of what most people would like to
> pay for a scan tool. They must be doing pretty well with professional
> mechanics though, as their site is #3 on Google, when you search for "scan
> tool". We've been catching up to them in terms of functionality, with the
> help of third party developers, and IMHO ScanXL is in some ways better than
> Autoenginuity software. :)
>
> Unless you plan to eventually make your scan tool into a commercial product,
> I would advise against spending your time developing it. With the exception
> of ISO (which looks a lot like UART), the protocols are pretty complicated.
> If you want to do it for fun, cheap OBD cables are available, just search
> for "obd cables" on Google. :)
>
> If you have any questions about OBD, feel free to ask (but remember to
> change the tag).
>
> Vitaliy
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>
>
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist