i2c filament sensor doesn't work with the latest firmwares
I purchased an early mk3 with a i2c filament sensor. I have been running PrusaLink 0.7.2 for a while but the only firmware that works is 3.10.1. Today I revisited the problem and tried the latest 3.14.1 but the problem is not fixed.
Prusa has obviously abandoned the hardware but is there a work around? Currently I am stuck on PrusaLink 0.7.2 because 0.8.1 require firmware higher than 3.10.1 and none of those firmwares work with the i2c sensor. Any advice or is it the end of the journey for this printer?
RE: i2c filament sensor doesn't work with the latest firmwares
I purchased an early mk3 with a i2c filament sensor. I have been running PrusaLink 0.7.2 for a while but the only firmware that works is 3.10.1. Today I revisited the problem and tried the latest 3.14.1 but the problem is not fixed.
Prusa has obviously abandoned the hardware but is there a work around? Currently I am stuck on PrusaLink 0.7.2 because 0.8.1 require firmware higher than 3.10.1 and none of those firmwares work with the i2c sensor. Any advice or is it the end of the journey for this printer?
What doesn't work with the MK3 and i2C PAT9125 (laser) filament sensor with FW 3.14.1?
RE: i2c filament sensor doesn't work with the latest firmwares
I purchased an early mk3 with a i2c filament sensor. I have been running PrusaLink 0.7.2 for a while but the only firmware that works is 3.10.1. Today I revisited the problem and tried the latest 3.14.1 but the problem is not fixed.
Prusa has obviously abandoned the hardware but is there a work around? Currently I am stuck on PrusaLink 0.7.2 because 0.8.1 require firmware higher than 3.10.1 and none of those firmwares work with the i2c sensor. Any advice or is it the end of the journey for this printer?
What doesn't work with the MK3 and i2C PAT9125 (laser) filament sensor with FW 3.14.1?
It is totally dead, you insert the filament and it just ignores it. Put 3.10.1 back on and all is well with the filament sensor again but your can't run the latest PrusaLink 0.8.1.
Your username reminded me of a chat we have previously had about this issue on Github. Back in May 2024 you indicated that was a known issue and would be fixed in 3.4.1. Sadly, it didn't happened that way and it is still broken.