Hi,

thank you very much for your howto. It is very well written and correct. I just wnated to not, that the SKR Pico actually has a 3.3v source for the CAN Adapter to run from. it is located on the 5-pin SWD header. the middle pin is GND and the outer pin towards the tmc2209s is 3.3V.

https://gadgetangel.org/build/electrical/images/SKR_PICO_V1.0_Color_PIN_diagram.jpg

hi there, thanks for the write up. i followed all the insructions and i get the following error:

sudo ip link set up can0 type can bitrate 500000

output : Cannot find device "can0"

any ideas what i did wrong?

SET_TEMPERATURE_FAN_TARGET macro is used but never defined as a macro anywhere. Might be in the missing printer.cfg

When attempting to run the mostly stock command CHANGE_TOOL TOOL=1(or 2) I get this error
sh: 0: cannot open ~/printer_data/config/tool_swap.sh: No such file

I changed the directory to /home/pi/ in place of ~/ and I get this error:

/home/pi/printer_data/config/tool_swap.sh: 37: [[: not found
Error: Invalid input. Integer required.

So it looks like with /home/pi/ it can make it to the file but the tool_swap.sh code rejects the 1 and 2 stating they are not integers.

Commenting out the integer check in tool_swap.sh results in printer.cfg being erased.

I followed the instructions here:
https://github.com/rootiest/zippy-klipper_config/tree/master/extras/tool_swap
and I have made no adjustments to the code in swap_tools.cfg and tool_swap.sh but did add my tool configs to the tool1.cfg and tool2.cfg to prevent klipper errors.

Is your feature request related to a problem?Add [smart_effector] support to get_probe_limits macro
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I use the [smart_effector] in my printer.cfg, when running this it errored out on get_probe_limits

10:40:01 $ GET_PROBE_LIMITS
10:40:01 echo: Failed to detect probe in configfile

So I added the following in the macro.

{% elif config["smart_effector"] %}
# smart_effector probe section found
{% set probe = config["smart_effector"] %}
{% set has_probe = True %}

And it then functioned properly.

10:41:46 $ GET_PROBE_LIMITS
10:41:46 echo: Configured Probe X-Offset -5.00
10:41:46 echo: Configured Probe Y-Offset 0.00
10:41:46 echo: Configured Probe Z-Offset -0.1
10:41:46 echo: Minimum PROBE position X=-9.0 Y=-5.0
10:41:46 echo: Maximum PROBE position X=228.125 Y=212.125

Describe the solution you'd like
A clear and concise description of what you want to happen.
I am not familiar with adding this via pulls or anything, but found it useful. And wanted to let you know somehow or another.
So forgive if would be better another meathod.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I can use the [probe] definition on my system, but prefer [smart_effector] as it lets me set probe move acceleration
It would be handy to see other output related to the [smart_effector] features, but not required for the fix.

Additional context
Add any other context or screenshots about the feature request here.

Checklist

• [x ] I have included a clear description of the feature
• [x ] I have included a description of the solution
• [x ] I have included any alternative solutions or features I've considered
• [x ] I have included any relevant screenshots or videos

With the recent launch of the Beacon inductive sensor, their documentation requires the removal of the [probe] section and the usage of [beacon] instead.

Can we update the GET_PROBE_LIMITS macro to also include [beacon]? Currently, it errors out with the message "No probe or bltouch sections found".

Documentation: https://docs.beacon3d.com/quickstart/

Hi Rootiest,

Thank you for the awesome Macro and write up.

Quick question for you, when the COLOR_CHANGE macro is triggered on my setup I get the following error twice in my console.

Error on 'SET_IDLE_TIMEOUT TIMEOUT=': unable to parse

Have you seen this before?

Thank you for the help and time.

i try to use telegram plugin ( https://github.com/nlef/moonraker-telegram-bot/wiki ) + smart-m600 to send a notification whey runout is detected.
the telegram stuff is working but the command TELEGRAM_FILAMENT_RUNOUT
gives the error

Unknown command:"TELEGRAM_FILAMENT_RUNOUT"

how to setup correctly ?

I need to adjust mcu_timing because I keep getting communication errors when running QGL on my voron 2.4 350mm. I have no other can bus issues I could find but this is becoming more of an issue. Google led me here. I just can't figure out how to install and make this script work.

I’m not yet that proficient at writing macros with lots of variables passed, but the thought crossed my mind that the way your great smart M600 raises z up high and parks the tool head to hold temp.. with a few variable adjustments could be adapted to a great nozzle change macro..

1. heat hotend if not at set temp for nozzle change
2. retract/unload material if present
3. raise z to max, x to middle, send y bed back to limit
4. hold temp
5. resume after pause after nozzle changed
6. load new filament
7. end nozzle change

i’m going to try and figure it out but it’ll take me some time…. putting the idea out there in the event there’s interest from others.

cheers.

So i have been running a few test prints on my v0 using SKR Pico as CAN bridge, an EBB36 and a Pi3b. Everything is reliable so far, but the resonance testing. The test starts fine and works until ca. 100Hz and than crashes klipper with a "Timer too close" Error on the mcu (SKR Pico), not the pi nor the ebb36. Did you experience something similar?
I am wondering if during resonance testing maybe the SKR Pico's 3.3V supply gets overloaded by the CAN adapter, which i supply from that.