There are settings if you compile your own to change up the memory/versions. I thought we were on the largest one. Adding memory (cost) to me is not as beneficial as figuring out exactly how to test it and optimizing what is there. I am confident the fluid guys have squeezed out ever drop of memory they possibly could. That is not to say I don’t think things can get better, Jamie proved that already, there are things to be fixed still. I will say if we have a test that everyone can replicate we then have an easy issue to present to the fluid team and they will surely be more interested in fixing it, or one of the smart people around here can more easily fix it for them.
As an example why I am not getting memory issues, I should swap out with one of you that is to see if it is hardware or not. We are using $3 boards, not $9 boards. It is starting to sound like I need to start using $9 boards just to eliminate a variable. My first instinct is never to throw more money at a problem, I throw time at it…probably even worse but that means it is cheaper for everyone after me.
The idea with the jackpot using the esp32 is price. I am not trying to make the best board in the entire world that works in every circumstance. I am trying to make a board as inexpensively as possible that works for 99% of us. This all started with the Ramps board and some drv8825 drivers, and every single time we have switched boards it just keeps going up in price. Ramps were $7 and the drivers were like $1.5 each. So to me it feels very weird to be at a $140 board almost 9 years later for honestly not all that much gained. When an SKR has an issue I spend a lot of time trying to fix it. Back in the day if a ramps had an issue I just threw it away if I did not see the issue in two minutes or less.