BCCFInd Mistakes, Wants, ETC

[1project2many]

Corrected 3/10/12
I figured I should keep a running list of issues that need attention.

BCC used in 1994. (Scroll down for more info) 
BCC= BDKR6887 Scan id= 6855 Part number= 16186703 
Release date= 09/04/92 Engine size= 5.7 Trans Type= Auto trans 
ECM/PCM: PCM #16168625 
Used in trucks:GMC 

Possibly used in:S10,2WD,1/2 TON S15,2WD,1/2 TON T10,4WD,1/2 TON 
T15,4WD,1/2 TON 

Options: 
With L05 5.7L GAS 8 CYL (5.7K) V8 TBI 
With MY2 MAN 5 SPD 
With NA5 FEDERAL REQUIREMENTS 
Without NM8 EMISSION SYSTEM, LEADED FUEL 
Without NN5 EMISSION CALIFORNIA OVERRIDE SYSTEM 

So if GM certified an S10 with 5.7 TBI and manual trans in 94, why are so many of us bothering with conversions??? :)

[EagleMark]

We also found an Astro Van with 5.7L and 4L60E! I want one!

ADSU says came in GMC and possibly Chevy blah blah like your example. But it was not a possibility, it was. Not sure if stuff as little as that is worth effort. Your just looking for mistakes and updates right?

Added features:
Now spitting out mask id would be cool. Spitting out ALDL file number would be cool. Spitting out xdf and adx would be cool. Spitting out the info, with all files would be cool but a lot of work when spitting out link to all would be just as cool and links with that info are already started. ECM Information forum.

Can you add an AutoTune feature?

[1project2many]

The "possibly used in" was because of the coding in the database. It makes more sense when it comes to the cars since a cal might be used in a Buick W body but not an Olds or Chevy. I may have found a way to make it more specific. Mask ID and ALDL data number can be done. Best to include link to ecm info page. Keeping up to date files in the database might become a nightmare.

I can add autotune but I'm not sure you'd like my taste in music!

[1project2many]

How about reverse searches? Anybody interested? And I should probably try to include later GM part nos for the ecm / pcm so it matches GM data. After using the TIS VIN based lookup I wonder if I can write in a VIN decoder that works off engine size, year, make, model.

Feature creep... another invasive species.

[EagleMark]

Mask ID and ALDL data number can be done. Best to include link to ecm info page. Keeping up to date files in the database might become a nightmare.

Link to ECM information page would be one more simple piecs of information. Since we update ECM information pages the info and files are there and only mods can update those pages.

How about reverse searches? Anybody interested? And I should probably try to include later GM part nos for the ecm / pcm so it matches GM data. After using the TIS VIN based lookup I wonder if I can write in a VIN decoder that works off engine size, year, make, model.

Feature creep... another invasive species.

to include later GM part nos for the ecm / pcm so it matches GM data. would be good. Reverse search what?

[1project2many]

Reverse search...

"Search for +L19" (454 TBI truck)
"Search for +MG5" 5 speed truck transmission
"Search for 7427" last four of PCM part number

"Search results: .... BMHJ, BMHK, BMHL"

[EagleMark]

That would be cool! ECM reverse search too? How hard to do?

CalData does that...

[1project2many]

the standalone version already does that. That's how I can do so many cool searches. 8)

[EagleMark]

Corrected 3/10/12

oops!

http://www.gearhead-efi.com/BCCFind/....shtml?BCC=cpk

[1project2many]

???
I thought everyone got in on the 7.8 powered Camaros?

[EagleMark]

It's on my list of must have vehicles along with an S10 and Astrovan with 5.7L 4L60e vehicles!

[1project2many]

Getting closer to implementing reverse searches. Current program prints out everything returned one screen at a time, same output as on BCCFind results page. With potential for lots and lots of output for a search (ex: search for all L98 calibrations) that's a very large page and it can get a little clumsy when looking for specific data within the cals. So I'm thinking of a short list of cals returned from a reverse search with clickable links for more detailed info for each cal. The short list might simply include the GM RPOs without any decoding. Any thoughts?

Also, current standalone version of program has option to get RPO data for every year cal in the database to aid in searching. Searches look like "L05 MT1 7427" which would search for everything with a 350, 4L80E, and 7427 pcm. Can add this functionality to webpage for reference. Because the database is set up to use RPO codes it's more work to change the search strings to plain English such as "5.7 manual transmission." I'd love to do that but I'm going to get the current form of the program online first. Would having the RPO codes a click away be useful?

[EagleMark]

If it can do reverse search by RPO code would a page of RPO codes help? Give the user acceptable search terms?

I may be able to build a form with say three boxs, one for engine, one for trans and one for ECM number to spit out acceptable search term?


What would be useful is if a search result came up, a link from the ECM number to our ECM information thread where bin could be found? This could get complicated when same number ECM used different mask ID...

[1project2many]

I'm asking if the RPO page would be helpful. All search terms are acceptable but some are guaranteed not to be successful.

I can build the query page ok. Not all searches are for engine/trans/ecm. You can search for GVW, or open loop cals, or Cali emissions. Anything you might want to know is open if GM included the info with the BCC.

Including the links and external data requires changing the database. I want to build a tool so it's much easier to add/edit data. And I need to look at the database format to see if it should be changed or modified now that I'm thinking about expanding it's purpose.

[PJG1173]

What would be useful is if a search result came up, a link from the ECM number to our ECM information thread where bin could be found? This could get complicated when same number ECM used different mask ID...

this could be accomplished if the bin files and wire diagrams were stored in the database and not a thread. you could then make a relation between the bin and the different ecm's that support them. this could also make searching for bin's faster and easier.