Author Topic: Upgrading Anet A8 Firmware  (Read 8901 times)

0 Members and 1 Guest are viewing this topic.

Offline bostonmanTopic starter

  • Super Contributor
  • ***
  • Posts: 1739
  • Country: us
Re: Upgrading Anet A8 Firmware
« Reply #25 on: September 29, 2021, 01:06:22 pm »
I think it’s personal preference. I’ll still check the leveling manually should I remove the bed and reassemble it because if it’s far off, then the Z axis will constantly be working to compensate.

I’m just tired of checking the leveling and think the BLTouch is a great tool.

Unfortunately it uses lots of memory (from my understanding), and this is one drawback.
 

Offline bostonmanTopic starter

  • Super Contributor
  • ***
  • Posts: 1739
  • Country: us
Re: Upgrading Anet A8 Firmware
« Reply #26 on: October 13, 2021, 01:18:27 am »
I'm not understanding the differences in bed leveling techniques.

It seems bilienear is the one to use for (after setting in the firmware) nine-point calibration, but the others don't seem to have a clear explanation.

Does anyone know the differences?

Also, from what I can tell, bed leveling uses lots of memory. Why can't bed leveling be turned off in the firmware and the code added to the gcode? I'm assuming it has something to do with where the calibration data is stored as I could only conclude that it's stored in RAM memory and not written to the SD card.

Does anyone know the answers to the above questions?


Edit: these are the ones listed:

//#define AUTO_BED_LEVELING_3POINT
//#define AUTO_BED_LEVELING_LINEAR
//#define AUTO_BED_LEVELING_BILINEAR
//#define AUTO_BED_LEVELING_UBL
//#define MESH_BED_LEVELING
« Last Edit: October 13, 2021, 01:34:06 am by bostonman »
 

Offline gmb42

  • Frequent Contributor
  • **
  • Posts: 294
  • Country: gb
Re: Upgrading Anet A8 Firmware
« Reply #27 on: October 13, 2021, 09:14:35 am »
I'm not understanding the differences in bed leveling techniques.

It seems bilienear is the one to use for (after setting in the firmware) nine-point calibration, but the others don't seem to have a clear explanation.

Does anyone know the differences?

Also, from what I can tell, bed leveling uses lots of memory. Why can't bed leveling be turned off in the firmware and the code added to the gcode? I'm assuming it has something to do with where the calibration data is stored as I could only conclude that it's stored in RAM memory and not written to the SD card.

Does anyone know the answers to the above questions?


Edit: these are the ones listed:

//#define AUTO_BED_LEVELING_3POINT
//#define AUTO_BED_LEVELING_LINEAR
//#define AUTO_BED_LEVELING_BILINEAR
//#define AUTO_BED_LEVELING_UBL
//#define MESH_BED_LEVELING

For 3POINT, LINEAR and BILINEAR see Automatic Bed Levelling.
For UBL see Unified Bed Levelling.
For MESH_BED see Mesh Bed Levelling.

I guess if you can't compile Marlin down to fit your current board you'll have to upgrade to a better one that can cope.
 

Offline bostonmanTopic starter

  • Super Contributor
  • ***
  • Posts: 1739
  • Country: us
Re: Upgrading Anet A8 Firmware
« Reply #28 on: October 13, 2021, 01:52:08 pm »
I had read that on Marlin before, but I find it's not exactly clear on the points probed; nor does it seem clear to me. All I know is to use bilinear (which is what I've un-commented).

So far with all the features I want enabled, I'm only at 86% or so. The two features that are a game changer are SDCARD READ ONLY, and SD SUPPORT.

Again, it's not very clear on what these both do. SD SUPPORT allows for power recovery loss. Disabling this saves lots of space, but it states disable this if you don't need to print from the SD Card. SD CARD READ ONLY states to enable this for SD card printing.

So SD SUPPORT implies you can't print from the SD card unless this is enabled, but then SD CARE READ ONLY implies to enable it for SD printing.

https://crosslink.io/marlin-2-0-memory-usage-by-feature/

My only other question that I had asked is can bilinear leveling be enabled in the gcode in order to save memory? This way the gcode would tell the printer to perform bilinear and this would free up more memory in the firmware.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf