ok. the way the config works is you don't actually enter the dpi you want, there's a built-in calculation it does and you have to have the right variable to get the resolution you want.
// Enter into the brackets which DPI you want available.
// The numbers represent the DPI: for example (3+1)*100 = 400 DPI, (15+1)*100 = 1600 DPI.
// So the below example can be read as: 400, 800, 1600.
// uint8_t dpis[] = {3, 7, 15};
so in your case you want:
uint8_t dpis[] = {7, 13, 19};
## representing 800, 1400, 2000 dpi
- now, if the 800 & 2000 are in the wrong orientation to what you prefer we can switch it as it's saying that the first number "800" is profile 2, "1400" is profile 1/default, and "2000" is profile 3
// The first number is for Profile 2 (rear side button)
// The second number is for profile 1 (Default profile)
// The third number is for profile 3 (front side button)
if you were trying to change it and it wasn't changing, my guess, the values were stated in another one of the files. so i opened them all did a grep search for "dpi" and sure enough it was noted in "bst3360.lss" & "main.lst" as well with the default values you're trying to change.
i've run across this before, you're supposed to change a value in... say "config.c" but that same value is stated in a couple other files it references when it compiles and the "config" file has the least authority over the other files.... so the variables you're trying to change, don't actually get changed.
also, when compiling, make sure you either delete the previous .hex file or at least rename it so you get a clean, fresh compiled file & there can't be an issue with duplicate file names, etc... not saving the new hex file because the file exists or is open....
i like to keep an organized set of folders (OUTSIDE of the "firmware" folder because the compiler has full authority over the "firmware" folder and can delete any usable hex files) with successful hex files, naming the folders with what i'll know the changes were. as all the hex files will have the same name
/mouse
/initial working/bst3360.hex
/changed dpi/bst3360.hex
another note when compiling after the 1st attempt.... make sure you "clean" before you rebuild "all" meaning...
// To rebuild project do "make clean" then "make all". (this clears out all the intermediate config & other "old" files)
config is also defaulted to "Teensy 2.0" MCU = atmega32u4, pretty sure that's what you're using, but please confirm.
i don't have the hardware yet to test it, but i didn't have any issues/errors compiling it either, so give it a shot & see if it works. you should easily be able to tell the resolution difference, the mouse will feel a lot quicker. going from 400/800/1600 -to- 800/1400/2000
