I recently changed out the O2 sensor on my z600 after it gave me 0134 and 0030 errors, but the ECU is still giving those errors.  I've double checked all continuity between the socket and the ECU and everything is intact, both before and after the sensor replacement.  Could this just be an erroneous signal from the ECU?  Everything else still seems to function properly.  Voltage from the sensor is in range and the heater element passes resistance test.

[2015 Z Force 800 53/Trail EPS]

Might check the ECU pin connections. Look very closely to each one. Does indicate a connectivity problem but could also be a problem with the ECU. Let's hope not.

I had checked the ECU pins before installation and they are all nice and straight.  I've looked up new ECUs on Ebay for just under $200.  If a new on of those if what I'll need to do then I'll do it.

[2015 Z Force 800 53/Trail EPS]

I'm thinking its either a bad connector somewhere or a problem in the harness somewhere. Odd that just the O2 connection would be effected by a burn-out in the ECU. Maybe ohm the entire paths between the ECU pin and the last connector.

The symptoms do seem to suggest a connection problem, but as I had mentioned I checked continuity from ECU plug to O2 sensor plug and all showed closed circuits.  I'm still very willing to perform further troubleshooting even if it means taking the older sensor (or even the new one) and wiring it up at the harness right next to the ECU plug.  That way I'll at least be able to eliminate a few feet of wire.  I agree that it seems odd that ONLY the O2 sensor functionality is effected.  I'll go a step deeper and check the resistance of each of the harness wires too, any significant amount would still show a 'closed' continuous circuit, but certainly effect the readings at the ECU end.  (Speculative) Maybe I have a crushed/pinched area of the harness reducing electrical flow to a minimum?  Many thanks for your responses.

[2015 Z Force 800 53/Trail EPS]

Looking more like the ECU. But how about grounding? Are the chassis grounds from the frame and harness still connected to the engine case?

Tested continuity between battery negative to frame and then to engine case.  Both pass.  Tested 0 resistance in sensor pin 4 to ECU plug pin 24.  Showed 3 ohms when going from sensor pin 3 to ECU pin 21.  Zero resistance sensor pin 2 to ECU pin 15.  When the ECU is connected the battery ground also shows continuity from sensor pin 3 AND sensor pin 1.  My understanding is that sensor pin 1 is the power to the sensor's heater, and I'm not so sure that one should be grounded.  Grounding to pin 3 disappears when the ECU is disconnected but for pin 1 it does not.  I know that's a lot of data but I wanted to be as thorough as possible with my findings.

Ok, wired leads 4 and 3 of an O2 sensor directly to the wires on pins 24 and 21 of the ECU plug and that does not stop the 0134 error.  Unless there is something to attempt I am not thinking of looks like I'll be ordering an ECU soon.
https://www.ebay.com/itm/185334798924?_trkparms=amclksrc%3DITM%26aid%3D1110006%26algo%3DHOMESPLICE.SIM%26ao%3D1%26asc%3D20201210111314%26meid%3D1fb06c634c8547109f7759178baa085d%26pid%3D101195%26rk%3D2%26rkt%3D12%26sd%3D144455246693%26itm%3D185334798924%26pmt%3D1%26noa%3D0%26pg%3D2047675%26algv%3DSimplAMLv9PairwiseWebMskuAspectsV202110NoVariantSeed%26brand%3DUnbranded&_trksid=p2047675.c101195.m1851&amdata=cksum%3A1853347989241fb06c634c8547109f7759178baa085d%7Cenc%3AAQAGAAABIIIp3bTCXFAKw6S9crk9CpCrrtOgadqFiC10NVPbN0936eprYVB4SXfDa52e1mbPLCrB3E9VUWIaZd5IfGou%252BD5RJmNy1hO%252FQWVkBsE%252FKqVc1Z7xUG1VNv0wwUqxXbC%252BkIOGhwuaX9NzNxPX7%252F8ig9Ueq7NYVe7tcZpuTqGV7wkuMuubf7iQ4aKbE4mVDLS2iHWjRvljZrjnw011BpHEloGeaD9jf%252BBSxxhKm2F97%252FgrdJHmUaY%252Fjg9wV6U%252BKCeweQHUOmr%252FB8NrY7EDmDmRqCDHH5kZCOJcu3SjJQfggUqs1pElsCv9JKDKeWMSi2FyMNIPxc23LwsOin9L1U%252Fmx4Q5uxZsjtNAaoP7Noz9Oa9dlbnblgcqLpshS4%252FZEE5P2A%253D%253D%7Campid%3APL_CLK%7Cclp%3A2047675
This one has all the same numbers on it as mine.

The codes clear themselves on older machines.

I recall reading that codes need to be manually cleared on newer machines, though I have no first hand knowledge of this.  I wonder if youfixed the problem, but the stored code is not cleared.

Before you do anything, you need to connect a reader to the ECU and inspect/verify the O2 signal to the ECU.

Do you have a reader to watch the O2 sensor signal, or to read or clear the trouble codes?

I have no access to one of their readers.  Unless someone knows how to rig a modern OBD2 reader to the CFMoto 3 pin diagnostic plug.  Also, from a post back in January 2020 you told another 2013 z600 owner that the codes do not get stored.

Re: Help with a Trouble Signal Light 2013 Zforce 600
« Reply #7 on: January 02, 2020, 03:19:12 PM »

If you correct the issue, the light will go out immediately.

It's not like a modern car where the light stays on until the next time the ECU runs and passes the internal tests.

I found a schematic for a 16 pin OBD2 to 3 pin diagnostic plug and made a little adapter for my scanner.  It powered up but was unable to connect to the ECU even with testing different pin configs.  I'll see if my local ATV dealer happens to have a 3 pin diagnostic reader, but in the mean time I'm just going to allow my Ebay order to process for a new one.  If my original is by some chance still good then it looks like I'll have a spare.

Right. I didn't catch that you had a 2013. The code should clear when the issue is resolved in that case.

Check this out to make your own analyzer tool.

https://netcult.ch/elmue/HUD%20ECU%20Hacker/

Yeah, the 3 pin config in those schematics is what I tried.  The OBD powered right on when I plugged it in but (as I said) it was unable to communicate with the ECU.  Many thanks for the response, it had a LOT of useful and specific things about connecting an OBD to different set ups.

A standard OBD reader won't work. This is a K line only interface with manufacturer specific packet headers.

You will need a PC to read the data off the K line.

Got the new ECU.  Hooked everything back up, started the engine and NO codes given... initially.  I took it for a ride and nothing happened.  Next day after I put in some gas and turn the key it's giving an error code.  This time only the 0134.  The 0030, for now, is gone.

[UPDATE]  Had a fuse go out due to the control box for the light whips, uh, melting.  I installed it just behind the back plastic right in the center and apparently WAY too close to the muffler.  But in any case in testing systems after its removal I noticed that no error was being shown.  Just to see, I put the old ECU back on and it gave both 0134 and 0030 codes again, so, it would appear as if it is showing false O2 sensor signals.  At least the purchase wasn't for naught.