Tevo Little Monster Delta. I used the T3P3 Kossel as a starting point. Using a borrowed config from Facebook it worked fine. Generating a new config in the Configurator I get a Json error as soon as I home all. I'll try a catch the particular error but it was something along the lines of invalid parameter in json response.
Oh I set the Configurator to firmware 1.17+ and I'm running 1.18.2 with all the recommended components for that version.
Is the Duet Configurator mentioned in the documentation the best way to create the initial config?
I tried to generate a config using the tool and every time I issue a G28 I get a Jason error and it disconnects requiring a reboot before I can reconnect. I also found it was inconsistent in generating the zip-file at the end. It only seems to work every other time.
Using firmware 1.18.2 and the components bundled with it.
This works with my the borrowed config from FaceBook. So it seems to be something with the Configurator.
I had things going well on my Delta using a 0.4mm nozzle and 0.25 layers. Z-probe is a BL-Touch with a height set at 2.0mm. So naturally I switched to a 0.8mm nozzle with 0.6mm layers and the first layer was too tall and I got poor adhesion. When I measured it it seemed about 0.4mm too tall so I changed the probe height to 2.4mm and ran G28/G32/M500 after the reboot. First layer still seemed too tall and about the same size as before. Tried probe height of 3.0mm and ran G28/G32/M500 after the reboot. First layer still seemed too tall and about the same height.
Any ideas?
What linear rails work with this setup?
The Tevo Little Monster uses an anodized plate with a machined lip to hold the glass in place with the heater glued to that. That is held in place by some standoffs and M5 bolts. Wouldn't be hard to adapt that idea to the Onyx stack. I like the removable glass on a Max V3 versus the glued in glass on the Tevo.
The web interface is very good but sometimes it is nice to not have to wake up my PC or tablet to do something quick. For example starting another job when one finishes late at night.
I like the base plate / top plate idea but why not use 40x60 verticals instead and then you have a center groove to mount rails on.
On my Delta I'm getting 141 points using 20mm spacing at 170mm radius. The firmware isn't complaining but am I building to large a mesh?
Yes, Duet uses the layout common with RC stuff which is setup to not kill things if you plug it in backwards (just won't work). The legacy 8-bit boards pin-out can result in VCC being sent to a signal pin or ground if plugged in incorrectly (bad). I prefer David's way (long time RC guy), he also uses locking connectors which is another smart move.
A less than perfect but quick solution would be to have the slicer insert comments that identify when it is printing something related to a particular model on the plate. If this were standardized then the printer firmware could ignore those sections on command.
I had it set at 600 and raised it to 800. My towers are 1000 so maybe 600 was too short.
Most of the time my G28 homes perfectly on my delta but in one scenario it seems to give up before it is fully homed and a second G28 is required.
The scenario is when probing at the outermost supported radius (170mm) with the effector opposite one of the towers. It is as if it is running out of time before all the carriages reach the stops. Is there a timeout I need to set or do I just need to set my movement speed a bit higher when homing?
For now I just have each manual probe macro return to X0 Y0 Z25 first before G28 and it seems to be OK.
That would be very cool. I was printing some badges for the kids attending the company picnic and one or more out of the seven I had on the plate would occasionally peel up and cause a problem. would have been great if I could have just killed them instead of trying to manage the air printing in those spots.
"Just for the fun of it"
It would probably work best if the slicer could ear mark what specific gcode was associated with each component being printing. Once something has failed just be able to state which part to terminate and all further gcode would be with that ear mark would be commented out.
I'd be interested in those files also. Not sure I'm quite ready to build one but I'd love to look at how you did it.
…................P.s. -> hey Ian, would you mind if I essentially copied your machine?
Cheers.
Jonathan
No problem but I don't have a build log or complete bill of materials. The entire thing was designed using OpenScad. I'm happy to put all the OpenScad files into a folder on my Google drive and create a shareable link so that you can download them. Note that I'm not by any means a professional when it comes to OpenScad, so some of the files might not be pretty but they get the job done. I haven't got time to go through the machine and catalogue all the various bolt sizes and lengths, but you can work them out from the OpenScad files. Send me a PM and we'll take it from there.
Ian
As you may have already noticed I ordered a Piezo from you right after I posted those results 
I was getting decent results until I foolishly decided to have it do a quick calibration before each print like David talked about in his blog. That's when the BL-Touch inconsistency truly bit me. I started getting first layer adhesion problems that shifted from spot to spot on the build plate. I even tried adding in the G29 mesh leveling but I still could get good adhesion at all spots on the bed using PrintBite. Hopefully I can get deviations like other posted in the 0.005 or less range as opposed to my current close to 0.1 range with BL-Touch. BTW the Tevo Little Monster comes with the BL-Touch from the factory and I had hoped it would work well because people at MRRF 2017 seem to like it on their printers. I'm not impressed with it though.
IMO both the BLtouch and IR sensor have their limitations, BL touch is not as accurate as it really needs to be, the notion that if a probe is within 50 microns its good enough is clearly not correct. IR works fine if you have an evenly reflective surface to IR, and on a delta, no effector tilt. In practice neither of these conditions are easy to meet. IR on a cartesian with an evenly reflective surface is a good prospect. Join the piezo revolution guys
Tevo Little Monster with BL-Touch converted to Duet WiFi and 0.9 degree steppers on X, Y, Z.
7:50:34 PM: Bed probe heights: 0.149 0.161 0.155 0.158 0.149 0.155 0.158 0.155 0.152 0.143 0.136 0.146 0.115 0.102 0.090 0.036 0.021 -0.003 -0.020 -0.026 -0.023 0.018 0.061 0.121 0.130, mean 0.098, deviation from mean 0.066
7:56:14 PM: Bed probe heights: 0.149 0.183 0.186 0.155 0.152 0.083 0.049 0.021 0.005 -0.014 -0.026 0.002 0.058 0.118 0.155 0.177 0.186 0.186 0.149 0.146 0.130 0.111 0.086 0.043 0.018, mean 0.100, deviation from mean 0.070
7:58:47 PM: Bed probe heights: 0.015 0.015 0.008 0.015 0.018 0.018 0.021 0.015 0.015 0.018 0.018 0.015 0.021 0.015 0.015 0.018 0.018 0.018 0.015 0.011 0.015 0.011 0.015 0.018 0.005 0.008 0.008 0.011 0.018 0.018 0.018 0.018 0.015 0.015 -0.004 -0.010, mean 0.014, deviation from mean 0.006
8:01:26 PM: Bed probe heights: -0.020 -0.026 -0.029 -0.029 -0.032 -0.035 -0.032 -0.035 -0.029 -0.035 -0.039 -0.039 -0.039 -0.035 -0.042 -0.042 -0.042 -0.035 -0.035 -0.023 -0.017 -0.001 0.024 0.046 0.068 0.080 0.102 0.108 0.118 0.115 0.118 0.124 0.127 0.127 0.136 0.140, mean 0.021, deviation from mean 0.069
Probably explains my troubles getting a consistent first layer.
Very nice. that will be a nice upgrade.
With firmware 1.19 beta and the latest DWC you can do all of that in a macro. Use the M290 command to display the message and wait for a response. Before long, PanelDue will support M290 too.
Is there a way do do the equivalent of M600 in Marlin which
1. Stops the print
2. Moves to a new location
3. Unloads the filament
4. Waits for the operator to change the filament
5. Extrudes filament to prime extruder
6. Waits for operator to signal new filament loaded (and old filament purged)
7. Resumes printing at the stop point (saved at #1)
I got spoiled by this one on my Wilson 2 for switching colors.
