@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.0 19-04-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 io7.in
@dc42 Solved. Will check later to see if I can measure what is happening on io7.in and i5.in on those 2 boars, to see if I can measure the values you told me to measure. SHpuld I create a new post or stay here with an update later?
-
RE: Problem on io7.in
@dc42 thanks, I this this would be the last: if I use ou7.in for a swich and out.out for the other swith, both will share GRND, right. Any problem with that config?
In formware would be
M950 J4 C"!io7.in"
M950 J7 C"^io7.out"With this config something is wrong: I connect both switches and the status on the boject model changes. If I activate (manually) the switches, there is no response. Both switches are NC
-
RE: Problem on io7.in
@dc42 thanks , will chek that . As an alternative: I dont have any other free io.in pin, reading docs says I can have 32 gpin ports. Is that number taking into consideration the use of expansion board or I can transfor and .OUT pin into an .IN pin?
-
RE: Problem on io7.in
@T3P3Tony have a surprise jajajaja. Since I dont know what to measure on the board to check if the pin is faulty or not, I tried on another board, this one is a v1.02. This board has the same exact configuration and the sensor BUT io7.in was being used, so in this case I had io5.in free so I connected the sensor there... and it doesnt work, exactly the same failure like with the other board.
I modified the config in order to use io7.in... and the sensor works perfect.
I go again to the V1.01 board, change config to use io5.in... and works!
This is very strange!
Update: I have tested a third board, V1.01b, in this one io7.in is also failingIs there any value I can measure on the board or something ??
-
RE: shutting down a servo?
@droftarts I remember having tried that servo, I changed it just becauso of it torque (the futaba one is almost double). And the other important differentce is that your servo is analog, mine is digital
-
RE: shutting down a servo?
@jay_s_uk ok. My intentio is not to cut the power" but to achieve what in the documentatios is refered as away to avoid having the servo in a stall situation.
lets forget about the noise, if I execute m42 P0 S0 even if I have the noise I can trust no control signal is being sent to the servo? -
RE: shutting down a servo?
@droftarts Sorry, I missread. You meant M42 and I read M280 jajaja. Sorry again.
I intentionally moved the servo to a position that I know will create a stall situation. I can hear the buzzing sound on the servo. Then I executed M42 P0 S0, and the sound is still there and it is not possible to move the servo by hand, it is definitely having power and trying to reach the commanded position, so the M42 command seems to not have the effect Im looking for? -
RE: shutting down a servo?
@droftarts that was my understanding, yes. But as I posted above, reading the documentation again on the link provided, says "then use M280 P# S0 to stop commanding the servo"
To my understanding stop commanding meand stop sending command signal or something similar. An as stated on the documentation, that comand is an option in the case where the servo is may be neing prevented from reaching position, so the servo will start to draw a lot fo current. To avoid taht we can command the movement , and then send M280 P# S0.
Then the information on docuemntation might need to be updated/corrected?
Going back to my problem: any idea on how can I shut down the servo?
-
RE: variable to objects are pointers or something like that
@dc42 DSF Version: 3.4.6
Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.6