#PAM issues

42 messages · Page 1 of 1 (latest)

balmy halo
#

Having some trouble to get PAM working:
Internal error on command: "PAM".

I thought I followed all the steps correctly, but it must be something I'm doing wrong.

Attaching a screenshot of the dashboard and the printer.cfg in the comment section.

lament mountain
#

We're gonna need your klippy.log

balmy halo
lament mountain
#

Seems like you didn't follow the steps correctly as you're missing the PAM macros.

#

You need to include ratos_v2 in this case

balmy halo
#

Thanks! I'm not in front of the computer right now, but I'll look into it later today.

#

Would it be better to just delete all this and do a fresh install, do you think?

lament mountain
balmy halo
#

All these macros in the first link are located in the pam.cfg and ratos.cfg in the PAM-folder. Do I need to copy all of it into my printer.cfg?

When adding [include pam/ratos.cfg] to my printer.cfg, I get this error message shown in the attached photo

lament mountain
balmy halo
#

Aaaahhh...

#

Include file '/home/pi/klipper_config/pam/ratos_v2.cfg' does not exist

lament mountain
#

oh wait sorry @balmy halo i see you're still on RatOS v1

#

So it's pam/ratos_v1.cfg

lament mountain
#

Oh.. pam.cfg just includes ratos.cfg

#

Okay.. @lilac nest i'm gonna need your help here, i'm confused.

lilac nest
#

reading.....

#

remove EVERYTHING pam related from your printer cfg, i see a huge pam config, remove all of it

#

then just use this
`[pam]

[gcode_macro _START_PRINT_BED_MESH]
gcode:
{% set default_profile = printer["gcode_macro RatOS"].bed_mesh_profile|default('ratos') %}
BED_MESH_CLEAR
{% if printer["gcode_macro RatOS"].calibrate_bed_mesh|lower == 'true' %}
PAM PROFILE={default_profile}
BED_MESH_PROFILE LOAD={default_profile}
{% elif printer["gcode_macro RatOS"].bed_mesh_profile is defined %}
BED_MESH_PROFILE LOAD={printer["gcode_macro RatOS"].bed_mesh_profile}
{% endif %}`

#

assuming you are using ratos2

balmy halo
#

Still on v1

lilac nest
#

one sec

balmy halo
#

so when I update to v2, I'll use this?

lilac nest
#

RatOS V1

#

`[pam]

[gcode_macro _START_PRINT_BED_MESH]
gcode:
{% if printer["gcode_macro RatOS"].calibrate_bed_mesh|lower == 'true' %}
PAM PROFILE=ratos
{% endif %}
BED_MESH_PROFILE LOAD=ratos`

#

you can tag me directly next time btw

balmy halo
#

Thanks! I'll give it a shot, at least got no errors on reboot this time 🤞🏼

#

So when I update to v2, I'll use the first one you posted?

lilac nest
#

you copied every pam related settings you could find into your printer cfg, but yu copied a lot of ratos 2.0 related stuff, thats the reason why it didnt worked

balmy halo
#

Thanks a million!!

#

starting a test print right now

#

Worked great! 👍🏼

#

Regarding RatOs v2, I just assumed that the update Manager section would handle that automatically when the v2 was available..
But in order to do the update, I have to go through the same process as I did the first time I installed everything?

lilac nest
floral agate
#

@lilac nest I've removed all traces of PAM from printer.cfg. I also removed all entries from moonraker.conf
I then even used WinSCP to del all PAM folders, including the cached compiled pam python script.

#

BUT.... pam still shows in the update manager even after a full reboot.