Initialize the PS_ON-Pin to HIGH

[emtrax-ltd]

Can you initialize the PS_ON pin to HIGH on boot so that a connected BTT relay 1.2 does not automatically shuts down after 15 seconds? I know there is no point in keeping the relay connected this way, but it's the original wiring.

BIGTREETECH-TouchScreenFirmware/TFT/src/User/API/extend.c

// Power Supply Control pins Initialization
void PS_ON_Init(void)
{
  GPIO_InitSet(PS_ON_PIN, MGPIO_MODE_OUT_PP, 0);
  GPIO_SetLevel(PS_ON_PIN, infoSettings.ps_active_high);
}

[teeminus]

I will have a look into that. Which TFT, mainboard and mainboard firmware (Marlin/Klipper) are you using?

[emtrax-ltd]

• tft35 e3 v3.0
• skr mini e3 v1.2 ->since 2 days with klipper 0.9.x (based on the latest mainsailos-img with all upgrades afterwards, everything on a pi zero w), before that it was marlin 2.0.7

[teeminus]

Can you please post your klipper display config here so that I can add that to the wiki?

I am currently working on an other issue but as soon as I finish that I will add the PS_ON feature. I think that will be done in a couple of days.

[emtrax-ltd]

ps: you can check the "pin-high" with a voltage meter at ps-on-connector between ground and signal (should be finally above 3 V).

[emtrax-ltd]

Can you please post your klipper display config here so that I can add that to the wiki?

I am currently working on an other issue but as soon as I finish that I will add the PS_ON feature. I think that will be done in a couple of days.

[board_pins]
aliases:
    # EXP1 header
    EXP1_1=PB5, EXP1_3=PA9,   EXP1_5=PA10, EXP1_7=PB8, EXP1_9=<GND>,
    EXP1_2=PB6, EXP1_4=<RST>, EXP1_6=PB9,  EXP1_8=PB7, EXP1_10=<5V>

[display]
lcd_type: st7920
cs_pin: EXP1_7
sclk_pin: EXP1_6
sid_pin: EXP1_8
encoder_pins: ^EXP1_5, ^EXP1_3
click_pin: ^!EXP1_2

[output_pin beeper]
pin: EXP1_1

currently, the py hack is running in klipper's st7920.py - does not work reliably and flickers frequently (with original btt-firmware)

[teeminus]

Thanks for the config.

I am curious about the hack, what does it do?

[emtrax-ltd]

Thanks for the config.

I am curious about the hack, what does it do?

it's "well known" hack from https://github.com/KevinOConnor/klipper/issues/2231

    def write_text(self, x, y, data):
        if x + len(data) > 16:
            data = data[:16 - min(x, 16)]
        pos = [0, 32, 16, 48][y] + x
        #self.text_framebuffer[pos:pos+len(data)] = data
        for c in data:
            self.write_graphics(x, y, font8x14.VGA_FONT[ord(c)])

[teeminus]

Ah, okay. That one 😄

[teeminus]

I havn't forgotten your request, I will take care about that on monday.

[teeminus]

Well, it's not monday yet but I created a feature branch for you to test: https://github.com/teeminus/NoTouchScreenFirmware/tree/add_ps_on

You will have to compile the firmware yourself as I don't like pushing binary files to github, so I only update the binaries when creating a new release.

[emtrax-ltd]

great job... it works!

lost 1h in testing... after ripping all apart too ... until i noticed, that i'm in the wrong branch for compiling lol

BOARD: BTT SKR MINI E3 V1.2 TFT: BTT TFT35 E3 V3 KLIPPER: encoder and beeper are functional [display] lcd_type: st7920 cs_pin: PB8 sclk_pin: PB9 sid_pin: PB7 encoder_pins: ^PA10, ^PA9 click_pin: ^!PB6

[output_pin beeper] pin: PB5

[teeminus]

Thanks for the feedback and the config.

EDIT: I just noticed that you posted the alias pins above. Are they still correct?

[emtrax-ltd]

Thanks for the feedback and the config.

EDIT: I just noticed that you posted the alias pins above. Are they still correct?

both cfg versions are effectively the same. however, i have noticed a some instabilities - the display does not always activate reliably. I'll investigate this in more detail over the next days.

otherwise the function for ps-on is 100% ok and so this issue is solved.

I would contact you when I got more information about the problem about the cfg and activation problem.

[teeminus]

• That's a known problem. I have been working on that for the last week. There will be an update to both Klipper and this firmware that will hopefully fix the issue.