Pages: 1 2 [3]
Author Topic: Ignition timing at cruise  (Read 18581 times)
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #30 on: January 10, 2013, 09:52:07 AM »

Forget about start to finish; id be happy just to see proof of concept source (like 360's checksum code). The rest wiill just take some long term tweaking.
« Last Edit: January 10, 2013, 09:58:53 AM by nyet » Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
prj
Hero Member
*****

Karma: +1072/-480
Online Online

Posts: 6035


« Reply #31 on: January 10, 2013, 10:09:38 AM »

I started looking at the FTDI documentation a while back; is that the right place to start?

I think right place to start is how to open a com port and write to it.
You don't need anything FTDI direct. Just serial comms.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
sweegie
Full Member
***

Karma: +10/-2
Offline Offline

Posts: 137


« Reply #32 on: January 10, 2013, 02:53:03 PM »

FTDI have some code examples on their website, one specifically shows how to open a port & set baud / comms parameters. Handling the 9 bit transfers looks ok too, with 8 data + 1 parity bit. Change the odd / even parity parameter to set the parity bit 0 or 1 depending on the transmitted byte, and you will end up with 9 bits to sent. Receives can be handled by inspection of the parity error bit from the driver & some logic to set the 9th bit appropriately. I cant think of any other way to do this.

I'll try to have a play when i get some time....
Logged
Pages: 1 2 [3]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.027 seconds with 17 queries. (Pretty URLs adds 0s, 0q)