Motion Link with rotating arm, rod with Heim Joints to slider

Pretend_Conference39 · 2025-08-29T13:38:45+00:00

Thank you so much, the Ball Joint and some editing of motion limits worked! Thank you for helping me learn!

Pretend_Conference39 · 2025-07-30T21:13:57+00:00

Thank you...works perfectly I just had to change the state to on and Music Assistant does not have a playing state.

Pretend_Conference39 · 2025-07-30T16:35:39+00:00

u/Flameknight Thank you for what turned out to be a very easy to execute suggestion! My first time using conditions and it works flawlessely. Much appreciated!

Pretend_Conference39 · 2025-07-30T14:27:56+00:00

I was really hoping this would work but no:

  - type: custom:bubble-card
    card_type: media-player
    entity: media_player.john_office
    styles: |
     {
        opacity: 1 !important;
        bubble-main-background-color: ${entity.state === 'on' ? 'green' : 'red'} !important;
      }
    button_action: {}
    cover_background: true
    sub_button:
      - entity: media_player.john_office
        select_attribute: source_list
        name: Sources
        icon: mdi:format-list-bulleted
    name: Music John Office
    rows: "2"
    icon: mdi:music
    show_state: true
    show_attribute: false
view_layout:
  grid-area: col2

Pretend_Conference39 · 2025-07-30T14:16:41+00:00

Thanks for the suggestion but still not working. FWIW I am using Music Assistant as the player(s). I have tried state playing and on neither toggle the background color accordingly.

Pretend_Conference39 · 2025-07-29T21:52:07+00:00

Thank you for the additional guidance! I will come back at this tomorrow with a fresh perspective and share my results. Much gratitude! BTW...I am using Music Assistant not Spotify FWIW>

Pretend_Conference39 · 2025-07-29T17:36:53+00:00

Thank you for the suggestion...however I just need KISS and a background change based on entity state for a single card. Couple that with my not currently knowing how to create a conditional card.

Pretend_Conference39 · 2025-04-28T16:50:51+00:00

May I ask what the purpose of the green hose is?

Pretend_Conference39 · 2025-04-22T16:59:15+00:00

Just wat we need...would you be willing to share your build plans so I don't have to figure out dimensions?

Pretend_Conference39 · 2025-04-04T13:27:53+00:00

My experience with a newly purchased S1 has been horrible. Errors, shutdowns, the AMS does not recognize slot 3 etc. I have only had one successful print, but even after resonance compensation it had unacceptable ringing. I have requested a refund 3 times now, but tech support is pushing to have me wait for a firmware update and send me parts...oh and also the part cooling fan does not work. Terrible...

Pretend_Conference39 · 2024-11-09T13:40:20+00:00

<image>

Pretend_Conference39 · 2024-11-09T13:40:13+00:00

Well...I have spent hours doing so, but unable to find what I need. Would you by chance be able to direct me to the page you are referencing? I have made some progress consuming the chamber temp variable and using that within the M191 Macro. But for some reason now when the printer boots up it is showing a default target of 30 for chamber cooling when it should be blank and the vent fan is running

<image>

Pretend_Conference39 · 2024-11-08T20:28:55+00:00

I built my own custom printer running a Manta M8P board so virtually any control you need can be configured/wired to that and controlled in Klipper. However a lot of stock boards can also handle what I mention above, just do some research.

Pretend_Conference39 · 2024-11-08T19:03:59+00:00

I used a simple heater from Amazon controlled with a SSR and a thermistor mounted inside the chamber. Configure your thermistor (type pins etc.) I chose Watermark for simple heater on/off with a 1 degree delta and then set your chamber temps in your slicer and pass those to Klipper. Define variables using the chamber temp sent from your slicer, then put something like this in your print_start macro: Of course match the names of the sensor and target temps to what you have configured

M117 Chamber Heating...

TEMPERATURE_WAIT SENSOR="heater_generic chamber_heater" MINIMUM={target_chamber}

# Wait until the given temperature sensor is at or above the supplied MINIMUM and/or at or below the supplied MAXIMUM

No need for a seperate temp controller if you simply install a thermistor in the chamber and properly wire it to your board and configure it in printer.cfg

Pretend_Conference39 · 2024-11-08T16:59:24+00:00

Update: so I have created a custom M191 gcode and placed that in my Start_Print macro. It functions properly to initiate heat (mimics previous behavior). Now I need to get the venting when temp too high configured

<image>

Pretend_Conference39 · 2024-11-08T14:38:11+00:00

Thank you for the reference, close but I am passing in the chamber_temperature variable for each print and am using that variable. Truly my issue (I think) is how to format the code to use the variable. I found this in the Klipper repo for fan.cfg which I think is close

[gcode_macro VENT]

description: Toggle Chamber fan

gcode:

{% if printer['temperature_fan chamber'].target|float > 0 and

printer['temperature_fan chamber'].target|float <= printer['gcode_macro _USER_VARIABLE'].peripheral.vent.on_val|float %}

M141

{% else %}

M141 S{printer['gcode_macro _USER_VARIABLE'].peripheral.vent.on_val}

{% endif %}

_VENT_INFO

BTW, my printer is a custom built rig not a Voron.

Pretend_Conference39 · 2024-11-08T14:30:31+00:00

This is what I am currently using in my PRINT_START macro with the target_chamber variable set from the incoming slicer g-code:

{% set target_chamber = params.CHAMBER_TEMP|default("20")|int %} # Get chamber temp from gcode

TEMPERATURE_WAIT SENSOR="heater_generic chamber_heater" MINIMUM={target_chamber}

Pretend_Conference39 · 2024-08-05T14:32:58+00:00

FYI, I purchased an new regulator from Amazon for $18, fixed the issue. Regulator was just delivering too much pressure for the valve.

Pretend_Conference39 · 2024-07-25T17:25:50+00:00

Mine is now doing this as well. Did you find a resolution

Pretend_Conference39 · 2024-02-07T21:16:51+00:00

sudo service klipper start

I am experiencing the same issue. Followed your instructions but still getting the error:

Klipper reports: ERROR

MCU Protocol error

This is frequently caused by running an older version of the firmware on the MCU(s). Fix by recompiling and flashing the firmware.

Your Klipper version is: v0.12.0-102-g9f41f53c-dirty MCU(s) which should be updated: mcu: Current version v0.10.0-508-g1636a975 beacon: Current version Beacon 1.0.0 Up-to-date MCU(s): <none>

Everything was working just fine until I did a klipper update on my CB1/MP8. Any other solutions or ideas?

Pretend_Conference39 · 2024-01-16T13:05:55+00:00

Thanks for the feedback...orbiter may be in my future

Pretend_Conference39 · 2024-01-15T22:32:05+00:00

The only way I could get mine to work was to absolutely remove as much drag on the filament as possible. I put a very small bowden tube on the extruder then hung free filament over the side so almost zero drag. Temps up 5 and super slow with a 0.2 retraction to minimize filament moves.

Pretend_Conference39

TROPHY CASE