I have received PMs and emails from people who cannot rename the zipped BixCheck42.txt attachment, above, to BixCheck42.exe. For a Windows-based system, the steps are:

- Ensure that you are logged into your computer with ADMINISTRATOR rights.

- Click on zipped attachment, above, then select SAVE to a local destination of your choice.
- Unzip the single txt file in the zip file. Save it locally.
- From Windows Explorer of from My Computer, navigate to the local txt file, right click on it, select RENAME (this step is important), then edit the file name to BixCheck42.exe.
- Reply OK to the two subsequent warnings about renaming file extensions.

Alternative:
- Download and unzip as above.
- Move the unzipped txt file to your root directory (e.g., C:\). This step isn't essential but it will make navigation easier in the next steps.
- Run the DOS Command Prompt by clicking on START, then RUN, then typing CMD, then clicking OK.
- Using DOS commands, navigate to the folder that contains your txt file (e.g., CD C:\) .
- Type in the following DOS command, then press ENTER key:
RENAME BixCheck42.txt BixCheck42.exe
- Copy the renamed exe file to your folder from which you wish to run BixCheck.

I've been using the 2.02 bixcheck software but still haven't been able to upgrade. I have a second 115 in my garage that had the board out so I could send to Bixby to fix the resistor for a #3 light. I put the board back in and tried to upgrade that one which also has 2.02 on it. I'm running into same problem of not getting past the "waiting for bootloader. plug in stove".
I'm now thinking it's a communication problem between installer program and bootloader and that it's either the cable, drivers, or com port. I know it's possible but I don't think two different boards have bad bootloaders.

hub0000 wrote:


I'd bet your cable, didn't you say in an earlier post you were doing something with tieing rts and cts?

The easist way is to find and old laptop that has a serial port, then buy the
bixby cable. (I think Rona also sells a cable that works)

You will not have any issues this way.

I didn't use the RTS and CTS wires since the stove doesn't use handshaking. That could be the problem and I've been thinking that is the most likely cause but I have no trouble with the monitor and checkout parts of the program. I also talked to a tech support rep at FTDI and he said that at the low baud rates I'm using to connect that not using handshaking should not be an issue.

Hub0000,
I had the same problem and I sent it to Bixby-they loaded 2.71 with no problems. I,like you, could use part of the program to run a test but it would not load 2.71. I think Blume said he will load it for you-send it out it is less aggravation. If its working wait until summer. I sent mine in during the off season. Good luck.

I'm running win 7 & I was having a problem renaming the file because the file type extension was hidden. I went into my computer, clicked organize, clicked folder and search options, clicked view, UNCLICKED hide extensions for know file types.

Easy as pie after that. I'm going to try it out tonight when I get home.

Thanks

if when starting ash dump makes 3 rounds without stopping on 2.02, on 2.06 it will stop momentarily each time around, also will not make ash dump with bad igniter on 2.02

Hello everyone, I have to get this thread back to the top because I just helped my neighbor install a used 115 in house and we are running into the exact same issue. I have been running mine for 4 years now I think on corn and haven't tried to upgrade to 2.71. My neighbor is running pellets so we tried to upgrade his with no sucess. The stove "talks" to the computer through bixcheck 2.06 just fine. It gets stuck on the waiting for bootloader like the other previous posters. I am not sure on the software in the stove 2.02 or 2.06 but the stove falls in the category of the 2.06. Did anyone figure out what the issue is?

Mary, this is the cable I bought from you the 1st year along with the totes etc. Any ideas?

Winter, I haven't gone back to re-read the thread, but I'm wondering if you're using the correct version of Bixcheck.
forum.iburncorn.com/wiki/index.php/Bixby...e_with_your_Stove.3F

Data structure has changed between different versions of stove firmware, so the bixcheck data versions must match.

Can you get to the Monitor screen and press Readback? That would show you the stove firmware version. You'd also be able to see whether the stove data format matches the bixcheck data format. These fields should be green (not red) along with the checksum fields. Apologies if this has been covered earlier.

yes the 2 are talking to eachother on 2.06.