It can't open a port to the first FTDI device on your system.

 

Do you have the Tactrix cable connected to the car and computer with the ignition on?

 

Would anyone be willing to take a look at a log to give me a good starting point for sd? I have a 2.4l and the base settings are way off. running a gm 3bar if it matters. pm me your email and I will send it to you cuz i dont know how to post it here.

 

The easiest thing to do would be to take the map vs load table and do some multiplication on the load table to compensate for the stroker say add 15% should be pretty close. You can highlight the whole table and press the * key and use 1.15 to add 15% to all the values. If its rich revert and add only 10%

 

well i calculated the ve by using the 100*load/map, and i am getting ve's ranging form 65% at idle to 130% at 4500 rpm....its going to be hard to dial in the map/laod table

 

You have to be logging data before you try to write anything to RAM.

 

I tried that initially but it honestly didn't help me much in the end the values ended up being really close to what banks set to begin with for VE.

Here's what i mean by the map load table the one on the left would be a stroker setting. Its just a straight 15% difference.

Edit:
I noticed the left hand columns don't match just ignore that fact I forgot to copy it when i was setting this up as a demo.

 

Could you please tell me how to connect ? Is there anything special steps I should do ? I've done all the steps from the 1st page of this thread, got the prepatched rom file from 2nd step.

Yes I have it connected (ecuflash can read/write, so the cable is working), but the livemap says it cannot open port

Is there any chance someone can sent me already configured rom file + xml for it, incase I've done something wrong ?

 

OK, just installed my BlueMax 1250s today and flashed v7 final. To my surprise, they idle perfectly at my stock 850 RPM. I'm sure I may need to tweak them over the next couple of days, but I was surprised they worked so well at idle and cruise.

I not only edited the scaling and latency, but I edited all of the IPW cranking and running maps as well. Over the next couple of days I will see how cold starts and warm starts act and will tweak the IPW tables as needed, but so far, way above my expectations on pump gas. I may switch to E85 this weekend as well, but want to get DMA ported over to this v7 final first. I think I will let logic handle that part since he has done it already.

Anyway, maybe next weekend, I will try SD again with the new 1250s to see if the jumpy IPW is dampened by the bigger injectors.


Eric

 

If im using 96530706 but not using SD will it be ok to use this?

Im a little confused over setting up the MUT table, I can either use my ROM one or setup a RAM one? What blocks in the 'alt maps' do I put the items I want to log and in the livemap app what do I change.

What is the advantage of setting up the RAM mut table vs the ROM mut table?

Thanks and I appreciate your patience.

 

tried to run livemap on another computer today and it still says "unable to open port". I am using original ecuflash drivers (1.42) for tactrix cable (openport 2.0 rev. c), v7t6 ROM from Logic (from step 2 on the first page), the only thing wich I changed in ROM file are: created custom mut table, enabled AutoICS switch for ALT maps, and followed step 4. No other changes. I start livemap program and try to log and it gives that error (tried 5.1 rom with livemap - same error). Tried to change logging adress from FF FF A7 40 to 00 03 62 00. Guys any ideas what is wrong ? Maybe the cable, but on the other hand it works with ecuflash and evoscan.

 

Is your cable the only ftdi device on your computer? Have your tried to check what port it's using and switch ports. I haven't looked at that part of the source code, but John stated that your issue is that it can't connect to your first FTDI device in your computer.

Also, just to be sure, you have to have your ignition on to connect as well. But, I think you know that...just making sure.

 

If you're not using SD (ie. you just want DMA logging and live map updating), you only have to do the part listed in my original post. If you apply all the changes in this thread, you'll be running speed density.

There's a couple of advantages for tweakers like Eric and I, but the main reason for putting the MUT table in RAM is so you can whittle down the list of things you care about to something reasonable, in a useful order, rather than the old default of "give me the first 0x30 values of the MUT table, whatever they are".

And honestly, there's no reason it has to live in RAM for that; you could find another chunk of unused space in the ROM and put it there, especially since most of us don't change our list of logged items very often after we've settled on a useful set (especially since the additional overhead of adding values with the DMA logger is so much lower, and you can always crank up the baud rate as a countermeasure).

So, short version: open up the ROM in ECUFlash, copy the memory addresses you want to log (ie. the addresses in the MUT table) to the A740 location in the "alt maps space" table (there's room for up to 24 items there, as Eric defined it), and then make sure the logging address in the "Data" tab of the Livemap client is set to FFFFA740. You also need to make sure the list of items you're logging in the big pane on the left is correct (ie. they're in the order you set them up as in the RAM MUT table, and the formulas are correct); if not, I find it quicker to just edit config.xml with a text editor.

Even shorter version: if you stick with Eric's configuration and pre-defined logged items, you should have very little to actually change, if you just want to jump in and get your feet wet.

----

We really have some user-friendliness issues to deal with, don't we?

Dev tangent: my perfect interface for this kind of logging would be substantially different. I'm thinking a list of pre-defined memory locations that you can log, perhaps seeded by well-known request IDs from the ROM's real MUT table, that the user could select from. A RAM logging lookup table (like the current "RAM MUT table") would be defined at runtime based on that list of items you want to log, up to whatever maximum amount of spare memory you can set aside for this. Combine this with a runtime ROM ID test, and you'd have a pretty generic client for all ROM versions. Yes, I know none of this is trivial with the current client...

Another dev tangent: I'm a little concerned with how we're currently just blindly copying a big-chunk-o-tephra to RAM at boot. It made the code short and easy, but it means we're copying stuff we don't need to, and using RAM that we could free up for other stuff. I wonder if we shouldn't be more selective in what we copy? I wouldn't think it would be too hard to define a list of addresses and lengths somewhere to copy to RAM in sequential chunks, or even a simple table of sourceaddr,sourcelength,targetaddr in case you wanted to spread tables around in any unused portions of RAM. It also means we could easily move arbitrary tables to RAM, not just tephra's alt-map stuff. (Obviously, in all cases, you'd still need to fix up the original code to refer to the new RAM address rather than ROM; there's no "easy" fix for that.) Any thoughts?

More and more, I'm wondering how viable it would be to run a 96530006 variant on an IX ECU (but physically installed in an VIII), just for the additional memory and ROM space...

Also, Eric: sorry it's been taking me so long to get to forward-porting the DMA stuff to V7-final; I'll hopefully be getting to that today, if work remains slow.

 

It's the only FTDI device, tried it on different laptops, changed com port from 6 to 9, ignion is on...the only thing wich comes to my mind - something is wrong with the cable

 

What are your settings (Injector scale and latency) ?