Can anyone explain what this means, re CC ECU. Extract from web
"https://www.blackbox-solutions.com/shop/help/SM039.html"
Sorry Paul, I have always regarded you as a friend, and as such have not posted on this thread until now, but i have to disagree.The squeaky wheel approach works really well with BBS,
In consideration of the involvement and participation i have personally had on this board and the vast amount of effort that many members here will remember and appreciate that BBS has freely put into improving the nanocom in respect of hardware and software, freely adding Autobox and SRS for the Disco II and adding the option to cover the V8 Motronic ECU, debugging the bejesus out of it and even to the degree of asking for suggestions, all without raising the cost by a single Cent, i feel this comment that insinuates we need bullying and pressuring by any means to be entirely unwarranted and totally insulting to me and BBS.
I think you are being overly sensitive Colin, and are most definitely misreading "squeaky wheel" if you think that means I'm advocating bullying and pressuring. I'd hardly be recommending users who were interested in Cruise Control Module support send BBS support a nice email requesting a feature be added if that were the case, would I? Nor would I be writing posts like this one in the EDS Forum: http://www.aulro.com/afvb/showthread...29#post1817429
That said on some issues BBS support has a tendency to fall into a default "not our problem" mode. As an example the issues some users have had with Td5 map uploading falls into that category, and it took considerable effort to convince you that was something that needed to be looked at. I classify that as "requiring the squeaky wheel treatment" as that problem had to be repeatedly raised before it was even looked at.
cheers
Paul
Please refer to my post in the Electronic diagnostics forum:
I think Collins maybe referring to the lack of support for the Hella Cruise Control - https://blackbox-solutions.com/shop/help/SM039.html - which is supported on the Faultmate MSV-2. Given the price differential between an Evo with D2 V8 unlock with no VIN restrictions (€299/$375AU ex-vat) and a MSV-2 Extreme with full D2 V8 coverage (€549/$685AU ex-vat locked to a single VIN, €1014/$1265AU ex-vat with MultiVehicle licenses) it's not really surprising there are a few feature differences.The MSV-2 is BBS's high end diagnostic tool, and has evolved through a number of incarnations since the Rovacom. The EVO was a product that was taken over from another developer at the end of 2010, and essentially rescued from oblivion as the original developer was unable to cope with the demands of producing, selling, and supporting the device. Colin and BBS have undoubtably moved the Nanocom to a much higher level than it was at when they took over it's development.To be fair to Colin and BBS the Nanocom D2 coverage has never included support for the Hella Cruise Control, so basically what is being requested is that BBS add an additional module to the D2 V8 coverage.
Looking at it from a business perspective you can see Colin/BBS's quandary. The EVO in part cannibalises sales from the Faultmate MSV-2, so there is an understandable reticence to make the EVO identically featured to the MSV-2 D2 coverage. On the other hand the EVO allows BBS to compete at a similar price point to the Hawkeye so helps prevent loss of sales in that market segment. The juggling act is how do BBS balance features and pricing across it's product range. The MultiVehicle unlock for the MSV-2 Hella CC module is €47 (the Motronic V8 Module is €175) for example, so how do you price the same functionality when selling what is effectively the module for the EVO?
cheers
Paul
| Search AULRO.com ONLY! |
Search All the Web! |
|---|
|
|
|
Bookmarks