PDA

View Full Version : Nanocom Broken



Mk1_Oz
24th October 2017, 11:01 AM
My 9 month old Nanocom has failed. It wont power up using the OBDII cable but does respond when connected to the USB port.

I am doing an interstate trip in 2 weeks and wanted to take the unit.

I have left a PM with Colin but so far have no response. I contacted Nanocom direct via their website and they want it returned to CYPRUS!! Plus there is the AUD $100 cost to get it there!!!

Are there any Australian repair options so i have half a chance of getting it back in time?

biggin
24th October 2017, 12:22 PM
This happened to mine. I believe it only required a fuse be replaced. As pulling it apart was fraught with danger I just sent it back. Must have cost about $150 all up. It's been good for a few years now. Was a little peeved at the time though.

Mk1_Oz
24th October 2017, 12:28 PM
Def unhappy. A warranty should not cost me anything.

You returned it to Cyprus?

biggin
24th October 2017, 09:21 PM
Yep. That's the problem with buying from overseas. Even a warranty job costs you a fortune.
How come the Chinese can post their rubbish over here for virtually nothing.

discorevy
27th October 2017, 06:31 PM
Might be worth checking the lead for continuity, as well as making sure it has power / earth supply from the port before sending it off

Mk1_Oz
27th October 2017, 07:24 PM
Might be worth checking the lead for continuity, as well as making sure it has power / earth supply from the port before sending it offWhat

is inside the lead? There is a dirty great sticker saying VOID I BROKEN so they obviously don't want you going in there.

I asked Colin if there were any tests I could do before returning but his communication is extremely slow (funny how he communicated better when selling me the unit!!!!!!). Will run the multi-meter over it. Not sure which is the power pin but I am sure I can work it out.....

biggin
27th October 2017, 10:47 PM
Might be worth checking the lead for continuity, as well as making sure it has power / earth supply from the port before sending it off

Yeh, I tried that. Definitely worth checking, but unlikely it seems.

BBS Guy
30th October 2017, 02:46 AM
Hello MK1_Oz

With your comment


(funny how he communicated better when selling me the unit!!!!!!)

You publically portray me on this forum in a very negative light and seem to leave out some releveant information.

I would therefore and quite naturally take the opportunity to defend myself against such defamatory comments as you have made on this thread.
You first wrote me a PM on 21st October stating


Hi Colin.

My Nanocom broke today!!! I plugged into the OBDII port then went to plug the other end into the Nanocom. As the plug got close I saw a small spark. rom that point on the screen is dead and it wont power up.

I had it plugged in and working 5 minutes beforehand (had to read the MAF sensor output before cleaning it) but this time something happened. Not sure if the spark is related or not.

Where do we go from here? This unit is only a year (or less) old.


Despite even your knowing and realising that the damage caused to your nanocom was self inflicted and by not following well known connectivity instructions, that you then accuse me of a lack of concern and unwillingness to help, despite my having since written you 3 PM's in an effort to try and help and assist you beggers belief.

I hold my head high on this forum as someone so well known and respected for providing a well respected solution to diagnostic equipment needs for Land Rover Owners and Lovers, I regulary provide discounting opportunities, and as the owner of my company I am right here to answer for my or any of my staffs errors, shortcomings or failings.

I would hope other owners would post up, however If concensus deems me to be a baddie, than so be it.

Regards

Colin

Xtreme
30th October 2017, 07:37 AM
Thanks for painting the other side of the picture Colin and bringing this thread into perspective.

I generally leave my lead connected to the Nanocom but was wondering if there was some electronic modification possible to eliminate this known connection sequence problem?

weeds
30th October 2017, 07:45 AM
Thanks for painting the other side of the picture Colin and bringing this thread into perspective.

I generally leave my lead connected to the Nanocom but was wondering if there was some electronic modification possible to eliminate this known connection sequence problem?

Er what is the correct connection sequence.....

I normally connect the nanocom with ignition off.....than turn on/start the car

I than try to disconnect after I turn the car off...but have pulled the cable a couple of times without thinking.

Xtreme
30th October 2017, 08:23 AM
Er what is the correct connection sequence.....

I normally connect the nanocom with ignition off.....than turn on/start the car

I than try to disconnect after I turn the car off...but have pulled the cable a couple of times without thinking.
Always connect cable to Nanocom BEFORE connecting to OBD2 port.

weeds
30th October 2017, 08:31 AM
Always connect cable to Nanocom BEFORE connecting to OBD2 port.

Cool, don’t think I have ever disconnected the cable after assembling first time.

Mk1_Oz
30th October 2017, 10:26 AM
Colin,

I am sorry you took offence to my comment re your slow communication. Not deflametory just calling it the way I felt the communication timeframe went. In no way can my comment be construed as me saying that you have a lack of concern and unwillingness to help so you are unfair in that comment.

As to the possible cause of the connection failure. I was not actually aware that there was a correct connection sequence (and it appears that maybe others with Nanocoms are also unaware of this). I/we maybe have missed a bit of information which if so appears may have had an unfortunate result? However, without seeing the unit you have jumped to a big conclusion that it has failed due to my actions. Maybe it has but maybe not.

However, I should not have posted the comment on the forum, apologise, have no intention of giving you a bad name and do not wish to have an online fight.

gavinwibrow
30th October 2017, 01:16 PM
Colin,

I am sorry you took offence to my comment re your slow communication. Not deflametory just calling it the way I felt the communication timeframe went. In no way can my comment be construed as me saying that you have a lack of concern and unwillingness to help so you are unfair in that comment.

As to the possible cause of the connection failure. I was not actually aware that there was a correct connection sequence (and it appears that maybe others with Nanocoms are also unaware of this). I/we maybe have missed a bit of information which if so appears may have had an unfortunate result? However, without seeing the unit you have jumped to a big conclusion that it has failed due to my actions. Maybe it has but maybe not.

However, I should not have posted the comment on the forum, apologise, have no intention of giving you a bad name and do not wish to have an online fight.

Well responded Mk1_Oz.

You are actually right in that any number of owners haven't read their info correctly and don't know ALWAYS Nanocom first, then OBDII port for connecting.
I have just sent one back to Cyprus for repairs after suspecting that persons unknown have done just the reverse whilst my old beast has been in a number of hands for repairs/remedial work (I leave mine on board permanently in instrument mode, particularly for the coolant temp with warning).

I have every confidence in Colin and his team, and although he may have misunderstood the intent of your comments, his response re his service to this forum is spot on. I have 2 Evos (I've purchased 3 if you count the one that was stolen and replaced) and a BBS kicker, and have received nothing but excellent support once my dumb questions have been understood at the other end). Their forum, although not necessarily formatted to suit all tastes, is an excellent source of info, and highly recommended for questions.

Good on you for clarifying - we can't afford to lose those who support our passion/madness! Cheers Gavin

donh54
30th October 2017, 01:38 PM
Always connect cable to Nanocom BEFORE connecting to OBD2 port.

Yep, says so right there in the instructions!

I've got no complaints whatsoever with Colin and the BBS staff. Does help to remember the time difference between here and Cyprus, too. [bigwhistle][bigsmile1]

PhilipA
30th October 2017, 02:32 PM
BUT! BUT!

It's unmanly to look at instructions until the flat pack furniture is a complete mess , or maybe until you have blown the fuse inside the Nanocom.
Everybody or at least every wife knows that.
Regards Philip A

bee utey
30th October 2017, 02:37 PM
Sounds like the cable should be securely anchored to the box to prevent random people accidentally undoing it in the wrong sequence. Something that easy to blow up may need a secure screw type connector.

PhilipA
30th October 2017, 03:37 PM
Sounds like the cable should be securely anchored to the box to prevent random people accidentally undoing it in the wrong sequence. Something that easy to blow up may need a secure screw type connector.

They do have a multi plug like used to be used to run a computer to a screen, with 2 screws to hold it in place.
But it is more space efficient to unscrew it and store the cable around the Nanocom, as long as you remember to plug it in first! LOL.
Regards Philip A

BBS Guy
31st October 2017, 03:28 AM
Hiyas All

Many thanks to all for your many helpful comments and input on this thread.

Mk1_Oz, many thanks to you for your apology, it is much appreciated, graciously accepted and reciprocally, I offer mine if you believe I over reacted to your comment.

Although there is indeed quite some time difference, I do try my very best to log in on this forum as often as I possibly can, and respond to PM's etc, but sometimes it can be a few days, due to my overwhelming work load.

Please try to appreciate that my position and role within Blackbox Solutions, is not Sales, Administrative or Support oriented. For these roles I am blessed to have a very close knitted family of very skilled and dedicated staff that so many members here have had the great pleasure of dealing and working with.

As a company manager, I have to oversee and solve problems well above and beyond these three mentioned aspects, like purchasing / stock control, returns, accounting, on going development to name just a few.
Today I have a much bigger problem with sourcing a part for building Nanocoms that is being discontinued, which I already had to make changes in the Nanocom firmware to also use an alternate part barely a year ago.

In noting that after my pointing out in this thread the most likely cause in this particular case of your Nanocoms failure may well be due to your not following the advised connection sequence that we document, I feel that too much ephasis on this. So I would like to share the fact that In the many years and with large numbers of Nanocoms being supplied, I believe that less than a dozen have been damaged by what we believe is incorrect connection sequencing.

I have lots more returns for broken touch screens !!!!

I believe that in most cases of incorrect connection sequencing it just takes out the low value fuse in the vehicles fuse box for the OBDII socket, but if larger values are fitted in place of the blown fuse, this raises the risk. Automotive fuses are also quite slow to blow, so as per Extremes comment

wondering if there was some electronic modification possible to eliminate this known connection sequence problem
You could fit a lower value faster acting fuse in the wire that feeds pin 16 (+12 Volts) on the OBDII socket etc.

I will always continue do whatever I can to advise and help anyone and everyone as best as I can, and although not perfect, most will realise and appriciate my positive efforts.

ATB to all

Colin