• Hi everyone,

    As you all know, Coffee (Dean) passed away a couple of years ago. I am Dean's ex-wife's husband and happen to have spent my career in tech. Over the years, I occasionally helped Dean with various tech issues.

    When he passed, I worked with his kids to gather the necessary credentials to keep this site running. Since then (and for however long they worked with Coffee), Woodschick and Dirtdame have been maintaining the site and covering the costs. Without their hard work and financial support, CafeHusky would have been lost.

    Over the past couple of weeks, I’ve been working to migrate the site to a free cloud compute instance so that Woodschick and Dirtdame no longer have to fund it. At the same time, I’ve updated the site to a current version of XenForo (the discussion software it runs on). The previous version was outdated and no longer supported.

    Unfortunately, the new software version doesn’t support importing the old site’s styles, so for now, you’ll see the XenForo default style. This may change over time.

    Coffee didn’t document the work he did on the site, so I’ve been digging through the old setup to understand how everything was running. There may still be things I’ve missed. One known issue is that email functionality is not yet working on the new site, but I hope to resolve this over time.

    Thanks for your patience and support!

Do special parts ECU's have CO1/2/3 locked out?

B

bbcmat

Husqvarna
A Class
I just installed my 8000H2004 Husky special parts ECU / exhaust insert (short DB killer) - with Ibeatv2 I can set TPS value and clear alarm values / read sensors etc BUT I have a com error when trying to read CO values. No problem with standard ECU.

Anyone else experience the same?

MAT
 
What year is your bike. I have 09 te310. I have the special parts ECU too and have no problem adjusting the co values. You only need to move it a little. It is very close to where you should be.
 
You should definitely be able to adjust CO values with the race ECU with either Ibeat V 2.0 or 2.1.
 
I have the 2.0. If it is working on the stock ECU it should work on the race ECU. With the bike running when you click on co setting what happens. Do you have the o2 sensor by pased.
 
The error is "read error" - it occurs just after the normal warning message and "OK" is clicked.

I am familiar with Ibeat and this ECU was purchased as final troubleshooting on a no spark / no fuel inject / no crank rpm displayed while cranking problem I'm having.

I'll start another post for that issue - but there definetly looks like something is up with this ECU.

MAT
 
I know that my special parts ECU had a lot of error codes before I cleared them. Although it could still set CO settings even with the error codes. Once I cleared them they did not return
 
Yes - I did clear all error codes

The "read error" message occurs in every circumstance. I'm going to put back the stock and test to be sure before returning the dud to my excellent dealer.

MAT
 
This is an incredibly strange situation.

Try to get as much information about this as possible if you don't mind. Any identifiable version/serial number information for the ECU that causing problems.

Does the ECU have your bikes VIN encoded?
 
Rob at Ross Rocker Sales was right on the nose (again LOL) - version 2.01 Ibeat and everything is accessible. The ECU was perfect.

MAT
 
You must log in or register to reply here.
Back
Top