|
Bische
|
 |
« Reply #15 on: January 09, 2013, 11:54:26 AM »
|
|
|
Wow, this is heavy stuff.
Im thinking of a mini-logger that can log or at least display the varibles needed to tune timing, then a this feature to alter the timing.
Would it be possible to do that? Read a couple of varibles and write the timing channel at the same time?
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #16 on: January 09, 2013, 11:55:20 AM »
|
|
|
I don't see why not...
I don't have any interest spending my time on this though, because I have an emulator, so there is no point for me to do this.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #17 on: January 09, 2013, 12:11:27 PM »
|
|
|
Bische: i am interested in this project.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease 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
|
|
|
Rabbid
Full Member
Karma: +0/-0
 Offline
Posts: 55
|
|
« Reply #18 on: January 09, 2013, 12:18:53 PM »
|
|
|
I am too but what is the compatibility of all this with the ECU's used in the Opel world which are ME1.5.5 and ME7.6.2?
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #19 on: January 09, 2013, 12:31:38 PM »
|
|
|
Wow, this is heavy stuff.
Im thinking of a mini-logger that can log or at least display the varibles needed to tune timing, then a this feature to alter the timing.
Would it be possible to do that? Read a couple of varibles and write the timing channel at the same time?
IIRC, the calibration interface via McMess can write the 17 VS_VERST variables and read up to six bytes synchronous to the crank. I really don't know alot about serial communication or Bosch comm protocols, but is my understanding that the protocol is difficult to implement because it requires 9 bit transmission with a start and stop bit at 10400 or 125000 baud. I brought this up a while back, but it didn't draw much interest. I think mostly because Setzi was critical of the McMess protocol itself, but his perspective was mainly from a datalogging standpoint. I have only come across a few documents on this subject and they are scattered on this site. Tony posted a document on the calibration protocol from the Journel of European Communities, NVR posted and EDC document on McMess, and Setzi also posted a small writeup. |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #20 on: January 09, 2013, 12:36:39 PM »
|
|
|
I really don't know alot about serial communication or Bosch comm protocols, but is my understanding that the protocol is difficult to implement because it requires 9 bit transmission with a start and stop bit at 10400 or 125000 baud. Works just fine here with a dumb mode K-line cable... The 10400 9 bit thing. If you look up KWP 1281 it is also 10400 and 9 bit, at least that is how it is setup in the code of the older '90s CPU's. |
|
|
|
|
Logged
|
|
|
|
|
|
|
prj
|
|
« Reply #22 on: January 09, 2013, 12:48:48 PM »
|
|
|
11 bits are transmitted (through TxD) or received (through RxD): a start bit (0), 8 data bits (LSB first),
a programmable 9th bit, and a stop bit (1). This is from an older MCU documentation... And such data can be received through the dumb K line->serial cable without any extra work. |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #23 on: January 09, 2013, 01:00:55 PM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
sweegie
Full Member
Karma: +10/-2
Offline
Posts: 137
|
|
« Reply #24 on: January 09, 2013, 01:09:21 PM »
|
|
|
Setzi's "notes"
I didn't use the McMESS protocol for logging, it is so braindead ...
Good luck to everybody trying to make some use of this protocol.
If it could modify parameters without an emulator however, it would certainly warrant investigation, but phrases like that worry me! |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #25 on: January 09, 2013, 01:41:31 PM »
|
|
|
If it could modify parameters without an emulator however, it would certainly warrant investigation, but phrases like that worry me!
I brought this up a while back, but it didn't draw much interest. I think mostly because Setzi was critical of the McMess protocol itself, but his perspective was mainly from a datalogging standpoint.
I don't think logging speed is an issue for this purpose. Assuming 125000k baud is achievable, crank synchronous logging of dwkrz(0...5) is suitable. |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #26 on: January 10, 2013, 07:21:36 AM »
|
|
|
125000 might be achievable through the custom baud rate settings of the FTDI chip.
But you will need to use the D2XX driver to do this I think.
So quite a bit of extra work.
Then again, do we really need it to be crank synchronous?
There is 20ms between the time you can change variables, so let's say you change the variable every 20ms and you have 6 variables.
This means you still get a logging rate of 8-9 samples per second.
I think that's plenty for real time dyno tuning of ignition advance, is it not?
You will have like 1/8th of a second delay on a 6 cylinder engine. I don't think it's bad at all.
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #27 on: January 10, 2013, 08:34:32 AM »
|
|
|
I'm convinced.
IMO, following the least path of resistance just getting it up and running is best anyways, then improvements can come later as needed.
Unfortunately, I'm behind the curve on this subject, so it will be awhile and alot of reading before I could bring this to fruition.
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #28 on: January 10, 2013, 09:14:04 AM »
|
|
|
I could easily develop this from start to finish with a nice UI, but then I'd charge for it.
There is no sense for me to spend time otherwise developing something I don't need... Not trying to be selfish, but just the way it is.
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #29 on: January 10, 2013, 09:27:57 AM »
|
|
|
I could easily develop this from start to finish with a nice UI, but then I'd charge for it.
There is no sense for me to spend time otherwise developing something I don't need... Not trying to be selfish, but just the way it is.
Makes sense. Flat rate for source? I started looking at the FTDI documentation a while back; is that the right place to start? |
|
|
|
|
Logged
|
|
|
|
|
