Extruder calibration on the Snapmaker A250

This article on the Snapmaker forum outlines how to do it. https://forum.snapmaker.com/t/extruder-calibration-a-must/7724/33

I use the calibration card to measure and cut the filament at 10 on the card, i.e 100mm plus the dead space before the 0. But since I measure the extruded distance also with this space it can be ignored.

Make sure the hot end has reached the correct temperature for the filament you are calibrating with. And issue the command to start feeding the 100mm of filament. Once that finished measure the amount of filament left.

I had 23mm left this time. Then it is time to do the calculation. I find it easiest to start the developer tools in the browser. In the console there I just enter the expressions in the article.

Then use the Luban console to enter the newly calculated value and permanently store it. If you want to understand the M-commands like M92 this page was good, https://snapmaker.github.io/Documentation/gcode/M092

Finally make a test run with the same command that feeds 100mm of filament. Mine fed a few mm of extra filament.

This time I ignored the difference but if you want you can re-calibrate. Use your calculated S value as the new E in the calculation and enter how much filament that has been fed. Repeat until you are satisfied.

Alternatives to get Nexa support in Home Assistent

I found the OpenMQTTGateway project and got really interested since it can open up for a lot of interesting integrations to Home Assistant. I bought a LilyGo to start experimenting and could get it to read 433Mhz devices like Nexa. All this is possible due to the RTL_433_ESP library.

I wanted also to be able to write to the devices since I have several power plugs that use Nexa. That is not possible with just the LilyGo and the radio module on it. With the STX882 it should be possible to transmit. So I bought both a STX882 and a SRX882. This page describes how to connect these to a ESP32 or NodeMCU.

Have not yet tried to make the full setup and connect everything. Will update this post once I have tried that.

Maytech remote and MakerX VESC

Building the tow boogie I am using the Maytech MTSKR1905WF Remote and the MakerX Hi200/75V VESC together with the Flipsky 65161 motor. Here are som some quick notes about the settings I have used to get things to work as I want.

There is a circuits diagram on the Maytech page which makes it easy to connect the remote receiver and the VESC together using the pinout picture on the MakerX page.


VESC App settings:

  • if you are using firmware version 5.03 (VESC TOOL 3.1) or above – turn off the phase filter, see here for more details
  • Set App to Use to UART – gives much quicker response than the Maytech recommended UART and PPM.
  • Use the Maytech recommended Control Type: Current No Reverse under VESC Remote
  • For quicker response on the remote, change the Input Deadband to something like 3% under VESC Remote

VESC Motor Settings:

  • Set Motor Current Max to 140A
  • Do not set Motor Current Max Brake to 0A but some negativa number like -1A
  • Set Absolute Maximum Current to 180A

Here are some screen dumps to better explain the settings

App to Use: UART
VESC Remote settings
Motor Settings


Reklamfritt – både vanlig reklam och reklambreven!

Äntligen går det lätt att regga sig för att slippa adresserad reklam! Plus man slipper den vanliga reklamen med!

Dock dom har lite kvar o fixa på sajten, jag klarade inte registrera mig via Flock utan var tvungen att köra Internet Explorer. Men det är nog bara lite barnsjukdomar så här i starten! Så hjälp dem gärna att sprida ordet och få chans och få ett år reklamfritt spotify med!!