FAQ & Troubleshooting¶

It can occasionally happen that the flash process gets stuck. This problem is known and is caused by a serial overload during the flash process.

In this case, please simply switch off the printer and switch it on again. FreeDi will detect the corrupted screen firmware and start to flash the firmware again.

Note: Sometimes it needs several attempts.

When I release a new version, you will find them in the release section.

Normally you will find important release information there such as update and install notes.

Sometimes there will be even announcements at the issues section that additionally will pop up on your Mainsail notification bell.

Check this first before you update - that's why I use announcements!

In any case: Check if the additional information/instructions I gave solves your problem.

If not, contact the community on discord or open an issue or a discussion here on git.

Firmware update failed: SerialBase.read_until() got an unexpected keyword argument 'expected'

It tells you that you installed an older version of pyserial.

You must have at least pyserial v3.5 for FreeDi to work.

To solve this, please install pyserial 3.5 (or higher) by doing this:

/home/mks/klippy-env/bin/python3 -m pip install pyserial==3.5

If you updated klipper, it will delete the klipper klippy/extras folder and break symlinks by that.

On FreeDi v2.03 and later I included an auto-repair-mechanism for that.

Everyone can simply run the installation script to fix this:

cd ~/FreeDi && ./install.sh

Simply run this command, to delete, download and install FreeDi again:

cd ~ && rm -rf FreeDi && git clone https://github.com/Phil1988/FreeDi ~/FreeDi && cd ~/FreeDi && ./install.sh

On some installations it can occasionally happen that your local git doesn't fetch the right tags or heads.

For v2.00 if you see this:

It means that you are still on v1.42.

To check it yourself, you can go to the commits and check the number you are seeing. In the example the commit 30c9b57 is not the latest and was pre v2.00:

There is no such a thing as "do always this and it fixes it for you" and you need to check why it is not seeing the latest update with:

cd ~/FreeDi
git remote -v
git remote show origin
git config --get-all remote.origin.fetch
git rev-parse --abbrev-ref --symbolic-full-name @{u}

In most cases this will be enough to fetch the missing tags:

cd ~/FreeDi
git fetch --tags

Some don't see the branch refspec and need to add this:

cd ~/FreeDi
git config --add remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*"
git config --add remote.origin.fetch "+refs/tags/*:refs/tags/*"
git fetch origin