sounds good to me
jeff, I'll make a thread for this when I get a chance & when I have more concrete info. but for now just going to throw some of the conversation up here that I've been having with a few nissan techs.
***********the following post is going to be long & maybe boring to those that don't care, so you've been warned

***********
I'm now talking to several nissan techs & trying to reach out to see exactly what resources I have available to me... it's going to suck having to tow my fx to the dealer in pieces just to have them connect a consultIII & try to program it, maybe it works, maybe it don't... then tow it back, make blind changes & tow it back again... could be fun... I don't think there are any techs out there that are allowed to remove a 13k piece of equiptment from the dealership, so this may indeed be necissary
first & preferred way would be to get it running on the HR box, which so far is my main goal & target. my thoughts are that the can communication buss that communicates from the different modules can be connected to the 07 ecu & that chances are pretty good that the 03 components will more than likely still communicate with the 07 ecu for the most part. the can buss is nothing more than just 2 wires, can high & can low, & all the modules are connected to each other through this buss. each component sends packets & sniffs for packets made for itself, just passing on the packets that are not useful to the next module in the daisy chain & I think the chances are pretty high that the language & packet specs on the 03 stuff is going to be the same as the 07, I'm hoping that for example the 03 IP module is sending out & receiving the same basic data that the 07 might have, same for the body computer & hopefully even the security module or the NATS, the cruise module etc...
now where I'm getting a bit concerned is, even if all of this is true, I still will need some external help. for example, even if I get it in & fully wired up & everything is a go, I'd still need someone with a consult III to be able to reprogram the keys to the HR ecu before it could have any hope of even starting because of the NATS system. of course after the fact I could indeed realize that there may be communication differences elsewere too, would I need to swap out to a 07g35x body computer?... is it possible that the IP module is different enough that I need to source even more g35x components? the adaptive cruise, the ABS, stuff like that. even though I'm thinking that the communication protocols & the language is probably all the same or similar enough that most things will still function I of course have no way of knowing for sure until after the fact.
second option I see is to drop the HR motor in, but then run it off the existing DE ecu combined with a Utec. I believe this is a more sure fire way of doing this, as I'm fairly sure that I can get the DE ecu to run the HR motor. this would involve me having to build a custom intake though & going back to a single TB setup instead of the dual TB of the hr. the only other issue would be the exhaust valve timing control which of course the DE knows nothing about, but, from my research too I'm lead to believe that since the exhaust valve solenoid is very simplistic & basically either on or off & rpm based, this control may be doable with the utec that I already have now on the DE ecu.
third option of a stand alone can't even be considered yet because even to use a stand alone, I still must first have a factory ecu installed & functional for the communications anyway. many think that a stand alone completely replaces the factory ecu but it does not, it installs & works much like a piggyback in that it will still use the existing ecu for communications to the rest of the vehicle, only a stand alne does not depend on the factory ECU for any perameters in regards to the running of the engine, hence stand alone... it doesn't literally "stand alone" it just stands alone in it's fuinction, but is still dependant on a stock ecu, so I can't even consider a stand alone until after I get a stock ecu working with the engine, either DE ecu or HR ecu
I've already decided that I am doing it, & since I've already decided that, that means that I've already decided that I will do whatever it takes too, weather it involves having to source a whole bunch more g35x parts or going stand alone or whatever else it might take I do realize that most would consider something like this impractical & of course this is the reason it hasn't been casually done before, but I refuse to believe that it is impossible either, & this belief is enough to make me want to do it & know that I will in the end pull it off one way or the other.
the emissions control & state inspection is a very big issue & should be a primary concern in dealing with a swap like this, this is not a race car for off road use only & has to be inspect-able to not be a big waste & destroy the worth of the vehicle really.
I have a friend with an inspection station & another who is an investigator for the state dmv and today I have talked to both of them about the ways of getting a valid inspection, in NY if the vehicle does not have a valid inspection the dmv will not even renew a registration. I'm now seeing that the day of just sticking another vehicle on the machine & generating a sticker is no more, an inspection is done with a live connection to the state computer & likes been said, one of the first things that the state equipment does is confirm the Vin #.
initially guys have come up with a method of initiating the inspection on the target vehicle & then switching the cable to an alternate vehicle & successfully completing an inspection, but the newest state software does another Vin check mid way through & this has become very difficult to trick, bottom line is for a swap to be considered successful then the vehicle must be done in such a way that it can legally pass a state inspection through the obdII interface at least. what the state computer don't see doesn't matter so much, the idea is for the ecu to not see any problems & pass with no red flags.
incidentally, the state inspector also tells me that in the case of a Vin not matching the vehicle's pcm stored Vin, the inspection can still go through, but it will raise a red flag in the dmv & they will investigate, they investigate the inspection station mainly & the fines for improperly done state inspections start at $1,000 each, his own words are that they are giving the shops just enough rope to hang themselves because this is a big revenue generator for them, so you better make sure that all required emissions components are in place & nothing else is tampered with or altered in such a way that the vehicle should have failed visually at least to protect the station, but the station will not be penalized just for the fact that the Vin is incorrect if everything else is 100% legit, if the car has a turbo setup or anything else that is not carb certified then you def don't want to kick up any red flags though & need to stay under there radar with a green flag inspection, the NYS dmv is actively searching for situations just like this, also if it detects one Vin on initiation & another midway through the procedure of an inspection the inspection station is going to get screwed for sure
I'm told they are seeing issues pop up here & there with salvage pcm's swapped. he even told me of one of his more recent cases of 2 identical Nissan's that belong to 2 separate owners on either side of town. they got a double red flag because each vehicle had the incorrect Vin # stored in there ecu's... turns out they had each others vin... the investigator eventually traced it down to the local dealer at some point having these vehicles side by side & troubleshooting an issue winded up swapping the ecu's to test, & then for some reason was never swapped back, the tech just thinking it didn't even matter because they were both the same & it wasn't the problem anyway... I only spent about 20 minutes speaking with the state inspector & I didn't have the time to ask him 101 other questions I have, but I will find out more from him next time I speak to him
my goal here is not to try & find a way to circumvent a legal obdII scan inspection, I want to pull off a swap that is legal enough to legitimately pass a state inspection at the obdII interface. my understanding of rules for an engine swap is the new engine must be of the same year as the vehicle or later, & must have all of the emissions components of the later engine in place & functioning & meet all of the requirements of the later engines requirements, at that point it is a legal legitimate swap. I don't want to have to compromise the inspection station in any way either & red flags while I have a set of twins on this thing can be trouble.
I need to find out if my 03 Vin can be entered in the 07 ecu, I've asked a few Nissan techs & have only gotten a few "I don't know but I'll try to find out for you" answers so far. I guess this may also be a question for the aftermarket ecu re flashers too maybe? if the state computer verifies a correct Vin, & then verifies that the readiness monitors required to be ready are ready, & that there is no check engine light for an emissions related issue & no stored codes for an emissions related problem then the vehicle legally & legitimately passes a state inspection with a green flag at the obdII scan level & were good to go. this must be achieved for this to be a successful swap to me. the vehicle will not fail if the abs doesn't work, or the stability control or the cruise control or even the airbags & the dash is lit up like a Christmas tree, the pass or fail with the state computer hookup is strictly emissions & check engine light Dependant.
from the FSM's there are like 16 different can bus system types, depending on the engine & the options the vehicle has, they are broken down by the options the vehicle has, & mine being a tech package awd vehicle should mesh well with the g35x ecu I have if it was a tech package ecu with Ikey too, which chances are it was. for example my body control module is not set up for a push button ignition, but it is still a proximity sensor Ikey system, & in the end the important part of that is that it will still be able to communicate with the newer ecu & still perform the key coding communication necessary to re-learn the keys, it should work & I would of course rather keep it if it does work, your words are reassuring, I would think it's possible to get something like this done & have all trouble codes solved & everything working 100% if everything communicates, which it should... what kind of codes would you get that can't be solved? maybe for a race car shooting it down enough to satisfy the ecu is not a priority, but I can't imagine a fault that couldn't be corrected really for a street swap
there has been much speculation on the fx forums about converting to a push button ign, swapping the bcm from a push button ign system like the g would be the ideal way to accomplish this, & may be a good enough reason alone to swap out the 07 bcm eventually if I ever get my hands on one with the harness pigtails, wish I had the one from this drive train & the keys even, but initially I will connect it with the existing 03 key & attempt to have it programmed with the 07 bcm. I've already installed a 07 ipm earlier & it communicated no problem & works fine, hopefully everything plays nice with each other
forced induction is the reason for the swap in the first place I want to increase to ~450 to the wheels, not looking to go crazy, but looking to go past the point I'd feel comfortable with on the stock DE motor, I'm looking for ~525 to the flywheel reliably. the hr motor is more than enough for my use, where I'd have to use a built DE instead, I feel more comfortable with a factory assembled low mileage motor than a rebuilt anything from some unknown, & a good reliable built substitute in the DE engine from a reputable builder is maybe triple the cost of this HR motor, & in the end I'd probably still trust the factory engine more tbh
I agree that this swap is probably not worth it in a 350z, I mean even if you had an 03, you could probably just sell it for 11k & get an 07 for like 19k, your not going to save a whole lot by performing this swap & considering that the investment of upgrading to the 07 will also result in a vehicle with a higher resale value it makes this even more of a no brainer, but the fx is different, the HR motor only became available in the 09's... the 09's are a whole different animal, & even if I did want to do the trade up the gap between what I have now & what I'd have to spend for the new one is much wider than the gap with a Z, were talking +25K more to update to the fx with the HR... compare that to my original plan of new HR engine & transmission, complete with FI making 500+ at ~ the 10k mark, can't do that with the dE at all, the HR is the budget bang for the buck way of doing this in my eyes...
I was considering ordering up the beginnings of the turbo components but I have since decided to just not let the turbo's distract me from the main goal right now & will have FI be stage 2 of this project, I'll consider options for the FI depending on how I get this in & running.
I really think it would be pretty simple to get this running on the DE ecu if I'm willing to loose the dual throttle bodies & the variable cam timing, & in the end this is still enough to be worth this swap considering my goals, but of course I'd much rather have it all with the HR ecu...
I agree that having a complete donor vehicle is the ideal way to have everything you need, but this is not always practical or possible & not necissarily manditory for this either. it's easy to just take everything as a whole & drop it into an old body & get it to work, one guy is doing one & even using the 350z dash & all from the donor car, but I think it can be grafted into an existing car that already has all systems in place too & may even be cleaner & easier than swapping out whole dash harnesses.
ok, Nissan's NATS system is designed in such a way that the BCM is paired to the Ikey for the vehicle's actual ign lock mechanism, the bcm controls the whole show as a wireless ign lock all by itself, but if Nissan just left it at that, then anyone would be able to swap out the BCM with a new key programmed to the new BCM & be able to drive the vehicle away, the NATS system simply expands on this by also requiring the BCM to transmit it's learned key code each time a start is attempted, & requires the code to also match the ecu stored code, that's it in a nutshell really. if the NATS was removed from the ECU then the electronic ignition lock would still function fine with just the BCM, but this would be a security vulnerability in that anyone would be able to start the vehicle with a new BCM/Ikey combo. of course if all Nissan's were set up this way it would be a huge vulnerability, but if just one vehicle happened to have the NATS removed from it's BCM who would even be the wiser? what are the chances someone is going to steal your car by breaking in & replacing the bcm with one that they brought with them & had a key programmed to it? especially since of course this would never work on any other Nissan/infiniti, I don't see that as a big problem if it had to be lost but I will keep it if possible of course which it should be.
the BCM itself does all of the transmitting & receiving with the key for confirmation to allow the electronic unlocking of the ignition, now granted the 03 system is very different from the 07, but in the end it shouldn't really matter, I mean the 03 BCM will still control the existing 03 ign lock equipment, & should still transmit the key code to the ECU through the can buss with the correct PID's, first time for programming & then each start same thing, allowing the ECU to send a start signal to the IPDM. if I had to swap out the 07 BCM then of course I would have to swap out the rest of the components that the 07 BCM uses for it's ign lock architecture, the button & maybe the later lock assy & also including of course a latter oval shaped key (another good reason for a BCM swap even if not necessary otherwise) but I really think the 03 should work the same & will send a key code to the ECU that it can in turn learn & work the same as it would otherwise & retain the NATS functionality.
the Nissan control system works in such a way that each individual system is primarily a stand alone control for the system at hand, be it the ABS or the BCM with the IPDM as the common module used by the others for the higher amperage switching & power distribution chores. of course these individual systems also rely on communication with any other module on the buss that it may need to communicate with through the can buss, both transmit & receive.
all of the systems that are in place & fully functional right now will still all be in place & have the same potential to continue to work as they do. they will still send the data over the buss that is addressed to the ECU as it always has & the new ECU should be able to recognize this data & send data out that the respective modules addressed to should be able to recognize & respond appropriately. the data sent over this buss is sent in packets called PID's. each PID is a specific bit of data & every PID initiates with an identifier that allows each module that it passes to know if this PID is addressed to itself or not. where potential problems would come in is if:
A, the new ECU receives a PID that is addressed to itself but it doesn't recognize the data(unknown result)
B,the new ECU sends out a PID that it needs a specific response for, but doesn't receive it(unknown result)
C,one of the existing 03 modules receives a PID addressed to it from the ECU but the module doesn't recognize the data(unknown result)
D,a situation that one of the sub systems needs a PID that would be generated by the original ECU but the new ECU doesn't send it.
chances of any of these situations happening may be Dependant on if the newer system happened to use something that the older systems are not aware of?. also probably somewhat Dependant on the can buss system type, which is basically a matter of the options packages on the vehicles being compatible with the options packages of the ecu. try to use a rwd non tech ecu in a tech awd vehicle then of course your going to have problems with stability control & many trouble codes with improper communications, it's not that the actual PID data is any different for any specific can buss types though, they are all speaking the same language really, it's a matter of recognizing & expecting what it is receiving & getting the expected results from the data it sends. the different can buss types identified are only for trouble shooting purposes so they can just go through a tree appropriate to the systems in the particular vehicle, so if there are 30 different can buss types then that means there are 30 different trouble shooting paths that can be gone down depending on the systems installed.
while there are potentials for communications problems, for the most part I bet that everything will play nicely & the main functionality of all systems should be able to be retained as long as the ecu is from a vehicle that had the same options. now to be able to program the 03 vin into the 07 ecu, that's the first hurdle that needs to be overcome. I'm thinking this shouldn't be so difficult, I'd be a little surprised if it can't be done...