Thread: IID Tool vs Faultmate MSV-2 for D4

So what you are saying is the Nanocom will be upgraded to have the same functionality as the MSV-2 for the D4? If so, when is the expected release date, and what's the advantage of the MSV-2, when the Nanocom would appear to have a better screen than the MSV-2? Sorry if the questions are dumb, but there isn't a whole lot on your website that tells me why one is better than the other.

Hiya phl

I really cannot add any more to what i have already stated.

we have started developing coverage for all CAN BUS based vehicles on our incredibly successful and low cost Nanocom hardware with it's full color touch screen, that will also provide full CCF edit and hopefully also full flashing capability,

And i would suggest that you draw no further assumption or conclusion to this statement.

I can however tell you that as long as BBS is in business, we intend to ensure that absolutely nothing we or any other company provides will ever match the MSV-2 from it's top dog spot.

Hi Colin,
Wanna bet the displays we have coming are nicer?

Just kidding. A little competition will do everyone good!

Cheers,
Steve

Steve and Colin,

Thanks for your participation; I look forwards to both of your new products in the coming months.

A little competition will do everyone good!

Absolutely Steve

We have been the market leader for so long with our MSV-2 for CAN bus stuff i really did need something to wake my chaps up and certainly do i hope that this reciprocates for you in motivating your team and developments.

Wanna bet the displays we have coming are nicer?

ohh now i do like a challenge

Everybody loves pictures so here are some

We are planning a general all vehicle systems tool as well as a dedicated EAS controller.

This is a typical Menu page that allows selection between the various vehicle systems.
The 2 arrows at the bottom allow you to scroll to other pages.

Click image to enlarge

The Backgrounds can also be changed on the Nanocom setup page

When you select a vehicle system, you will get a function page like this.

Click image to enlarge

Inputs will look like this.
As the code has not yet had error handling added and is not connected to a vehicle when these pictures were taken, they currently show gibberish from the buffer or nothing.

Click image to enlarge

Click image to enlarge

Click image to enlarge

With such a graphical display we have typically used it to provide quite a unique function to this hardware in the form of an Instrument mode, where the unit provides a constant display of some real time values.

For this reason we also have an optional Stainless Steel mounting bracket and universal suction cup holder

Click image to enlarge

These are examples of screens for the EAS control capability.

Click image to enlarge

Click image to enlarge

For editing the CCF this is done on line using our Genesis system

The steps to use this feature are very simple

Go to the Genesis web site and Log in

Click image to enlarge

Although Genesis has other functions as previously posted up, you select the CCF Edit function.

Click image to enlarge

This gives you 3 choices



The first is to load your own "AS-BUILT" file in case you have one you already modified some etc.

The second is to load a session file you can take from the SDD, which is effectively a copy of the CCF that the SDD read from the vehicle itself, for completeness.

The third Blackbox copy option is one most will use to start with at least.

This pops up a box where you simply enter the VIN. This is one chosen at random




Then the editor screen quickly pops up populated with all the settings for that vehicles CCF.
There are two editing modes, Basic and Advanced, which can be toggled between using the circled button. settings are listed alphabetically

Click image to enlarge

On this next picture i have already toggled the edit mode to advanced, switched to the Infotainment section and edited the Audio Amplifier type Fitted setting so you can see that any edited item changes to Red and provides an undo button as well.

Click image to enlarge

I have also re opened the Audio Amplifier Type fitted edit box using the edit button to better explain the AS BUILT analysis percentages.
As you can see, we have analysed 200606 Disco 3 AS BUILT files and from this see that 19% were set as having no Amplifier, which would be base Audio, 29% had the AUD4 fitted which is the Logic 7 premium amp and the remaining 52% were AUD2 which is the Hi line amp.

Of course changing anything is a case of clicking on the arrow for the drop down selection and then clicking on the desired setting.


Finally when editing is done, you simply click on the Complete- download CCF button circled in this next picture and this opens the save as box that allows you to save the file wherever you want, hard drive, USB or SD card.

Hi Colin,
I have the nanocom for my D2, but have just purchased a LR3, is there any further progress on this software?
Thanks,
Daniel.

Hiya Daniel

Things have certainly not progressed as fast as i would like, causing quite some time to now pass since i posted up that we were going to develop coverage. This is because we have encountered many more problems than even we anticipated that have slowed us down considerably, as well as us closing for nearly 2 weeks for Easter.

However overall, i can say that there has actually been very significant progress, especially on the really complex flashing functions and on Genesis.

I am also especially pleased with myself and extra excited about this development because just before we closed for Easter in a thinking outside the box session, I had a really quite deep epiphany.

At the risk of boring some, but also knowing some will be quite interested i will explain.

Traditionally diagnostic equipment (Including our MSV-2 and Nanocom) starts off with a main Menu that allows the user to select their vehicle model. Then they get to choose the Vehicle system, this then runs a specific Module or Application specific to that Vehicle system. You then get a choice of functions you can perform, many of these functions are basically the same for every vehicle system such as Fault Codes, Settings, Programming etc.

This methodology of having one Module / App per Vehicle makes sense as Traditionally Vehicle systems fitted to Land Rovers have always been produced by different manufacturers with absolutely no standardisation between them and how these functions are accessed.

To follow this methodology for all the later CAN BUS vehicles with 25 to 30 Vehicle systems in each model on the Nanocom would mean a huge amount of Apps and a lot of Menuing for them.

Since accessing so many of the basic functions of CAN BUS systems is standardized, this also would mean a lot of Code duplication in each App.

My epiphany is to scrap this methodology of creating menus and Apps for each vehicle system on each CAN BUS vehicle but to create instead Menuing and Apps for each function.

This will solve many future problems, speed up developments, be vastly more expandable, make the end result much better, more functional, capable and even easier to use.

In Practice this will mean that from the existing main menu that currently has Defender, Disco II and p38 Range Rover on it, there will not be additional selection buttons like Disco 3, Disco 4, Range Rover Sport etc.
Instead there will be a single button marked CAN BUS VEHICLES

Under this there will be a Selection of functions like FAULT CODES.

Under this there will get some choices of reading all fault codes or only those by some filter, but there will also get a Configuration option that will allow the user to select anywhere between just one or all Vehicle ECU's which is what will be read when the other buttons are used.

I really hope that it is not that much longer before this is all implimented and working, but so far all goes really very well.

ATB

Colin

Hi Colin,

This is fantastic news.
and thanks for the detailed response, I really appreciated the information.

Cheers,
Daniel.