Reading fault codes

Joined
Jun 25, 2019
Messages
31
Country flag
Has anyone been able to read fault codes on later (2017) bikes? When I was at Norton yesterday, Ash mentioned I had a few codes but as I have a few scanners I wanted to clear them at home and then see which if any return. I have a cheap ELM based OBD reader using Torque Pro but this would not connect to the ECU. I then tried a more sophisticated Delphi laptop based scanner which I have used to diagnose many faults on various cars and this system usually can read all of the vehicle systems but in this case still would not connect to the ECU. Mine is running an OMEX ecu - there is some software on the OMEX website but no idea if that woul work with the Norton version of the ECU?

I have seen that others have used the cheap eBay scanners successfully so it does seem to be something specific to the latest (Euro 4) models?
 
I've just got off the phone to OMEX - it would seem that the latest ECU's (Black ones!) cannot be read by generic OBD readers which is odd as I thought this was a requirement of Euro 4 (or even much earlier) specifications. Every petrol car since 1997 I believe has to be OBD 2 compatible but this does not seem to be the case for bikes (or Norton at least). The software you can download from OMEX also will not connect to this ECU - only the Norton supplied kit which is not available to anyone other than Norton.
 
Resurrecting this thread I have got a misfire and the MIL light on. Has anyone managed to talk to the later 2017+ Omex ecus? If we are not going to get support from the factory I can't believe the option is to replace the ECU. I think it is important we can find a way round this so some of our more isolated owners could at least borrow a reader to diagnose their bike. I have tried to get in touch with the factory but no reply yet. When I was at the factory a while ago they said they were having a few communication problems with Omex and weren't sure if they were continuing with them. Wonder what the new 961 has got......
 
To clear the light, once you've cured the misfire....I find if you coast down a long decline, leave it in a high gear and clutch out ...reach over and turn the ignition key off. Wait for the ecu shut down relay to eventually turn power off (seemingly takes for ever when you're watching the lights), then turn the key back on, so the engine instantly bump starts its self. This usually puts the light out.
 
Euro 3 Omex doesnt have the ability to store codes, so an ignition cycle clears those once you've repaired the fault.
 
Thanks for that - this is a euro4 bike and normally the light resets itself. The problem is identifying the cause of the misfire without systematically replacing everything cos it is bound to be the last thing. Yes Stu - you know a man who can help with that and I might need to call on your services as it also seems to have developed an engine speed related noise. Have checked timing chain tension but not looked at top end. Your assistance on the forum is as ever pure gold.
 
Unplugged the Lambda sensors and it runs smooth. Don't remember seeing any direct replacement references on this forum; let's see if Norton are supplying parts yet....
 
If unplugging lambda's, it should default to an open loop map...by rights. So it may be masking another fault.
 
Still thinking about being able to connect to Omex ECU for proper diagnosis. There is a code about on this forum which may unlock the software but as we have discovered it doesn't seem possible to connect the ECU using the obd port. The Omex ecus connect to their software using RS232 so I am thinking that the RS232 signals must be presented on the OBD type connector. Work out which ones then connect an USB to RS232 adapter and maybe we are in.

As I understand at higher revs the ECU is in open loop anyway. So this decision is based on the o2 sensors signal being way out of range which implies one/both is sending within range but wrong values to the ECU?

And no Nigel I don't want to buy a pair of carbs off you. Yet.
 
Last edited:
To clear the light, once you've cured the misfire....I find if you coast down a long decline, leave it in a high gear and clutch out ...reach over and turn the ignition key off. Wait for the ecu shut down relay to eventually turn power off (seemingly takes for ever when you're watching the lights), then turn the key back on, so the engine instantly bump starts its self. This usually puts the light out.
Would hitting the kill switch do the trick?
 
Thanks this is kind of interesting - is there a standard for providing an rs232 signal out through an OBD connector? Shame it is out of stock - it seems to give pinouts so I shall investigate. I need to get an OBD connector and get probing with the scope......
From the Amazon website :

  • 【NOTE:】This cable is not meant to be plugged directly into a computer’s serial port. It's just a cable with two different types of connectors on each end.this is not a signal convert level adapter.
 
Thanks for this - have got one off ebay as the amazon one out of stock - have been looking at circuit diagram and there are 2 Vendor Option pins on the OBD port which I am hoping are the tx/rx lines and I can rewire the ebay harness to test it.
 
Back
Top