Giving in and Reverting to Marlin/Ramps?

pro3d

@joergs5 It used to be good before I converted to Duet. Now it seems like a bad probe...

I guess I just had to high expectations for this board and did not anticipate these problems I have run into and all the macro world I dont really like

pro3d

@djdemond How do I attach a PT1000 to the heater block? Or do I need another heatblock? seems like they are 4mm?

Dino

@pro3d if you're using an e3d hotend @DjDemonD sells the pt1000s on his web store.

https://www.precisionpiezo.co.uk/product-page/pt1000-sensor

pro3d

I also experience whining. I read about this on the trinamic 21xx but is this the same thing? They whine a lot I think. 24v 1200 mA

pro3d

One more thing I miss about this setup some camera solution. Seems like we need the rpi anyway or some wifi cam.

Or what do people do for camera?

Phaedrux

@pro3d said in Giving in and Reverting to Marlin/Ramps?:

One more thing I miss about this setup some camera solution. Seems like we need the rpi anyway or some wifi cam.

Or what do people do for camera?

I use a PiZeroW with camera module running MotionOS as an IP Cam. It works well for viewing, but no time lapse function.

There is currently no solution as easy as that provided by Octoprint.

T3P3Tony

@pro3d at certain microstep/current settings the Trinamic drivers have an audible whine when standing still (I have only experienced this when they are holding a position, not while moving). This is not unique to the Duet, but a "feature" of the drivers, however because we have SPI control of the drivers we have idle current reduction and standstill current reduction that drops the current by a configurable % when the stepper is stood still or moving very slowly. See:

https://duet3d.dozuki.com/Wiki/Gcode#Section_M906_Set_motor_currents
(the I parameter)

This is the percentage of normal that the motor currents should be reduced to when the printer becomes idle but the motors have not been switched off. The default value is 30% and always be at least 100mA.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M917_Set_motor_standstill_current_reduction

This command sets the percentage of the current set by M906 that is to be used when the motor is stationary but not idle, or moving very slowly.

pro3d

@t3p3tony thanks. This is while moving for sure so maybe some other setting

T3P3Tony

@pro3d Odd, all reports we have are that with the TMC 2660s the steppers are significantly quieter while actually moving. are you using interpolation to 256 microstepping? Something like

M350 X16 Y16 Z16 E16 I1

The interpolation is set by the "I1" but it only applies at 16 microstepping.

pro3d

@t3p3tony
Yes it seems so

Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes back
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z3200 E470 ; Set steps per mm
M566 X900 Y900 Z12 E300 ; Set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z360 E1500 ; Set maximum speeds (mm/min)
M201 X1500 Y1500 Z250 E750 ; Set accelerations (mm/s^2)
M906 X1300 Y1300 Z1200 E1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

dc42

@pro3d, you can continue to use a thermistor if you want, but the firmware needs to know what its characteristics are just as Marlin does. The configurator allows you to select from a number of popular types, or to enter 3 points from the resistance vs. temperature table.

HTH David

pro3d

I thought I could just use the NTC3950 as normal but I understand it is more complicated

Also I wonder about the difference between M561 and G29 S2 in the GUI. Why are these to options there?

And sometimes it seems they dont clear out the compensation when when I home Z after using the GUI for these two options - Z should read the offset value but somehow reads different due to some compensation I guess?

dc42

Yes you can use a 3950 thermistor, just use parameters 100000 for the R25 value, 3950 for the B value and 0 for the C value in the configurator, or in the M305 command if you are setting that up yourself. You should be aware that as there is no resistance vs. temperature table published for those thermistors and the 3950 will be the B value at low temperatures, the temperature readings for the hot end at printing temperatures will be highly inaccurate no matter what firmware you use. That doesn't necessarily matter because you will need to experiment to find what temperature reading works for your hot end and filament anyway.
M561 and G29 S2 do exactly the same thing. M561 was implemented a long time ago. When we added G29 mesh bed compensation, we included G29 S2 because it is easier to remember than M561.

HTH David

JoergS5

This post is deleted!

pro3d

@dc42

Thanks. I guess I need to read up on thermistors and check what this PT1000 thing is

Here is a link to a table for the 100K NTC3950. (I think it is table 11 in Marlin)
https://cae2100.wordpress.com/2014/03/08/beta3950-thermistor-table-for-marlin/

I still wonder why we have two options to clear the bed comp in the gui but I guess that is for the GUI developer to answer

Anyway it seems it does not clear the table all the time but I might be doing something wrong or the BL Touch is playing me

Thanks for trying to help out. I was just not aware of what a noob I was transferring to another platform so took some things for granted

dc42

That Marlin thermistor table assumes that the B value of 3950 is constant at all temperatures. It will be OK for a bed thermistor but likely to be rather inaccurate at extrusion temperatures. If you want accurate temperatures, you should use a thermistor for which the manufacturer publishes a resistance vs temperature table, or a PT100 or PT1000 or other better temperature sensor.

You can replicate that table by setting B3950 C0 in the M305 command for that heater.

Does DWC provide separate options for running M561 and G29 S2? I am on vacation so I can't check. If it does, then I agree that it shouldn't.

DjDemonD

I take your point @pro3d that if you want a simple controller, then marlin running on one of the plethora of cheap controllers that exist now, is probably a simpler and cheaper solution. I have one machine still running on arduino/ramps and marlin (3 year old version at that) because it just works. I agree to some extent that if I was an OEM, it might be easier to just send a hex file to customers when I updated the firmware on their machines. It seems to work for Creality etc.

Duet is a product aimed at those who want to utilise a broad array of very useful features but not everyone needs them all (or even most of them), if the machine they are operating is fairly simple. I have a cr10 and wouldn't bother with a duet upgrade as it works out of the box. However my delta is complex and my corexy a platform for developing sensors, so the feature rich landscape with duet works there. I can't see an easy way to have a simple mode and an advanced mode, but maybe this is the way to go.

T3P3Tony

@pro3d those two options are to disable two different functions

"Disable Bed Compensation"

and "Disable Mesh Grid Compensation"

Bed compensation is G32, normally used now for autolevelling the bed using two , 3 or 4 independent Z stepper motors (so the concept of disabling it does not make much sense any more). Also used on delta printers for delta calibration.

Mesh Grid Compensation is what you are using (from your other post).

pro3d

@t3p3tony

Ok but then remains one question as I was told M561 does the same as G29 S2.

Are you now saying that "Disable Bed Comp"(M561) has a different function than "disable mesh grid comp"(G29 S2)?

This is what the GUI tells me they are anyway and that notation in the GUI might be wrong

But from what I now understand I should stick to G29 S2 in any .g file? If just one Z lift that is

T3P3Tony

@pro3d ahh good spot. I must be getting mixed up with the behaviour on the delta with G32. I just checked on my IDEX printer and the diable runs M561, and the other runs G29 S2.

I will ask @chrishamm why we have the same option twice.