RomRaider

Relabeling, and documenting scalings... No, I wouldn't say it "adds nothing". A lot of parameters have direct equivalents even in non-VQ35DE ROMs; even if they don't line up 1:1 it's still good info.
Not that it matters much to me, but having 3-4 different repos is more of a pain for (new) users. Maintaining a unified (as much as possible) set of templates and defs isn't easy of course, but so much nicer.

Eh, if you're doing the work, you do whatever you want P )

I honestly do agree that I'd rather have them all in one repo. But I'm trying to get a good foundation setup with Z/G ROMs atm and it's much easier to manage when you only have to go through ROMs that you're actively modifying than having to try remembering Z/G specific ECU ID's or managing them elsewhere. The nice thing about the redacted template is that I can just add all the ROMs back whenever and they'll work as intended. So once the Z/G ROMs are all up to spec, I could add the others back in and then have the Z/G defs also stored in another folder. Since at that point, that would be smarter than modifying the files in the repo itself like what I'm doing now.

Made some major progress recently! I feel very good with where the defs are at this point in time. The majority of USDM ROMs now have at LEAST the bare minimum defined for them. Enough where you could legitimately tune a vehicle with the provided defs haha I focused heavily on utilizing ROM bases, as to keep the amount of ROMs needing defined to a minimum. Niche things like limiters, thresholds, etc will come later. I also focused mainly on maps that were at least somewhat understood, as there's no point in defining maps with unknown functionality. (For public defs) I also re-included the non-USDM Z/G ROMs, except they're in a separate folder now. Same for non-USDM Z/G ROMs, as they aren't really needed yet.

What I'm really happy with is how well my DTC calculator works. I've been able to define all DTC's for all the USDM ROMs just from locating the start of the DTC block. While I do need to either extend the bits for a some, or individually add separate locations for others, the main DTCs are defined for all the USDM ROMs. The main outliers will be G35's (both RWD and AWD) and Rev-Up's. But the DTC addresses are still accurate it appears.

Eventually I want to expand the logger defs. But given how it appears that not many people use the logger, it wouldn't be beneficial at this point in time. However, if you want your ROM defined, just let me know! I'll always prioritize active ROMs over random ROMs I just found on the forum Also, send me any and all 350z/G35 ROMs! Post them in the stock ROM list here -> viewtopic.php?f=65&t=11098

Also, if anyone has any ideas on further automation, feel free to share!

1.maybe not needed, however, its good to have the JDM rom for a reference in changes. Helps to understand whats going on inside the ecu, as far as , values are concerned.Its interesting to see the changes made betweern country platform.

2.I would use the logger if i could. I need to get an openport cable ( i think thats correct???) as the vagcom k-line adapter is obviously not J2543 so it does not communicate with the logger.Ithink this may hold up many as the price point is 60$ + from what ive seen.

3.no ideas on automation,Im not a coder. I can be a tester for your DTC program or any other testing you want done on my g35 and report if you want to further develop.

Yea, the main thing really is that they'll have different emissions and potentially different values for certain maps. IIRC, their timing is more aggressive than ours. So it's definitely cool to at least have the basics defined for a few, like trimming maps, VVT, QH0, etc.


Unfortunately, you do need a J2534 cable. But yea, the best one for the money seems to be the OpenPort 2. I paid ~$183 when I got mine. So just a taddd bit more expensive than a $10-$20 VAG-COM cable haha But while it's definitely quite a bit more expensive, still cheaper than UpRev's $225 cable AND you get some really fast logging speeds. So it's well worth it for sure. But there isn't really another option. I'm sure you could make the VAG-COM cable work with custom code and such, but it just wouldn't be fast enough I'm guessing to be worth the time and effort.


Actually, CM30B already has the automated DTC code added So if you find anything that looks incorrect or is missing, let me know! I know that G35's can come in AWD, so AWD stuff will probably have some extra DTCs. Alongside this, it seems that earlier model G35's use SLIGHTLY different bits for some things, but it still looks like the bits line up. So it should just mean that all I have to do is bit extend some DTC templates, but further testing is required

Took a decent bit of time, but it was well worth it Definitely gonna take a break from the public repo for a while, except for fixing errors, adding descriptions, etc. Not much of a reason to go further than what's currently defined until everyone has time to better understand the currently defined maps. I want to focus on the logger defs a bit more for sure. But given how we have a solid three people here who actually have a J2534 cable, it just isn't the right time for it. NDS2 is more than enough for anyone doing basic tuning, so I'm not too worried about it at the moment

If you want basic logger support for your ROM, or need certain parameters defined for your ROM, just let me know!

Great work.[/quote]

Based off the auto-defined results, it seems to be 100% accurate for any USDM Z/G ROM, with G ROMs being a tad bit different due to different sensors, AWD, etc. But it seems that the only adjustment needed is bit extending some of the DTC templates to support them.[/quote]

Now this is a breakthrough. Suddenly it's looking like you may be able to have an all in one or all in the same bundle of program/s for tuning and clearing falls and actually knowing what they are.
Superb!

First off, you are the man. I downloaded my ROM for the 2005 G35 Sedan AT and loaded your defs and everything just worked. Now for a weird question. If I wanted to tune for "economy" instead of performance..... is that a thing? E.g. can parameters be adjusted such that fuel consumption is lowered etc. ? Would be fun to flash economy ROMs for daily driving and then performance ones for fun

Thanks again for all of your hard work.

I uploaded the 2005 ROM to the main Nissan ROM section.

Technically you can, but it just isn't going to be worth pursuing. Most fuel economy gains come from regular tuning anyway, so the only real tuning you'd do specifically for fuel economy is lean burn maps and messing with the ETC. Lean burn won't have any noticeable effect for VQ's and ETC is, well, entirely dependent on your accelerator input. So really you just want to go about tuning normally and you'll potentially see increases in fuel economy.

But the best thing you can do is change your driving style and habits. Go the speed limit, use cruise control as often as possible, properly accelerate for the given scenario (slower in the city, faster on the highway is the very basic and general idea), etc.

Hi!
Newbie with a JDM -03 350z here. I've been reading these threads trying to learn as much as I can while waiting for my kkl cable to arrive. I should have the CD415 ecu and I noticed that while there is a definition file for it in your github repo, it's very minimal. Apart from dropping a dump of the bin to the forums once I get the cable, what else could I do to help out fill its definition file so it could be tuned? Any resources you could point me to regarding reverse engineering and looking for the maps in the bin etc?

We already have a CD415 ROM dump, so no need for that. But you could definitely checkout https://nissanecu.miraheze.org/wiki/Rom ... isassembly to attempt to be able to cross reference new maps from CF48D with your ROM. If I can find time at one point, I could define the standard maps for your ROM, but I've been extremely busy lately. Haven't even had time to continue analyzing CF48D haha

Thank you for the link! Read it through and seems it shouldn't be too difficult, assuming the jdm ecu is similar to yours and you've already done the hard part of defining the maps in the first place. I suppose I could start crossreferencing already using the available rom dump? Is there anything I should keep mindful of since it has the SH7055 instead of SH7058 like yours does?

Your best bet would be to cross reference with CF48D, as it cross references nicely with all Z/G ROMs. (03-06) The main thing to keep in mind is SH7055 has half the ROM space as SH7058, so a lot of the empty space found within CF48D won't be there within your ROM. So things won't look as pretty for your ROM since everything's typically just crammed together haha

Would CF44A rom dump be at all beneficial to you? A friend of mine has said ECU, and there are defs for B, C and D though they seem to be lacking definitions.

For sure! I don't seem to have that one yet. Funny enough, its master ROM is CF44E, with B/C/D being completely unrelated to it.