Duet WiFi firmware new feature priorities
-
When you increase the speed with M220, the maximum speeds, accelerations and jerk you configure in config.g are still respected.
ok cool, i was not sure about that one,
is the M220 the one on the interface? ( slider bar on web interface and PanelDue?)
so really its mainly Homing, ( this is where i normally have seen it) as well i have seen it on the start of a print. or a finish, but that could just be that i did not have my max speed set right at the time.
Thanks !!!
~Russ
-
Yes, the speed slider uses M220.
Currently the speed of homing moves does get affected by M220. This is one of the reasons that I am thinking of changing M220 to affect printing moves only, so not travel or homing moves or retractions. Firmware retractions are already not affected by M220.
-
Yes, the speed slider uses M220.
Currently the speed of homing moves does get affected by M220. This is one of the reasons that I am thinking of changing M220 to affect printing moves only, so not travel or homing moves or retractions. Firmware retractions are already not affected by M220.
ok, thanks David!
yeah, I've had a lot of experience with marlin, and homing in not effected by speed settings. However even marlin will crash on the start of the print if the speed % is set way to high. That first move from home to the bed is a "Print" move.
with that said, it would be smart to have the the homing moves not be effected by the % speed settings.
I'm not sure if there is an easy way to do it within the firmware with out other things being effected.
I do agree with others that if the %speed is set to xx value then it constantly being overwritten is a pain.
Is there was a way to " read" the value of the % speed setting? Then we could set up a simple line of code at the beginning of the home.g file to read and save that % speed in memory, then set it to 100% run the homing stuff, Then at the end just wright back to where it was ???…
the same with all other things we all ways want to run at 100% of speed. like bed probing and stuff ( I'm not sure if that speed is effected or not?) but we could use that command to read speed setting> do something at 100'%> wright back speed setting from before.
this might be a useful thing for other things as well...any how just a thought, I'm not even sure is possible from the front end ( code) or if its something already there i don't know about..
Thanks!!
~Russ
-
On option would be to have the speed setting included when the firmware saves parameters before executing a macro file. Then you could use M220 S100 at the start of the homing files, bed.g etc. But then you wouldn't be able to define a macro that e.g. sets the speed to 150%.
-
I wouldn't go much farther than disabling the speed override for homing. If maximum speeds are set for all axes, and they are reasonable, no crashes should ever occur. In my opinion, max speeds should be set so that no g-code can cause undesirable behaviour. If I accidentally home my printer at 10,000% speed, it will (presumably, I haven't tried it) home at the max Z speed of 60 mm/s. Isn't that what limits are for? If your printer is crashing upon first move, limit the Z speed to one that will not cause a crash.
-
When you implement "Support for three independently-controlled Z motors" can you also add support for two independently-controlled Z motors? I have two motors on each side of the heated bed, and I believe this isn't an uncommon setup.
-
Yes I will be supporting 2, 3 and 4 independent Z motors.
-
Yes I will be supporting 2, 3 and 4 independent Z motors.
Hi David…We talked on the RepRap forum about using 2 Z motors and multiple belts to sync the 4 corners of the XY carriage on my fixed bed (non-adjustable) Core XY build. You confirmed that Duet will soon have ability to independently control and sync multiple Z motors. Since I have 4 lead screws supporting the XY carriage in Z motion, will it be feasible to do away with the belts and run separate motors on each screw to level the XY carriage to the frame mounted bed? I'm at a stage where I can add two additional Z motors to the build for little cost. If you see this as a practical scenario I'd like to make that change now and be ready when the firmware upgrades are in place. Thanks...TP.
-
Yes you can do that. You will need a DueX5 expansion board so as to have enough drivers. Until the new firmware is ready, be prepared for the motors to get slightly out of sync when you power cycle the printer.
-
So then I assume a thumb knob at the top of each shaft would allow one to manually adjust the four corner back to level after power up. Will we eventually be able to probe the four corners through a program routine to level the XY carriage to a fixed bed?
-
Yes, that's correct. You might want to temporarily reduce the Z motor currents using M913 while doing the adjustment.
-
Not a very useful feature for most people, however I would love to see support for the Z-endstop being a safety for the Z-Probe homing. I've crashed the nozzle into the bed sooo many times while messing around with Z-Probes of different natures all while that mechanical Z endstop switch is triggered but doing nothing. I know, not many people would care. I guess I could wire that in to kill the machine if it's triggered somehow. So I guess my request would be for support for mechanical Z endstop while using a Z-probe for homing.
Jeff
-
@(In)Sanity:
Not a very useful feature for most people, however I would love to see support for the Z-endstop being a safety for the Z-Probe homing. I've crashed the nozzle into the bed sooo many times while messing around with Z-Probes of different natures all while that mechanical Z endstop switch is triggered but doing nothing. I know, not many people would care. I guess I could wire that in to kill the machine if it's triggered somehow. So I guess my request would be for support for mechanical Z endstop while using a Z-probe for homing.
Jeff
You can do that already (I have). Just wire the mechanical switch to a spare end stop (say E1) then use M581 - something like this M581 E1 S1 T0 C0.
-
I'm going to expand on my request to say, if any endstop is triggered stop trying to move in that direction. It's crazy you can get the printer in a state where it hits the endstops but just keeps on grinding away. It seams like some kind of Sanity check would be useful.
Thanks,
Jeff
-
@(In)Sanity:
Not a very useful feature for most people, however I would love to see support for the Z-endstop being a safety for the Z-Probe homing. I've crashed the nozzle into the bed sooo many times while messing around with Z-Probes of different natures all while that mechanical Z endstop switch is triggered but doing nothing. I know, not many people would care. I guess I could wire that in to kill the machine if it's triggered somehow. So I guess my request would be for support for mechanical Z endstop while using a Z-probe for homing.
Jeff
You can do that already (I have). Just wire the mechanical switch to a spare end stop (say E1) then use M581 - something like this M581 E1 S1 T0 C0.
Ok, I just moved my Z-Endstop over to E1 and did as you suggested just changing S1 to S0 due to makerbot style endstops. Works like a charm, if I dig the nozzle in even a little bit past normal calibration it just shuts down….love it!! So now I guess I need double trigger endstops to do this on the X and Y also. Easier in software.
Thanks,
Jeff
-
There's nothing to stop you having the shutdown trigger if the X and Y endstops are activated too. Just change the command to:
M581 X1 Y1 E1 S1 T0 C0
but you will have to disable this during homing, obviously!
-
There's nothing to stop you having the shutdown trigger if the X and Y endstops are activated too. Just change the command to:
M581 X1 Y1 E1 S1 T0 C0
but you will have to disable this during homing, obviously!
That is a fantastic idea. Thank you!
Jeff
-
Something else I did was to install switches on all the axes maxima, wired together in series and connected to yet another spare E stop. Then if I do something stupid like send an axis beyond it's maximum position before I've homed it, then it'll trigger an emergency stop before the frame gets mangled. I also have a physical emergency stop button wired the same way to yet another spare. It isn't a true emergency stop in that it doesn't cut all power - if I want to do that, I just press the button on the RCD I use to kill everything.
-
Something else I did was to install switches on all the axes maxima, wired together in series and connected to yet another spare E stop. Then if I do something stupid like send an axis beyond it's maximum position before I've homed it, then it'll trigger an emergency stop before the frame gets mangled. I also have a physical emergency stop button wired the same way to yet another spare. It isn't a true emergency stop in that it doesn't cut all power - if I want to do that, I just press the button on the RCD I use to kill everything.
That's a good idea. It would be kind of neat if the firmware had the option to Not travel in a direction opposite of the end stops if you've not already homed. That way it would prevent some stupidity on the users end (myself). I've implemented the X Y and Z endstops triggering trigger2.g which I then just put an M112 in the file. Why did I go with the file…IDK...seamed like a good idea. It shuts off during homing moves except for homing the Z axis which is for really bad situations.
Thinking about it the option to prevent Non Homing moves if not homed would be good. Pretty much if your not seeking a home during a move and your not already homed prevent the move. Just a thought.
Jeff
-
@(In)Sanity:
It would be kind of neat if the firmware had the option to Not travel in a direction opposite of the end stops if you've not already homed.
This is incredibly common in industrial motion controllers. I also think this is a fabulous idea.
