Daid
-
Posts
4,700 -
Joined
-
Last visited
-
Days Won
19
Content Type
Forums
Events
3D Prints
Posts posted by Daid
-
-
Got an RC11 for you guys:
http://software.ultimaker.com/Cura_closed_beta/
Fixed the problems with the UM2 firmware build. So it should include the "change filament while paused" function now. As well as fixing the loading/unloading speed.
It also contains a change list now, compared to 14.12.1
Pretty sure this will be the 15.01 release soon.
-
In the past I noticed that when the print head follow the far right side, the side of the right fan and screws will scratch the side panel. Is that still possible?
That's not changed. And it depends on your UM2 build if it can scratch the sides. The official clearance is quite small, and if you slightly bend the fanducts it can already hit the sides.
-
I agree with Nallath here. We should improve this (actually, we should be sure to include the "standby" function in the next machine, so you don't even need to use the power button, it will just go into super-lower-power mode on it's own)
Anyhow, for the hacky method. You could just solder 2 wires to the switch, and connect a 2nd switch on there which actually switches the machine on and off, and just leave the button at the back at the off position.
-
Well, the selection and dragging of objects in Cura works by drawing the 3D model in a single solid color, grabbing the pixel color under the mouse, and checking of that is a pixel that corresponds to a color chosen for the model.
This all happens before the actual screen is drawn and refresh, so you normally never see this.
One of the things that can cause problems here is 16bit colors, and possibly color correction (I know for sure 16bit colors cause issues. But who does that these days?)
-
Well, those are "extra" triangles in your 3D model, which confuse Cura.
-
All latest video card driver installs?
Any "color correction" enabled or configured?
-
I added an offset to the 3D buildplate, because the nozzle is actually on the left side of the printer head. So this area you see now, is actually where the nozzle can get to. And thus, it needs less space for the right clips. Giving you slightly more build space (yay!)
-
How does the object look in XRay view? any red parts indicate problem areas.
-
Which OS?
-
I think to remember Daid having tested a driver like this one and having mentioned the far future of Ultimaker...
Yes, the TMC260 (I think) is pretty silent, due to it's 256 microstepping. Which puts the frequencies it generates out of hearing range.
-
Is there any progress on this problem. I'm using Cura 14.09 and I'm having this exact problem. I.e. Choosing brim and support at the same time causes the brim to be offset by a few mm.
'Touching buildplate' and 'Everywhere' and both cause this problem.
Made some adjustments for this in the latest beta:
http://software.ultimaker.com/Cura_closed_beta/
-
Yes, it's a bug, caused by fixing another bug, which happened after fixing another bug.
The latest firmware code is already patched, but no RC has been made yet.
-
Nadeel van dit ding is dat het filament lange levertijd heeft en ik tot nu toe niet de beste ervaringen ermee heb.
Alle Ultimaker modelen slikken ook gewoon filament van andere fabrikanten (zoals ColorFabb, Faberdashery, GermanReprapFoundation) dus levertijd op materiaal is minder een probleem hier.
Keuze komt neer op:
* UM2 ziet er beter uit
* UMO+ is goedkoper
* UM2 haalt iets betere print qualiteit (niet super veel meer, want de UMO+ haalt ook al super kwaliteit)
* UMO+ heeft meer mogelijkheden om print qualiteit op te offeren voor snelheid
* UM2 is makkerlijker in gebruik
* UMO+ is meer hands-on
-
Maybe try the latest beta:
http://software.ultimaker.com/Cura_closed_beta/
I'm not sure which version handles large models better but it's worth the try
The latest beta handles large GCode and thus large models a bit better. The current release isn't even hitting the 3GB memory barrier, as it's getting problems before that. (It's 3GB, not 3.5GB. And some applications are limited to 2GB in windows. It's an odd world)
And, yes, it's polycount that we need to talk about. Currently. I'm limiting my testing to 3mil polygons. That should give you ample resolution in the current Ultimaker machines.
In the future, I do want to be able to offer a 64bit windows version as well, which then can handler larger models. But there are some huge hurdles in the way for that on Windows. (On Mac everything is 64bit by default. On linux lots of things are available in 64bit already, and 95% of the users of Linux have 64bit systems)
Note that about 30% of the users currently still use a 32bit OS.
-
I assert that 3D mice are never going to become popular unless and until they at the least provide some haptic, i.e. touch, feedback.
Current devices are like waving your hand around in the air with only your eyes telling you where the "cursor" might be, and on a flat display, no real feedback about where it is located, so precision suffers greatly vs. a mouse or trackball.
Further, having no support for the hand and wrist, they will be about as popular as large touchscreens, i.e. not very, because it is far more fatiguing to hold the arm up in the air unsupported than to have a desk on which to rest the forearm.
Sorry folks, but it will be a long time coming for this technology, and market projections agree.
Clearly you never really used one.
We're talking about this device:
-
1
-
-
Daid it looks like that patch fixes the issue.
However, I'm still seeing a lot of checksum errors:
< Error:No Line Number with checksum, Last Line: 54
< Error:No Line Number with checksum, Last Line: 83
< Error:No Line Number with checksum, Last Line: 114
< Error:No Line Number with checksum, Last Line: 157
However, at least now the print isn't halting like it did before....
That's because Cura is intentionally forcing buffers to be full on the firmware side. Which sometimes causes checksum errors. These are corrected and re-send.
-
-
I'm leaning towards an issue in BigDataStorage.
That sounds like a pretty good possibility.
EVERYONE is potentially affected by this.
My guess is on only USB printing is effected by this. And only if the GCode size is over a certain amount of size.
And, could be that plugins play a part in this as well.
-
Maybe they changed the law because I met some airsoft players from the Netherlands at an event in the Czech Republic last year and they all said that they have a ban on airsoft guns.
Yes, that's a recent change. (Not that the ban stopped people from having airsoft guns, or even clubs)
@drayson: Gun laws in the netherlands are very strict. For example, none-functional guns (for example, 3D printed replica of a gun) are also illegal to carry around. No matter the color. So you could even be fined for having a transparent 3D printed AK-47. (Which I might or might not have printed
) -
Nope, drivers haven't changed in like... forever.
-
I would recommend PET instead of ABS. As PET is a bit more food-safe, and should be able to survive dishwasher.
-
The next firmware release will have a "change material" option when you pause the printer.
-
Sounds like a bed issue indeed.
Does the bed actually get warm? Does the red LED on the electronics turns on when it wants to heatup?
-
By the way - if you look at the gcode, it is commented very well. Each new layer has a comment (although the gcode and layer view are off by one because one starts at 1 and one starts at 0). The very next G0 or G1 command that has an "E" in it will specify exactly how much filament you have used so far in mm. For example:
G1 X10 Y10 E1017.12432
means you are just over one meter of filament at this point.
Unless you have UM2 GCode, where the E value is in mm^3.
And the E is reset every 20 meters.
)
Ultimaker 2 Dual extrusion
in Third party products & modifications
Posted
No it isn't.
HIPS printing isn't that hard, but printing is a bit nasty (bit more then ABS) and the solvent is super nasty. So that's not a real route.
PVA works, sort of, when it does not totally jam and destroys your nozzle.