Topics created by patakopecek

Hi everybody, I need help. I am trying to implement coolstep feature (I have DUET 3 and firmware 3.0). I am sending a command e.g. M915 X T32904 (I tried little/big - endian) and there is no change in log - still coolstep is 0 - and the motor sound is also the proof - my parameter S (stallguard) is well set - about 300 with no load (bigger stepper is set for 600 with no load). My answer is - is it impelentet for TMC516x and duet 3? with firmware 3.0? Because - sending a command e.g. M915 X T99505454 - return no error etc. and after many tries (combination from tmc datasheet) - there is still no change and coolstep is in the log 0. Please @dc42 , could you provide en example of setting a coolstep command? Thanks for any help

On my list to investigate.

@jacotheron oh, actually you are right, I should use the non mini file then, because I report a lot of problems with DWC2 to @chrishamm

for some reason it started working, will be watching it

@patakopecek Yes, I can add it to DWC2-RC4.

There is already an app for Android which does an mDNS broadcast in order to discover Duet WiFi boards on the local network but once you select a machine, it only displays the web interface in a web view. mDNS support on the DuetM and Duet Ethernet still needs to be implemented.

@dc42 said in 12864 lcd on duet wifi?:

and re-jig the connections to avoid the need for custom cables.

My Wanhao D6 has screen/encoder and sd-card cables that plug right into the similarly named ports on the board. (I'm almost stupid enough to just plug them in and turn it on to see what happens.) I'd love for them to work and not just be lifeless. If there were enough folks interested in this feature, would you all make a way to bring it to life?

@elecsteppers said in Stallguard homing not that consistent, any tips?:

What can I do to fix the stall guard issue?

reduce acceleration to reduce the likelihood of false detections

Thanks, exactly what I needed to know😀👍🏻

See the S and C parameters in the G31 command, https://duet3d.dozuki.com/Wiki/GCode#Section_G31_Set_or_Report_Current_Probe_status. It's not currently possible to use a separate thermistor.

I know, but where to add them?

@t3p3tony it connects fine on the tp-link but the dwc does not start up, it does not even create a dwc.json file in the www folder, there was a serviceman yesterday and he replaced the Huawei router and it now works on both bands, so it is usable

@patakopecek said in Stall detection custom actions:

Maybe ability to run custom macros would be enough, like r4 would run stall4.g and so on

Added to the wishlist.

@patakopecek said in Prusa laser filament sensor:

And how hard would it be for you to integrate it?

I'm not going to, because using I2C feed data back from the hot end is poor engineering and would create a lot of support issues, because of interference from extruder, hot end and fan cables. I only implement things I can support. But RepRapFirmware is open source, so you or anyone else can fork it and add the support if you want to.

The Duet3D one is undergoing an extended beta test and is not yet on sale.