34 Daughterboards

[darkhalf]

okay sam

http://test.nice.com.au/ed/sau/grid1.jpg

http://test.nice.com.au/ed/sau/grid2.jpg

these are the sheets that came with the board. im sure you have these already.

the boards came out in two revisions, Peter from PLMS has the first revision (without the ER34 connector). Eds board is the second revision

* first thing is while the ecu is in the car, plug in consult and retrieve the entire ROM image (0000-FFFF). (actually the ROM code is actually 1000-FFFF the first 0000-0FFF is memory mapped I/O and RAM).

* use only that ECU ROM image in your car otherwise if you run into problems later having a different ECU image wont help you troubleshoot

* if there is any coating over the PCB on these pads you will need to remove it using acetone and a cotton bud. we didn't really need to do that

* next thing you need to do is used a solder sucker to remove the solder on pads 1-40 on the ecu as shown in the pic

* using acetone/circuit board cleaner again remove the coating around surface mount resistors J903 and J904 and spare pads J902 and J905.

* using a soldering iron on both side remove the 0 ohm resistors. these are very small and easily damaged. resolder these to J902 and J905

* next thing is using a bit of solder, join the jumpers J1,2,3,4,6,7,8,9 together for the ER34 ecu

* next thing I did was solder the sockets into the daughterboard. rather than the standard 28 pin sockets that came with the board I went to the electronics shop and got 32 pin strips and snapped them into 14 pin rows and soldered 8 of them in. this way I can use either 27C256 in odd/even or 27C512 in skip mode. the EPROMs must be 120ns or less according to the sheet

* final thing was soldering the board to the ecu. got the orientation the right way (sockets facing down) and then put it all together

[27C256 ODD/EVEN MODE]

* next i loaded my 64K ROM image into ROM Editor against a dummy address file. rom editor is a bit dodgy/buggy however

* I saved the images as ODD/EVEN from the file menu as 512 size. 256 size should have worked but trunscuated the file in half 0000-3FFF filled with FF for 4000-7FFF.

* 512 puts the image at 0000-7FFF and then FFs for 8000-FFFF. i cropped them to 0000-7FFF in a hex editor and resaved the files

* first used 27C256-100ns EPROMs and programmed one with EVEN and the other with ODD from the files out of ROM editor

* Rom editor also saves ODD as EVEN and EVEN as ODD!!! so i swapped over the stickers and the order of the chips in the board after it didn't work the first time

[27C512 SKIP MODE]

* this time just put the consult 64K image burnt straight onto two 27C512 chips and plugged those in, and it worked. these chips were 150ns so a bit slower than the sheet specifies but should be okay

after you socket, if you have the customers car there, just plug the ecu in and then the chips, fasten the board and try it out. make sure you get the EPROMs in the right direction otherwise you will definately fry something. my main problem was i had to run the ECU by itself on the bench so had to solder a heap of wires to the pads on the ECU just to get the thing running

each time you want to change the tune you will need to either plug in a decent emulator (or two pocket romulators doing skip mode) or see if a badbiki board is going to do it. however the badbiki board will be a pain since you will need to turn off the car, change the map, start the car again, test and then repeat (better than eproms however but you need a decent emulator).

anyway I'm going to buzz the board out tonight and put the schematic for a modified one together so I can run it from NVRAM. i've got modified consult patch code for this ECU which will let you retune the thing via consult so once the board is in you will never need to touch the ecu again

[Dr_Drift]

Darkhalf,

Cheers for that, I can't wait to plug my 16 bit real time emulator (with working map trace) into one of these.... have been using it quite successfully using the current PLMS boards, as well as 8 bit single eprom ecu's.

Just wanted the address file locations for the ER34 so I can start putting an engine config file together for our software. Hopefully you don't mind sharing?

Sam.

[darkhalf]

well you're going to make money from it right? its taken me a lot of time to do what i have so far together.... and it will take more time to finish it

finished buzzing out the ER34 schematic last night so i can get some boards made from these

[Dr_Drift]

lol..... ok... how much do you want? PM me and I'll gladly contribute to your research....

but seriously, I'm only doing this for the love of 'lines and to help out some 34 owners... really I am

Edited August 31, 2005 by Dr_Drift

[ed]

I don't think it should be sold until the address table is 100% complete with k-constants and such.

[mad34]

ill be happy to pay a small research fee for the finished product guys.

if you guys can do it good on you. You definatley deserve money for your troubles.

[darkhalf]

need to work out some more of this daughterboard so i can plug NVRAM into it. also i found that the fuel tables have an extra bit set so it wont look right in romeditor or other programs. i've put in a tick box in nistune to turn that off so it displays okay.

the er34 consult code has been modified and i can change RAM values via the consult port, once the NVRAM is plugged in i can then modify maps from the software in realtime

next i'll try and find RPM/TP RAMvalues for maptracing

.... finished working out the schematic for the NVRAM. i'll start putting the parts together in the next few days

Edited September 5, 2005 by darkhalf

[ed]

good stuff Matt.

does the hacked up board look messy? haha

[darkhalf]

sorry i hadn't started it yet... little one is getting up too early in the mornings so i hadn't much time at night to go and mod it!!!!

the changes shouldnt be that messy anyway since only have to cut a couple of tracks after drawing it all up

[darkhalf]

okay its done and it works fine! we have realtime tuning on ER34 via the consult port

two small adaptor boards and one cut track (plus some wires hanging off). i'm going to get this schematic done properly and look into getting some boards made up. this will also work for other ECUs supported by this board (S13,S14,S15,Z32 etc etc). guess i better hunt down TP so you can maptrace the fuel/timing maps properly also

[Abo Bob]

How smart are you?

Do you think you will be able to modify the shifting on the autos?

[mad34]

well done!!

[darkhalf]

i wont be able to do the auto chips without knowing the IDs and being able to match it against a datasheet to get the pinouts (and then retrieving the contents of the chip and making a board to change them). either that or i need the pinouts of the rest of the unused solder pads which use the ECU and the jumpers to change to read from the external board

whoever made the multiboard would have had inside information of how the ecu works in order to know which pins did what and what resistors to change. that JECS chip is really an all in one MELPS with other stuff connected.

for this job on Eds board, I already had the multiboard and using the pinouts of the EPROMs and the S13 SR20 pinouts on the multiboard let me figure it out further to fit NVRAM and know the pinouts of the ER34 socket

[Downforce]

So what's the update on this? Do we have a working solution yet? or are we still waiting to decode the addresses for the ER34 ECU?

[Abo Bob]

Why don't you read the last few posts.

[Dr_Drift]

I thought that was a valid question...

The way I understand it is that Matt can now tune in real time R34's with the limited address table. Still needed is TP scale for 'calculated' map tracing, k constant and injector dead time for swapping injectors, VQ map for swapping AFM's, speed limit, af limit (boost cut)....

Only when we have all the pieces will the daughter board make the PFC inadequate and also provide a solution for auto's... hooray!!!!

Matt,

Please update us all with your progress on the adress file identification?

Sam.

[Dr_Drift]

...

Edited September 9, 2005 by Dr_Drift

[Downforce]

Thanks Sam... Looking forward to this happening. Hopefully we can get the remaining address files.

[darkhalf]

okay what i have worked out from disassembly currently is...

Fuel map Hi

Fuel map Lo

Ignition map Hi

Ignition map Lo

Fuel map TP index table

Fuel map RPM index table

Ignition map TP index table

Ignition map RPM index table

Voltage Quantifier map (aka Swap your AFM over with another one)

also I have just been going through and working out the TP and RPM indexes themselves for fuel/timing maptracing (be nice to see where you are tuning)

dont do calculated TP from MAF voltage for tracing since the TP forumale can vary between ecus and may alter where the map is really being accessed. sersiously the whole TP equation is dependent on a multitude of tables and constants which are indexed depending on values of inputs (temperature, sensors etc)

what i plan to look for when i get time to work on this particular project next is...

Theoretical Pulsewidth Limiter (aka AF Limit aka Boost cut)

K Constant (aka Injection multiplier)

there is also speed and rev limiters. these single values are so difficult to find. there are like 1000 or so possible places it could be

I think there are also boost solenoid maps like S14/S15 but needs to be confirmed

[Downforce]

Very Nice work darkhalf, keep us updated !