Swell! It is working now! And feeding off USB power it gives me the option to switch on through WebGUI also. I implemented the "pushbutton-on WebGUI-off" method, as well as the "USB powered Duet WebGUI Switch on and off" method. I would like a small mains2USB power adapter to built in also, so I have only one powercord and one main-switch to the device. That will take some googling, unless someonby DeltaCon - Duet
Since I have my whole printer open for surgery, I am trying this suggestion for a buzzer. I have a 0.6 board too but I am not egtting any sound. The buzzer works, as a 9V battery proved. However I am gettin abou 0.6V regardless of M42 P67 being S0 or S1 or S100 for that matter Any idea how come? EDIT: I found that the PIN pointed to in the picture actually is PIN 30, not 32. But when I move oneby DeltaCon - Duet
Ooh, looking at the picture of the duet I posted in my other thread (about the PS_ON thing) I am not so sure I have my + and - wires correct indeed. I was so sure that I put them back the way they came out that I did not even check that, but now I see on the wiring diagram the red wire in the upper screw terminal, and the black in the lower. I am pretty sure I have them wrong then. I will have toby DeltaCon - Duet
Quotedc42PS_ON is an open-drain output. So you need to connect the SSR positive control terminal to either +3.3 or +5V from the expansion connector, and the negative control terminal to the PS_ON pin. Thanks David, Are you suggesting this?by DeltaCon - Duet
Quoteo_lampeThat's funny, you know you are in the Duet section, don't you? Yeah, as we say in Dutch: I could not make any chocolat from it ;-)by DeltaCon - Duet
As you can see in my other thread I am expanding my RMax with an autoshutdown and thermal fuses. Now a second problem has risen. When is switch on power the board does not light up and no fans are blowing (I have 2 fans directly on the 12V circuit) I hear a ticking sound, looks like my 12V stepdown is clipping. I am measuring 20V to the 12 V stepdown, but 0V on the 12V side of the stepdown. Whenby DeltaCon - Duet
I am sorry to bring this topic up again. I am implementing an SSR and switch following this guide: However I am thinking about powering through USB charger and switching the PSU on and off through the webgui. I have an older 0.6 Duet board and soldered the needed pins to it. Powering the board through USB works fine and the GUI is up. However when I switch on the PSU in the webgui, I get 0V betby DeltaCon - Duet
Quotedc42 I've traced it to a firmware bug. On a Duet 06/085 it will occur when the rectangular mesh uses more than 96 probe points. So the problem won't occur if your grid is 9x9 or less instead of the intended maximum of 11x11. On a Duet WiFi/Ethernet the same bug will occur if you use more than 416 probe points (maximum is supposed to be 441). Release 1.19.1 will include the fix. Thank you fby DeltaCon - Duet
Yes, I could try varying the distance between probepoints too of course. I am counting on David to get an "Aha moment" that solves this. But I am happy I am not alone on this issue ;-) I am thinking about something like this: A square grid is defined for mesh-levelling. For a round bed certain points on this square grid "fall off" the bed. These points are skipped while probing. At this point,by DeltaCon - Duet
It is a Duet 0.6 I bought early this year. Sorry ;-) It was cheap, and besides this issue I am really happy with it. It beats most modern day controllers! Bear in mind the different probes that fail always get the same value (it gets calculated despite the fact that it does NOT get probed at all) and are outside my round bed. I already talked to MHackney on his slack channel to ask about Hinge Efby DeltaCon - Duet
Quotedc42It's not usual to load a height map in config.g, but some users load one in their slicer start script. If people do that from their slicer start script, why is it unusual to load the most recent heightmap from firmware? Maybe I am misunderstanding the whole concept, but my intention to load a heightmap from config.g is that I seldom take off the printbed and therefore have no need to rerby DeltaCon - Duet
Thanks, I will try that tonight (CET+1). But isn't it common practice to load the map at system-start? My previous heightmaps all differ slightly, so I am quite confident I am not looking at the same map each time.by DeltaCon - Duet
@ayudtee: the 32 points limit is for the auto Delta calibration routine. Here we are talking about mesh bed levelling. Thanks for your quick reply DC42. I downloaded the bugfix but cannot see any improvement: Below as requested my config.g It would make sense to compare what changed between the versions 1.18RC1 and 1.17e. Since the probed off-values then ended with *.000 and they do that now eby DeltaCon - Duet
Hate to bring this up again... But I just upgraded my FW from 1.18someRC to the 1.19 stable and the problem I started asking about in this topic fully returned. Did something change back to a previous state concerning the bed compensation feature? My heightmap.csv: RepRapFirmware height map file v2 generated at 2017-07-21 20:53, mean error 55143424915650900113760737820672.000, deviation inf xminby DeltaCon - Duet
I am looking to integrate an IP cam, and was wondering which (hopefully cheap) IP cam is suitable considering it must be able to produce still images.by DeltaCon - Duet
Did you measure the thickness of the first layer with a caliper? You will probably find that it is a bit above the pre-set layer height. That would mean you have to adapt the probeheight (Z parameter in your G31 command in the config.g). On a sidenote: the Z-lift that can be set in your slicer, it is not uncommon to lift 3 or 4mm, with a high speed, to help prevent stringing or webbing in your prby DeltaCon - Duet
OK thanks dc. But my Rostock V2 does not do anything when I chose the "Run Mesh Grid Compensation", that's why I thought-up the mesh.g file ;-) Edit: I think there is a use for a fixed macro: I have put a M558 H1 in it before the mesh grid probing, and restore it to H3 afterwards. That makes the mesh probing a lot quicker, and since there has always been an auto calibration before, there is nooby DeltaCon - Duet
Quotedc42The default filename is heightmap.csv. Yes, thanks, I found that. But I meant a .g file for invoking the mesh grid compensation, like bed.g is used for invoking auto calibration.by DeltaCon - Duet
QuoteDeltaConOkay Will try again tomorrow while heating to see if that makes a difference. Happy to report that my issue seems to be solved. Makes me wonder DC, there must be something different in this RC1 compared to the 1.17e regarding the calculations of mesh heights, why else advising me an unstable version ;-) QuoteDeltaCon...attempt to do mesh grid compensation doesn't do anything. Shouldby DeltaCon - Duet
I would like to make laser-etched images on the backside of household mirrors. This is a technique to etch a raster-image to the backside of mirrorglass. The silver mirror-coating gets burned away, and the resulting image is blackened by a simple spraypaint. The result looks like this: I would like to be able to laser mirrors op to 30 x 40 cm. I have some experience building a delta 3d printeby DeltaCon - Laser Cutter Working Group
Okay I did the update to 1.18RC1 as suggested. I ran 2 bed height compensation routines (both cold) and it appears as if it is okay now. Don't now what changed exactly. Will try again tomorrow while heating to see if that makes a difference. One remark though, there is a nice new dropdown at the auto calibrate button, specifically for bed compensation. But if I run the mesh grid compensation fromby DeltaCon - Duet
Thanks for your reply dc42. I just ran 2 bed height compensation routines. Still on 1.17e but this time without any heating to exclude the possibility of EMI. I thought to have found it, because it actually gave me a believable map. But the second (also cold) routine introduced the previous error again. map and figures are attached. Again all impossible values are ending with .000. I will updateby DeltaCon - Duet
For the first time I wanted to try the height-mapping feature of the DC42 firmware, because I updated to the 1.17e DC42 firmware with the 1.14a GUI and the "show heightmap" button got me curious. I repeatedly get these kind of crazy maps though: Really not fun and I guess that makes my printer unusable if turned on. The routine just runs like I would expect it to. I am using a bit coarse gridby DeltaCon - Duet
I went the same route and bought a 0.6 board from Think3dPrint3d (I believe it was 66 pounds...) It is the one with the screwterminals instead of connector sockets. I wanted to make leads, but eventually I cut off all connectors because they were in a bad shape anyway. I can tell from experience that the steppers are a whole lot quieter than they used to be. The board runs really well, and the Deby DeltaCon - Duet