I'm trying to get 5160 drivers working with octopus pro, successful stepper buzz but g28 causes
TMC 'stepper_x' reports error: GSTAT: 00000004 uv_cp=1(Undervoltage!)
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
#48 problems and a Boop ain't one
wary hound
@lunar wyvern any advice?
lunar wyvern
Please post relevant config entries of [stepper] and [tmc5160] and ill try to assist. I don't have a lot of mileage on 5160s though
wary hound
Please post relevant config entries of [stepper] and [tmc5160] and ill try to as...
https://pastebin.com/bRNWQzLM, heres the most recent config just in case
lunar wyvern
Which mainboard?
wary hound
446 octopus pro, in canboot with ebb36
lunar wyvern
Looking at this section -
[tmc5160 stepper_x]
cs_pin: PC4
interpolate: false
#spi_bus: spi1
run_current: 1.4 #0.8
sense_resistor: 0.075
stealthchop_threshold: 0
#spi_software_sclk_pin: PA5
#spi_software_miso_pin: PA6
#spi_software_mosi_pin: PA7
spi_software_miso_pin: EXP2_1
spi_software_mosi_pin: EXP2_6
spi_software_sclk_pin: EXP2_2
From my observation, the commented spi_software_* entries are the ones commented, not the active entries
spi_software_sclk_pin: PA5
spi_software_miso_pin: PA6
spi_software_mosi_pin: PA7
Otherwise, I can't find other issues
These look legit in your config
wary hound
Under the screen config the pin aliases are assigned for spi
wary hound
Undervoltage makes me wonder if it might be to do with run current
lunar wyvern
Your run current is plenty high even for 2.5A motors.
I didn't confirm aliases vs PIN designations, and honestly I do prefer MCU pins over aliases..
mental orchid
I have recently played with Octopus pro and 5160's, if it's any help this is what worked for me
[stepper_x]
step_pin: PF13
dir_pin: PF12
enable_pin: !PF14
microsteps: 16
rotation_distance: 40
full_steps_per_rotation: 200
endstop_pin: ^PG12
position_endstop: 225
position_max: 225
homing_speed: 50
[tmc5160 stepper_x]
cs_pin: PC4
run_current: 1.41
spi_software_sclk_pin: PA5
spi_software_miso_pin: PA6
spi_software_mosi_pin: PA7
sense_resistor: 0.075
wary hound
I didn't confirm aliases vs PIN designations, and honestly I do prefer MCU pins ...
It was previously a known working config I grabbed from voron docs. What run current would you use on 5160? That's the run current the zero g hive Mind told me to run back in November although I'm now actively cooling stepper drivers and have whacked some heat sinks on my stepper motors until I find an active cooling set up that tickles my fancy
wary hound
I'll drop it to 0.707 when I get home, if it works then I'll try 0.8 just to see
lunar wyvern
If you feel like, squeeze some more to 0.9, or more if feeling adventurous
It's 0.707 multiplied by stepper max current
wary hound
Tap and I've got CNC tap ordered because I want that 3mm of y back
lunar wyvern
How’s you find it?
wary hound
Super nice build!
I really appreciate the 5 plus now
wary hound
It's great, no scratched beds, no changing z offset except when changing between smooth and textured due to the difference in needed squish
lunar wyvern
Yeah I like it too. Too bad it came so late when the bacon is out. I feel the need to test that also
wary hound
Yeah I like it too. Too bad it came so late when the bacon is out. I feel the ne...
There's a sb carriage that runs beacon and tap
Here's a list of mods, copy paste of my post on voron FB
The "finish" line is almost in sight!
Tap, crown cooler, CPAP, ebb36, ramas idlers, CF gantry, pinmod, CF pins, umbilical, tophat, k3 style "fridge door", octopus pro with 5160 on a&b, fancy front power switches for pi and printer, titanium hardware on all moving parts, ge5c z joints, tool free z idlers, magnetic panels. Canboot is up and running thanks to esotericals seminar on canboot. Now I just need to wrap my head around how to configure the 5160s, CPAP and the new RGB strip on the top front of the frame.
Pogo pins for "the filter" are due in 1-3 days, CNC tap is ordered and there is a half built ercf on my desk.
Why CF gantry, titanium hardware and CF pins if I'm running tap? I enjoy tap and I want to offset the weight gained so I can still go brrrr
lunar wyvern
wary hound
Just need to get these 5160 drivers playing nice
lunar wyvern
Sorry for not having any other ideas 🤷🏻♂️
wary hound
Sorry for not having any other ideas 🤷🏻♂️
Figured it out.... 100w psu
lunar wyvern
😬
wary hound
😬
Installed a more suitable psu, homed successfully at 0.4a, raised to 1a, error! Unplugged mini12864 screen homed successfully at 1a run current.
lunar wyvern
Unbelieveable...
wary hound
I don't know if I want to go headless or klipperscreen
lunar wyvern
Do you have a Pi compatible screen already or will need to acquire one?
wary hound
Need a new one, not sure which to get do you have a recommendation from these ?
lunar wyvern
I use a Pi official 7" screen that I had for years before building the printer. It works very well and is super reliable. However, I believe it requires that the Pi is attached to the back side of the screen, which may not be suitable for you.
Perhaps take a look at the BTT Pi TFT?
wary hound
That has the same requirement from what I saw. Would free up some space in the electronics bay
lunar wyvern
I see. 7" is fairly large, is there a mount available for this printer? I wouldn't go there if you had to design one and reprint the front screen, seems like too much hassle... Nevertheless, you seem to have invested enormous energy and funds on this project, so... 🤷🏻♂️
wary hound
The btt 5 inch has many mounts available
All the wiring is getting redone as I'm genuinely not happy with how it sits
lunar wyvern
Oh. more energy to be invested...
Well that BTT Pi screen has a detachable ribbon cable, you can source longer ribbon an decouple the Pi from the screen. If I recall correctly, this isn't possible with the OEM screen, so +1 for the BTT.
wary hound
Well that BTT Pi screen has a detachable ribbon cable, you can source longer rib...
But pi on screen would clear up a pi worth of real estate in my electronics bay
lunar wyvern
True. As long as you don't plan on connecting anything to the 40-pin header, it'll be fine. Otherwise, wiring starts to be ugly and possibly unreliable
wary hound
There's one lead on gpio pin 26 for the CPAP pwm signal
lunar wyvern
I see it in the photo. Not a big deal but perhaps you can run it over a spare output from the mainboard? Might also be safer that way, because as you probably know (you should know...) the Pi's gpios aren't tolerant to voltages above 4v.
But hey, if it works....
wary hound
I see it in the photo. Not a big deal but perhaps you can run it over a spare ou...
This was the recommended way based off all the information I could find for cpap
lunar wyvern
There isn't something particularly special about the Pi's GPIO26 as far as I'm aware. It's not even tied to hardware PWM, which would've made sense if you wanted the Pi's hardware to generate the pulse signals, as done for gpio12, 13, 18, and 19.
I'm assuming you're controlling it from klipper by specifying pin: rpi:gpio26 or something similar?
wary hound
Yes, I'm controlling it exactly like that, I was referring to the mcu being used for signal apparently results in blower starting up at max power on start up
instead of the bambu CLACK you get a hurricane
lunar wyvern
Oh I get you. There's a way around it, btw
When compiling Klipper for the MCU you can instruct it to activate (or deactivate) a pin upon startup
wary hound
I only just got canboot working 😂
dull pike
Could anyone give me some assistance? I have a Manta M8P and I am trying to get TMC 5160 Pros to work and I am getting an error that spi1 is reserved for PC6.
here is my config:
Motor1
[stepper_x]
step_pin: PE2
dir_pin: !PB4
enable_pin: !PC11
microsteps: 16
rotation_distance: 40
endstop_pin: EBB: PB3
position_endstop: 372
position_min: 0
position_max: 372
homing_speed: 50
#homing_retract_dist: 5
#Motor1
[tmc2209 stepper_x]
uart_pin: PC10
#diag_pin: PF3
#driver_SGTHRS: 53
run_current: 1.2
stealthchop_threshold: 0
Motor2
[stepper_y]
step_pin: PF12
dir_pin: !PF11
enable_pin: !PB3
microsteps: 16
rotation_distance: 40
endstop_pin: !PF4
position_endstop: 366
position_min: 0
position_max: 369
homing_speed: 50
#homing_retract_dist: 10
Motor2
[tmc2209 stepper_y]
uart_pin: PF13
#diag_pin: !PF4
#driver_SGTHRS: 80
run_current: 1.2
stealthchop_threshold: 0
########################################
TMC5160 configuration
########################################
[tmc5160 stepper_x]
cs_pin: PC10
spi_bus: spi1
interpolate: True
#stealthchop_threshold: 999999
#diag1_pin: ^!PG6 # use the same pin that was previously the endstop_pin!
#driver_SGT: -64 # -64 is most sensitive value, 63 is least sensitive
run_current: 1.5
#hold_current: 0.2
sense_resistor: 0.075
spi_software_mosi_pin = PA7
spi_software_miso_pin = PA6
spi_software_sclk_pin = PA5
[tmc5160 stepper_y]
cs_pin: PF13
spi_bus: spi1
interpolate: True
#stealthchop_threshold: 999999
#diag1_pin: ^!PG9 # use the same pin that was previously the endstop_pin!
#driver_SGT: -64 # -64 is most sensitive value, 63 is least sensitive
run_current: 1.5
#hold_current: 0.2
sense_resistor: 0.075
lunar wyvern
Could anyone give me some assistance? I have a Manta M8P and I am trying to get ...
I'm observing several conflicts in this config.
First and foremost - comment the [tmc2209] sections for stepper_x and stepper_y.
Secondly, your config calls for hardware SPI and software SPI on the [tmc5160 stepper] sections (for x and y). Comment the line spi_bus: spi1 .
Additionally, your [tmc5160 stepper_y] section should mention the 3 spi_software lines.
To summarize, the two sections should look like so:
spi_software_sclk_pin: PA5
spi_software_mosi_pin: PA7
spi_software_miso_pin: PA6
cs_pin: PC10
interpolate: False
diag1_pin: !PF3
run_current: 1.0
[tmc5160 stepper_y]
spi_software_sclk_pin: PA5
spi_software_mosi_pin: PA7
spi_software_miso_pin: PA6
cs_pin: PF13
interpolate: False
diag1_pin: !PF4
run_current: 1.0
Last, but not least - if you still have issues, I suggest you open a separate troubleshooting post. It will probably be noticed by a wider audience.
dull pike
I'm observing several conflicts in this config.
First and foremost - comment th...
Thaks for the help, after I posted i realized it was within a trouble shooting not its own post . Ill see if it works!
wary hound
BTT also has issues with using spi and screens that use exp pins
If using a mini 12864 (whatever combination of numbers) screen check the config section where the screen is defined, if using exp connectors the standard voron config has aliases defined for the spi pins
dull pike
BTT also has issues with using spi and screens that use exp pins
I dont have any screen hooked up, Now im getting an error saying that PA6 is used multiple times. but it is supposed to be right?
wary hound
Check the screen section of your cfg
dull pike
I dont have a screen section?
wary hound
I'm at work on mobile
dull pike
I think i found it!
wary hound
Can't open CFG, ctrl F on your CFG and find where it says pa6
dull pike
yeah it was in a seperate config file thats refrenced, thats why ctrl f wasnt helpful
lunar wyvern
separate config files are the mother of all evil
dull pike
I can never decide if separate configs or one 3 km long config is better
lunar wyvern
...Until the klipper is made to advise which config file is making the conflict I refuse to use this method. I've had 70kb config file on one of my machines.
Search works well, I don't mind it
dull pike
Yeah thats smart i may switch to that, current have 5 configs referenced. its a nightmare
lunar wyvern
One of the biggest reasons I disliked klicky probe is the fact it's spread over countless files. Compare this with the 5 lines needed for tap probe. Bahhhhhh.
dull pike
I messed with klicky on one printer and it was cool but a pain. My Zero G plus i bit the bullet and got a beacon probe. its been a killer setup
@lunar wyvern what silcer do you use mainly?
lunar wyvern
I messed with klicky on one printer and it was cool but a pain. My Zero G plus i...
I’m vegan, I don’t do bacon 🤣
It’s too expensive to implement on 4 (soon 5) machines, and tap/boop works well in my setups (I’m using SB/mini SB on all machines)
I’m using Orca Slicer on all my printers.
dull pike
I’m vegan, I don’t do bacon 🤣
It’s too expensive to implement on 4 (soon 5) mac...
HAHAH
I only use it on the Mercury. Having an almost 400mm build plate a decided it wass worth it. If its not a hassle would you mind sending me your start print and your pause / resume you use for Orca slicer i am getting some werid issues.
My 5 other printers just have a very random collection of probes😂
lunar wyvern
I can do that, no problem, I’m just not near my machine anymore, closed shop for tonight 🙂
DM me and I’ll send it on my morning
dull pike
sweet thank you I appreciate that help on the drivers and the chat!