Thread: Nanocom Evo problem

Originally Posted by stock d2

I seem to having problems with my nanocom. When I connect to the obd port it does not turn on. However when I connect it to an external power supply the nanocom powers up and I can access my D2s ecu and read all the fault codes. Is there a fuse in the d2 that is blown or is it a fault of the nanocom? Does it have an internal fuse?

I don't think the cable is broken as I only just got the nanocom and it was powering up fine up until this evening through the obd.

Bit hard to read speed sensors if I'm reliant on an external 240v/12v dc transformer.

Have you checked that you are getting 12V at the OBDII connector?

Offtrack is almost certainly correct in that the most likely cause of your problem based upon the symptoms you mention is that you have blown the fuse in your vehicle that supplies power to your OBDII connector.

I would surmise that to do this you have not been explicitly following the connection sequence detailed in the owners guide and have connected the lead to the OBDII socket before connecting the 15 Way D connector on the Nanocom Evolution, rather than the other way round.

At best this will only blow the fuse in the vehicle, but at worst can permanently damage the Power supply in the Nanocom requiring it to be returned for repair.

Bit hard to read speed sensors if I'm reliant on an external 240v/12v dc transformer.
1000m Roll 10mm2 2C + E Circular Electrical Copper Cable | eBay

Sorry couldn't resist the mental image.

The abs sensor readings will cut out at 7kmh unless you are really really really lucky, then they'll drop out at around 20kmh.

Jack the vehicle up and spin the wheels, then you don't need a long cable.

Mine turns on ok. It's getting it to stay on that's the challenge. In gauge mode (where it boots to) I might get 30 seconds if I'm lucky. Am considering running a external source from the car to it if it'll make a difference.

Have asked the question of their forums to no avail.

To follow on from previous comments, I pulled the SD card the other day and have noticed since it stays on longer (but not necessarily full time). It's a genuine Sandisk 8gig SDHC card. It works for general running (save for the turning off) and for updates. Is it a case of the card, when fitted, becomes a default storage area and if incompatible (by type or size) in trying to write logs to it fails and shuts down?

Does the same thing happen with the motor going? Wondering if the voltage is getting a bit low.

Low voltage shouldn't be an issue. The Nanocom's regulate power down to 5V (and possibly 3.3V) internally. Commonly used regulators only need an input of a volt or two above the output voltage to maintain regulation. Low dropout regs can manage with less than a volt. The battery would have to be well below 12V to cause significant problems.

As has been discussed in other recent threads SD Card access has been a bit problematic, most noticeably in relation to uploading remaps. I suspect the same underlying issue causes problems with any module that reads or writes a substantial amount of data during logging. My understanding is that data writing only occurs when you specifically choose record to sd card.