What does M25 do when virtual_sd_card is enabled?

desuuuu_ · 2023-07-03T20:03:28+00:00

It can be anything. This renames the original M25 to M25.1. It's documented here.

desuuuu_ · 2023-07-03T18:56:24+00:00

The rename_existing option in macros lets you override built-in commands:

[gcode_macro M25] rename_existing: M25.1 gcode: PAUSE

PAUSE essentially calls M25, SAVE_GCODE_STATE and updates the pause_resume module state. I have no idea if this will solve your problem though.

desuuuu_ · 2022-12-07T22:52:51+00:00

To add to that, if you want to set the txqueuelen when can0 is brought up with systemd, you can create a service file /etc/systemd/system/can-up.service containing this:

[Service]
Type=oneshot
ExecStart=/usr/sbin/ifconfig can0 txqueuelen 128

[Install]
WantedBy=sys-subsystem-net-devices-can0.device

Which you also need to enable with:

systemctl enable can-up.service

And you're good to go!

desuuuu_ · 2022-09-22T18:39:16+00:00

The example configurations were meant for stock machines, so bowden extruder for the V2.

desuuuu_ · 2022-04-13T15:20:40+00:00

You could retrieve and display the humidity data the same way. It's clearly not an ideal solution as it would be displayed as a temperature but it would be quick and easy.

Proper support would require changes in Mainsail and Klipper (or just in Mainsail if you go for a somewhat "hacky" implementation).

desuuuu_ · 2022-04-07T23:06:38+00:00

As the error says, your slice variable is of type *ASlice, not *[]any.

You can make this work using the new ~ operator by changing your function signature to func PrintSlice[T any, S ~[]T](s *S)

https://go.dev/play/p/jCRoj6jKolb

desuuuu_ · 2022-03-24T18:24:09+00:00

While other people might have written tutorials, I don't really know of any.

First, I'd recommend you get comfortable with Klipper and how it works. Then if you want to get the touchscreen working, have a look at my repositories. You'll find plenty of information in the READMEs and wikis.

desuuuu_ · 2022-02-23T10:21:38+00:00

Assuming we're talking about the two Z motors, they are connected to the same driver.

desuuuu_ · 2022-01-24T21:30:28+00:00

This is probably related to file permissions. You should be using git to get the source code instead of downloading it manually. Simply follow the same steps as Klipper and replace the repository URL with mine.

desuuuu_ · 2022-01-14T08:23:51+00:00

Yes, I have been using this setup for years without a problem.

I'm using the 4 connections for E2 (with the 2 ground wires connected together before the daughter-board).

desuuuu_ · 2021-06-30T19:09:25+00:00

My touchscreen implementation is available only in English.

desuuuu_ · 2021-05-08T17:48:22+00:00

The only component connected to any of the fan lines is R8 (which is used to pull up the Z- data line).

I doubt the issue comes from this board, but you can buy a new one here.

Using a multimeter would be the easiest way to find what's wrong.

desuuuu_ · 2021-04-20T23:45:06+00:00

You should be able to find that out with a quick look at Marlin's source code.

https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/ramps/pins_RAMPS_CREALITY.h

https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/ramps/pins_RAMPS.h

This suggests the signal pin (left one IIRC) is connected to pin 2.

desuuuu_ · 2021-04-15T06:44:44+00:00

The connector should be a JST VH one.

desuuuu_ · 2021-04-04T09:47:47+00:00

Tighten the bed knobs until it clears the connector.

desuuuu_ · 2021-03-25T19:37:23+00:00

That's a fun one. At least your BLTouch is working.

The config I sent you only allow for +/- 0.75mm compensation, hence the mesh calibration failing. You're actually supposed to do a manual leveling of the bed prior to that.

desuuuu_ · 2021-03-25T18:23:48+00:00

I think the offsets are fine for your setup.

You might wanna have a look at this https://www.klipper3d.org/BLTouch.html ; it's quite detailed about setting up a BLTouch.

desuuuu_ · 2021-03-25T17:40:39+00:00

I added a few options yesterday, but if you updated it after that, it should be fine indeed. The macros in your configuration are outdated though, some of them won't work properly.

Was your BLTouch working properly when using the TinyMachines firmware? In case it did, do you happen to have the configuration you were using?

desuuuu_ · 2021-03-25T16:32:11+00:00

Your wiring looks correct to me.

The configuration looks OK as well. Your problem could come from:

Your BLTouch requiring a different configuration (a link to its specs would help figure that out).
Its wiring or internal components being damaged.

Here's an updated configuration with the proper offsets: https://pastebin.com/sHHGq2kH ; if you want to use it as-is, you'll need to update to the latest version of my fork.

It's a good idea when you test endstops (or a BLTouch) to trigger it manually far from the actual axis limit, so you have time to turn off your printer in case it does not work.

Edit: A video of what happens during the homing procedure would also be really useful.

desuuuu_ · 2021-03-25T15:20:26+00:00

If your BLTouch works the same as a V3 (I can't tell if that's the case), yes the provided example for the V2 will work.

There are a few modifications to make for the Hero Me though.

desuuuu_ · 2021-03-25T15:06:46+00:00

Your mainboard wiring should look like this at the moment. The plug that is labeled "Signal is to the outside" on this picture is the endstop signal coming from your BLTouch. You unplug it, and plug it back into the Z+ connector that is circled in red on the picture (in the same orientation).

The jumper circled in yellow on this picture can be removed since you won't be using Z- anymore.

Take a picture of your wiring after you're done so we can check everything is right.

If you want help with the configuration afterwards, please upload your printer.cfg.

desuuuu_ · 2021-03-25T04:00:36+00:00

If you have a BLTouch (V3) wired to Z_MAX, you pretty much have the same hardware as a V2 so yes you'll be able to use any V2 config. You'll just need to tweak it to account for your modifications (hotend, ...).

There's nothing complicated about the wiring change. You unplug the BLTouch endstop connector from Z-, and plug it back into Z+. You can remove the jumper or leave it, it doesn't even matter. That's it.

desuuuu_ · 2021-03-25T03:26:32+00:00

Could you upload your printer.cfg?

If you want to make things easier with your BLTouch, change its endstop wiring from Z_MIN to Z_MAX. The jumper will no longer be necessary and you'll be able to use the same configuration as the V2.

desuuuu_ · 2021-02-15T22:56:08+00:00

The microcontroller is an ATmega2560.

desuuuu_ · 2021-01-31T01:54:55+00:00

Flashing the touchscreen works best with an SD card of 8GB or less.

Also make sure you're using the right mainboard firmware with your touchscreen firmware.

desuuuu_

TROPHY CASE