Replies: 2 comments 21 replies
-
|
yes this can be the Mesh Inset. change the mesh Inset values. you can find them in the Mesh settings in the menu. |
Beta Was this translation helpful? Give feedback.
-
|
thats odd, are you sure the firmware flashed? if you are unaware, sometimes you have to rename the file if it has the same name or it won't flash the new file. so when you click Maximize Area, it should reset the mesh insets (max/min, x/y) to the max and min they can be. Center Area basically just sets the mesh square evenly. even if you change the configuration parameters, it shouldn't load old settings as if it were somehow hard coded, it really should update them. so you're not able to change the physical bed size in the settings?? I know there is an option to set it using custom Gcode commands, but I think with the more recent versions I disabled that to make room for other things. but it should work normally through using the LCD. maybe you if you can upload a video id be able to see whats going on. and to get things straight, youre able to use the printer normally at 400x400? you're able to print and everything moves as it should? but the only issue here is probing for a bed mesh right? so like only half the bed is probed? so in Control menu, Physical Settings, once you change the Y/" in which menu is it restricting you going passed 230? |
Beta Was this translation helpful? Give feedback.
-
|
I just checked this out and realized you need to "store settings" after changing the bed size, thats why it was restricting to 230. |
Beta Was this translation helpful? Give feedback.
-
|
With the precompiled firmware I can change the bed physical settings to a max of 230 but no higher in the UI. However I have compiled my own with it set to 400 and that seems to read just fine. I have not attempted to print anything without needing first to complete a bed level. But I have used other settings outside the level menu and it is aware that the bed is 400X400. I have set the mesh inset sizes once I had the physical settings correct from my compiled version. I did also hit store settings after setting these values. Do I need to completely restart the printer after saving these settings? Or should I be able to run it instantly? I have tried running after store settings and it still uses 230x230 even though the mesh size and physical size have been made to 390x400 |
Beta Was this translation helpful? Give feedback.
-
|
you should not need to restart after saving the settings. I tested this and I do not run into the 230 restriction once settings are stored/saved. I have also posted a new release build for March you can try out. which precompiled firmware file was it you were using? also if you can either post some pictures or video, or write out the steps you take like:
I mean I dont know what more I can say to help if it works as it should on my end. What I might be able to do is have it automatically save after changing the values. in Marlin\src\lcd\e3v2\proui\dwin.cpp line ~3000 void SetBedSizeX() { HMI_value.axis = NO_AXIS_ENUM, SetPIntOnClick(X_BED_MIN, X_MAX_POS, ProEx.ApplyPhySet), WriteEeprom(); }
void SetBedSizeY() { HMI_value.axis = NO_AXIS_ENUM, SetPIntOnClick(Y_BED_MIN, Y_MAX_POS, ProEx.ApplyPhySet), WriteEeprom(); }
void SetMinPosX() { HMI_value.axis = X_AXIS, SetPIntOnClick( -100, 100, ProEx.ApplyPhySet), WriteEeprom(); }
void SetMinPosY() { HMI_value.axis = Y_AXIS, SetPIntOnClick( -100, 100, ProEx.ApplyPhySet), WriteEeprom(); }
void SetMaxPosX() { HMI_value.axis = X_AXIS, SetPIntOnClick(X_BED_MIN, 999, ProEx.ApplyPhySet), WriteEeprom(); }
void SetMaxPosY() { HMI_value.axis = Y_AXIS, SetPIntOnClick(Y_BED_MIN, 999, ProEx.ApplyPhySet), WriteEeprom(); }
void SetMaxPosZ() { HMI_value.axis = Z_AXIS, SetPIntOnClick( 100, 999, ProEx.ApplyPhySet), WriteEeprom(); } |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to pop back and update now that I've had time to try more things. I downloaded the April N32 compiled file and it seems to be working great and respecting the new sizes! |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problems with auto leveling on november firmware. Not level over 220x230 |
Beta Was this translation helpful? Give feedback.
-
|
i uploaded a new release you can test out: when they are uploaded you can choose the file and let me know if this works and fixed the problem. |
Beta Was this translation helpful? Give feedback.
-
I have a question: How to enable or find the input shaping? I try to enable in configuration_adv.h file, but i can't find nothing in display |
Beta Was this translation helpful? Give feedback.
-
|
after Main Menu > Control > Motion > Input Shaping |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I have uploaded a new release this should be fixed |
Beta Was this translation helpful? Give feedback.
-
Hi! I have attempted to compile my own firmware from this source code and have changed any values that I have been able to find to allow my 400x400x400 Aquila X3 Max to use a modified version of the Aquila X3 firmware.
However, I am running into a problem during the Auto Mesh Level where it only ends up probing 1/4 of the bed as if it was still a 220x230 bed like the X3. I have checked the settings in the firmware before compiling and even again once it has been flashed on the printer and everything shows 0 min and 400 Max but the leveling isn’t respecting it. Could anyone assist me with this? I’m not sure what I’ve missed
Beta Was this translation helpful? Give feedback.
All reactions