Posts made by ctilley79

@dc42 Onto 3.6!! What’s next on the feature roadmap? Any hints?

@jay_s_uk Thanks Jay. That'll work. I appreciate it.

@Phaedrux That'll remove it on the status page but not the dashboard. I don't want it connected directly to vin running at 100% because it's loud. My option is to buy a less powerful fan or convince you to create a boolean parameter in M106 or M950 lol. I understand it would be low priority. It's not that big of a deal but it would add a little flexibility.

@Phaedrux On a duet 3 mini5 which output is an always on port?

I have a case fan that I set up as an always on fan. Is there any way you can set a flag to hide this fan from DWC? I tried searching the forum but didn't come up with much.

@ctilley79 seems the ramping moves may need firmware support.

@Exerqtor Have you had a chance to see what gcode that option produces? You could slice a small model and see what's injected with firmware retraction checked and unchecked. Who knows, it may grey out the firmware retraction option. I haven't looked yet but plan to. I agree that it may be as simple as omitting the Z parameter in M207 depending how the slicer places the G10/G11 gcodes

@oliof said in Orca slicer and Duet:

@omni it doesnt work without Bambulabs' proprietary libraries so I am very wary about this poisoning of an open source project with binary blobs.

You sure? I'd like to investigate this myself. Are you sure the binary blobs aren't specific to the bambu printers themselves? They mentioned that the tweaked slicer algorithms were open sourced and had to be to satisfy those license requirements

@gringo those are short segments where input shaping is not being applied. 3.5 RC1 attempted to fix that but I’ve found that there are still moves where input shaping is ignored. My understanding is RRF’s input shaping may receive another overhaul after 3.5 is released.

For that reason I installed klipper on my duet boards and can confirm klipper does not have the same limitations. I look forward to coming back to RRF because overall, I do love RRF much better and the hardware is just much higher quality. My goal however is to print faster without the reduction in quality, and right now klipper provides that with exceptional results.

@ctilley79 I have an older 6HC and plan on getting a 32v power supply and run it alongside a 24v power supply for fans. Since IOs are ground switched PWM, you can use different PSUs as long as the two power supply's grounds are tied together.

@Anon1337 You don't need it. No reason you would need to drive 1 extruder motor at 48v. Just get a very small 24v psu. Run the 6HC off the 48v psu and the toolboard off the 24v psu.

@oliof Gotcha. I have my E jerk set ridiculously high at like 3000, so I'd never hit any limit with acceleration. It was my prior understanding is that for PA, you need high jerk values for E. I guess I need to reevaluate that.

@oliof

Can you give an example with typical jerk settings for a geared direct drive extruder motor?

@Phaedrux One that you don't support lol. I've got Klipper running on this board for the time being. Since it's a legitimate Duet 6HC I was mainly interested how I could troubleshoot any hardware issues. Since it's happening with two different sets of motors from different brands makes me think it's not anything specific to the stepper motors. In klipper, all configuration options are the same for the two motors.

@deckingman Motor currents are identical, and I measure with two very precise methods. My hand, and a laser thermometer. This is after homing when the machine is idle, but motors still engaged and on hold. It's strange it's happening with only one motor. When the machine goes into idle, the motors cool to room temperature.

@ctilley79 I just checked the drivers themselves and all 6 are cool to the touch.

I have a Voron 2.4 and one of my AB motors is running hot when on Idle hold. One motor is at 35C, and the other is at 55C. I tried two different sets of motors, and its the motor plugged into driver 0. The motor seems to operate normally otherwise. Where should I start troubleshooting and what's the potential cause?

@Threepwood

Something mechanical is going on here. PA works great for me on RRF. your issues are something else entirely.

@CCS86 I've been doing some research and it seems Duet took the wrong approach. I just recently installed klipper on my duet 6hc and toolboard to fool around with until Duet figures out a new implementation. David hinted at reevaluating after 3.5 is officially released.

If you want an interesting read, look at Dmitry Butyugin's comment thread about 2/3 the way down.

https://www.youtube.com/watch?v=bqf382QDSKY