• 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!

The iBeat Thread

Anyone have some CO settings for 2010 te 510, stock exhaust but have the pu kit as far as lambda sensor removal and the race map plugged in

Anything under 100 on the CO setting and the bike won’t even start let alone idle. 120 on the first setting seems crisp and no stalling around corners.

Anything under 110 on setting 2 is stalling and bogging out, no throttle response.

Almost all my values are higher than others I have seen, I’m also riding on a hot day in Phoenix

Have you set up your TSP? that will be your first step before you start adjusting your COs

Ed
 
Have you set up your TSP? that will be your first step before you start adjusting your COs

Ed

Yes I set the tsp with ibeat, but I keep seeing people mention setting tps 100.2 which I’m not sure how to do.

George at uptite mentioned to try 102 104 100 for CO settings and the bike won’t even idle with those.
 
I had trouble getting Virtual XP to run on my laptop. So I purchased an old IBM Thinkpad running XP on eBay. Didn't spend much, I know it was under $50. I only use it for iBeat and it worked well!
 
I had trouble getting Virtual XP to run on my laptop. So I purchased an old IBM Thinkpad running XP on eBay. Didn't spend much, I know it was under $50. I only use it for iBeat and it worked well!
I got an old laptop as well. It lives in the workshop, just for ibeat and looking throigh PDF manuals.
 
TPS set to 100.2, still runs like ass unless the first CO setting is super lean and even then it’s not running great. Pretty over the bike at this point, thinking about waiting until November and just dropping it off to George at uptite. The bikes only got 150km on it and I can’t get it to run right.
 
TPS set to 100.2, still runs like ass unless the first CO setting is super lean and even then it’s not running great. Pretty over the bike at this point, thinking about waiting until November and just dropping it off to George at uptite. The bikes only got 150km on it and I can’t get it to run right.

Let us know what they found and the fix if you would. It might help someone out next time.
 
Will do, I’m not sure what else I could possibly try. The bike has 150 km on it, basically a brand new bike.

With the age of the bike and mileage, I would say it has been sitting for a while. I would start with the injector make sure it has a good flow, maybe check timing, and these are known for coolant temperature sensor issues, that's easy to check with the iBeat program. These thing can be temperamental but once you get them figured out they do run good.
 
My bike suddenly quit on me a couple of blocks away from home and wouldn't start. Pushed it back to the garage where it fired up and seemed to work fine (of course!). I'm planning a week-long off-road trip and didn't want to have any doubts about the bike, so I drained the tank and inspected the fuel pump (which looked good). Then my OBD cable arrived and hooked it to iBeat which showed 7 historical occurrences of code 2180 "Ignition Open Circuit". Then I pulled the coil out, measured the primary winding OK at 5Ω and the secondary seems indeed to have failed with an open circuit. Given that the ECU is connected directly to the primary winding which was within spec, does anyone know whether it would be able to detect an open circuit at the secondary winding, or should I start inspecting the primary winding connectors and wires on the loom as well?
 
Can anyone direct me to a copy of iBeat? Bike just died, will not restart....fuel pump appears to be running. Need to do some troubleshooting.
 
Hi guys,

I know I'm very late to the game on this one. I have a 2011 TE630 I'm trying to connect to iBeat, and not having much luck!

I have the blue KKL VAG-COM that everyone else is using, and I also picked up the Lonelec cable (https://www.lonelec.co.uk/Motorbike-OBD-Diagnostic-Cables/component/Husqvarna-6pin-OBD2-Adaptor), as I tried doing it myself and had the same issue, so I was hoping a proper cable would fix things.

Running a fresh windows XP install on VirtualBox on a macbook, drivers install fine and device appears in device manager. Every time I try to connect in iBeat it fails with "Communication Stops". I've tried a bunch of different drivers, windows XP on Parallels , to no avail.

Has anyone else had similar problems? I've read every thread on here and most people seem to get caught on the cable step, which I think I have resolved. My only other option at this point is to run a virtual XP on my PC and drag that to the garage, but I dont see why VirtualBox on a mac would change anything!
 
Back
Top