I'm running 6.1 now but those were originally started with 5.5 IIRC. I upgraded them from 5.5 to 6.1 without issue?
Printable View
I'm running 6.1 now but those were originally started with 5.5 IIRC. I upgraded them from 5.5 to 6.1 without issue?
weird. i'll see if i can figure it out, otherwise i might just see if ya can get me an ascii dump of hex n comments (i think ida does that?)
been a while, but it should, in a few different formats. it's so much nicer to work with inside of IDA though... i'll see if I can find a reasoning behind it and get it functional.
any possibility to add a dropdown list on the wideband tab for choosing a different input pin, say pin D27?
yeah if you test it for me i'll do it
I'll test it. Trying to avoid using the ac pressure input. I've got pin d27 working as an alternative input for the wideband, thanks to kur4o.
itll be in the latest beta released soon-ish. im going to do more wide band data analysis too I think youll like it
great, thanks! i guess it'll be in the next release
one other thing, a kind eehack user is donating a wideband, so new wideband analyzer features etc will surely be in the works...
already digging the wideband analysis. Question, is it by design that the wideband analysis rounds to the nearest whole number? I'm analyzing open loop cruising with the wideband.
also
I have a feature request. It would be helpful to have a Time (sec) display on the main tab somewhere. it would be useful when trying to move to a specific location. I can see the time on the graph, and would like to be able to go to the same area on the main tab.
a damn good point and very easily done. just have to make room for such a control. nearly every pixel on that tab is either used, or i have a plan for it
edit: you should also know that clicking anywhere on a graph will move you to the closest available record; there's just no cursor on the graphs so you don't realize it's happening...
no, it isn't.. damn, it was working fine. i'll fix that today.Quote:
already digging the wideband analysis. Question, is it by design that the wideband analysis rounds to the nearest whole number? I'm analyzing open loop cruising with the wideband.
i fixed it, and i added the timestamp display just as icing on the cake. thanks for the feedback.
3.5.1 available here: http://fbodytech.com/eehack-2/download-eehack/
v6 mode4 stuff for reference. so it does have commanded spark, afr, and cyl cut. awesome.Code:RAM:0360 word_360: rmb 2 ; DATA XREF: sub_9F91:loc_9FA5r
RAM:0360 ; SPI_chatter_failed_defaults+Fw ...
RAM:0360 ; ALDL mode 4
RAM:0362 byte_362: rmb 1 ; DATA XREF: sub_9FBA:loc_9FCEr
RAM:0362 ; SPI_chatter_failed_defaults+12w ...
RAM:0362 ; ALDL mode 4 stuff
RAM:0362 ; b0 set causes m4 value to be subtractive
RAM:0362 ; b1 clear makes the m4 value a total value
RAM:0362 ; b2 is required to be set to allow any mod
RAM:0362 ; b3 will reset BLM cells
RAM:0363 byte_363: rmb 1 ; DATA XREF: sub_9FBA+19r
RAM:0363 ; ALDL mode 4
RAM:0363 ; b1 and b2 set uses 364 as cylinders to disable
RAM:0363 ; b2 set, b1 clear uses 364 as target AFR
RAM:0363 ; b3 set causes choke fueling to be disabled immediately
RAM:0364 byte_364: rmb 1 ; DATA XREF: sub_A594+A9Fr
RAM:0364 ; SPI_chatter_failed_defaults+15w ...
RAM:0364 ; ALDL mode 4
RAM:0364 ; mode 4 commanded target AFR
RAM:0364 ; or disabled cylinders
RAM:0365 byte_365: rmb 1 ; DATA XREF: sub_D4A5+7Ar
RAM:0365 ; sub_D4A5:loc_D526r
RAM:0365 ; ALDL mode 4
RAM:0365 ; mode 4 commanded spark change(or total)
RAM:0366 byte_366: rmb 1 ; DATA XREF: sub_A057+52r
RAM:0366 ; sub_B76E+74w
RAM:0366 ; ALDL mode 4
RAM:0366 ; duty cycle for ???(106C)
RAM:0367 byte_367: rmb 1 ; DATA XREF: sub_ECEE:loc_ED56w
RAM:0367 ; sub_ECEE:loc_ED69r ...
RAM:0367 ; 8885 stored here, gets counted down
RAM:0368 byte_368: rmb 1 ; DATA XREF: sub_E26Cr
RAM:0368 ; buffer overflow test byte
RAM:0369 rmb 1 ; bottom of stack
so what 'bout idle target?
im going to pull your adx and have a look too. at least if i can get V6 commanded spark to work with my autospark table thing it'll be super useful for V6 tuning.