tuning open loop

kwick6

Donating Member
I am trying to understand this....

The open loop AFR correction vs. MAP and AFR correction vs. coolant temp
tables are only used in open-loop (no O2 sensor feedback). These 'corrections'
are used until the engine and O2 warm up enough to go closed loop.

Once in closed-loop, the desired afr is set to 14.7 (this is used in the bpw
calc).

If starting to tune in open-loop (no O2), then set the afr vs. map table to the
14.7 value. You can then look at the O2 sensor and make the gross adjustments
required. Once close, go to closed-loop (O2 feedback), set the blm min/max
to 128, and use the int to tune.

Open-loop tuning is only needed when you are starting with an engine that
is radically different from anything gm has produced. I've used it on
occasion in a couple of areas of the ve table.

To switch to open loop, I only need to change 0x034A to maximum temp correct?

Next... where is the AFR vs. MAP table that I need to set to 14.7?

And once set to 14.7 what will the 02 sensor do?
At idle I assume that it is going to do its normal sway from low to high (100mV to 900mV),

then while driving...this is where I want to see what mV the 02 is putting out. ? What should I be looking for(600s, 700s, 800s)?

The VE table is RPM and MAP, so how will I know by watching the 02, which areas of the VE need to be leaned out or fattened up.... just look at datamaster and follow the 02 readings, looking at RPM and MAP?

What I'm looking to find out is... Once in open loop, the 02 is going to be my guide, as in 900s during cruise is too fat, so lean those areas....and how lean? 600-700?


Ok, once I feel I'm close go back to closed loop and set the BLM min/max to 128 and go off the int. ? If that is true how is the BLM min/max set?

I found 0x0355 and 0x0356, but they looked like they were different values....such as 1.17 for MAX BLM, and .82 for MIN BLM on stock bin. I see that at the 1.17 and .82 are values, and the int looked closer to normal and were in units.... 80 min, 218 max.


TIA.
Scott
 

sytyguy

Moderated User
Correct....to go full time open loop, just set "Temp Thresh. For C/L Determination" (0x034A) out of range (151.6 degC max).

The map in question is probably 0x0561 - "Cold Engine Temp Dependent AF Ratio vs Coolant Temp vs MAP (N2MAPLD)"

The O2 mVs are going to follow whatever you have dialed in fuel-wise when in open loop. So, a rich cruise might have 800-900 mVs while a lean cruise might have 200-300 mVs. Idle will reflect this as well (solid 800s, 700s, etc...). The "switching back and forth" you see is when in closed loop and the ECM is trying to lean/richen the mixture to achieve stoich. Each truck is unique in what it wants. Dial in what's good for you. Best way is to use a WBO2 so that you know what you're seeing is indeed correct. For instance, my truck likes 850-870 O2 mVs @ WOT for best performance and 400-550 mVs at cruise for good economy (and no lean spots). A good starting point for WOT O2s is 920-930 and 650-750 for cruise. Tune from there.

Just use datamaster to guide you as to what cells to modify for certain fuel conditions (remember to set MAP to kPa in DM). Then make adjustments as necessary. For instance, cruising down the road....2000 rpm, 60 kpa, O2s in the mid 800s. You can afford to take some fuel out of F29 (0x0422) and/or F30 (0x04AD) in this situation. Use caution, however, as too much fuel removal will result in a noticeable flat spot at this point when you give it some gas. Best way to attack this.......use closed loop to dial in idle and cruise......make adjustments to get blm/int happy (again, whatever feels right for your truck - what's best is NOT always 14.7). Then go open loop on a bin and see what the O2s are, how the truck feels, etc....tune from there. Once, you get it all dialed in right for your truck, you'll see just how much control you have. It's really nice. When I used to cut my elec fans on @ idle with closed loops chips, it'd kill the truck. Open loop allows me to address that (as well as some other maps).

This is where the Ultimate really pays itself off. Burn 16 bins with varying fuel levels and toggle thru them. See which ones work best. No more one chip/one change crap. Just remember to label the PROMID (0x000) accordingly and you can see when you toggle to a new bin in DM.

BTW, if you have questions about the blm/int in closed loop, check out this page - http://www.gnttype.org/techarea/faq/BLMINT.html

Hope this all helps somewhat,

Michael
 

kwick6

Donating Member
First off, thanks for taking the time to help me understand these things.

Second, I hope this next round of questions doesn't get me killed here. YIKES.



sytyguy said:
Correct....to go full time open loop, just set "Temp Thresh. For C/L Determination" (0x034A) out of range (151.6 degC max).

The map in question is probably 0x0561 - "Cold Engine Temp Dependent AF Ratio vs Coolant Temp vs MAP (N2MAPLD)"


Would setting the entire table (F56 0x0561) to 14.7 be appropriate for idle and light cruise until I get it close?

Would this make starting a cold engine difficult? (usually want an engine to start really rich)?

Would table F57 also need to be changed to 14.7 to accomplish this?

The O2 mVs are going to follow whatever you have dialed in fuel-wise when in open loop.

While tuning VE, is the F30 table usually just left as is? When would it be necessary to change F30, as it would affect both F29, and F29E.


What would be a reasonable rate of changing the values in the VE table(s)?
say 35.9 is too lean, adding .5 be too much ? would .1 be too little ?


So, a rich cruise might have 800-900 mVs while a lean cruise might have 200-300 mVs. Idle will reflect this as well (solid 800s, 700s, etc...).
The "switching back and forth" you see is when in closed loop and the ECM is trying to lean/richen the mixture to achieve stoich. Each truck is unique in what it wants. Dial in what's good for you.


Will the DE and AE need to be dialed in?

I don't want to just switch to open loop and not be prepared about where all the changes should be made.

What if a DE or AE table is adding or taking away fuel, and I am trying to tweak the main VE tables, not realizing that these are contributing to the fueling as well, or something of that nature. Is that a potential problem?


Best way is to use a WBO2 so that you know what you're seeing is indeed correct. For instance, my truck likes 850-870 O2 mVs @ WOT for best performance and 400-550 mVs at cruise for good economy (and no lean spots).

What will designate a lean spot? Is it something I could see on datamaster?

A good starting point for WOT O2s is 920-930 and 650-750 for cruise. Tune from there.

Just use datamaster to guide you as to what cells to modify for certain fuel conditions (remember to set MAP to kPa in DM). Then make adjustments as necessary. For instance, cruising down the road....2000 rpm, 60 kpa, O2s in the mid 800s. You can afford to take some fuel out of F29 (0x0422) and/or F30 (0x04AD) in this situation. Use caution, however, as too much fuel removal will result in a noticeable flat spot at this point when you give it some gas. Best way to attack this.......use closed loop to dial in idle and cruise......make adjustments to get blm/int happy (again, whatever feels right for your truck - what's best is NOT always 14.7). Then go closed loop on a bin and see what the O2s are, how the truck feels, etc....tune from there.

Can you look at the bold portion above.... Did you mean use closed loop to dial in idle , cruise.............................then go open loop on a bin and see what the 02's are. ?

I assume so, just want to make certain.

So instead of the method I originally posted about switching to open loop to adjust idle, cruise... it would be better to use closed loop and look at what the BLM, int are doing. ?

I was thinking that doing the idle open loop, would make things easier if the BLM were way off, it just seemed that doing open loop would be easier because you only need to watch the 02 mV's.


Once, you get it all dialed in right for your truck, you'll see just how much control you have. It's really nice. When I used to cut my elec fans on @ idle with closed loops chips, it'd kill the truck. Open loop allows me to address that (as well as some other maps).

This is where the Ultimate really pays itself off. Burn 16 bins with varying fuel levels and toggle thru them. See which ones work best. No more one chip/one change crap. Just remember to label the PROMID (0x000) accordingly and you can see when you toggle to a new bin in DM.

BTW, if you have questions about the blm/int in closed loop, check out this page - http://www.gnttype.org/techarea/faq/BLMINT.html

Hope this all helps somewhat,

Michael


Yes this is very helpful. Not an easy thing to grasp quickly, as you can see. :-?

Yes I ask alot of questions, and I try to learn quickly. Don't worry I don't rush things when it could cost me an engine, and the reason I ask all these questions, is because I don't want to buy a new one. :wink:


This is where the Ultimate really pays itself off. Burn 16 bins with varying fuel levels and toggle thru them. See which ones work best. No more one chip/one change crap. Just remember to label the PROMID (0x000) accordingly and you can see when you toggle to a new bin in DM.

I plan on getting a socket that will carry the 29C040(think thats it) , and I'll copy the same program throughout it with slight changes to each one, then toggle through them and see which is getting closer to what I need.

Sorry for all the newbie questions. Once I get started on something I really tend to try and get the questions out there to cover all the bases. :eek:

I appreciate the time anyone takes on helping with the questions I posted as it might be a bit much for one person to answer. I try not to get to carried away, but as the questions come to mind, I need to ask them.


TIA,
Scott
 

sytyguy

Moderated User
Thanks for catching that, should have read "...then go open loop on a bin...". Corrected now.

F57 only needs to be changed if you want to modify the cold engine idle AFR. Works like this....if temp is below 0x0361 = 56 degC (132.8 degF) and the TPS is at 0% (idle) then F57 is used to calibrate an AFR dependent on coolant temp. If you move the TPS from idle during this condition (cold engine), then F57 is ignored and an AFR is calibrated from F56 based off of coolant temp and map. If temp rises about 0x0361, then the ECM will begin using the AFR at 0x0392 for stoich. Most Ultimate chips have C/L determination set around this point as well, so that the blm/int will be used at about the time the engine goes into warm engine AFR enable (although stock is 21.5 degC - 70.7 degF for C/L determination).

* All of this is covered in Section 9.1.4.3 in "The Document". Read up on it and it should answer most of your questions.

As far as tuning VE (AE & DE will still need to be tuned separately), since F30 does affect all (even though only a small portion of F29E is used that F30 affects), I like to do most of my cruise/idle VE modifying in F29 & F29E. You will use a lot of other tables for dialing in the whole fueling curve, but those 2 can get most of your idle/cruise dialed in. Funny you should ask this as I just got through doing some VE tuning on our '95 Silverado. Here's my example:......Condition - steady state cruise, rpm @ 1600, map at 60 kPa, BLM hovering around 117-118. The truck was getting poor gas mileage, so I really only wanted to modify this one area of the VE table (WOT & idle were fine). Open editor and see that VE in that cell is 84 (NA Silverado remember). Drop it 80, reburn it, and go for a drive. Fueling is better, but BLM is still low (121-122). Reopen editor, drop VE to 76, reburn, and go back out. Fueling is good now, BLM around 128 with a tendency for lean. Right where I wanted it. This might be a bit drastic of a change for your condition, but .5 changes are gonna take forever to get a noticeable improvement if it's off a good bit. Use changes of 2 or 3 to get it close then fine tune it. Best advice is to use as much clarity as possible (meaning stay out of conditions where EGR, AE, DE, etc... may be active). For cruise your rpm is usually gonna be between 1600 & 2200 and map between 50 kPa & 80 kPa. Put emphasis on those areas to modify cruise. (Idle rpm is usu around 700-900 with map around 40-50 kPa). Now, that was cruise/idle. To dial in WOT fueling there are a lot of factors to keep in mind. (AE, PE, etc...). This is gonna be a balance of a number of tables (F30, F29, F77, F61, & F31M). Each has it's own place, so use it accordingly. My advice, start rich and tune down. Don't wanna go lean @ 22 psi and 5000 rpms. WOT fueling has been covered by a lot of us in the past. Do a search and you should dig up some good info on what does what.

Lean spots can occur when you remove fuel in one spot and don't "smooth" out the table around it. For instance, the example above. I went from 84 to 76 in one cell in the VE Open table. This got the result I was looking for, but if I had just left it like that, I'd have had problems. Accelerating slightly out of that spot would have made a jump from 76 to 88 to the next cell. Pretty big jump for no real rpm/map change. There would have been a little bog and would have been noticeable when driving and in DM (int/blm around 128 and suddenly back to 117-118). I, in turn, smoothed out the rest of the table to "flow". This way you get a smooth transition from cell to cell. No big jumps or drops. You want to take this same mentality when editing the Main Spark Table.

To dial all of this in, I suggested it was best to use the blm/int as your friend and get close in C/L. Use whatever is easiest for you, but instead of just looking at the stock O2 readings while trying to drive and keep track of what was rich/lean, use C/L. Go for a run, record with DM, and come back and use the histogram to help you see where it was lean, where it was rich. Neither substitutes for a WBO2, but the blm/int will spot trends in rich/lean conditions, versus you trying to see what the O2 itself is doing (which isn't very accurate). Once you have it close, switch to O/L and tune for your truck from there. Your's may want a richer idle or cruise. You can address that in O/L. Like I said 14.7 isn't always best.

Once you get going with it and have all the tools at you disposal, it's really quite easy to get it dialed in. Now, if this emulator takes off then it will be SO much easier.

Again, HTHs and reply if you have anymore questions.

Michael
 

kwick6

Donating Member
sytyguy said:
Thanks for catching that, should have read "...then go open loop on a bin...". Corrected now.

F57 only needs to be changed if you want to modify the cold engine idle AFR. Works like this....if temp is below 0x0361 = 56 degC (132.8 degF) and the TPS is at 0% (idle) then F57 is used to calibrate an AFR dependent on coolant temp. If you move the TPS from idle during this condition (cold engine), then F57 is ignored and an AFR is calibrated from F56 based off of coolant temp and map. If temp rises about 0x0361, then the ECM will begin using the AFR at 0x0392 for stoich. Most Ultimate chips have C/L determination set around this point as well, so that the blm/int will be used at about the time the engine goes into warm engine AFR enable (although stock is 21.5 degC - 70.7 degF for C/L determination).

Is table F56 and F57 open loop? I thought that since these tables have AFR's , they are using feedback from the 02 to acheive the AFR, therefore closed loop.

I'm confused about how the F56 and F57 tables in open loop can develop the AFR's they show. For example at 20*C and 60Kpa it is set to 13.0... and you want to fatten it up at that point. Do you add fuel to the corresponding point on the VE table or would you change the AFR from 13.0 to say 12.5?

* All of this is covered in Section 9.1.4.3 in "The Document". Read up on it and it should answer most of your questions.

As far as tuning VE (AE & DE will still need to be tuned separately), since F30 does affect all (even though only a small portion of F29E is used that F30 affects), I like to do most of my cruise/idle VE modifying in F29 & F29E. You will use a lot of other tables for dialing in the whole fueling curve, but those 2 can get most of your idle/cruise dialed in. Funny you should ask this as I just got through doing some VE tuning on our '95 Silverado. Here's my example:......Condition - steady state cruise, rpm @ 1600, map at 60 kPa, BLM hovering around 117-118. The truck was getting poor gas mileage, so I really only wanted to modify this one area of the VE table (WOT & idle were fine). Open editor and see that VE in that cell is 84 (NA Silverado remember). Drop it 80, reburn it, and go for a drive. Fueling is better, but BLM is still low (121-122). Reopen editor, drop VE to 76, reburn, and go back out. Fueling is good now, BLM around 128 with a tendency for lean.

Thats a great example. However since BLM won't change very quickly, how can you pinpoint the exact block of the VE that needs to be modified to remedy the problem.

Did you just change the value at 1600rpm and 60kpa, and it was the correct place that was causing the BLM number to be low? I know this is kinda hard to explain and I'll just have to try it, but I'm wondering if..... as soon as you see the BLM change from the desired 128, could the problem have been back a little further where the integrator had been trying to correct for it but it wasn't enough causing the BLM to change? I would think that the integrator would be a sooner sign of a condition that if addressed would avoid the BLM having to change.

Right where I wanted it. This might be a bit drastic of a change for your condition, but .5 changes are gonna take forever to get a noticeable improvement if it's off a good bit. Use changes of 2 or 3 to get it close then fine tune it.

That is what I wanted to know. Didn't want to be making changes so small that it wouldn't make much of a difference.

Best advice is to use as much clarity as possible (meaning stay out of conditions where EGR, AE, DE, etc... may be active). For cruise your rpm is usually gonna be between 1600 & 2200 and map between 50 kPa & 80 kPa. Put emphasis on those areas to modify cruise. (Idle rpm is usu around 700-900 with map around 40-50 kPa).

EGR is disabled so that shouldn't be an issue. AE, and DE are conditions in which a large change of TPS or MAP is present, correct? Like your driving along and your TPS is 20%, and you increase it to like 70% in one quick motion? Or your driving and TPS is 70% and you pull your foot off the pedal and it goes to 0%. Are these areas that require drastic changes such as those mentioned, as well as MAP, to enable those tables to become a factor of increasing fuel , or taking fuel away.


Now, that was cruise/idle. To dial in WOT fueling there are a lot of factors to keep in mind. (AE, PE, etc...). This is gonna be a balance of a number of tables (F30, F29, F77, F61, & F31M). Each has it's own place, so use it accordingly. My advice, start rich and tune down. Don't wanna go lean @ 22 psi and 5000 rpms. WOT fueling has been covered by a lot of us in the past. Do a search and you should dig up some good info on what does what.

I'll be doing a lot of searching, reading, etc. before I do much WOT tuning.

Lean spots can occur when you remove fuel in one spot and don't "smooth" out the table around it. For instance, the example above. I went from 84 to 76 in one cell in the VE Open table. This got the result I was looking for, but if I had just left it like that, I'd have had problems. Accelerating slightly out of that spot would have made a jump from 76 to 88 to the next cell. Pretty big jump for no real rpm/map change. There would have been a little bog and would have been noticeable when driving and in DM (int/blm around 128 and suddenly back to 117-118). I, in turn, smoothed out the rest of the table to "flow". This way you get a smooth transition from cell to cell. No big jumps or drops. You want to take this same mentality when editing the Main Spark Table.

That makes sense. But while your trying to pinpoint the area that needs the changing, I suppose you can come back and smooth it out after the area is identified. How big is a cell? Just for the sake of explaining it, say the table is made up of blocks, each having a value, are cells a group of blocks and how big, or how are they laid out?

To dial all of this in, I suggested it was best to use the blm/int as your friend and get close in C/L. Use whatever is easiest for you, but instead of just looking at the stock O2 readings while trying to drive and keep track of what was rich/lean, use C/L. Go for a run, record with DM, and come back and use the histogram to help you see where it was lean, where it was rich. Neither substitutes for a WBO2, but the blm/int will spot trends in rich/lean conditions, versus you trying to see what the O2 itself is doing (which isn't very accurate). Once you have it close, switch to O/L and tune for your truck from there. Your's may want a richer idle or cruise. You can address that in O/L. Like I said 14.7 isn't always best.

As far as 02 readings... I was thinking of just graphing them on datamaster, watching mV's. The blm/int idea sounds better for looking at the big picture though, as you said, trends when the truck may be starting to run too lean/too rich.

I am positive 14.7 isn't always best. I've heard the 02 sensor may be a bit more accurate at 14.7, and emissions are usually best, but I can tell changes to the AFR will result in much better performance.

Once you get going with it and have all the tools at you disposal, it's really quite easy to get it dialed in. Now, if this emulator takes off then it will be SO much easier.

Again, HTHs and reply if you have anymore questions.

Michael

I'm anxious to get started. There is nothing like having your own calibration suited to your mods. 8)

thanks agian,

Scott

just a side note... it took me awhile to read/think/type a reply. During that time, the BB logged me out. When I hit preview it asked me to login. OH SHIT. I immediately hit back and copied what I wrote, then logged in and everything that took me a long time to write was gone. That would have been a bad thing if I would have had to start all over.
:microwav:
 

kwick6

Donating Member
Is table F56 and F57 open loop? I thought that since these tables have AFR's , they are using feedback from the 02 to acheive the AFR, therefore closed loop.

After giving this some more thought, I think I get whats going on. :D



Since the ecm uses the AFR at 0392 for stoich, if the temp is never reached(staying in open loop), then the ecm will use the values in F56/57 for stoic, which would be all over the place based on rpm/map/coolant temp. The fueling would be all messed up IMO, since our 02 sensor doesn't work with real AFR's.

The way to add/remove fuel is at the VE tables., and now I can see your point about tuning closed loop...

To dial all of this in, I suggested it was best to use the blm/int as your friend and get close in C/L. Use whatever is easiest for you, but instead of just looking at the stock O2 readings while trying to drive and keep track of what was rich/lean, use C/L. Go for a run, record with DM, and come back and use the histogram to help you see where it was lean, where it was rich. Neither substitutes for a WBO2, but the blm/int will spot trends in rich/lean conditions, versus you trying to see what the O2 itself is doing (which isn't very accurate). Once you have it close, switch to O/L and tune for your truck from there. Your's may want a richer idle or cruise. You can address that in O/L. Like I said 14.7 isn't always best.



Scott
 

myclone

Donating Member
Just wanted to say GREAT POST!! Definately printing this out and puting in my ever growing "chip burning for dummies" binder. :wink:
 

sytyguy

Moderated User
Sorry for the delayed reply (hectic holidays). I'll touch on a few points that might clear things up some for you.

Thats a great example. However since BLM won't change very quickly, how can you pinpoint the exact block of the VE that needs to be modified to remedy the problem.

My example was of a '95 Silverado. If you've ever scanned a late model P4 ECM you'll notice that the BLM is much more active. That enabled me to see just how bad the problem was, not just that it was bad. I knew I had to get things back to 128 across the board, so I did some runs that helped me narrow down what area needed work. Here's how:

Get up to operating temp and go for a drive. Don't use cruise while doing this test as it will fluctuate TPS and can alter what you see on DM. Watch DM and see when you get to 50 kPa. See what the rpm is at and what the fueling looks like while cruising at this condition for about 10-15 seconds. Now bring it up to 60 kPa and repeat....70kPa....80kPa....etc....finish. Now go back and open up your editor and F29. Open DM and that run as well. Modify the VE table to cure those conditions. You get the point.

Did you just change the value at 1600rpm and 60kpa, and it was the correct place that was causing the BLM number to be low? I know this is kinda hard to explain and I'll just have to try it, but I'm wondering if..... as soon as you see the BLM change from the desired 128, could the problem have been back a little further where the integrator had been trying to correct for it but it wasn't enough causing the BLM to change? I would think that the integrator would be a sooner sign of a condition that if addressed would avoid the BLM having to change.

You may notice that the fueling might be off in the 60/1600 cell and closer in the 70/1600 cell and dead on in the 80/1600 cell. Does that mean that the VE value in 80/1600 is what you need to insert in 60/1600? No, of course not. Obviously the throttle is open less and will require a lower VE, but you need to just plug in values until you get close. You will begin to spot trends in the table and will soon be able to just "know" what will get you close. Obviously, if you have a major issue at 60/1600, then things aren't going to be perfect at 70/1600. That's why I say to do a series of tests. See what the fueling looks like at 70/1600 on DM and make changes accordingly. So, now that you have that one particular area cured, you will want to smooth things out like I mentioned before. Just look for any big drops or rises in values throughout the table. OEM tables are littered with spots that are like this (maybe not so much in our application, but some others are horrible). Albeit, this isn't something you must do. I just hate to go in and change one spot drastically and leave it without seeing if it "flows" into the next group of cells. Otherwise, you could eventually wind up with a truck that acts sort of jerky when slightly accelerating.

AE, and DE are conditions in which a large change of TPS or MAP is present, correct? Like your driving along and your TPS is 20%, and you increase it to like 70% in one quick motion? Or your driving and TPS is 70% and you pull your foot off the pedal and it goes to 0%. Are these areas that require drastic changes such as those mentioned, as well as MAP, to enable those tables to become a factor of increasing fuel, or taking fuel away.

Correct. Whenever you meet the criteria for AE or DE enable, a new set of tables begins to be used. That's a whole other topic, so read the document and see what tables are used, what criteria needs to be met, etc....but you are correct in your examples. They won't require anymore drastic of a change than any other map under similar conditions. Remember that larger injectors, a big cam, etc....can all cause DE/AE (and every other thing for that matter) to require more attention. For instance, BG had to take some fuel out of DE when dialing in the 50# cal to get it close. You may encounter similar instances.

How big is a cell? Just for the sake of explaining it, say the table is made up of blocks, each having a value, are cells a group of blocks and how big, or how are they laid out?

When I say "cell", I'm referring to one block of info in a table (i.e. 60/1600). Tables are scaled based on what the modify, what they use as variables, etc.... For instance, F29 is a relatively large table, utilizing an rpm scale (800-4000 in 400 rpm increments) and a map scale (20-100 in 10 kPa increments) to make up the 81 cell table. On the other hand, F30 is a smaller table, ultilizing only an rpm scale to make up the 17 cell table. So, you could plot F29 in a 3D style graph (like Tunercat does) and F30 could only be plotted in 2D (line graph style).

Sounds like you're getting a grasp on it. Do some reading and some testing and let us know how it goes. Feedback (as well as questions) are always welcome.

Michael
 

kwick6

Donating Member
Michael ,

Thank you for being so helpful, I am learning a great deal of very useful information, that I am anxious to use. I can't wait to get going. pocket programmer is on the way, as well as a socket that uses a 29F040, found here

I have a bin that I will start out with, so I need to get a hex editor and need to learn how to stack binaries. So that I can go through and test 16 at a time.

Something about starting at 0x0000-0x3FFF, then the next one would be 0x4000-0x7FFF, etc.

I'll go download a hex editor and see if I can make sense of this.

I think I'll be able to make more sense of it once I get the pocket prog.
and see how to do it first hand.

absolutely no problem with the delay of your response, jeez, I'm glad that you are contributing here, and I'm sure that I'm not the only one that is benefitting from it. :D


later,
Scott
 
Top