# PicoMite 6.00.02 RC17 for PicoCalc **URL:** \ **Category:** PicoCalc\ **Created:** [April 22, 2025, 6:16am UTC](https://forum.clockworkpi.com/t/picomite-6-00-02-rc17-for-picocalc/16943 "2025-04-22T06:16:09Z")\ **Posts on this page:** 1\ **Showing post:** 25
**Author:** ![adcockm](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/adcockm/32/1664_2.png) [@adcockm](https://forum.clockworkpi.com/u/adcockm)\ **Post date:** [April 24, 2025, 11:46pm UTC](https://forum.clockworkpi.com/t/picomite-6-00-02-rc17-for-picocalc/16943/25 "2025-04-24T23:46:15Z")
There _might_ be solution to the keyboard disconnect issue here… It mentions “other bugfixes from current firmware related to i2c and such”: > [@Plans for keyboard / battery STM32 firmware](https://forum.clockworkpi.com/t/plans-for-keyboard-battery-stm32-firmware/17009/2): > > I don’t know about the plans, but I have my own version with various fixes and improvements… [http://ffauploads.com/picocalc\_keyboard.ino.bin](http://ffauploads.com/picocalc_keyboard.ino.bin) differences from stock shipped firmware: ability to read backlight of screen and keyboard ability to read battery % allows setting backlight of keyboard other bugfixes from current firmware related to i2c and such differences from both stock and current firmware: improved backlight curves (in my opinion) for display and keyboard ability to read batte… Though it appears to only be available as a binary, with no link to sources (yet). I found another updated keyboard firmware, with sources, that I mention below that post with links, but it only added features and didn’t seem to have any bugfixes. Perhaps the problem wasn’t in changes to PicoMite, but was something to do with the keybaord firmware all along? I’ll test this out when I get a chance. Though since the problem is hard to reproduce, it might help if others try it too. --- _[View the full topic](https://forum.clockworkpi.com/t/picomite-6-00-02-rc17-for-picocalc/16943)._