@oozeBot what you want is a tweak on DWC to display your logo!

@oozeBot said in synchronize prompts between DWC and PanelDue:

Apparently displaying the macros on the control tab is extremely sensitive to Tool 0 being defined.

Yes, that's correct. This limitation is removed in the new PanelDue 3.2 beta firmware.

No you're not, I've requested this feature in the past along with others. As of now I'm using the bed heater controller to set my chamber temperature (I don't have a bed heater).

@T3P3Tony good to know that this will be included in the new firmware!

@dc42 Thanks! Was just reading this as you replied:
Z probe trigger height second order temperature compensation is now supported. To use it, specify a 2-element array as the temperature coefficient, e.g. "M558 ... C0.01:0.0005"

@bearer said in Logging, Syslog or HTTP:

this is probably by far the simplest approach https://forum.duet3d.com/topic/13194/dsf-extension-exec-on-mcode-was-shutdown-sbc

So your idea is that I do something like this?

M2342 F"my log message"

Yes this is a nice option to have for custom log messages, but actually I was after system logs. Something like:

system started, RRF Version 3.2.xx heater 0 configured network initiated: got ip 12.34.56.78 via DHCP-server at 12.34.56.1 User $username logged in via webinterface from 12.34.56.23 leveling started from PanelDue leveling done homing successfull ran macro "load-filament.g" started job: "myprintjob.g" error: heater fault on heater N canceled(/stopped/resumed) job "myprintjob.g" for reason X after HH:MM:SS [...]

That should go to some default log-file automatically, doesn't it?

I have added this to the firmware work list. For Duet 3 there will be a restriction that both outputs must be on the same main or expansion board.

@dc42 I didn't know this feature was considered for debugging only. I guess the drivers are using some indirect type of measurement and not some plain resistance measurement.

I guess making it configurable and documenting it well to informing that it might trigger false positives, especially at low currents.

While reviewing the RRF 3.2 roadmap, I see the following item:

Consider making 2-, 3- and 4-point probing available to correct an overall tilt while still using mesh bed compensation

This is what I was trying to ask for, but wasn't very clear.

Any idea if this will make the release? I'd love to see a 4 corner probe routine which then applied save mesh bed compensation.

Thanks!

Hi @dc42,
is there any chance to see "G5 Bezier curves" implementation in the forthcoming period?
We are almost ready with our experimental slicing software, so it would be nice to test it on our machine ,-)

Thanks you so much for your work!

@sixfeetunder well the new release of the RRF is supposed to have this changed according to @dc42

If the correct version of the tool board firmware binary is already in /sys then you can use M997 B# to update the tool board, where # is the CAN address of the tool board.

@skezo said in Stealthchop2 to Spreadcycle switch:

@CCS86 did you manage to find a solution for this? I experience the same thing with my maestro. For now I have disabled stealthchop2 but would love to use it as it makes my printer very quite.

I haven't.

Was hoping to get some insight from the devs here, but it's not high on the priorities I guess.

@T3P3Tony

The octoprint Visualizer is the only thing I miss about using octoprint.

@dc42 thank you David!

@dc42 That would work fine for my application! As long as I keep the number of axes which need it low.

Unfortunately, M106 doesn't support frequency change in RRF3 :(. Gotta use M950.

@Phaedrux thanks!

Moved to the wishlist.