RomRaider

Can anyone shed some light of the missfire detection problem going from ms41.0 to .2 . Im interested in the differences in ECU logic behind that. Can it be implemented in the custom code , so as to keep missfire detection on an ms41.0 engine? I am willing to test that(if there isn't anyone doing that as of now) as i have both engine types in 2 running cars.
The sensors for the different types of engines (rear and front mounted) are different and i have managed to make MS41.2 software run with the OBD2 sensor and missfire detection enabled, with hints from a post in the conversion thread. So i believe it should be a matter of signal interpretation in the code.(pinouts and tooth counts are the same).
OBD2 sensor price is 50% more than the OBD1 one ,so i believe it is justified to look for a fix to that. Not mentioning machining ,and wiring work involved.

I'm very interested in your CustomCode.
If i understood correctly, you have found MAP INDEX et how read and write them.
I would like to understand how works and where the MAP INDEX is in a full read. Can you explain us ?
On BOSCH 402/403...Index is the end of code adress...

Diablo

IS anyone else experiencing issues with the logger when running the new custom code,i had it working after being sent a version that should work with the code, it then just stopped working totally, not event allowing a connection to the ECU, i deleted the entire rom raider from my laptop, reinstalled but again it will not work. When loading the logger def for the original code even diconeected from the car all the parameters are there to select but when loading the new Logger definention it straight away pops up the message about needing a logger def as if i havent loaded anything, Really annoying now , any help would be great
Update.........java.lang.nullpointerexception keeps coming up

Did you try deleting your setting.xml file?

I did but the same result, I can select the standard Def file without the car connected and it acts as if it will work but does not see the ECU and will not sync so i had a modified def sent to me, this worked but stopped, I deleted everything and started again and worked but again has stopped working randomly but now when selecting the modified def it still says no "No logger def found " , I wish Quickflash logged Knock then i wouldnt have to worry about using rom raider logging as quick flash works well

One thing i will ask though is where do you choose to put your logger defs, I just have them in a folder on the destktop and select from there, always have done but is it better to have them elsewhere in a directory.

a mate from mine has had the issue that on windows 10, its working with the cloud, and if the files were in a folder on the computer but that this folder is cloud based then he has issues. as long as it is a local directory it should be ok.

No Matter where i put the folder it wont work, It allows me to select the EN. xml original def but the new one i was sent doesnt work and the issue is the original def files dont work with the new code.

Is there the possibility quick flash will be or is able to log knock.
As it stands quickflash is very quick when logging and does a good job but it is limited in parameters it logs.
I am using quickflash as the Romraider Logger does not like the new code so i am unable to log now.

If anyone has info on this or able to make quickflash log know then please drop a reply

email the developer instead of asking in a public forum.

Since your logger worked at one point, I doubt it’s the custom code. Likely user error

As you are already aware Kyle custom code was not able to be logged using the standard definitions so i was sent a def to allow my ECU to log but this stopped, I then had it working again but once again it has randomly stopped, I ask about quick flash here as many ROMRAIDER users use it and if additional parameters where able to be logged then it would be an even greater tool.

And everyone else testing custom code are not reporting this logging issue. You said yourself you’ve gotten it to work twice. It isn’t an issue with the custom code. I’m willing to bet if you flashed a stock rom and uses stock defs, you’d have the same issue.

I suspect the logger XML file is corrupt in some way, this can result in a "No logger def found".
The XML file can reside anywhere in your personal folders. Just tell the Logger were it is via the Settings menu. Once set though, don't move, rename or delete the logger XML. That will result in the Logger being unable to find the XML file you previously told it to use.

And what does the rr_system.log say about the logger XML file you are trying to use?

The logger accepts the original def file that we all use but it wont even accept that my new one i was sent exists so it just holds onto the EN def.

I have attached the rr log

The logger accepts the original def file that we all use but it wont even accept that my new one i was sent exists so it just holds onto the EN def.

I have attached the rr log[/quote]redownload the attachment that was sent to you and try again. If the original def is sticking, it will not work on a custom rom which isn’t defined.