Topics created by zapta

I do my preheat in start.g but it's only a few minutes, not hour. I can't recall off hand if the time taken in start.g is applied to the total print job time.

Thanks @jay_s_uk ! This is exactly what I was looking for.

Thanks @Phaedrux. I switched to incognito mode and can now download, so must be something with my browser profile settings and I will look into it.

BTW, why the DWC version is not shown with the rest of the versions?

@dc42, must be fixed along the way. On 3.4.6 this is what i get

var x = "123" echo "String: " ^ var.x echo "Length: " ^ #var.x

fa0fc418-7c7e-4bc9-918c-2419ea74bc77-image.png

Thanks @gloomyandy. I added there a comment.

@chrishamm, reversing the order of the groups (oldest top, similar to Panel Due) should avoid the mixed order.

BTW, is it possible to split the lines in each group and display them in reverse order as independent messages using the same timestamp from the group?

@Phaedrux, found the problem. 100% my fault. My Prusa slicer startup code injects the snippet below to the files I send to the printer. That's a result of lazy programming. Thanks for your help.

... ; This forces an immediate update of the neopixels color M98 P"/sys/daemon.g" ...

Hi @T3P3Tony, I get now the corporate logo. Thanks.

@DonStauffer state.status is "processing" only while a job is running from SD card. It's still "processing" even if the job calls a macro.

Thanks @droftarts. 1Khz is high enough for my use case. I wanted to measure the power of my Revo 40W and higher PWM frequencies makes it easier with the RMS to DC integration.

BTW, in my system, with 24V supply, Duet Min 5+, and Revo 40W, the average power during the 100% PWM phase of warming to 245C, is only 25.5W. This is due to the intentional increase of resistance with temperature (PTC).

1b585080-2341-42c4-8140-4e46a55979eb-image.png

@dc42, any thought? Does the polarity of the axes matter?

@zapta perfect location for the accelerometer. About as close to the nozzle as it gets.

@zapta yes you should disable mesh bed compensation when collecting accelerometer data.

Automatic checking of the accelerometer axes is a good idea.

@zapta you could get round the Z homing issue by homing X and Y and then sending G92 Z0. But I take your point, the connector is too deep for the accelerometer to fit the right way up on some hot end assemblies.

Thanks @dc42. That worked.

Thanks @mendenmh. I am close to sea level but will make sure to check the barometric pressure. I also saw all kind of other rules of thumb (e.g. immersion depth) and realize that I will just scratch the surface with my limited knowledge and means.

E.g.

http://www.isotechna.com/v/vspfiles/pdf_articles/Temperature Calibration-Depths of Immersion.pdf

@zapta said in Best coefficients for extruder thermistor?:

As for the difference between the nozzle temperature and the thermistor, I presume that this is a also a good argument against switching to more accurate sensors such as PT100[0].

Yes, pretty much. I replied in your other thread and mentioned that I did a video and posted it on my YT channel. It's focus was primarily on the effect of deflected part cooling air but the difference between the temperature inside the nozzle and the temperature inside the heater block were orders of magnitude greater than the accuracy errors of any sensor. Hardened steel nozzles were especially bad. Which is why, imo the only thing one can do is print temperature towers to find the best setting for the hot end/nozzle/filament combination.