Hi Dave. Been using the Duet/delta firmware and starting to get some very nice looking parts, best ever in fact! (after endlessly dialing in the print settings) Two questions: 1) My dimensions seem to be a hair off; would this be caused by the wrong rod length? 2) I sometimes see stuttering of the nozzle motion. Is the web interface streaming the g-code and if so how can I make sure it runs atby shadowphile - Firmware - mainstream and related support
ok thanks. is that in a log someware?by shadowphile - Slic3r
Anybody else have this problem on Win7-64? thanksby shadowphile - Slic3r
I looked in the config file and there is no setting for 0.3 extrusion. I have a .4mm nozzle as well.by shadowphile - Delta Machines
I don't know if they are related but the browser control has a bug I keep encountering: -Pause a print, then cancel. -Try to re-run the same file and it tries to start where the last print canceled. I have to delete and reload the gcode file to get it to start correctly. I'm can't guarantee this happens every time, too hard to test it out much.by shadowphile - Delta Machines
I can't seem to get this test object to print well. It runs ok first the first several layers but after that it starts to randomly starve filament. It's PLA at 205 deg running .2 layers at 40mm/sec perimeters, 3mm filament on a Bowden extruder. I've attached the gcode file and the slic3r settings to somebody to see if it runs ok on their own machine. thanks gcode:gcode slic3r config file settingby shadowphile - Delta Machines
No matter how small I trim my external perimeter extrusion-width down, I can't get a 2mm hole to actually be 2mm. It seems like Slic3r puts outer perimeters exactly at the hole dimension then the external extrusion squishes out further. I don't want to have to oversize my holes in the design... mini kossel with 3mm PLA, 205 deg, bed 40 deg on blue tape, 40mm/sec perimeter, 90% width small periby shadowphile - Printing
I had same problem with not triggering on glass. I would try a flat black sheet of paper like construction paper. Permanent marker on glass is very shiny. He also recommended painting the aluminum plate, not the glass if I recall correctly. That should optically decouple the backside better. But get the height correct first . Maybe make the mount adjustable? I also had to bend the IR componenby shadowphile - Delta Machines
I just installed the 0.9 motors and they are noticeably smoother and quieter. Micro-jogging has no noticable aliasing either. I can clamp and unclamp a sheet of foil with a single .01 step, which is pretty darn nice!. I paid $57 for the three from MatterHackers and they are actually longer than the 1.8s they replaced. Why is anybody still using 1.8s? Oh, right..RAMPS. I am looking forward toby shadowphile - Delta Machines
Dave, I used your suggestion of G1 Z5 then G30 S-1 to get a consistent read of the probe-trigger height, but the same spreadsheet statistics didn't get much better. Then I realized I still have the same problem to manually determine when the nozzle is just touching the paper, which is harder to fix but possible with a certain tedious sequence of motions. What to do... I noticed a subtle but impby shadowphile - Delta Machines
After a lot of head-scratching I suddenly realized a great solution: removable shelf-liner/contact paper. You can get it anywhere, it works great, doesn't peel off the PVA, nice finish for the optics. Mine is light grey, satin finish. I can just subtract the thickness. Being vinyl, it gets fairly soft and stretchy on a 65 deg bed but it didn't melt down or pull off the PVA. That said, a 110 deby shadowphile - Delta Machines
Thanks for the feedback Dave. I was randomly jogging the trigger point so I expect there would be more repeatability if I descended at the same rate. I want to try what you suggested with G30 S-1 but at different rates and positions. With z movements the position shouldn't matter because all the steppers are commanded the same movement. (I have motor steps set at 100 in the config file.) Actualby shadowphile - Delta Machines
For those who like data... Trying to calibrate my bed with the duet electronics running a mini kossel with the dc42 IR probe attached. Everything here is cold. I am trying to nail down where my quality issues are, so I am touching the nozzle to the glass to set the Z=0 point, then re-descending until the probe triggers and collect that Z offset. (to be precise, I sandwich a sheet of paper betwby shadowphile - Delta Machines
I have converted my Kossel Mini to Duet and have been printing simple test parts ok, and the auto-cal looks like it is running well. Today I started on a large (PLA) part and it is terrible and don't know if it is firmware problem or settings in slicer. It looks like too much speed and/or extrusion width but I can't seem to pull it back enough without getting silly settings. Here are some pics.by shadowphile - Printing
Observation about the IR sensor sensitivity to bed surface. A clear glass bed returns a height of 1.25mm, but when I put on blue painter's tape it jumps to 2.2. I will have to keep editing the config file whenever I change filament type unless some way is added to automatically switch based on selected material. (multiple definitions or z offset)by shadowphile - Delta Machines
thanks, that fixed it right up, get very tight numbers now.by shadowphile - Firmware - mainstream and related support
I need to get out of bed earlier! BTW, I found a scrap of junk text in the config file but I deleted it and reran auto-level + justreport.g and it didn't make a difference. more diagnostic feedback: -I removed the homing command in the justreport.g file and run it after a calibration run. It reports expected values. If I home the machine after a cal run, then do another justreport.g run, theby shadowphile - Firmware - mainstream and related support
For some reason I have to disconnect the LAN if I reset the board or Pronterface won't connect, error message: Connecting...could not open port COM9: The system cannot find the file specified. I am running the recent RC firmware. Probe points appear to be close to the same. I also notice that after every probe the head is jerked upward very hard, more like a snap. I have the max speed in configby shadowphile - Firmware - mainstream and related support
edit: retracted question and thank you!by shadowphile - General
Here is the message queue from my actions (browse interface for Duet). First I run auto-cal with good results, but when I run the exact same bed.g macro with the last M30 command using S-1 to just see the actual offsets, I get large errors that don't make sense. The large errors are the real ones when the nozzle is touching the head, so the auto-level says it all looks good, 'cept it isn't. (Reby shadowphile - Firmware - mainstream and related support
I was just given the link from somebody else to , which is what I needed. But if I back up to just there is no link to the Calibration page. I have to do a global search then stumble through a bunch of un-useful links until I stumble onto something useful. I went back to the main page and tried to drill down to some place like Calibration. Hmm, no, not Development. Not Resources, Not anythingby shadowphile - General
I stumbled across it once, now can't find. thanksby shadowphile - Delta Machines
Even with the g release I installed, I keep getting an repeated AJAX error that disconnects me (umh..once or twice an hour, maybe more). I don't have the actual message because I copy and pasted but the copy didn't take.by shadowphile - Delta Machines
Cool! The age of software makes every new release like Christmas!by shadowphile - Delta Machines
I went the FSR route and finally decided it was too unreliable approach. My goal was to get a bed level to within .05mm across the surface or that first layer can have problems when printing with a typical 0.2mm layer thickness. Compensating with a thicker first layer works but then that layer sticks out enough to see and measure. For auto leveling I ran the G30 command but that cna take forevby shadowphile - Delta Machines
Quotedc42 PS - don't enable the Move debug (M111S1P4) or any other debug unless you have the USB port connected to a PC and a program such as Pronterface ready to receive it. The debug code uses blocking I/O to make sure that none of the debug output gets lost, and that may cause the main loop to hang if there is nothing to receive it. Well that explains one problem I had today...by shadowphile - Delta Machines
My thoughts are a mess after trying to read Google-translated German but here is what I think they are saying: ground ROSC pin for quiet hold and noisy moves, or connect to +5 FOR noisy holds and quiet moves. I may have this backwards from memory but the concept is what matters, yes? I will have to read the data sheet for those drivers. The Duet so far has been much more noisy than what I had Rby shadowphile - Delta Machines
I noticed with the original RAMPS that very small jogs on the vertical axis would sometimes not even move and I blamed the limited motor/math involved. I assumed it would go away with the Duet. Today I am jogging up and down and I can visibly see the head zig-zag as I jog it straight up and down. In one case I put my fingers on the stages and jogged .01 down. The X and Y towers did no move atby shadowphile - Delta Machines
Nevermind, I finally found the G-code interpretation in the code. (H parameter is a float so must be in mm not steps). Right now I'm calibrating the tilts and I did it with no heat, with just the head at about 240 and then also with the bed heated to ~100 c. DC42, have you studied how the IR pcb responds to temperature? The hot-end doesn't put out a lot but the IR board floating over a hot bedby shadowphile - Delta Machines
also, what are the units of the H parameter in G30? can I use fractions? thanksby shadowphile - Delta Machines