I thought I knew what I was doing but apparently not. I ordered a nvsram assy from moates with super aujp burned on it. After installing the nvsram I downloaded the eprom in using the GUI and was comparing all the values to my last eprom burn. I changed the values (in tunerpro) to what I had in my last burn. All was going fine until I got to the extended spark table. The downloaded bin contained 0s while my last burn had values. So I copied my values into the downloaded bin. But then I got to thinking maybe that table hasn't been defined in the downloaded bin. Is there a specific Super AUJP bin to use with the nvsram module? I think my burned bin is based off of saujp version 2. Also by clicking the download eprom button that is downloading from the EEprom on the nvsram correct? When I selected download bin It downloaded a file but all the values were 0. I am having some ALDL cable issues because I cannot get tunerpro to connect since installing the nvsram nor can I upload bins. I've read over all the threads I can find on the nvsram but I guess not everything has sunk in yet.

 

OK, ignore what I wrote above. I decided to try the s_aujp V4. I changed all the necessary values to work with my setup. Here's my problem. I can download the Eprom using the GUI. Which I assume is just downloading the contents of the Eeprom on the NVsram module. Download bin tries to do something but whenever I open the bin most all table entries are 0s. Also after closing the NVsram GUI and opening Tunerpro RT I can't connect to data log. So I disconnected the NVsram module and plug my memcal with my burned prom back in and Tunerpro instantly connects. I checked over the 3 wires to solder and everything looks good. I checked for continuity between where the wires were solder on the ECM board and to a trace on the PCB for the NVsram everything was fine. I'm stumped unless I am missing something? Any help is appreciated.

 

The nvsram module should have come with the software and Binary. I don't know if the originator or someone else has modified the SAUJP to be used with the module. The binary needs to custom modified to be used with the nvsram module.

the binary and module work as a system, so you have to make sure you have both pieces.

 

https://www.thirdgen.org/forums/diy-...-released.html

JP already did the bin for you but it is untested though, and I haven't tried it either.

 

Yes, I did find JP's thread last night. I also found the specific V4 bin to be used with the nvsram module. I have modified the 41024NV1.BIN file for my settings on the cyl vol, injectors, spark, and VE table values. But my problem at this point is that I cannot upload that bin to the nvsram. Now I am able to download the eprom. I also cannot connect to the ECM for a datalog. But if I unplug the nvsram and put in just the memcal with my prom I can connect to the ECM just fine.

 

The bin I prepared does work. I tested it several times before posting it up so you should be able to load that bin via MonteCarSlow's GUI initially.
Then load it up in TP to make your edits, then use the GUI to do updates.
The Module bin has different communication setup for mode 4 to allow the data transfers to be done. If you loaded the "Std" SAUJP to the "Chip" on the module (The backup starting program) then the communications may not work after the first update.
Take a step back, make sure you have what you think you have and give it another shot.

 

The Module bin has different communication setup for mode 4 to allow the data transfers to be done. If you loaded the "Std" SAUJP to the "Chip" on the module (The backup starting program) then the communications may not work after the first update.

This makes sense but I didn't put the S_aujp on the flash chip (on the nvsram). Moates had a blurb on the order form that you could specify a bin to be burned on the flash chip. So I assumed that the bin he was using would be compatible with the nvsram. I'll have to shoot an e-mail to confirm.

 

You don't need to bother.
Just take the chip out and burn the correct bin (your modified NVSRAM bin) to the chip.
Then upload the same bin to the module using the GUI.
Should be good to go if that was the problem.

 

I wish it was that simple. I bought the nvsram module because I have an old pocket programmer. Which doesn't work with XP on the free laptop I got. The whole point of buying the nvsram was because I can't easily burn eproms anymore.

 

OK, I got bought a new prom and have the proper bin for the NVsram. I installed it and using the GUI I downloaded the bin and eprom. The bin file had values of 0 for everything again. The eprom was the calibration I sent to be burned on the flash prom. I then made some changes to the downloaded eprom file and used the upload and it seemed to work. It was all going well until I went to connect. My laptop still will not connect to the ECM with the NVsram installed. So again I disconnected it and used my old prom and had no problems connecting. Also I was able to get my pocket programmer I to work with Windows XP. So I can burn proms again. Although I only have 2 eproms right now. The car is running rich see my other thread. Is there some way documented way to troubleshooting not being able to connect to the ECM with the NVsram installed? Thanks

 

Use the bin that was supplied with it NOT the new S_AUJP V4 for the module.
I over did the size of the additions and have not ironed it out yet.
It wasn't the issue you have but thought I let you know in case you missed the other thread about it.
Seems that I put some additional tables outside the bounds of the module update range.
If you changed anything above the top boundary the checksum would not confirm the program and cause an SES.
The original bin for the module does not have any issues and should connect normally.
for those waiting, I'm hoping to confirm the fixes on the new one shortly.

 

Can I replace the flash chip (C2 SST 27SF512) on the nvsram with one of my standard eproms (27C256)? I haven't tried to start the engine using the nvsram because the laptop won't connect to datalog. Until I get that figured out I am stuck burning eproms.

Also does the ecm use the eprom on the memcal for anything with the nvsram installed?

Using the GUI what is the difference between download bin and download eprom?

When I download from the bin and open that file in Tuner Pro all the values have zeros. So it seems like I am not able to access the actual nvsram. How does the nvsram get the eprom information? Does it only have a calibration once you upload a bin file? Otherwise it will run off of the eprom on the nvsram board?

Sorry for the 20 questions but I am trying to get this car on the road so I can drive it now that the weather is finally warming up.

 

OK, let's see......

yes, you can replace the flash chip with any 28 pin rom/eprom/flash chip.

the prom on the memcal is not connected when plugged into the nvsram board.

The special bin in the prom for the nvsram board tells the processor to pull the calibration data from the prom into the nvsram on power up. if that fails a checksum, it will revert to the calibration in the prom only.

 

Thank you for answering that.

 

To elaborate on what JP described: If the checksum fails on boot up, the calibration data in the prom will be copied into the nvram module. This keeps you from being stranded on the side of the road incase your upload fails and corrupts the nvram. You simply turn the ignition key off - count to 10 - and turn the key back on.

 

When you download the bin, you are getting a bin file that is a merge of the calibration data in the nvram module and the code portion of the eprom. You edit this bin file with TunerPro/CATS/etc and re-upload your changes.

When you download the eprom, you are getting a bin file that is a 100% copy of whatever is in your eprom only. This is more of a debug aid, and can actually be used to pull the prom from any $8D TPI car without opening the ECM to get to the memcal. Consider it a hidden feature from GM.

That is unexpected. Insert an eprom with the special nvram bin into the eprom socket on the nvram module (the eprom in your memcal is not wired up to the ECM cpu when the memcal is plugged into the nvram module). The first time you do this, the code in the eprom will recognize the empty nvram module and fill it with cal data from the eprom. From then on forward, you should be able to download bins and edit them. If you still see 0's... then you've got a problem-o.

 

the eprom in your memcal is not wired up

Maybe that's my problem. I've been doing this with the memcal plugged into the nvsram board and an eprom on the memcal. So I should remove the eprom from the memcal?

When does the nvsram get populated with the data from the eprom? I haven't started the engine yet with the nvsram attached because TunerPro doesn't connect with the nvsram plugged in.

Thanks for the help/info

 

If your eprom is in your memcal, and the memcal is plugged into the nvram board (and assuming the socket on your nvram board is empty) then you have the situation where your ECM is doing nothing. Remove the eprom from your memcal and place it into the socket on the nvram board. The moment you power up the ECM with the eprom in the right socket, the nvram will get populated with a known good set of values (and TunerPro will connect).

My assumption with the above comments are that your eprom contains a copy of the AUJP or AXXC bins that I released for use with the nvram module.

Also ... double check the VATS bit. I can't remember if I disabled it or not in the bins that I released. In your case, you'll want it disabled.

 

Actually what I had was the regular prom I burned installed on the memcal. The memcal plugged into the nvsram. The nvsram has a flash chip burned by moates that I supplied but that was based off of S_aujp V4 for the nvsram. Of course JP posted earlier that the file wasn't 100%. So I am going to burn the AUJP you originally posted and burn that to one of my proms. I'll let you know how that goes.

 

OK guys,
I have relocated the problem areas and all seems good now.
There is a new version of the S_AUJP V4 posted on Moates site under Custom Binaries".
S_AUJP V4 1026.zip

The new version is mainly to correct the bin for use with the NVSRAM module.
This version has items changed so be careful when copying your current calibration info over. The extended table will need to be manually entered if you used it.
Read the doc for instructions Please.
Items at locations >L8993 will need to be manually re-entered because of relocation.

The XDF has been changed so that the NVSRAM version can use the same XDF as the std version.
XDF has suffix of "a" on it.

You can tell the new bin versions by looking at the Sequence # L8004
= 4A is the standard version for use in 730
= 4B is the NVSRAM version

I did add one feature to this version (V4 1026) that is not in the old one (V4 1024).
For myself and others who use a switcher, You can now have your program number at location L800A (Custom ID 1) for a zero to 15 display.
The ALDL can display this in the "Engine/Vehicle Speed Ratio" item (nobody uses that anyway) at item # 16.
Changes
The revised documentation has instructions how to set that up.

I've wanted to do that for some time now because its hard to mark logs at points where programs were changed. This will help identify what program was running at the time. Guys without switchers can still use this to identify versions if desired.

The Launch mode code still does not work. No ill effects, just doesn't do what I expected. Future version hopefully will have that corrected.
I've been running the bin for a couple weeks now and havn't seen any problems.
Please report any good bad or ugly.
Jp

 

I am having the same problem.
Can not data log, and Tuner Pro will not see the ALDL.
I also had Moates burn the chip, with VATS and the car would not run.

Thanks for all the help with this,
Dave

 

Ok, I'll bump this up to the top so I can read it in the am.

Lots of good info I hope helps me get my setup working correctly

-jason

 

Hi Guys,

Since this got bumped up, just an update-
The temp air cleaner was collapsing and the engine was not getting enough air flow.
Now with the basic 40126B with a few adjustments the car burns rubber through 2nd even though it is currently a single legger.
Needs tuning, but the potential is there.
Outstanding setup NVSRAM, simple and reasonably priced.

Thanks,
Dave

 

I think the NVSRAM is the best way to go if you use the 730 ECM and want on-the-fly tuning. I wonder if any of the freeware and buyware tools will adopt the communication protocol.

 

Well this thread certainly helped me sort out my issues with the setup. Once I uploaded the lastest version to the chip, it fired right up and I was able to up and download without any problems

Now I just need to learn what all the new stuff I can change does! LOL Way over my head, but I'll get there. Gotta love the search feature, which has gotten me a long ways!

-jason

 

I want to keep posting this until its corrected in a later version.
The Extended VE table address is not correct in the 1026 XDF provided.

Select the item, Highlight the item.
Press ""F2"
Change the address box to "09A0"
Save.

Table will now look correct

Also I want to tell people that don't know or never use it...
If you use the "F7" key to display the Summary List in TP.
The individual addresses of all the bin locations are shown.
Helps keep everyone discussing the same item even though the name may be different between different definition files and programs.


That would be good.
The source is there and looks easy enough to figure out (If I could understand C a bit better )

 

Good tips, I'll check it out later and see if I can fix the Extended spark table.... I've never used it honestly. I mean, I am still running TPI, so why bother?!?!?! LOL

-jason

 

Extended VE was the issue, Spark was ok.

You really don't need to go to the extended tables until you have a good handle on the stock tables.
Will just be more numbers to deal with while "roughing" it in.

 

ahhhhh, thanks for catching that

reading comprehension is good

and I'll leave it zero'd out, but try to fix the address issue so it displays correctly once I get to that point

-jason

 

Alright, I fixed the address... *YAY*

thanks

-jason