Topics created by kuon

@kuon @T3P3Tony Yes something like that - I think in Klipper - you can specify in a Macro - Rename_existing: - That renames the original command, and then you can then put some logic before or after it - and if required still call the original command using its new name.

For example in the SV09 Klipper config the M106 fan control command has been overridden to cause both print head cooling fans to turn off and on at the same time.

In the standard SOVOL SV08 configuration the following commands have all be overriden.
M109, M190,M106, M107, M600.

So in the example of M203 you could either completely disable it, or have some logic that set some limits or circumstances when it could be called.

@dc42 Ah, thanks for the name. I'm able to find some. I also considered a vacuum to hold the bed in place and electro magnet but they seem impractical.

Also, is there any build surface, beside glass, that can be used for high temp plastics? As glass is heavy and also cannot be used with magnet base.

@Phaedrux Thanks for the reference. For some reason when searching with google their products do not come out.

@Proschi78 As I said, if I select the tool before doing G29 so, T1 + G29 it works. But I think it should work without T1 as I specified U axis in M557. Also it should not go crash in other tool. Perhaps @dc42 can chime in. I'd be happy to try to help debug the issue.

@chrishamm After many prints, this issue did not appear again. So I have good hope it is fixed.

@Thorpydo many flat RJ11 cables are crossover cables. This doesn't matter for telephone or broadband use, but it does matter for CAN. So you should check that there is no overall crossover between each pair of boards.

@kuon you may be ok. It certainly won't damage anything but you may find the odd other feature that doesn't work

@Phaedrux Yeah, I read those. I'll try again. One question persist, will M570 affect the rising temperature tolerance? Like doing an average over the time of the P parameter?

@dc42 Great thanks

@dc42 No problem. It's my first fail in about 50 boards, so I'm not complaining. I will follow your instructions. Thanks

@kuon Yes, and a Mini 5+ could also drive a 1A motor. However, the phase resistance and inductance is high. For guidance, see https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_choosing#inductance

The inductance of the motor affects how fast the stepper motor driver can drive the motor before the torque drops off. If we temporarily ignore the back emf due to rotation (see later) and the rated motor voltage is much less than the driver supply voltage, then the maximum revs/second before torque drops off is:

revs_per_second = (2 * supply_voltage)/(steps_per_rev * pi * inductance * current)

You can use this calculator to calculate back EMF: https://www.reprapfirmware.org/emf.html

Ian

@MJLew OK, I found the hidden interface element (see the rant below) that Phaedrux mentioned, but even though it promises when the command key is down to open the link "in a new tab behind the current one" is does no such thing. It just scrolls the current tab to put the selected command at the top.

When I hold the control key down I can get the popup that Infiniteloop showed (and it works), that is not how I have to use proper links in the browser.

<rant> Hidden interface elements seem to be all the rage (even with Apple software) but they are terrible things for core elements of human computer interface. People should not have to hunt around for random hotspots that do surprising things, and people should not have to RTFM to work a web-page!

@dc42
Exactly, that was a problem I had with the hashPrinter. I wanted to use the "mini-Z axis" for z-hop and mesh levelling. But the firmware for simultaneous printing is still in the making.
Two tools using the same heightmap at different XY-coordinates simultaneously is another hurdle.

@chrishamm Yes that was it. I did follow the update instructions, but I didn't notice there was TWO services, duetpluginservice AND duetpluginservice-root. I enabled the later and now it works.

I am sorry for this "long" thread.

Thanks, your support was great. I built many machines with duet and I'm very happy with it.

@kuon Sorry for the slow reply. I added the following to the M950 description a while ago:

Pnn or Snn Output/servo pin number. Each P and/or S number needs to be unique, eg P1, P2, S3 P4, S5 etc. Servo pins are GpOut pins with a different default PWM frequency.

Ian

@kuon Thanks for the note, I just replied. Please provide further feedback on GitHub.

@dc42 Is the behaviour I am observing normal? I mean the duet ignoring the SBC if SBC's 5V comes a bit late after duet powering up.

@T3P3Tony Thanks. I totally missed that in the doc.

I have a better sequence of how things are happening:

initial state: SBC and duet booted, everything works.

I press emergency stop in the web UI

new state: web UI is asking for password, and remote upload doesn't work (401) if I enter the password in the web UI, the UI works, but I can not upload files from prusa

I SSH into the pi, and restart the duetcontrolserver.service

now the file upload works again

When I press the emergency stop button, I have the following control server logs:

Oct 31 13:06:35 lili DuetControlServer[819]: [warn] Emergency stop Oct 31 13:06:35 lili DuetControlServer[819]: [warn] Resetting controller Oct 31 13:06:35 lili DuetControlServer[819]: [info] Application has shut down Oct 31 13:06:35 lili systemd[1]: duetcontrolserver.service: Succeeded. Oct 31 13:06:35 lili systemd[1]: duetcontrolserver.service: Consumed 25.798s CPU time. Oct 31 13:06:35 lili systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 1. Oct 31 13:06:35 lili systemd[1]: Stopped Duet Control Server. Oct 31 13:06:35 lili systemd[1]: duetcontrolserver.service: Consumed 25.798s CPU time. Oct 31 13:06:35 lili systemd[1]: Starting Duet Control Server... Oct 31 13:06:36 lili DuetControlServer[982]: Duet Control Server v3.4.4 Oct 31 13:06:36 lili DuetControlServer[982]: Written by Christian Hammacher for Duet3D Oct 31 13:06:36 lili DuetControlServer[982]: Licensed under the terms of the GNU Public License Version 3 Oct 31 13:06:36 lili DuetControlServer[982]: [info] Settings loaded Oct 31 13:06:36 lili DuetControlServer[982]: [info] Environment initialized Oct 31 13:06:36 lili DuetControlServer[982]: [info] Connection to Duet established Oct 31 13:06:36 lili DuetControlServer[982]: [info] IPC socket created at /run/dsf/dcs.sock Oct 31 13:06:37 lili systemd[1]: Started Duet Control Server. Oct 31 13:06:37 lili DuetControlServer[982]: [info] Starting macro file config.g on channel Trigger Oct 31 13:06:38 lili DuetControlServer[982]: [info] Finished macro file config.g

And when I restart it to "fix things", I have this logs:

ct 31 13:07:41 lili systemd[1]: Stopping Duet Control Server... Oct 31 13:07:41 lili DuetControlServer[982]: [warn] Received SIGTERM, shutting down... Oct 31 13:07:41 lili DuetControlServer[982]: [info] Application has shut down Oct 31 13:07:42 lili systemd[1]: duetcontrolserver.service: Succeeded. Oct 31 13:07:42 lili systemd[1]: Stopped Duet Control Server. Oct 31 13:07:42 lili systemd[1]: duetcontrolserver.service: Consumed 10.851s CPU time. Oct 31 13:07:42 lili systemd[1]: Starting Duet Control Server... Oct 31 13:07:42 lili DuetControlServer[1089]: Duet Control Server v3.4.4 Oct 31 13:07:42 lili DuetControlServer[1089]: Written by Christian Hammacher for Duet3D Oct 31 13:07:42 lili DuetControlServer[1089]: Licensed under the terms of the GNU Public License Version 3 Oct 31 13:07:42 lili DuetControlServer[1089]: [info] Settings loaded Oct 31 13:07:43 lili DuetControlServer[1089]: [info] Environment initialized Oct 31 13:07:43 lili DuetControlServer[1089]: [info] Connection to Duet established Oct 31 13:07:43 lili DuetControlServer[1089]: [info] IPC socket created at /run/dsf/dcs.sock Oct 31 13:07:43 lili systemd[1]: Started Duet Control Server.

@dc42 It is actually in the doc, I don't know why I missed it. Thanks.