ECMTuning - wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

<h1>Installing on a PocketPC</h1> <div class="level1"> <p> Spyros Gounaropoulos has done an incredible amount of work creating a native PocketPC application to talk to a DSMLink ECU. We thank him greatly for this! Like the Palm port, this port involved a complete rewrite of the application. There is no way to overstate how much work was involved in this porting effort! Huge thanks to Spyros for posting this up on the forums. I'm going to copy his text below for archival purposes. </p> </div> <h1>Details</h1> <div class="level1"> <p> I have finished ( or so I think) the porting of dsmlink to the windows mobile version. Tested the 2g version on my car and it works pretty good. All code has been ported to C# with Visual studio. </p> <p> I was not able to test the 1g portion of it since the FakeECU do not support 1952 . It may have bugs for now but so far everything seems to be working ok. </p> <p> I was able to datalog on my car with my Axim X30 and a serial cable, no null modem was needed in my case using COM1 on the PocketPC. To install the program you will need Compact Framework 2 and the app. </p> <p> Files can be found here. </p> <p> <a href="http://www.dsmlink.com/images/forums/oses/ppc/" class="urlextern" title="http://www.dsmlink.com/images/forums/oses/ppc/" rel="nofollow">http://www.dsmlink.com/images/forums/oses/ppc/</a> </p> <p> You start by copying the <a href="http://www.dsmlink.com/images/forums/oses/ppc/NETCF.CAB" class="urlextern" title="http://www.dsmlink.com/images/forums/oses/ppc/NETCF.CAB" rel="nofollow">NETCF.CAB</a> file from your PC to your PocketPC and then execute it on the PocketPC. That installs the base .NET framework stuff. Then you run the <a href="http://www.dsmlink.com/images/forums/oses/ppc/dsmlinkInstaller.exe" class="urlextern" title="http://www.dsmlink.com/images/forums/oses/ppc/dsmlinkInstaller.exe" rel="nofollow">dsmlinkInstaller.exe</a> file on your PC to install the actual DSMLink application onto your PocketPC. </p> </div> <h1>More Details</h1> <div class="level1"> <p> More details were provided by one of our board users (JSMCPN). I'll copy his text below. </p> <p> Hi, I'm just making it known that my HP iPaq hx2490b works great with DSMLink_PPC running WindowsCE v5. </p> <p> Here are some 'Link installation tips for Windows Mobile devices: </p> <p> There are multiple processor architectures available for pocket devices: x86, ARM, MIPS, etc. You must install the correct version of <a href="http://www.microsoft.com/downloads/details.aspx?familyid=0c1b0a88-59e2-4eba-a70e-4cd851c5fcc4&displaylang=en" class="urlextern" title="http://www.microsoft.com/downloads/details.aspx?familyid=0c1b0a88-59e2-4eba-a70e-4cd851c5fcc4&displaylang=en" rel="nofollow">Microsoft .NET Compact Framework 2.0 SP1</a> that is compiled for your pocket device's architecture. </p> <p> When you install the Compact Framework on your Windows PC, navigate to </p> <pre class="code">%ProgramFiles%\Microsoft.NET\SDK\CompactFramework\v2.0\WindowsCE </pre><p> </p> <p> and you will see directories for WindowsCE v4 and v5. Determine which version your device runs and open that folder. Now determine which processor architecture your device uses, and open that folder. Sync the contents of that folder to your pocket device and install the appropriate CAB file. My iPaq is Windows Mobile 5 operating system, and is an Intel XScale processor which is ARM-based. </p> <p> <a href="/wiki/lib/exe/fetch.php?tok=08f413&media=http%3A%2F%2Fwww.dsmlink.com%2Fimages%2Fforums%2Foses%2Fppc%2Fnetcf.png" class="media" title="http://www.dsmlink.com/images/forums/oses/ppc/netcf.png"><img src="/wiki/lib/exe/fetch.php?tok=08f413&media=http%3A%2F%2Fwww.dsmlink.com%2Fimages%2Fforums%2Foses%2Fppc%2Fnetcf.png" class="media" alt="" /></a> </p> <p> Now install DSMLink.cab for PPC and have fun. </p> <p> This implementation by Spiro is very well done. My iPaq-to-serial cable, and a null modem adapter connect to DSMLink quickly and reliably, and communication rate is pretty good. The only problem with the software I have found is I get an error when trying to map the logged value ZT2WB to a physical signal input. </p> </div>