13brv3

Sorry guys, I forgot my secret decoder ring (secure ID token) for the company laptop, and have been out of touch for a few days.

My AFR's have been very accurate since we came up with the new poly, but I haven't had too much chance to play with it. If yours don't seem to be as accurate, you should try the test that I documented above, where you measure the analog output with and without having it connected to the Datalogit box. There may be a difference in the voltage drop between boxes, and these numbers were based on my (first) box.

Since I've been having so many interface errors with my datalogit, I have another box being delivered to my house today. I hope to be able to do some testing this weekend, and will take a look to see if the voltage drop is the same between the two boxes. It should really be pretty close, but you never know.

Goblin, maybe while you're hacking the Datalogit, you can fix their interface errors

Cheers,

Goblin

Funny you mention that... I get the same problem every now and then. I'm hoping it's just a comm error that will be easily correctable.

FCEdit is written in Visual Basic 6, I think, and I don't know how low level they can get with regards to serial port settings (I should note that I am NOT decompiling or disassembling FCEdit... That would be illegal.). Everything I'm doing is in C/C++, and if the error happens in my own software, I'm hoping to be able to get better state information out of the operating system than they'd be able to with VB. I've never worked in VB6, though, so that may not even be an issue. It used to be...

Quick progress update on the hacking.

I've got all the packets figured out that contain information displayed in FCEdit, with the exception of the packet for fuel injector settings (it's got some weird data in it that doesn't want to match up).

I've got all the reading, and all the writing figured out.

All that's left to hack is the real time data monitoring packets for logging/FC Commander display. There's not a whole lot of new information there, so it should go pretty quickly.

I've got a nice long document I'll post here in a new thread, and to the Big List once I've got the logging figure out.

13brv3

So are you taking requests for new features yet

Rusty

Boostn7

Well guys...the new poly seems to be working for me...

A/F's on the FCEdit are a bit slower but within .1 of the FJO display.....only from 13.5 and up is a bit more

I've so far tunned everthing to 17psi on the twins....on the logs it shows as 1.10-1.12kg/cm2 and A/Fs in the low 11's ...inj duty is hitting 92-94% so the 4 x 850cc are very much maxed.

Will update soon...
Thanks again.....

13brv3

Great to hear John. Glad it's working well for someone else. I'm installing the last of my goodies now, and will have to start tuning for real soon.

Cheers,
Rusty

rotorsrule

did datalogit or anyone ever respond to the right polynomial so the o2 sensor acutally displays what the fjo wideband sensors voltage is exactly like in their manual ? http://www.fjoracing.com/PDFs/MWI0002%20rev%20I%20(WBO2%20Controller%20with%20RPM&AUX%20Installation %20Manual).pdf

AFR VOLTS
10 .81
10.25 .91
10.5 1.01
10.75 1.11
11 1.21
11.25 1.31
11.5 1.42
11.75 1.52
12 1.61
12.25 1.71
12.5 1.80
12.75 1.88
13 1.97
13.25 2.06
13.5 2.14
13.75 2.22
14 2.3
14.25 2.38
14.5 2.45
15 2.54



everyone formulas so far are not close to this at all, this is the actual volts from the o2 sensor, my excel is on the way so i cant come up with one yet. before it do i wanna make sure that the voltage from the 02 sensor correct? i dont wanna get it and have it be based on somthing completely wrong.

rotorsrule

ahhh i see why its diff from what the actual PFC is, the impedance is diff. so the fromula posted by 13brv3, is it working for everyone or anyone having problem with it being off? thanks alot