Topics created by hauschka

@dc42 said in Change name of 1LC or Sammy board in Firmware:

That is where you would need to change the name of the file that is installed when you command a firmware update or a CAN reset.

Awesome, thanks, I will try it!

@hauschka I asked @dc42 about supporting lasers and spindles on expansion boards. He said:

Supporting lasers/spindles on expansion boards would not be impossible but would raise a few implementation issues.

I think it just hasn't been requested before, so currently there's no reason to spend the time implementing it. If you want, raise a feature request on Github https://github.com/Duet3D/RepRapFirmware/issues/new/choose so at least it's on the great big list of things to do!

Ian

Thanks @Falcounet
I somehow missed your message.

For now, I worked around it by querying a specific variable using the M409 command, which is not the most elegant way of doing it. I'll give your new solution a go right away.
Thanks for updating it!

@hauschka SBC mode in 3.1.1 wasn't great duw processing stuff out of sync etc. If I were you I wouldn't bother as this won't be the only issue you have

@hauschka Alternatively, if you are likely to switch back and forth, you could create two (or more) configuration files and switch between them. Check out M505 https://docs.duet3d.com/User_manual/Reference/Gcodes#m505-set-configuration-file-folder

@hauschka said in Execute gcode mid print - without getting queued:

Hi forum,

I wanted to know if there's a way to execute gcode commands in the middle of a print file without overwriting the ongoing printjob.

For example: babystepping to adjust printheight mid-print. Do these commands require a special prefix or can I just send any gcode command mid-print.

You can send almost any GCode command mid-print. A few will be ignored when printing from SD card unless they are in the print file, for example M0 will be ignored unless the print is paused.

Similarly, is there a way to immeditely execute commands, as opposed to having them queued in the buffer for execution?
(e.g. how is the software emergency stop handled?)

Movement commands will be put in the movement queue for execution; except that babystepping attempts to bypass the movement queue. Emergency stop is also treated specially (it discards the movement queue). Commands that affect the motion system will wait for the movement queue to empty. Most commands that do not affect the motion system will be handled almost immediately.

@hauschka said in Adjust printing parameters mid-print:

actors (other than motors) that are connected via analog out be addressed in a similar way

Thanks @deckingman,

Good point that this will change other speeds as well.

Our main application would be other actors via anlog out, these shouldn't affect print speed.
Another aplication would be globally adjusting temperature mid-print, for example.

For print speeds, it def makes sense to adjust the overall speed.

Regardless, how would I send this code?

set global.innerWallSpeed = 3200

Via the gcode console?

Awesome, thank you for your replies :))

@dc42 said in CAN development possibilities:

Currently there is no provision for user-defined messages, but I may add a few for users such as yourself to use.

That would be really cool!
I'm not familiar with C++, unfortunately 😞

@gtj0 said in DWC3 Webserver Documentation:

You're my hero!
Thanks! That was exactly what I was looking for. No clue how I missed it!
Thans a lot gtj0

@gtj0

Ok, I think I get the logic behind it!

Thanks a lot!

Awesome, thanks!

Let's see where this leads me 😉