Nanocom woes

[Tins]

I have a Nanocom Evolution that is causing me angst... It's maybe 18 months old and hasn't seen much use. It's my second one, the other got used quite a bit. Before I spend the next part of my life on the BBS forums I thought I'd try here first.

I was using the unit off and on chasing a SRS fault, and it got all sullen and showed me this:
186898

It then goes to this:
186899

If I plug it into my computer it loads the USB screen, but the Kernel and Nanocom Diagnostic options bring me to the screens in the pix. but the firmware and Graphics options bring me to a numeric keypad for which I don't know the code.
All this is on a mac, but I have Win 7 and 10 running under emulation. I have the latest firmware to flash to the unit, but it does not appear in Device Manager. I am not a Windows guy and could be missing something here.
Anyone have any ideas before I send the thing back to Cyprus[bigsad]?

[shack]

Anyone have any ideas before I send the thing back to Cyprus[bigsad]?

Hi Tins,

That's not a good sight, you might be in strife... However, I'd be trying to reinstall the firmware, i think the procedure is to plug it in to your computer with the sdcard removed, then start the update package, it'll either find it or not!

If it doesn't, you can grab a torx bit and remove on of the end covers, there is a jumper inside that can be moved to put it into update mode, instructions are in the update package when you run it (from my scratchy memory)... All the best!

You have nothing to lose!

[Tins]

Hi Tins,

That's not a good sight, you might be in strife... However, I'd be trying to reinstall the firmware, i think the procedure is to plug it in to your computer with the sdcard removed, then start the update package, it'll either find it or not!

If it doesn't, you can grab a torx bit and remove on of the end covers, there is a jumper inside that can be moved to put it into update mode, instructions are in the update package when you run it (from my scratchy memory)... All the best!

You have nothing to lose!
That’s worth a try. Thing that gets me is that it’s never had a card in it.
Thanks

[shack]

That’s worth a try. Thing that gets me is that it’s never had a card in it.
ThanksHmmmm, not quite sure I get your drift.... Can you explain?

[Tins]

Hmmmm, not quite sure I get your drift.... Can you explain?
Oh. Sure. I have never put a card in the SD slot, which is why the SD card error message confuses me.

[shack]

Oh. Sure. I have never put a card in the SD slot, which is why the SD card error message confuses me.Ah...

I'd suggest the first error is a missing firmware storage device, the 2nd is looking for the sdcard, maybe for some inbuilt recovery process.

[Tins]

Ah...

I'd suggest the first error is a missing firmware storage device, the 2nd is looking for the sdcard, maybe for some inbuilt recovery process.

Hmm... maybe it could be worth trying putting the firmware updater on an SD card, although I'm not sure how it would run, given it's an .exe.

[shack]

Hmm... maybe it could be worth trying putting the firmware updater on an SD card, although I'm not sure how it would run, given it's an .exe.The .exe needs to be run from windows.

There is a recovery option that requires you to have made a recovery backup, I think that can go on the sdcard, but the.exe won't work.

[Tins]

The .exe needs to be run from windows.

There is a recovery option that requires you to have made a recovery backup, I think that can go on the sdcard, but the.exe won't work.


Yes, and in windows I get "Device not attached" . Could be an issue with USB on the VM, but all the other peripherals work. Still, issues with a VM are not the topic of this thread, so I'll go and play with that for a bit.

[shack]

Yes, and in windows I get "Device not attached" . Could be an issue with USB on the VM, but all the other peripherals work. Still, issues with a VM are not the topic of this thread, so I'll go and play with that for a bit.That's where the jumper setting comes in... And you need to be using a data cable, not just a charge cable.

[Tins]

That's where the jumper setting comes in...

Yep, will give that a go. As you said, nothing to lose....



And you need to be using a data cable, not just a charge cable.

That one I'm aware of. I tend to ditch "No Data" cables.

[Tins]

OK James, do have any insight into which pins I should jump?[bigsad][bigsmile]

186909

[shack]

OK James, do have any insight into which pins I should jump?[bigsad][bigsmile]

186909You remove the jumper, then plug in and try to update, hopefully it works... When finished, power off.. Replace jumper as you found it and see if it works! Make sure it goes back on the same pins though.

[Tins]

You remove the jumper, then plug in and try to update, hopefully it works... When finished, power off.. Replace jumper as you found it and see if it works! Make sure it goes back on the same pins though.

Ahh. Simple when you say it slowly.... I have a picture for reference....

[Tins]

One thing this has done is remind me why I hate Windows so much.

[Tins]

I'll keep updating in case it's of use. Using VirtualBox for emulation, with the jumper removed as per shack, the VM sees the Nanocom but the 2 guest OS, win7 & 10 do not. So I'm now installing win10 using bootcamp on my laptop... ugh.

[V8Ian]

Should have got a proper computer in the first place! Apple, pah, they're for turning into cider. [tonguewink]

[Tins]

Should have got a proper computer in the first place! Apple, pah, they're for turning into cider. [tonguewink]

Oh really?? After more than an hour waiting for windoze to install, and get past all the bloody ads and creating a micro soft account etc needed to get into the thing, and dismissing all the nagging, I now have a windoze machine.... lucky me. And why, WHY, did they take the UI that they've had since 95 and ditch it for this abomination?

You should try cider sometime, Ian. Its better than the **** you seem to enjoy.[biggrin]

[Tins]

However, the pain may have been worth it. The BBS Firmware app is upgrading now. It even details the jumper thing you spoke of, James.

Pity BBS remain in the dark ages and don't support modern, UNIX based OS such as macOS and Linux. Still, I rarely use the laptop, so a dual boot is no hardship. Now.

[Tins]

Thanks, shack. And I was able to use their SD card formatter.

186932186933

[shack]

Thanks, shack. And I was able to use their SD card formatter.

186932186933You've done well!

[Tins]

You've done well!

Tomorrow it gets tested on the D2....[bigsad]

[Tins]

Hmm. Since doing this the nanocom has worked fine... with one caveat. It frequently won't power up at all. I suspect it's either the diagnostic port on the car that has a dodgy terminal, or it's the lead to the nanocom itself. Given the use it's had I doubt that one.
So, I've been trying to clean the terminals etc, which is awkward with my knees. Anyway, it pwered up, but has gone back to "firmware disk not found" Ok, been here before and can fix that.

Would it be a reasonable assumption that the issues may be being caused by the diagnostic port or the wiring leading to it? Is it possible to re-route this wiring. I don't mean physically, I can do that with a lot of swearing, but electrically can I screw it up? My port has never been secured properly to the under dash panel as it's damaged. I guess I could repair that.

Anyway, digging out the laptop with windoze on it. Guess I'll jump into RAVE while I'm at it.

[V8Ian]

Hmm. Since doing this the nanocom has worked fine... with one caveat. It frequently won't power up at all. I suspect it's either the diagnostic port on the car that has a dodgy terminal, or it's the lead to the nanocom itself. Given the use it's had I doubt that one.
So, I've been trying to clean the terminals etc, which is awkward with my knees. Anyway, it pwered up, but has gone back to "firmware disk not found" Ok, been here before and can fix that.

Would it be a reasonable assumption that the issues may be being caused by the diagnostic port or the wiring leading to it? Is it possible to re-route this wiring. I don't mean physically, I can do that with a lot of swearing, but electrically can I screw it up? My port has never been secured properly to the under dash panel as it's damaged. I guess I could repair that.

Anyway, digging out the laptop with windoze on it. Guess I'll jump into RAVE while I'm at it.
I imagine it would be, try using your hands. [tonguewink]

[AK83]

..... It frequently won't power up at all. I suspect it's either the diagnostic port on the car that has a dodgy terminal, or it's the lead to the nanocom itself. .....

One way to work this out is to use the USB cable.
IIRC the nanocom came with a USB cable in the box. Should do both data and power.
You can just power up the nanocom using the USB cable alone, obviously can't communicate to D2 tho, but this is just a test to see if it starts up 'every time'.

The power port only requires 500mA, so I assume that same power requirement from USB to start it up too?
Alternative is to connect a power supply of some type to the power port too.
Technically! ... the nanocom quick setup guide does specify to run a 12v 500mA power to the power port, and not just rely on the OBD cables' power alone.
In saying that tho, other than one time, I've never used the power port, and always just run off the OBD. Only time I used power port was when flashing updated map to ECU, where I also had the car on a power supply to be sure nothing randomly shut down.

[Tins]

I imagine it would be, try using your hands. [tonguewink]

Thanks Ian. You're a great help, as usual....[bighmmm]

[Tins]

One way to work this out is to use the USB cable.
IIRC the nanocom came with a USB cable in the box. Should do both data and power.
You can just power up the nanocom using the USB cable alone, obviously can't communicate to D2 tho, but this is just a test to see if it starts up 'every time'.

The power port only requires 500mA, so I assume that same power requirement from USB to start it up too?
Alternative is to connect a power supply of some type to the power port too.
Technically! ... the nanocom quick setup guide does specify to run a 12v 500mA power to the power port, and not just rely on the OBD cables' power alone.
In saying that tho, other than one time, I've never used the power port, and always just run off the OBD. Only time I used power port was when flashing updated map to ECU, where I also had the car on a power supply to be sure nothing randomly shut down.

Thanks. Yes, the nanocom works as expected when plugged in to the USB. Also, this nano, my second, has hardly been used so it's main cable should be fine. Yes, just because it's new etc.

[Tins]

Just to follow up. I'm pretty sure it's the plug in the car, as it's not secured to the dash, and was dangling so I have prolly trodden on it. I now have a new plug and bracket. So I'll get that installed and see what's wot.

Sigh, with my back injury I was hoping my days of crawling around under dashboards were over. Is there any reason why I can't extend the wires to the plug so I can get at it easier?

[eddy]

Could get an extension cable? Try jaycar.com.au (https://www.jaycar.com.au/1m-obd-ii-extension-cable/p/LA9037)

[Tins]

Could get an extension cable? Try jaycar.com.au (https://www.jaycar.com.au/1m-obd-ii-extension-cable/p/LA9037)

Thx. I already have one which can be used when under the bonnet etc.

[Tins]

After a bit of mucking about it works. The plug was full of that green verdigris muck. I have replaced it. I had a Chinesium one [bigsad]. Now I have one from a wreck and hey presto.

[Tins]

Well, I say "works". I seem to have lost some menus, like SRS and Autobox. Hmm. And my only windoze puter is in bits... sigh.

[Tins]

OK, I now have all the functions restored following a firmware "upgrade". I think I already had the latest one, so it was more a restore.

I believe that all of my issues have been a result of the bad diagnostics port in my car. Might pay to check. Mine was full of corrosive verdigris, possibly due to damp. Now, I wonder where that could have come from. In a D2....