Found an id, saved the config…and they are talking!!!
Finally, I get to do some config. This is not going to be easy, at least making changes is easy!!!
2 Likes
how much can they possibly save by not making them a real cable…stupid!
1 Like
gonna start here, klipper/config/sample-raspberry-pi.cfg at master · Klipper3d/klipper · GitHub and see how far that gets me.
Nope
It’s extremely easy to make changes. That’s what I love about it!
I couldn’t agree more!
What about this?
I know it’s says skr but it also said pico lol
I think you’re going to be on your own with the printer.cfg since your custom pinouts are going to be different than anything else. I wish I was more help
1 Like
Oh cool I saw that but did not realize it actually used a pico. I will see if i can get a couple of the non-multiplexed steppers moving.
Thanks!!
That seems to be easy now that I know it wants them as “gpio” not the pi’s “GP”
1 Like
Awesome!! I think if you can get everything that’s not multiplexed working that will be a huge step. Then just have to figure out the tougher part lol. Doesn’t the multiplex deal just add on gpio pins? If you have a way of knowing which numbers those are you should be able to address them like any other pin.
If the multiplex is i2c based this might help as well…
https://www.klipper3d.org/Config_Reference.html?h=i2c#common-i2c-settings
1 Like
Well…shoot.
fluid stuff, looks like all the steppers use i2so, cross your fingers this is all new to me. Your link should help.
uart1:
txd_pin: gpio.0
rxd_pin: gpio.4
rts_pin: NO_PIN
baud: 115200
mode: 8N1#X
motor0:
limit_neg_pin: gpio.25:high
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 4.000
tmc_2209:
uart_num: 1
addr: 0
cs_pin: NO_PIN
r_sense_ohms: 0.110
run_amps: 0.680
hold_amps: 0.500
microsteps: 8
stallguard: 0
stallguard_debug: false
toff_disable: 0
toff_stealthchop: 5
toff_coolstep: 3
run_mode: StealthChop
homing_mode: StealthChop
use_enable: false
direction_pin: I2SO.1
step_pin: I2SO.2
disable_pin: I2SO.0
Yeah kipper doesn’t usually need this much in the config. But in this use case I’m not sure.
I think I just need to define these two?
i2c_software_scl_pin:
i2c_software_sda_pin:
I got that
1 Like
That’s the way it looked from what I read. There is another section linked there to speed up the connection on the pico as well
Ahhh I have three in the esp fluid yaml
i2so:
bck_pin: gpio.22
data_pin: gpio.21
ws_pin: gpio.17
So there is your clock and data pins. I’m not sure what the ws pin is
It may make you give it the address and other stuff too but you can easily try it without first and see
1 Like
What does the exclamation point mean?
dir_pin: !gpio5
Inverted
2 Likes
and endstop_pin: ^gpio10?
Hi vs low?
Format of micro-controller pin names¶
Many config options require the name of a micro-controller pin. Klipper uses the hardware names for these pins - for example PA4.
Pin names may be preceded by ! to indicate that a reverse polarity should be used (eg, trigger on low instead of high).
Input pins may be preceded by ^ to indicate that a hardware pull-up resistor should be enabled for the pin. If the micro-controller supports pull-down resistors then an input pin may alternatively be preceded by ~.
Note, some config sections may "create" additional pins. Where this occurs, the config section defining the pins must be listed in the config file before any sections using those pins.
thanbks
Sorry it is making me define all three axis before it will even go to the next step