# Does the autoshift plugin work with the model 100?

**URL:** <https://community.keyboard.io/t/does-the-autoshift-plugin-work-with-the-model-100/5979>\
**Category:** Programming\
**Created:** [November 20, 2022, 4:39am UTC](https://community.keyboard.io/t/does-the-autoshift-plugin-work-with-the-model-100/5979 "2022-11-20T04:39:46Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![lgnakano](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/lgnakano/32/2441_2.png) [@lgnakano](https://community.keyboard.io/u/lgnakano)\
**Post date:** [November 25, 2022, 11:31am UTC](https://community.keyboard.io/t/does-the-autoshift-plugin-work-with-the-model-100/5979/3 "2022-11-25T11:31:16Z")

</div>

I had some help on this other thread:

> [@Is there a way to enable auto-shift, topsy turvy, or space cadet without recompiling firmware?](https://community.keyboard.io/t/is-there-a-way-to-enable-auto-shift-topsy-turvy-or-space-cadet-without-recompiling-firmware/5885/5):
>
> Before you flash the AutoShift example firmware, you’ll need to clear the EEPROM first. You can do this with the “factory reset” in Chrysalis. If you don’t, AutoShiftConfig will attempt to read configuration data from what is essentially a random location in EEPROM. Alternatively, you could comment out the AutoShiftConfig plugin from the example sketch. That’s very surprising behaviour. I have no idea what could be causing it, frankly, but it’s not really a valid test, because you’re getti…

If I turn off any settings related to the EEPROM, I can get the autoshift example to work.

I am not sure if reseting my keyboardio to factory settings using Chrysalis clears the EEPROM properly, since this plugin does not work for me with the EEPROM settings turned on.

---

_[View the full topic](https://community.keyboard.io/t/does-the-autoshift-plugin-work-with-the-model-100/5979)._