[Orb]

Originally Posted by shiv@vishnu

Why? There's nothing wrong with v2.0.1. Just a little overly conservative. Still considerably stronger than v1.

Ah... no one wants to deal with a single issue! The point of having a final code is one that is reasonably error free. Limp mode or shuttering is not acceptable for many of us so regardless what you say v2.01 is still beta in our eyes just not yours. You have been preaching that this release is going to well tested and of the highest possible quality. I know you will get there but what you have is not good enough for many of us as we don't want to have a single issue. Honestly, I though your own expectation would be higher.

The perception here is that you have not completed a final product. You lack of urgency on updating the code, or even properly communicating this is disrespectful to the customer base that has put faith in you to deliver a product of the highest quality.

You are here every day but you are not listening.

Orb

[zenmaster]

Originally Posted by shiv@vishnu

Why? There's nothing wrong with v2.0.1. Just a little overly conservative. Still considerably stronger than v1.

That's understood. I just want to do everything in one shot. At one point, I was all set to install the firmware, but that was "aborted" due to not knowing how to provide 12v to the orange wire (at that time). As I live in a condo that can't facilitate the install, it must be done at a friend's place. So, I'd rather not have to do that work twice. When v2.0.2 is available, I'll put that in, and install a bluetooth-to-RS232 setup that should make subsequent access much easier.

BTW, now that you're on switched power, I think you may want to provide a bluetooth kit, as an add-on.

[OpenFlash]

Originally Posted by zenmaster

That's understood. I just want to do everything in one shot. At one point, I was all set to install the firmware, but that was "aborted" due to not knowing how to provide 12v to the orange wire (at that time). As I live in a condo that can't facilitate the install, it must be done at a friend's place. So, I'd rather not have to do that work twice. When v2.0.2 is available, I'll put that in, and install a bluetooth-to-RS232 setup that should make subsequent access much easier.

BTW, now that you're on switched power, I think you may want to provide a bluetooth kit, as an add-on.

Got it And not a bad idea.

shiv

[stefano7171]

Originally Posted by shiv@vishnu

Got it And not a bad idea.

shiv

Well, good idea, but Eugen (e.n. 335) suggested it months ago....

[sambonator]

Originally Posted by Orb

Ah... no one wants to deal with a single issue! The point of having a final code is one that is reasonably error free. Limp mode or shuttering is not acceptable for many of us so regardless what you say v2.01 is still beta in our eyes just not yours. You have been preaching that this release is going to well tested and of the highest possible quality. I know you will get there but what you have is not good enough for many of us as we don't want to have a single issue. Honestly, I though your own expectation would be higher.

The perception here is that you have not completed a final product. You lack of urgency on updating the code, or even properly communicating this is disrespectful to the customer base that has put faith in you to deliver a product of the highest quality.

You are here every day but you are not listening.

Orb

... you must be on Shiv's ignore list. Has he responded to anything you've posted lately?

[e.n335]

Shiv,

Quite some people are reporting engine stutter or hiccups with map v2.0.1. I know that v2.0.2beta solves these issues.

Now, you say v2.0.2 final is finished. So please release it now with 91 octane user torque settings and provide the documentation for different user torque settings you announced later on.

You would make your customers really happy by solving their issues and reduce your support efforts.

Bluetooth: I have the complete solution, tested and working. If you plan to sell this as an add-on, I am more than willing to hand over everything to you.

- Eugen

[munters]

About the release, I fully agree... Writing and reading is boring installing is FUN

The bluetooth option is really cool. Made everything according Eugens description and it works great.

[Orb]

Originally Posted by sambonator

... you must be on Shiv's ignore list. Has he responded to anything you've posted lately?

I doubt it but you never know. I have never gone out my way to bash Shiv or be disrespectful. I just call it the way it is.

Shiv really has given no feed back on the issues with 2.01 so we have to assume it has problems as people have stated and just not ready for deployment. If he actually addressed the issue with a statement that identify any risk then I would be more inclined to install the Procede.

Orb

[lawdude]

Originally Posted by Orb

I doubt it but you never know. I have never gone out my way to bash Shiv or be disrespectful. I just call it the way it is.

Shiv really has given no feed back on the issues with 2.01 so we have to assume it has problems as people have stated and just not ready for deployment. If he actually addressed the issue with a statement that identify any risk then I would be more inclined to install the Procede.

Orb

If you're really interested in a PROcede why not go with v 1.47 lbt? That's supposed to be pretty stable.

[orientblue3]

Originally Posted by munters

About the release, I fully agree... Writing and reading is boring installing is FUN

The bluetooth option is really cool. Made everything according Eugens description and it works great.

Details?

[munters]

Here is the link to the Forum

http://www.vishnutuningforum.com/for...hread.php?t=40

[stefano7171]

Originally Posted by e.n335

Shiv,

Quite some people are reporting engine stutter or hiccups with map v2.0.1. I know that v2.0.2beta solves these issues.

Now, you say v2.0.2 final is finished. So please release it now with 91 octane user torque settings and provide the documentation for different user torque settings you announced later on.

You would make your customers really happy by solving their issues and reduce your support efforts.

Bluetooth: I have the complete solution, tested and working. If you plan to sell this as an add-on, I am more than willing to hand over everything to you.

- Eugen

If you need a Beta tester for your bluetooth solution I am available !

[Kbueno]

Originally Posted by Orb

Ah... no one wants to deal with a single issue! The point of having a final code is one that is reasonably error free. Limp mode or shuttering is not acceptable for many of us so regardless what you say v2.01 is still beta in our eyes just not yours. You have been preaching that this release is going to well tested and of the highest possible quality. I know you will get there but what you have is not good enough for many of us as we don't want to have a single issue. Honestly, I though your own expectation would be higher.

The perception here is that you have not completed a final product. You lack of urgency on updating the code, or even properly communicating this is disrespectful to the customer base that has put faith in you to deliver a product of the highest quality.

You are here every day but you are not listening.

Orb

Unfortunately, I somewhat agree with this, but it is too harsh. It's more of an inconvenience than something that is unacceptable. I agree that I do not want a single issue. And I do notice less power with my lowered torque settings, duh...but it's still better than 1.47. I'd rather have the beta 2.01 than not. WE just need to be patient as I'm sure the release is imminent.