Should work and that is a good price. You will need to buy the smaller 4 pin connector shell, DigiKey carries them but I don't have the part number handy. Rona should have it though. The USB versions of the cable require 2 drivers plus going into the advanced settings of the port the cable is on to set it to one Bixcheck can see. Not for the computer beginner.

MaryB I bought this cable and put the locking four pin connector on it. It seems to work however I seem to be getting some side effects. If I unplug the stove from the ac and plug it back in the stove doesn't seem to do the self test of it's systems. Also, I think the convection fan kicks off when the stove shuts down before the stove is cool. Some of the data I'm reading in bixcheck doesn't seem to make sense although I'm not sure if that's because I have version 2.02 on my stove and I was reading it with the version for 2.06.

Set to 9600 bits per second, data bits 8, parity none, stop bits 1, flow control none

Thanks for responding

If you have a LOT of USB devices on your computer (I lost count on mine, around 14 I think) the serial port number can be assigned to high for the uploader to work. Think it needs to be 8 and below as far as com port.

Hub, you should be running only the same version of software from which the firmware was installed on the stove. The stove parameters don't always agree between different versions. At one point, they were remapped to accommodate new features. This would explain some of your funny readings in Bixcheck. Consider reinstalling from the latest ver (2.71) then doing a Calibrate.

The com port that the cable is using is 6. Why would the cable stop the stove from going through it's self test when plugged in?


I tried upgrading but I had trouble getting the software to load. It would say "Waiting for bootloader. Plug in the stove". Do you need to unplug the igniters?

I appreciate the help

Hub, here's how to load the firmware: forum.iburncorn.com/wiki/index.php/Bixby...re.29_Using_Bixcheck .


You might need to wait a while after you plug the stove in. Some patience is needed.

For an earlier version, the recommendation was to unplug the igniters in case they came on and burnt themselves out. I think that that quirk was fixed in the latetest (ver 2.71), but it's easy to unplug the igniters. I'd do it as cheap insurance. Just label them so you don't later reconnect them backwards.

I tried several times last night and I still couldn't get it to upgrade. It wouldn't get past where it says "waiting for bootloader. plug in the stove" in bixcheck. Does the bootloader only run when you first plug in the stove?

If you have your bixcheck cable attached to the stove and you plug the stove in to the ac, is it normal for the stove to still do the p.o.s.t? Mine does not

Thanks

I tried to update again yesterday without success. From things I read on the forum, I thought I was going to get it because the first 3 or 4 times I tried the fans came on when I plug the stove in. It had never done that on any previous attempts. I couldn't get past the "waiting for bootloader plug in stove"
I have a 115 with version 2.02. I have stove 9041.
Has anybody else had trouble upgrading from version 2.02?

Thanks

Hub, I haven't downloaded software often, but from what I read, it should take IF there is an uncorrupted bootloader in the stove. If not, then you'd have to replace the board in order to upgrade the firmware.

You are sure that your cable and drivers are working? That would be another explanation for your prob.

Some users have reported trying multiple times and waiting long before the download "took." No harm in persisting and waiting, say, 30 minutes with each attempt.

Have you checked out the following multipage thread?
forum.iburncorn.com/viewtopic.php?t=6417
I can't say that I read it to the end, but it is on the subject of downloading and perhaps you'll find a useful nugget of information.

Here's another thought. Are you sure that your computer isn't blocking traffic on the COM port? If not sure, consider disconnecting from the internet then temporarily disabling all security. This is just a long shot. I'm not saying this from any experience, which is a nicer way of saying that I'm not sure that I know what I'm talking about.