@argo Update on this issue: using the curve smoothing solves the problem. Also, I made a copy of the original STL using solidworks, exported it as STL but using max quality for the STL and also the print came out PERFECT.
So all this issue is about the STL quality
Thanks all for the help
Best posts made by Tinchus
-
RE: "waves" on rounded prints
-
RE: BtnCmd-DWC Plugin - Customise DWC - v01.03.05 20-09-24
@chimaeragh Sure. For example, when I want to save the total uptime of the machine I execute count.g:
echo >"uptime.g" "global.ontime =",{global.ontime + state.upTime/60}This saves in uptime.g the value of the global.ontime, and I get that value from the object model
Next time the machine restarts, in config.g I have a M98 P"uptime.g", so the value of the global variable is read again and keeps being incremented.
-
RE: cant connect to https://pkg.duet3d.com for update
@Falcounet Today I tried again and this time connection was ok... weird. But problem is fixed. Thanks!
-
RE: delete
@blv there is no need to teach formulas or motion theroy, at least to me, Im a senior mechanical engineer, I guess I have those topics very clear. So Im pretty sure you can post your slicer profile, your config, and the STL so we can all see the sizes involved and it will be very simple to demostrate what I said is correct. But we can also do very super quick calulations looking the video: the size of the object is aprox 12 cms long. I has a soft cuve too. so lets say that segment is a real 15 cms as much it it is straight? If you print at 500 mm/s that means we should be watching your printhead cover those 15 cms in aprox 1/33 of a second without taking into consideration the acceleration. If we take into consideration the accel of 9000 you will reach something around 300 mm/s of max speed AND ONLY for a fraction of the path. Im dpoing all these calculation by my eye so I might be wrong in 20/50 mm/s max error.
And Im still not taking into account your jerk settings.
And this is the speed you get in your longest path, the rest of your STL model wont get even half of the calculated speed I have mentioned.
So...And Im not fan of nobody. I use what I considere that covers my needs. I have used klipper. It is based on python, python uses an interpret to work. That means an extra layer between klipper and the processor. So it works very nive, but no software till today is as fast as a well C++ / C code is working directly with the processor... Or have you ever seen an OS written in python ?
The firmware duet is working on is really powerful, enough for me moving from marlin.
But hey... if you are fine with klipper, OK! keep using. You have to use whatever covers your needs man.
Also I think it would be usufull if you clear what you mean with "extra perfomance", it would be a good way to contibute here to the developers.
-
RE: Unable to tune chamber heater
@davidewen @dc42 There are several post about this issue with heated chambers.
In my case the problem raised with version 3.3 and up. Something changed on that PID implementation. Before that, my heated chamber was using the old PID very good.After I upgraded, the problem raised. So I tried to autotune again and I was getting the same errors like you. After playing a while, what I did was: I raised deadtime value A LOT. That way, autotune was able to finish.
BUT then it didnt worked: the values I got from autotune, should have worked but every time I tried to heat up the chamber, an error was there: temp rising too slowly.
Running autotune several times worked again, but then again, using the reported values always failed with the same error.Then I did a trick: I ran autotune but using ONLY 80% of the PWM. Then to the reported values I changed the PWM to 100%. That is the only way I have been able to use PID on the heated chamber
I hope it helps
-
RE: Causes for heater instability
Im my case, the times this exact thing happened to me, was a bad connection on my thhermistor cables, a badly soldered crimp. Resoldering always solved my problem. This problem was never detected by eye, the graphics is the one that have indicated me the problem.
-
RE: Update interrupted
Thanks both. Yes, I had the local display, wich turned black after loosing the ssh connection.
I rebooted, it booted on 3.3 version. Then I repeated the comand in ssh and I got a "resume" message, wich worked ok. Thanks! -
RE: Z offset on Inductive sensors
@fcwilt because I planned the printer to have eough power to have all the build plate full of print, and since it is a big volumen, theoretically I can have like 15 kgs if I print metal. So Z motors have enough power to move that mass.
BUT, if something goes wrong, the also have the power to destroy my hotenfd and bend the bed if the printhead crash against the bed at full powwer. By reducing to 30% while homing, if something goes wrong, they will start to loose steps before bending my bed. -
oibject model "status" dcos.
Hello. I have checked https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation#statestatus
I see "printing" status is not there anymore. It has been replaced for what other value?
his property may be one of the following:
disconnected: Not connected to the Duet starting: Processing config.g updating: The firmware is being updated off: The machine is turned off (i.e. the input voltage is too low for operation) halted: The machine has encountered an emergency stop and is ready to reset pausing: The machine is about to pause a file job paused: The machine has paused a file job resuming: The machine is about to resume a paused file job cancelling: Job file is being cancelled processing: The machine is processing a file job simulating: The machine is simulating a file job to determine its processing time busy: The machine is busy doing something (e.g. moving) changingTool: The machine is changing the current tool idle: The machine is on but has nothing to do
-
RE: z probe sensibility and mesh calibration with G29
@jay_s_uk I created the mesh.g file, and modified accel and jer there for mesh calibration the restore the original values to normal after the G29 S0 command .
Latest posts made by Tinchus
-
RE: Problem on new installation / upgrade
@chrishamm Will do, thanks. Where can I find those releases? the images posted here https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup have same name and date as the others so I guess are old ones
-
Vibrations, resonance, stealhshop and emf calculator
Hello. I have another post similar to my issue regarding vibrations: https://forum.duet3d.com/topic/36540/vibration-on-motors-at-low-speed?_=1726668381705
My specs: cartesian printer, nema23 ballscrew motors, 1 in Y 2 for moving X connected in seriedReading others posts, documentation, I would say my "issue" is what @dc42 tld me about mid band resonance, most probably I can say after looking more deep into this. Mechanical reason are completly confirmed out of the scope
I decided after some reding to give a try to stealthchop2. My drivers are configured so far to be all the time on spreadcycle
I have some question if possible @dc42 can clarify because on some of his past answers some info is not clear to me (not an electronic guy here)
1.- Used the emf calculator and here it is a screenshot ; (My serious doubt there is how my X mmotors are connected, they are both connected to the same driver, but I dont know if it is a parallel connection or they are in series, help on this?)
. Stealshchop is not reliable if enough voltage is not supplied. So acording to me screenshot a switch speed limit of 12 mm/s is my limit, if I go up I start to get ugly numbers like for example if I go for 20 mm/s I get:
Approximate total rotational back EMF: 19.7 V at 20.0 mm/s
Approximate total inductive back EMF: 39.8V at 20.0 mm/s
So those 39.8 V tells me that I would need to get a PSU capable of supplying the duet3 board with 40 Volts?2.- The values of the emf calculaor only applies to stealhschop? because on spreadcycle I have no problems running at speeds of real 200 mm/s (my issue is onlky vibration of the motors on the range between 10 mm/s and 18 mm/s)
3.- I did a test M569 P0 H196 V196 These values removed almost all vibrations on the X motors and M569 P1 H196 V196 on Y. I also used
M915 P0 T196
M915 P1 T196But in my case I dont use stall detection, so is it necesary? Because those commands are intended for coolstep, withh these have any effect on my config?
4.- I have created a small macro in order to activate stealchop during my tests, is this ok?
silence.gM18 G28 X0 Y0 M569 P0 H196 V196 M915 P0 T196 M569 P0 H196 V196 M915 P1 T196 M17 X Y G4 S0.5 G91 G1 X1 F500 G1 Y1 F500 G90
4.- As I said, printing not at 12 mm/s using this config eliminated vibrations but even Im not loosing steps, all changing directions movements, like small zigzag infill, are done very noise with a "clak", Im not losing steps, I already printed test cubes. That noize comen in every direction change id it looks like every of thise movements are done purely using jerk speed (200 mm/min in my case on both axis), like there is no acceleration being used, but I know that is not correct. Ideas on this?
Thank you very much for the info I can use to learn and the help you can provide me.
-
RE: Maximum Acceleration Calculator
Hi all. Question: the calculator here https://wilriker.github.io/maximum-acceleration-calculator/ request some data but what is about the case where you dont use pulleys? (axis moved directly using ballscrews for example)
-
RE: vibration on motors at low speed
@droftarts jajajaj I have just read that article jajajaja thanks
-
RE: vibration on motors at low speed
@dc42 thanks a lot for the comments. I will look for information about this. So you think at this moment there is not much I can do about it??
Yes, I have interpolation enabled and motors are isen 1/16 microstepping -
RE: [feature] Adaptive / Feedforward Temperature setpoint
@timschneider that is what I meant. May be Im wrong so please clarify: the push request is using the new requested T parameter in terms of extrusion speed or volumentric speed? Because the firmeware actually never knows what size of nozzle you are using: if slicer request a 10 mm/s extrusion move and you are using a 0.8 nozzle volumen and needed temperature will be quite dfifferent if the slicer request the same speed but you are using a 0.4 nozzle. am I wrong?
-
RE: [feature] Adaptive / Feedforward Temperature setpoint
@timschneider I wonder if temp increase VS speed will be ok when you change to a bigger noozle and you go slow; in that situation you would have a potential huge increment of mm3/s but a lower speed. Example: 100 MM/s speed with a 0.4 noozle . The you switch to a 0.8 nozzle and go to 80 mm/s
-
RE: [feature] Adaptive / Feedforward Temperature setpoint
@droftarts I was just about to post a question regarding feed forward till I found this post.
I think the feedforwwar tool doesnt cover all the issue. As mentioned here, you can print perfectly PLA at 180 degrees with excelent quality, BUT you will be restricted on how fast you can print. On the other hand, you can print PLA at 150 mm/s on a 0.8 nozzle only if you go up in your temp to 230 degrees oir little more, but as soon as you slow down you quality goes to the trash bin because of that excesive temp.The feedforward config at least to me has not solved this in my prints, I have to either choose print really fast and hot or normal/slow and "cold". My question was going to be if the feedforward command could add some type of algorithm to take into account the cubic mms being extruded instead of the printing speed, in that way you would be covering all nozzle spectrum and printing speed at the same time.
And regarding where: I think the oposite. It should be the formware the one in charge of that because the slicer never knows the real speed of a path. Final real speed is decided by firmware, the slciewr never knows the real printing speed (and that is the reason why the time calculation on slicer are allways really off)
-
vibration on motors at low speed
Hi. This is a duet3, firmware 3.5.2, SBC
In this printer I have all nema23 motors with ballscrews. There is a huge difference in vibration when motors run at low speeds, they vibrate a lot, it is not a mechanical issue, I have double checked that very deeply. I can feel by hand how the motors start to vibrate at speeds in the range 19 mm/s to 10 mm/s, at higher speeds they stop doing that.
Im using a 1/16 stepping on the config.
Documentation about the drivers is really complex, could someone give me a hint on what clould I try from the config point of view to do some steps in order to see if I can improve this behaviour? this motors are suposed to be really good quality (Moons brand)
Thanks in advance for the help you can give me -
RE: Problem on new installation / upgrade
@Phaedrux This issue happened also to me. I did used the pi imager. During the config process it asked to create an user. I did it. Later that user nor the default pi user were recognized