• 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

What are anyone’s i beat settings that have a fmf pipe, just replaced the fuel pump so trying to make sure it’s running on a good set up, aslo has anyone had trouble with your bike pinging(pre detonation)
 
Check thru this thread and use DynoBob's settings. He updated the numbers a couple of years ago. I can't give my settings as I am doing something different using a power commander and auto tune. So my numbers would be irrelevant. Once the fueling is set properly I have never had a problem with pinging.

Welcome to the forum! Lots of info here on keeping your bike running.
 
Hi to all! First o fall, want to thanks DYNOBOB who posted his good tutorial, as well all the other users that shared their experiences with iBeat and its accessories. Thank-you to you all, now I managed to connect the bike to the PC.
My bike is a 2009 Husqvarna SM610 ie, arrow exhaust, O2-Lamba removed with the specific resistors cap.
The problem is that the neutral light on cockpit keeps on flashing.

Code error I find on bike is:
"Tilt sensor value LOW, code0840" .
Indeed, I did not have the tilt sensor mounted: plug was cut, sensor was gone, two of the three wire were jointed.
Bike starts and run perfectly

So, I got a new (used) tit sensor, and mounted it on the bike.

Now the sensor is in its original position, all the wire are corretcly connected as in original version.
Neutral light keeps flashing.
Now error code shown is:
"Tilt sensor value HIGH, code 0880"
Bike starts and run perfectly

Did some kind of test to avoid error: reconnected O2 sensor, set TPS as per iBeat and workshop manual procedure.
Test water temperatur sensor too, and it's ok.
Nothing is changed.
Error is still is "Tilt sensor value HIGH, code 0880" and I still can get rid of the flashing neutral light.

Anyone has any suggestion and/or has had the same kind of issue?
 
Sorry, my only experience with a 610 was years ago, I remember I could not adjust the CO settings for some reason.

With the tilt sensor in place does the bike shut off if on it's side?

.
 
Hi dynobob, thak again!
I tried to lay the bike on her horizondtal, with handlebar touching the gruond, but she did not shut off.
Tomorrow evening will try to un-mount sensor and flip it manually, without the bike attached, just to be sure it's working

The CO regulation would have been my second question: my values are pretty strange if compared with the ones you all guys have: 114,100,100 ! and I do not managed yet to regulate them, have to study a little bit more before trying it. At a first glance, it seem that regulation it's forbidden on my bike too. But may be I'm wrong, I did not have enough time to study on CO chapter &co.

Since the fact that Tilt sensor wiring is the one as shown in picture, the Black shoud be "ground" , "white/grey" shoud be tilt sensor signal to the ECU, and orange "+12" because it's connected to TPS and pressure sensor too. Do you agree?
24 is tilt sensor, 9 is O2 sensor, 3 is water temp sensor, 21 is TPS assembly.

In my previuos configuration of the bike without tilt sensor, Orange and white/grey wer linked together, and error was "low tilt sensor value"
Titl sensor wiring.jpg
 
Hi dynobob, thak again!
I tried to lay the bike on her horizondtal, with handlebar touching the gruond, but she did not shut off.
Tomorrow evening will try to un-mount sensor and flip it manually, without the bike attached, just to be sure it's working

The CO regulation would have been my second question: my values are pretty strange if compared with the ones you all guys have: 114,100,100 ! and I do not managed yet to regulate them, have to study a little bit more before trying it. At a first glance, it seem that regulation it's forbidden on my bike too. But may be I'm wrong, I did not have enough time to study on CO chapter &co.

Since the fact that Tilt sensor wiring is the one as shown in picture, the Black shoud be "ground" , "white/grey" shoud be tilt sensor signal to the ECU, and orange "+12" because it's connected to TPS and pressure sensor too. Do you agree?
24 is tilt sensor, 9 is O2 sensor, 3 is water temp sensor, 21 is TPS assembly.

In my previuos configuration of the bike without tilt sensor, Orange and white/grey wer linked together, and error was "low tilt sensor value"
View attachment 106233

My eyes cant read the chart very well. I think orange is probably 5v to all the sensors, not 12v. Don't know for sure but the ecu is prob looking for either ground or 5v coming back from the sensor, if it doesn't see either it throws the code and assumes the sensor is bad. I remember a few years ago someone on the forum got stranded in Mexico because of a bad tilt sensor. A lot of people bypassed them. My bike never had one because it's a TE.

Did the light just start blinking or has it always blinked since you've had the bike. If the bike runs w/o the sensor I'd prob live w/ the flashing light...

Did you disconnect the battery for a bit after reinstalling the tip sensor?

.
 
Will this software give me any codes I may be throwing ? Sorry if this is a stupid question. I have all the connectors I need just not sure if my computer will be compatible. I only have modern day windows 11
 
Will this software give me any codes I may be throwing ? Sorry if this is a stupid question. I have all the connectors I need just not sure if my computer will be compatible. I only have modern day windows 11
Yes, It will give you error information.

It will not work when installed on a windows 11 PC. The workaround is to install VirtualMachine on your windows 11 PC, install a 32-bit windows version inside the virtual machine and run the Ibeat software on the virtual machine...
 
That's actually what I'm running on my Mac and wasn't sure if the VM would work. I wasn't expecting anyone to be up on the VM process so I kept it simple lol

Good looking out!
 
I published a document and uploaded it here a couple of years ago of a workaround to ibeat, it isn't super user friendly in terms of interface but fairly simple. It uses the same cable setup you need to connect to ibeat.

This document lists the different commands you transmit and how to decipher the responses you get. The commands are "H memory" maps which is the methodology used by the manufacturer of the microprocessor.

The responses are in hexadecimal so you have to convert that. Honestly less complicated than it sounds.

You will need some kind of termnial emulator. Windows Terminal used to come with windows, but I don't think it does anymore.

I also use the USB-Serial app on my android phone and connect that way. It is easier than schlepping my laptop, and I make changes on the trail if I carry the cable. I made a prototype bluetooth connector that worked but found other priorities over developing accessories for a 13-17 year old bikes (I have 08 Te510 and 12 txc310).

Be aware, there aren't as many error codes as people think there should. The main thing is picking up bad or out of ranges sensors. If the bike runs shifty, but the sensors are all in range you won't get any errors.

My gut feeling is that many problems you see reported on this site are attributed to ECU fault or failure but rarely are.

I uploaded these docs prior to the Cafe Husly meltdown so unsure if they are available. They show available to me. I also uploaded them to a thread at thumpertalk.com

If you can't get them DM me and if that doesn't work I can email.

Thread where I uploaded:
Thread 'Mikuni EFI- You CAN connect to it WITHOUT iBeat!!' http://www.cafehusky.com/threads/mikuni-efi-you-can-connect-to-it-without-ibeat.92547/


Jeff
 
I published a document and uploaded it here a couple of years ago of a workaround to ibeat, it isn't super user friendly in terms of interface but fairly simple. It uses the same cable setup you need to connect to ibeat.

This document lists the different commands you transmit and how to decipher the responses you get. The commands are "H memory" maps which is the methodology used by the manufacturer of the microprocessor.

The responses are in hexadecimal so you have to convert that. Honestly less complicated than it sounds.

You will need some kind of termnial emulator. Windows Terminal used to come with windows, but I don't think it does anymore.

I also use the USB-Serial app on my android phone and connect that way. It is easier than schlepping my laptop, and I make changes on the trail if I carry the cable. I made a prototype bluetooth connector that worked but found other priorities over developing accessories for a 13-17 year old bikes (I have 08 Te510 and 12 txc310).

Be aware, there aren't as many error codes as people think there should. The main thing is picking up bad or out of ranges sensors. If the bike runs shifty, but the sensors are all in range you won't get any errors.

My gut feeling is that many problems you see reported on this site are attributed to ECU fault or failure but rarely are.

I uploaded these docs prior to the Cafe Husly meltdown so unsure if they are available. They show available to me. I also uploaded them to a thread at thumpertalk.com

If you can't get them DM me and if that doesn't work I can email.

Thread where I uploaded:
Thread 'Mikuni EFI- You CAN connect to it WITHOUT iBeat!!' http://www.cafehusky.com/threads/mikuni-efi-you-can-connect-to-it-without-ibeat.92547/


Jeff
I believe PowerShell is the newest windows terminal application. I'm a Linux guy myself. Pretty cool you went so technical on this project! I am very impressed and will be looking into what you came up with.

Is there any way to find odometer miles on the ECU so I can confirm mileage of my bike?
 
I believe PowerShell is the newest windows terminal application. I'm a Linux guy myself. Pretty cool you went so technical on this project! I am very impressed and will be looking into what you came up with.

Is there any way to find odometer miles on the ECU so I can confirm mileage of my bike?
To my knowledge it only stores the running hours. But you could estimate if this is logical with you mileage...
 
I only remember seeing engine hours in iBeat.

Powershell is a different kind terminal, might be my nomenclature is wrong. You need something for serial communications.

I kinda messed with Linux some a couple years ago while deep in this project, on Raspberry PI. I just used the default serial console from the CLI.

Most of my reverse engineering was done using Node Red.
 
Back
Top