- User Since
- Aug 16 2016, 11:31 PM (149 w, 17 h)
Mon, Jun 24
@karrad This settings don't have any resolve functions, also there is no idea how to make this functions work properly. So now I have two solutions:
- Add another field for setting from which extruder pick this values
- Move this settings to be global for printer instance(this will hold values in printer file and value will be set for all profiles of one printer)
@karrad fixed, please check.
Tue, Jun 18
Thu, Jun 13
Tue, May 28
This will prevent the need to duplicate all the 3mm profiles, and just allow us to use the same settings for 1.75mm?
When updating the 3mm profiles on the back end, it will automatically update any 1.75mm profiles?
@karrad Yes, profiles must be duplicated in this case too. As I see, it may be easy to add profiles inheriting, so profiles for 1.75 will have same settings as 3mm, but it will be ability to override some settings if needed.
May 24 2019
@anolen @karrad All settings above missing resolve functions. Fixed "Support infill layer thickness", but not sure which functions to use in all other cases.
For prime tower position possible solutions is (min, max, avg) of extruders, but in all cases resulting position may be not perfect(for example if T0 profile will set prime tower in front left corner and T1 will set rear right corner the resulting position will be in center of buildplate)
The same problem with settings for extruder properties, but in this case min, max or avg will not work, don't know how to fix this settings at all in current situation.
Maybe you have any suggestions?
May 22 2019
May 21 2019
@karrad Checked cura code and looks like diameter property is integrated in many places inside cura. So if we want to ever change any values for 1.75mm profiles the best way is to copy all files and set it up to new material diameter, otherwise we can change it to behave like in message above, but profiles will be the same as for 3mm without any possibility to change any default values.
May 20 2019
@karrad, please check
May 16 2019
May 14 2019
May 10 2019
@karrad Cura using this memory to hold models for Undo\Redo can work. We can add a menu row to clear actions history and free this memory. But it won't solve issue with models that have polygons over 1.5Gb in loaded state.
May 8 2019
@karrad Fixed. Now profile importing for material which it was exported, if this material exists, otherwise to selected material.
May 7 2019
@karrad @anolen Fixed support setting. Prime tower position now automatically generates from other adhesion and size settings, so we can't easily change resolve setting for this. Also there can be problem if using average value for this settings. Prime tower location is varying depending on model, so I'm not sure this should be set in profile. If we want to change location for all profiles for one printer, best way to do it is override it in printer settings file.
May 3 2019
May 2 2019
@karrad Any updates or logs?
Apr 30 2019
Apr 25 2019
@karrad fixed. Clear of cache required to work.
Apr 24 2019
@karrad Checked again and it sends correct data to engine now, not sure why files are identical.
Apr 23 2019
@karrad Set blank profile for global quality, so now extruders use only their own values. But now some values that are not overridden in extruder profiles can be set to default values from fdmprinter.json
Apr 20 2019
@Steven Tried to add some delays and disabled serial in firmware, to check if if printer issues, but this don't help. Only way that I was able to reproduce this when I disconnected usb cable from pc while connecting, so it looks like communication issues. Also sometimes I was seen that printer hangs on load, so may be that issues can be connected, but I not see it now while testing.
Apr 17 2019
@karrad Tried to reproduce this issue, but all attempts were unsuccessful. Used windows 7 on virtual machine hosted on ubuntu and taz 7 motherboard. Alse changed COM ports numbers for printer(3-256).
Can you please post log file and maybe some remarks on how to reproduce this?
Apr 9 2019
Mar 22 2019
@karrad Now should work. Also please check on all OS. It should default to:
windows: "This PC"
Mar 18 2019
- min_layer_time is set for each extruder and time is counted also for each extruder in layer.
- force slowing of extruder was triggered only for last extruder in layer(fixed by above commit in T5146 branch). Now it counted for all extruders and should work.
Mar 13 2019
@anolen @logan if minimum layer time is set to 0, there is also option called "Regular/Maximum Fan Speed Threshold" that alternates fan speeds.
Also there is no layer speed alternating, it's extruder speeds alternating(two extruders printing on different speeds, but it still one layer).
Cura changes extruders only one time at layer so it looks like:
layer1: E1 -> E2, layer2: E2 -> E1, layer3: E1 - > E2, layer4: E2 -> E1, etc... So changing speed happens when printer ends one layer with E2, and starts new layer from E2(and similar for E1).
If layer time goes below minimal value cura slows second extruder in each layer(for layer1 it is E2, for layer2 it is E1, etc) so you see that effect.
But cura not accelerating extruders it only slows it(in this case "faster speed = printing speed", and "slower speed = 30-40% of printing speed").
There is no need of changing engine algorithm(it's very hard), only need to set right combination of "printing speed", "minimal layer time" and "Regular/Maximum Fan Speed Threshold" to fix it.
Mar 8 2019
Feb 28 2019
function, which is a part of a system. So we can easily include only rambo driver to cura installer.
Feb 26 2019
Feb 14 2019
@karrad @marcio @logan Looks like it caused by "Minimal Layer Time" option, printer slow down second nozzle to get minimal 30sec that set in PLA profile. When I set it to 1sec for both extruders, all model is printed on the same speed. This bug don't happen on TAZ6, because this option is set to 10sec on it.
Feb 7 2019
@karrad, I see scenario in engine code when this issue may happen, but can't test it, because it don't happen on my pc with dev cura and 3.6.4. Can you please post model files, settings, and instructions to replicate this issue, so I can debug it.
Jan 24 2019
@karrad Is there any test results on taz 7 with backlash compensation disabled? M425 is only command in gcode that applied on layer change and may change speed.
Jan 23 2019
Jan 21 2019
@karrad, found reason of this issue. In pla profile this option is set
Jan 10 2019
Jan 7 2019
Dec 20 2018
Dec 4 2018
Nov 23 2018
@karrad path changed
Nov 21 2018
Nov 13 2018
Nov 5 2018
Oct 31 2018
Oct 30 2018
@karrad Fixed position of z down
Oct 26 2018
@tutley, There is hard to find where is "new position" while exporting gcode from engine. Currently I'm in search of place in code, that controls it.
Oct 22 2018
Oct 18 2018
@karrad, The application works normally, looks like mac caching the process. Also this exist only in 3.x.x, can't replicate on 2.6.69. Looking deeper into it now.