@dc42
The drivers are set to 1500mA (12v) and while the drivers could take more I am not comfortable running the motor at much more.
I suspect the real cause of the problem is the 8mm Y transfer axel instead of the 5mm that is usually used and the Iglidur G bearings don't like the kind of transverse load that the bands put it under.
I hope to be able to replace the Iglidur with roller bearings soon as that will likely solve the problem for real.
@dc42
yeah.
That was the first I checked, all the pulleys are well attached and all belts are tight.
I suspect the problem is in the end that the Gates power grip gt belts stretches just a little bit when changing directions.
As the weight in the Y carriage is substantial and I likely have too much friction in it that I need to remove by rebuilding the gantry.
The problem is that I won't have time to do that rebuild for a while so I was looking if any solution exist that I can use in the meantime
I have run into a interesting problem where the Y axis change direction a fraction of a second later than the X axis creating ovals that have its long axis instead of being at 0° and 180°(or 90° and 270°) the long axis are on 110° and 290°, Y also have a flat area from 90 and 270 toward 110° and 290° but not before 90 and 270.
I hope that description makes sense. In reality the issue is because of friction in Y byt if any way to change the timing between Y and X exist I would be interested to know about it as I suspect knowing about something like that will be useful sooner or later and might solve this problem until I have the ability to rebuild the Y transfer.
The machine is a Cartesian and the X band is direct drive but the 2 Y bands are connected to a shared axis that is driven by motor connected to it by a band.
I have locked into the m596 and M670 but can't make heads or tails of if any of those commands could do that.
I run a duet wifi on this machine but I also have a duet 3 in an other machine.
np
Thanks that was what I wanted to know.
as the page on cabling didn't say anything on powering the duet 5v from [5v_ext] so I wanted to check before I started to run the machine for any longer time.
Maybe I should note but I am not trying to power the duet 5v from the SBC so I do still fail to see why I should connect [JP5]
I do lack the knowledge or the experience to actually read something like that but form what I can see I guess you wanted to point out something like this:
So the [SBC -> 5v] are catastrophically mislabeled?
and it is allot better to just use the internal 5v?
Correct?
When I got the card it had [5v->SBC] and [int_5v] jumped.
having both [5v->SBC] and [SBC -> 5v] jumped at the same time seems counterproductive?
or is SBC in those cases actually referring to the [ext_5v +5V] pin?
It seem to work as it should with the SBC when I only have the [SBC -> 5v] jumped.
The way I understand it from the documentation is that the [5v->SBC] and [SBC -> 5v] change if the 5v pin on the flat cable is an output or an input pin?
If I want the duet to receive 5v power from the PSU and to power the SMC, would it be correct to leave [5V->SBC] jumped but not the other 2?
I also wonder if it exist any specific reason why it would be better to use the internal 5V or power the 5V with the [ext_5v +5V] pin?
It makes it easier for me to wire in a on/off switch on the [+5 V standby] cable and then control the rest of the PSU with M80/M81 commands
Thank you for all the help.
Turning the fans off works as you said with noctua fans.
But turning of out4-out6 even when set to work as regular fans don't seem to work though.
Edit:
I thought I got some odd values on the tachometer as I use rather long cables but apparently noctuas 40mm fans are supposed to go at 5000 rpm
Thanks.
Any idea if it might be possible to shut down the power to/from the fan it they are form a maker that don't shut them down completely or if someone have to use the out and gnd pins of the 4 pin connections to control "regular" fans?
Thank you.
Do it exist any way to get the RPM to show up in the new webcontroller GUI or are it hidden because it showed -1?
I also get my edits flagged as spam all the time when I try to clean stuff upp
@Adrian52 said in Anyone know why I wouldn't be able to turn 4-wire fans off?:
s that rpm only shows briefly then disappears, as mentioned by the op
I get this form M408 S2:
{"status":"I","coords":{"axesHomed":[0,0,0],"wpl":1,"xyz":[10.000,125.000,200.000],"machine":[10.000,125.000,200.000],"extr":[78948.0]},"speeds":{"requested":0.0,"top":0.0},"currentTool":-1,"params":{"atxPower":1,"fanPercent":[100,0,0,0,100,0],"speedFactor":100.0,"extrFactors":[100.0],"babystep":0.000},"sensors":{"probeValue":0,"fanRPM":[-1,-1,-1,-1,-1,-1]},"temps":{"chamber":{"current":22.9,"active":0.0,"state":0,"heater":0},"current":[22.9,22.7],"state":[0,1],"tools":{"active":[[210.0]],"standby":[[0.0]]},"extra":[]},"time":212261.0}
Still only "fanRPM":[-1,-1,-1,-1,-1,-1]
Version
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0 (2020-01-03b3) ```
I would really appreciate being able to just cut the power (or the gnd return) for out4-out6 if that is possible, as I am a bit limited in what manufacturers fan I need to connect to them and I need sometime need them to be off.Hi.
I have connected 3st 4 wire PWM fans to a duet 3 and got used to get the RPM value to show up (mostly correct).
But I am completely unable to turn them off.
I can turn them down to 10% speed and then the RPM go from 1300 to 700 (min for the fans should be 300).
But I am completely unable to turn them off M106 S0 just set them to 100%.
Anyone have any Ideas? I am getting a bit mad from this and I am sure is something simple I just haven't thought of but I can't find anyone having the same issue.
I tried to upgrade from the v3 alpha I was running but the only effect that had was that I first got a truly unpleasant web interface that didn't have the possibility to show rpm and when I downgraded to 1.22.5 it have the feeld to show rpm but only show it for a second each time I run M106.
@dc42 Thank you for the excellent and fast response.
I was thinking that it might work with the new one that can run on 3.3v but thank you for helping me before I tried something that might have damaged something.
Hi. I could not find any info if this could work so I post this.
I could not find any info if it is possible to use the BL touch in 3.3v mode only connecting to the 4 pin Z-probe connection in the same way as using 4 of the 5 pins on the duet Maestro or do it exist any reason why that would be a bad idea?
Would this work (Of Course set to use 3.3v not 5v)?
How it is connected to the Duet 2 Maestro for reference:
I am unsure if the sd card was corrupted when I powered it off but all files showed up as empty and unwritable before I unpowered it so I am not sure exactly what happened.
@dc42
Thank you for clarifying about the limits.
Would if be ok for you if I added that info to the gcode page?
If the G30 Pn Xnn Ynn are to be the coordinate you want the probe to touch are the coordinates in M671 the nozzle coordinates or the probe coordinates with the offset in the calculation.
Just wanted to check so that the offsets don't carry over onto the M671 part of the equation.
sorry for using significant my original title was more descriptive but it was to long. Could you remove that from the title as I am apparently unable to .
I did check the release notes but have not had time yet to read all of them and while I found some of the bugs I have listed I did not find others among them a tendency to format the sd card with all info
So I could not find a bug report forum so I might as well write everything in one post instead.
So I decided to start up an prototype printer we built at work a while back but had stood unused for about 1.5-2 years and set it up for use and calibrate it.
The upgrade first failed when I tried to install the latest immediately but worked when I did the step by step upgrade as the instructions said so that was my mistake and in the end no problem.
The problems:
Some other stuff:
What is the proper way to define the offset of the Probe in relation to the nozzle?
I have defined the print volume as the area that the nozzle can reach so that 0:0:0 is when the x and y endstop is triggered and the nozzle is in hight with the print bed. (furthest back and to the right).
My assumption was that if the probe offset was correctly set it would still move the print head with the previous defined limits and just do a software correction to the heightmap etc so that the height would be correct with regards to the tool position not the probe.
When I set the offset between the tool and the z-probe with G31 and run G29(and G32) the printer tries to move the probe to the right to reach 0:0 ignoring the triggered endstop and making a whole lot of noise as it was running full speed into the x- stepper.
Is this a bug or expected behavior and what is the way that corrections to probe offset should be used with the heightmap.
G32:
I think that it is a good idea and helpful with it giving information on how many turns to rotate the screws I am unsure how correct the values can be calculated without the offset set.
I would also like to be able to have it write out the z trigger heights as it did in previous versions so I can check if the values are looks to be correct.
G32 interactions with G29.
The company I work for use a removable build plate with 4 calibration points. We would of course like to use the heightmap to get the best possible result but we would like to be able to use the G32 measurement before print to do a quick check before print and to do some fine adjustments of the base plane the heightmap is applied on.
It would also be a good thing to be able to use the G32 for a confirmation that the build plate is within limits for what is considered flat and can be corrected for in print. If the build plate fails this test it would be good if an error msg was shown and the print aborted.
Best regards
Axel
The video https://photos.app.goo.gl/e78HytZowKtFqhjy9
The Z-axis is set to have a movement range between 0 and 22 mm and it is triggered ahead of time to not have it run into the print head.
In the video I tell it to go to +1 mm but each time I press +1 it moves to either 0 or 22 depending on what it was at before but it do not stop between those numbers.
P.S.
64 characters are to few for topic titles 