Sorry before I choke on my foot which adx you using? Assuming $0E???
Printable View
Sorry before I choke on my foot which adx you using? Assuming $0E???
hi stew
no, its $0D.
Attached bpsa14.bin and bpsa15.bin.I have changed spark advance in bpsa 15 completely but not driven it yet. My problem-zone is idling up to 2000 rpm, then the car is running.
Hi stew,
i read too fast. I thaugt you speak about the bin. The bin is $0D. The adx was $31 , i have improved it to §31_new.adx
Sorry for the delay just got back from a business trip and didn't bring my tuning laptop with me. Gonna try to cut to the chase...I opened two sessions of tunerpro and ran your logs side by side using a $0D.adx and your $31.adx. Good news is the numbers are purdy much dead on the same in the history although there's some disparity in knock retard in same reported areas. However when using a $0D.xdf and $0E.xdf...line address do start in different areas in the bin between the two areas I've looked at. Spark shows all negative numbers in the $0E.xdf. VE in $0E.xdf has areas where values random zero with areas in high 90s slightly off idle. Someone correct me if I'm wrong but if you're going to use a $0D.bin then you should be using a $0D.xdf and $0D.adx. Your screen shot a few post back, you don't find it odd that you have ~dozen peaks and valleys in the TPS that occurs in a few seconds? Or is that your foot feathering the throttle in that area???
Hi stew,
thank you for looking to my files.I will have a look for a 0D-xdf and a 0D -adx.I ordered an other Speed sensor and will wait until this works, then it will be much easier to to compare all the values to the momentary speed.I think the peaks and valleys were from feathering the throttle to prevent engine from dying.In the meanwhile i had copied the spark table from BHMC.bin to my bin but driving was worse. I took my spark table again and decreased spark advance at high MAP values and car ran better but still with problems below 2000 rpm.My question could I delete one table (spark advance near idle) or should I set all values to zero there in?
Don't waste your time using any of the stock Chevy timing maps. To be honest, I know nothing about AMC engines and what they like for spark timing. My approach to this would be to do a Google search for a AMC 304 spark timing table. There was one hit that I saw that they were using megasquirt. Perhaps you could experiment with that. https://grassrootsmotorsports.com/fo.../118096/page1/
Arghh...just reread it's referring to a AMC 360...
everyone needs to stop interchanging the letter O with the number 0 in mask names.
masks are hex, there's no letter "O" in hexidecimal
this will help you when searching for information about masks like 0D and 0E (also help others that might be searching for threads and posts like this one)
Hi steveo
you are right, so I wouldn`t mind if an administrator would correct this!
Two things that may help:
- A VSS is necessary in most all applications because there are many IAC positioning and other decisions made by the ECM code based on whether the car is moving or not. This applies to both manual and auto cars. Does not affect spark, but does many other important items.
- Playing hit or miss with spark is difficult. Best to just build a table based on your requirements. This may help: https://www.thirdgen.org/forums/diy-...ml#post6301288
One other general note. For those who don't have the ADX for your mask, it's always helpful to post a .csv or .xls* file that you export with your ADX rather than posting the XDL. More people might be inclined to review the log and help if this if done.
After some tries and errors, i could build a spark table what seems to work on the engine. But engine is not running round and when having a look to the graphs, I see some spikes in rpm. Could the ICM cause these spikes or should I search for an other fault?
The txt(csv) file is only a small part because its real size was too big for the upload.
Now I have changed the icm with brandnew one but the same spikes and interruption in ignition.
What to change next ? ignition coil ?
What other options do I have?
Those RPM spikes are odd. Are you using a duraspark dizzy/hall sensor? I wonder if your ignition (coil and spark plug) wires are so close to the hall sensor wires that they are interfering with the signal...?
No, it is the original AMC/Ford distributor , mechanical and vacuum regulation eliminated. The spikes are not that regular that they will be caused by interference but I will check that too. I had the car conected to an old motor-test with osciloskop and couldn't recognize afault in the curves. I tend to change the coil too.
Other ideas ?
Attached my last logfile.If I convert it to txt it has 6000kb and is too big tofor attaching!
Copy (Duraspark dizzy with advance removed). When you removed the vacuum advance, and welded your mechanical advance, did you screw down the hall sensor so it cannot move?
My understanding, in our situation (I have a 401 with a similar configuration), The computer gets the RPM signal from the Ignition module, the ignition module gets RPM signal from the hall sensor. If you have spikes, then the fault is somewhere in that chain. Do you have an extra ignition module you could try? Are you running the Ford wide cap or stock AMC tall cap? The hall signal is pretty sensitive so if your coil wire or one of your plug wires runs near it, EMI could distort the signal (especially if you ignition wires are acr'ing). I am also currently fighting really crappy ignition wires (arc'ing to each other and ground). I am not sure that failure would show similar results but might be something worth checking.