Mapping Problems

Hi All - I'm hoping that PaulDaytona or some smart person can help. I successfully loaded one of Mark's maps last night, though the reader, writer and Guzzidiag programs each had multiple failures before getting the job done. The writer program in particular took many iterations before loading the map. Unfortunately, the bike didn't run well with the map. Mark was very gracious in rushing me a new map to try. I've been trying to write the map to the ECU for over 3 hours now (off and on....but at least 40 tries). Sometimes I get to the erasing function and it freezes. A half dozen times I got to the upload portion and it starts uploading and then freezes and states and error occurred "try again."

I'm running a new Mac with OS 10.9.3, Lonelec cables, Guzzidiag V0.41, Reader V0.22 and Writer V0.20 and Driver v2_2_18.

I'll keep trying, but I'm hoping someone has some help for me.

Thanks

Ted,

I have to wonder how compatible Mavericks/Mountain Lion is with the GuzziDiag suite. I can't recall the specifics, but we were having intermittent connection problems with a Macbook Air running Mavericks (I think, could have been Mountain Lion).

I am running 10.6.8 (Snow Leopard) and I have never had a connection problem. I suspect that it is a problem with the FTDI driver. The driver readme file says that v2.2.18 was last revised in 2012. When you open the driver's dmg file, it only lists Mac OSX versions up to 10.7 (Lion).

I would bet dollars to donuts that it is a driver revision problem. You might want to see if there is a newer driver on the FTDI website, or try it again on an older Mac OS (Lion or older).

There is a technical document on the FTDI website that might provide a solution, but it is beyond my skillset with respect to modifying driver parameters...

The FTDI Knowledgebase infers that connection issues might be resolved by trying the D2XX driver vs. the VCP driver, or maybe in combination.

FTDI Knowledgebase wrote:

By installing the Windows CDM driver, both driver interfaces are available.  For other operating systems, a different VID and PID combination may alow driver conflict to be avoided.

The D2XX driver can be downloaded here, but I have no idea if this will help with your connection issues.  Maybe Paul or Beard would have some more valuable insight here.

You might read through this driver installation guide to see if the driver is connecting with the ODB-II cable successfully.

Steak -

Thanks! You nailed it! I guess the driver was unstable with the new Mac OS. I was probably lucky that I was able to do everything yesterday so (relatively) quickly. I lugged my home Mac (OS 10.7) out to the garage and wrote the new map on first try.

I still hope to find a solution to use the new OS on the laptop.

Now to go try Mark's creation!

Thanks,
TRw1 (Ted)