Jump to content

Recommended Posts

Posted

Absolutely. Your complaint is quite common, we have spent hundreds of hours fine tuning the shifts to meet the needs of most people right off the bat. The AutoCal allows us to further tune to the specific vehicle.

 

 

Stop waiting and order! :)

 

 

Ryan

You guys suck.

 

Just placed my order

 

:)

Posted

AutoCal shipped today.

 

Do I need a windows pc to get the AutoCal going? Or is preprogrammed with a tune? I have a Macbook so I might need need to get Bootcamp going.

Posted

I wosh Blackbear had a contact method other than email......that's slot of money to have to correspond via email.....sent one weeks ago with no response.

  • Like 1
Posted

I agree great tune results but unfortunately the Autocal doesn't come with instruction on how to load the stock tune back if you need to go in for major service and FAQ's is no substitute for a live person. Email only communication is definitely a drawback.

  • Like 1
Posted

I agree great tune results but unfortunately the Autocal doesn't come with instruction on how to load the stock tune back if you need to go in for major service and FAQ's is no substitute for a live person. Email only communication is definitely a drawback.

 

its also a reason why the cost is lower. if you need phone or in person support maybe you should visit a local shop.

Posted

 

its also a reason why the cost is lower. if you need phone or in person support maybe you should visit a local shop.

 

Maybe you should refrain from giving me your advice when I didn't ask for it. The price isn't significantly lower to not warrant a phone. It's just a model they have adopted. There are plenty of mom and pop businesses that are brick and mortar waiting on customers everyday with a working telephone.

Posted

I agree with the cost....it's not that much cheaper...try out www.guerragroup.com Pat did the tune on my G8 and did a great job, emails instructions and was always available when I called. I consider myself to be average with the autocal stuff but things still come up when loading the tune that make it essential in my opinion to have someone to call and ask questions. I have heard great things about blackbear not trying to bash them just making a suggestion.

Posted

 

Maybe you should refrain from giving me your advice when I didn't ask for it. The price isn't significantly lower to not warrant a phone. It's just a model they have adopted. There are plenty of mom and pop businesses that are brick and mortar waiting on customers everyday with a working telephone.

Well don't be a dick about it. If you didn't want someones opinion then maybe you should of kept this to a private message. Black Bear is still a relatively small business operation and they likely do not have the man power to man a phone line. Controlling all communication through email is probably easier for the to handle. I've personally sent several pm's to Jennabear and always get a response. If you insists on having instant communication with your tuner go out and find a brick and mortar performance shop that will tune your truck for you. Just be ready to bay $200 every time you want to get strapped into the dyno to adjust your tune.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...