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
MY16 D4 TDV6 - with a little Cambo magic for towing "The Brick"
MY95 RRC LSE Vogue Softdash "Bessie" (turning circle comparable to QE II) with MY99 TD5 and 4HP24 transplants. Back home Nov 22 after a magic overhaul by Chivalry
SADLY SOLD MY04 D2a TD5 auto Classic and MY10 D4 2.7 both with lots of goodies
-----
You have the right to remain silent. Anything you say will be misquoted, then used against you.
-----
1999 Disco TD5 ("Bluey")
1996 Disco 300 TDi ("Slo-Mo")
1995 P38A 4.6 HSE ("The Limo")
1966 No 5 Trailer (ARN 173 075) soon to be camper
-----
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
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.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.
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
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
You could fit a lower value faster acting fuse in the wire that feeds pin 16 (+12 Volts) on the OBDII socket etc.wondering if there was some electronic modification possible to eliminate this known connection sequence problem
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
Search AULRO.com ONLY! |
Search All the Web! |
---|
|
|
Bookmarks