Anyone data logging EEC-V using the Tweecer RT and the 32 byte version of Binary Editor? If so, can you post the data logging code you're using? I have a new definition file for BE and I'm having difficulty understanding how the code works.

Thanks
John

_________________
'85 SVO Mustang

I think sailorbob is still trying to figure out how to get the 8065 (EEC-V) stuff to datalog. I believe the problem relates to accessing of the upper registers (0x0100-0x01FF). He found 2 different ways to access them and he believes the way he originally wrote the code is not working because it's trying to access the upper bank the wrong way. Since I don't have an EEC-V, I haven't been following those details closely...just tidbits of things he mentions to me about the differences between 8061 and 8065 processors that he's learning.

What specifically is the code doing that you aren't following?

_________________
...Always Somethin'

89 Ranger Supercab, 331 w/GT40p heads, ported Explorer lower, Crane Powermax 2020 cam, 1.6RRs, FMS Explorer (GT40p) headers, Slot Style MAF, aftermarket T5 'Z-Spec', 8.8" rear w/3.27s, Powertrax Locker, Innovate LC-1, GUFB, Moates QuarterHorse tuned using BE&EA

Member V8-Ranger.com

I'm not sure if the code I'm using is correct for the application. I found the code in the CRAJO definition file. Any tips for troubleshooting?

Here's the stock code:


Here's the data logging code:

_________________
'85 SVO Mustang