Posts made by Tinchus

@T3P3Tony I dont have any printer on stand alone mode.

have created in the past a similar post but the proposed solution is like "too much" maybe and I would like to know if there is an alternative beucase the purpose of the original post might not been clear from my side.

Sometimes, I find a print paused, stopped, etc. The reason for this could be something "internal" (some error detected, some trigger, etc) sometimes can be someting simple like a student touching what he shouldnt touch (grrrrr)

But sometimes I also find that the duet interface is blank and I have a icon to "reload", I reload it and the interface connect again to duet. The problem with this is like it seems this connection is brand new frokm the duet perspective and if I go to console to see the logs in order to see what happened, the console logs are empty because of this brand new connection.

In the past I have activated looging through gcode command, but I find this option with time really uses a lot of sd card space, is there any log being kept with just the console contents of the ongoing print?

Thanks in advance

@Notepad Thanks for the feedback. Yes! I already tried the phone aprouch, not really sure yet how precise the app reading is but I have that data. I also found that input chaping ahs a grapgh where vibrations are shown, so Im in the process of getting an accelerometer in order to start test.
Yes, I have really high quality ballscrews. Im still not sure that resonance is born on the ballscrew itself and not on the stepper motor. The ballscrews are already included on the steppers, the re is no connector between them.
At the other end of the ballscrews since they are really straight, they are fixed into a a cnc with a bearing where the ballscrew tip fits. I was thinking on modify this and put some kind of rubber dumper and see (again: Im not sure if vibrations is being created by resonance on the ballscrew or in the stepper)

@infiniteloop I have not tried this material of course, but I have indeed trying to shorten queu lenght in the past several times wheing trying make a macro introduce code faster in the queu for example. I can perfectly agree and confirm that printing becomes "bumpy". So, in the case of this talking about this material, if the movement suffers this kind of artifacts, for sure we can predict flow will be completly out of control because we can maka a paralel situation when you have moisture on you filement: can can get away sometiomes with lot of moisture, but at the moment the nozzle stops just for hal a second, you will see material being extruded A LOT.
From an engineering point fo view, when you face a develpment where at the very beginning the posible solution already faces a lot of problems... that is my sign to "ok, this solution will not end up well, lets look for another aprouch" and this is the case.
In this case, if you already recognize that the material has not a predictable flow, trying to control that chaos is something that will not get to a good solution. I would go towards try to get a better material, OR just not try to get a eprfect flow control.
Remeber this: this has already happened in the past. Maaaaany years ago, in the time where filament diameters where not as precise as today, opeple tried to use optical filament diameter sensor in order to measure diameter on the fly and adjust the flo on the fly. And that aprouch NEVER worked because you had to provide the firmware with the exact offset between the sensor position and the tip of the nozzle, and just an error of 0.2mm gives you more error on the flow calculation than a +-0.1 in fialment diameter so...
I still have one of those sensors by the way lol

@oliof But The vibration Im describing has no visible effect on the print, so how can I measure the vibration (I dont have special equipment for that)

I hav a couple of printer, they have ballscrews on X and Y axis. The "propblem" is (already asked to the motor manufacturer) is if I run a 42/45 mm/s speed and in the middle of X position (printherad at the middle of the ballscrews lenght) you can hear a vibration starting to grow up till the vibration becomes an earthquake and only when moving on negative direction.
manufacturer says Im hitting the resonance point of the setup. This problem never happens with any other speed.
So my question is: is there any way from firmware to restrict this range of speed of being used?

@o_lampe You cant do this. In the moment you measured the flow at the output of the nozzle, the gcode command will enter the queu... The flow modification wont be at the proper timming never ever.
In my opinion this is one of those request where the solution is being looked at the incorrect place. Just make sure you extruder works properly, your filament is in the proper state (dry) and you are done.

You have flow rate control on many slicers already (superslice foe example lets you set a max extrusio rate and set every type of path to use that max value. So in your case ofr example if you want to limit a 5 mm3/s of flow you can do it.

A really nice one: The APUS extruder. I have been using since I got it,

@Tinchus I have an extra observation. while trying to separate the BL cable from the resto fo the cables, electronics were off, I moved the printhead by hand and the red led of the bl touch turned on, is that ok?

@Phaedrux Can you give more specific sugestions on what oyu se as a potential wiring problem, and how you would route cables? If I use the short cable for BL, it is kind of imposible to keep other cables away since they are loner cables Right now as you can see on th pictures BL cables are tgether on the printhead bundle. I have tries to look online for cable steup and ewverything I find are cable bundles, Even if I route every cable apart, they will somehow need to close each other when they get connected to the duet.
Please advise on what potential problem you see on pictures so I can specifically fix that
Are all sure thare is no bug in actual version or if compatible is checked on latest firmware version? Today I noticed something: when pin is not deployed, and if I manually deploy iit, led on BL readcts. If I push pin up with fingers, DWC never sees the BL activation (zprobe value is always cero). If I issue an M402 pins goes up, then M401 deploys the pin and if I try to trigger it, pin is trigger but DWC nevers sees that, probe value is always cero. Then If I do a software emergency stop, the pin drops down, and if I trigger it with my fingers, goes up and gets re deployed inmediatly and I need to turn of power in order to get control again.
Thanks in advance

@Phaedrux Sure.

On the left there is bltouch an its connections marked as 1 and 2. Cable is new, and shielded with a metal tape. En the right is heatsing fan cable, thermistor and heater cartridge cable all together marked as 3

All cables ogether with extrudet stepper motor cable get together on top of the printhead. On the picture you see them but in reality they are all together inside a chain cable (not in the picture since I jhad to remove it in order to do test but since the chain cable is plastic, should not make any difference in fact with cable chain should be worst scenario because all cables are tigheter, still the problem exist without the chain cable.
Numer 4 is extruder cable, number 5 is BL touch cable, and on the right the heater cartridge cable and 6 is the hatsing fan cables. As seen , stepper motor cable is also shielded

On duet side I have bltocuh conection on io7, as you can see on the last part is not shielded (does it matter). Above that there is X endstop connection and next to it the Y endstop copnnection.

The cable markes as SIGNAL bed is a cable that is just like 5 cms close, it si on the pictture but it is a conection from out1 that feeds a mosfet feeding the heated bed.

And this is the metal tape I use for shielding, I guess it works because it solved the noise problem on the flat cable of the SBC in about 8 printers using duet3 on the school.

@droftarts Ok, new cable installed. looks like situation is much better now but still Im having from time to time the pin droping and then going up very quickly but not enough becuse it hits the print and the pin as bent twice... I saw in real time that: when it happened I saw the red led blink for a second. Rading and reading this could be an interference issue or problem on the 5V line, also some people installed a small capacitor between S and GRND on the bltocuh.
Thoughts?

Hello. Im having an issue with bltocu on other post, but that issue brought this question: I have my bltocuh defined like this (actually taken from documentation)

M558 P9 C"io7.in" F100 H5 R0.2 T6000 A5 B1
This defines as probing dive height 5mm
At the end of my homez.g I set the Z position at 6mm
lets say a new print is launch, position is Z6 if the probing is done, shouldnt stop if after going down for 5 mm probe is not triggered?
Since my offsets are: G31 X-27 Y-4 Z1.76 P25 ; bltouch offsets, the nozzle will actually crash at Z4.24 if probe is not deployed/triggered

Is there any way to avoid the nozzle crashing into the bed if probing is not triggered?

@Phaedrux Ok, did it. It works, but as I wrote above, behaviour is really erratic. Sometimes the probe is deployed, sometiomes is doplyed like with a 2 or 3 seconds of delay, sometimes is never deplyed.
Since the post started, I have re donde the conection crimps, I have shielded the cable, I have re donde the crimp again on the duet side conector, I have shorten the cable like -20 cms.
I have been readin a lot of post with similar problems and from there is that I have tried all these posible solutions.
The only one left could be noise? While probing there is no heater on, no fan on either.
ANother observation: leaving the printer on, just IDLE, may be after 10 minutes sometimes after 1 hs, I can hear the bltouch being deplyed and inmedaitly retracted.
I have discarded the posibility of a broken bltocuh, this one was working in the same printer.The only change was: the printer is an old, REALLY old i3 style, instead of decomision it, I though "hey, lets give it a bump, new electronics!" and I used a duet3 board I have as a spare (+sbc). But the bltocuh was connected to a ramp 1.4 arduino mega 2560 and was working really well with no problem at all.
May be there is some campatibility issue with duet? I really dont know how much is has been tested since bltocuh is also a really "old" hardware by now? Just thinking aloud.

Logic is 5V? I would like to confirm this before trying to force a 5V logic woirking mode on the blotouch

@gloomyandy ot sure I understand on what position in home.z you want me to put the commands.
from console, I can execute M401 and M402, and in 20 tries I will have 100% rate success
Inside home.z xactly where?

@DIY-O-Sphere Thnka for the help. I did the chnages and still the same problem. Weird thing is: M402 and M401 works 100% all the times. It is just the homeall home Z routines that fail into deploying the probe randomly (fails 80% of the times or more)
It theory the voltage logic is automatic on version 3 of bltouch, I dont know if the duet3 has a 3 V logic or 5V, my huess is 5 because the only pin not conected to the bltouch is the 3V pin si I guess it is 5V? can someone confirm? I would try forcing the bltouch to use 5V logic just in case?
Im using the original bltouch, with the otiginal extension cable (80 cms long), it is already twisted so it has a noise protection, either way I wrapped metallic tape around to shield it, it is ok?
May be this cable is too long? (Still, the fact that M401 and M402 deploy and retracts the pin with no problem at all would say voltage it is not a problem)

And just to confirm: on wiring instructions on the grn pin, I have to conect in that pin2 cables: black and orange, is that ok?

@DIY-O-Sphere can you please share your homez.g file to me so I can see if there is something wrong there, and deployprobe.g and retractprobe.g files?

Things have improved, still something is wrong. Cable is shielded. And despite onw the positioning of the bltouch is way from stepper, sudfdenly Im having the same issue: home Z and home all doesnt deploy the sensor. If I press emergency stop the pin drops as being deployes, sometimes in error state sometime like just having been deployed, more ideas? I changed the cable, I crimpred the pins again, dont know what else to do

@DIY-O-Sphere , one question: bltouch seems to be ok now. But today I noticed something: the printer was on, idle state. I was on the computer entxt to it, and sudenly I saw the pin gown down without any instruction to do so, and inmediately was retracted again. Have you seen that in your setup? It worries me of course that happens during a print, since I guess that would mean at least loose steps, and also a posible damage on the pin...