Topics created by wschadow

@droftarts indent comments is working

@chrishamm They're all WiFi boards. I'm running the WiFi 2.1 that comes with 3.5.0

@wschadow have you upgraded to 3.5.2 yet? If so, is the problem still present?

@chrishamm I experience a similar issue, but when M291 is called from plugins... Here is the issue that I have opened to describe my problem: https://forum.duet3d.com/topic/36365/m291-issued-from-a-plugin-doesn-t-show-anything-on-the-paneldue

@wschadow I suspect DWC is reporting the tool state, not the heater state. The tool state is copied to the heater state when you release the tool or switch to the tool, but you can subsequently override it using M568, until the tool is next selected or freed.

@chrishamm Thanks for reminding me 😉 I have seen that a long time ago, but completely forgot about that and looked in other places to change this setting. Is there a way to trigger that the dwc-settings.json is reloaded into the browser, without reloading the page?

I'd really prefer less flatness in the UI .... buttons should be visually different from text labels.

@wschadow Thanks, I've got a fix ready for 3.5.0-rc.2.

@dc42 Thanks! I looked for that in all other places 😉 Thanks, exactly what I was looking for and works nicely.

@dc42 This brings me also to another request: https://github.com/Duet3D/PanelDueFirmware/issues/317

The object model seems to change the number of digits for x and y depending on the number it cuts off trailing zeros, which is fine. DWC and Paneldue show for x and y only one digit after the ".". It would be very helpful, e.g. the x y offset calibration of an ODEX machine, to display to digits. There is enough room for that.

wschadow created this issue in Duet3D/PanelDueFirmware closed Two digits for the display of x and y coordinates #317

It looks like an issue with numerics. I just cam across another post [(https://forum.duet3d.com/topic/33677/round-variable-to-nth-digit/2)] and gave this code a try

var rnozzle = heat.heaters[1].model.heatingRate var k1nozzle = heat.heaters[1].model.coolingRate var k2nozzle = heat.heaters[1].model.fanCoolingRate var dnozzle = (10.0* heat.heaters[1].model.deadTime) / 10.0 var enozzle = (10.0* heat.heaters[1].model.coolingExp) / 10.0 var vnozzle = heat.heaters[1].model.standardVoltage ; echo >"0:/sys/Set-PID-nozzle.g" "M307 H0 R"^{var.rnozzle}^" K"^{var.k1nozzle}^":"^{var.k2nozzle}^" D"^{var.dnozzle}^" E"^{var.enozzle}^" S1.00 B0 V"^{var.vnozzle}^" ; set PID parameters nozzle"

The output is

2de14787-3e32-40a8-8c1f-504782d42ca7-image.png

@jay_s_uk Thanks, that did the trick 🙂

Then just remove the M291 OK prompt and just have it as a timed message. One less click.

M24 won't work in this case because it's not a pause, it's a filament change.

You could try adding M25 to the beginning and M24 at the end but I'm not sure that would help in this case since we don't really want to evoke pause.g at all.

@dc42 Yes, I'm pretty sure that filament-error.g is executed. The sensor is configured as M591 D0 P1 C"e0stop" S1. In my case it will trigger when filament is inserted.

filament-error.g looks like this:

; ========================================================================================================= ; ; called when a filament error occurs ; ; ========================================================================================================= ; M291 P"welcome to filament error" echo "welcome to filament error" ; turn sensor off M591 D0 P1 C"e0stop" S0 ; ========================================================================================================= ;

This is what happens, when filament is inserted. First on the Panel first the error message pops-up:

IMG_1515.jpg

Then a split secend later the message from filament-error.g pops-up
IMG_1516.jpg

The console looks like this:

IMG_1517.jpg

Here the message from filament-error.g is displayed first.

According to the documentation the filament-erro message should not be displayed. In my opinion this is the preferrable way of implementation.

@dc42 Thanks!