wow, thanks, i didnt know you have to have closed paths...by 42loop - General
again i am going crazy on dxf extrusions in openscad. i have two different dxf files which i'm trying to import, one of them (sekunden.dxf) works fine, the other one (neu.dxf) just does not show, and also there is no error. i tried converting things back and forth with inkscape, pstoedit and so on but to no avail. also reversed the path direction in inkscape but this also did not work. does anyonby 42loop - General
great, this basically works. but it doesnt use the specified config file. the call to curaengine is reported as CuraEngine args:['/home/pi/CuraEngine/CuraEngine', '-s', '/home/pi/CuraEngine/cura_garage.ini', '-o', '/home/pi/.octoprint/uploads/18_40.gcode', '/home/pi/.octoprint/uploads/18_40.stl'] while the -s parameter supports single settings only, not a config file as a whole. like in 'CuraEnby 42loop - Developers
aehmm, how or in which context do you "set the variable openscadexecutable to a suitable path value" is this in the shell or is it a freecad parameter or do i have to edit some config file ? can't find anything in the docs. grtxby 42loop - General
hier ist eine quelle in polen: grtxby 42loop - Offtopic
is there a way to set z-offset with the lcd / rotary encoder menu and store it to eeprom ? since this is a very machine specific value it would be great to have it stored inside the machine. could not find it in the menues though. grtxby 42loop - Firmware - mainstream and related support
kannst du etwa so machen: vektorisieren, als dxf rausschreiben, in openscad extrudieren und eine stl datei exportieren, slicn usw. hab ich kürzlich mal als shellscript realisiert: hier benutzt ein kamerabild... grtxby 42loop - Offtopic
i don't have the raspi here right now, but just open pronterface.py in a text editor, look for the import line around line 17 and remove the 'gviz' import. then try running pronterface from the command line, and it will throw some errors concerning gviz not defined. go ahead and comment out all lines referencing gviz and gwindow, mostly these are in the popwindow() function. ugly hack, could be dby 42loop - Developers
i just disabled the graphic object viewer, now pronterface runs happily with 20% CPU load ;-)by 42loop - Developers
hm, have you connected your setup to an actual printer ? i have pronterface running now, but it chews up 95% CPU while serial transmission prints a few steps, then pauses, then prints and so on. the only task that could make pronterface use that much cpu while printing is the redraw of the traces on the screen, so maybe one should look into disabling this feature... grtxby 42loop - Developers
seems like the work can go on, the latest kernel patch seems to solve the usb speed issues. the driver uses something called 'fiq' now, which is a higher level interrupt (as I meanwhile learned). the advice is at had my rostock printer moving at normal speeds today ;-) my firmware spit a lot of positioning info back to the raspberry which made pronsole.py use 50% CPU time. after I disabled thaby 42loop - Developers
i have (for now) given up on this, looking at the 'elephant thread' on the raspberry forums every once in a while if there is a final solution to the usb woes... working on a tplink wr703 with openwrt now to get it to feed the printer. grtxby 42loop - Developers
tried again, it works if i change the nozzle diameter to 0.35 too bad i have a 0.5 nozzle... grtxby 42loop - Slic3r
hi there, just tried slicing the supersimple attached 8mm ring with 4 mm bore. in the first layer, it prints the inner hole, but on subsequent layers its closed. if i scale to 200% it works out fine... smells like the '100% infill on small layers' feature just to let you know, maybe someone have a fix ? using 0.84 grtxby 42loop - Slic3r
unter linux gibts fortlaufende nummern, ttyUSB0/ttyUSB1 respektive ttyACM0/ttyACM1 usw. hängt von der reihenfolge des anschliessens ab grtxby 42loop - Offtopic
bei uns funktioniert das wunderbar mit mehreren pronterface instanzen. wenn du dann noch kopien von der .pronsolerc in deinem home-directory machst und 'pronterface -c meinepronsolerc' zum starten benutzt hast du auch gleich die korrekten settings für den jeweiligen drucker. das betrifft aber nicht die slicer settings, da musst du aufpassen dass du die richtigen benutzt. grtxby 42loop - Offtopic
just went back to 0.72b for that reason. some things (gears for example) just don't slice very well with that new feature. voting for choice tooby 42loop - Slic3r
sorry, you were all right. didnt realize this 'full infill in small areas' was a feature. also since i always printed with 50% infill only i didnt realize there was too much plastic being extruded - but as a beginner probably you always use too much, for example to make it stick to the bed. thanx & grtxby 42loop - Slic3r
re-ing myself: Sound: I just looked at the gcode graphics and found that the smaller an area is, the earlier it tends do get full infill, as if it thinks its a solid surface. in the attach, the small areas at top and bottom already have full infill (without any reason) , while the one to the left has full infill in the next slice cause its getting smaller. hm grtxby 42loop - Slic3r
my extrusion multiplier is at 1, and everything is great in larger parts. but now i set the perimeter count to 1 and that somehow leveraged the problem... grtxby 42loop - Slic3r
hi all, basically slic3r just works great for me, and I'm not sure wether this question is slic3r specific: while on larger areas of a part everything prints fine and makes very smooth surfaces, on smaller areas the infill keeps bulging upwards, so some layers later, the extruder nozzle rumbles over these areas and eventually gets stuck or the printer looses steps. i'm using slic3r 0.61-dev, prinby 42loop - Slic3r
Sound Wrote: ------------------------------------------------------- > Please only report files after having processed > them through Netfabb or Meshlab or > hi Sound, the netfabb thing finally did it ;-) struggled to get a wade extruder body from openscad stl export through slic3r. on meshlab i didnt succeed to find the appropriate filters combination, also the GUI tends to crash on mby 42loop - Slic3r
hello, same here with slic3r 0.57, also fails on small rectilinear perimeters as in this t_mount. first attachment is with arcs disabled, second with arcs enabled. also with arcs enabled in this case slic3r outputs one single layer only. on larger object it sometimes works fine... grtxby 42loop - Slic3r