Quotedc42 That probably means that the skirt has some rather abrupt angles in it instead of smooth curves. Reducing the jerk setting in the firmware will make it sound better; but if you set it too low then curves will print slowly. In this instance, it was circular. The piece itself is one of my test files - a circle about 60mm diam with a few shapes cut out of it. The skirt was a few mm outby David J - Duet
Well, I set it to 460800 (another standard baud rate for Linux) and it continues to work nicely, which reinforces what you said about it being a true USB setup. The only thing that still sounds a bit clunky is when it's printing the 3-row skirt around the part - I have no idea why, as when it gets to the part itself it prints smoothly. I'm not going to stress about it though...by David J - Duet
Thanks. I might try setting Repetier-Host to 230400, which is a 'normal' speed for Linux... just for the hell of it...by David J - Duet
I have to apologise - yesterday must have been an off-day for my printer. Then, it wouldn't show the temps - today it does. It is a bit slower though... I will have to see if I can get the port speed up (but I don't like interfering with the kernel!). Sorry if I've made you waste time looking at this... Cheers, Davidby David J - Duet
Where should I set that in Repetier-Host if I'm only heating the bed and hotend, rather than running an object's gcode?by David J - Duet
I'll start by saying that the conventional way of using a Duet - using the web page - is fine for a lot of my work, especially when I'm printing a well-established design. However, when I'm deep into prototyping, the ability to load up a design and play easily and quickly with slicing parameters is a huge bonus (usually in Repetier-Host). It matches the workflow I like to use on my RAMPS-equippby David J - Duet
Trouble is, if you're burning any fuel you have the risk of creating CO, especially if it's an incomplete burn (insufficient oxygen). I don't know how prone laser cutters are to generating CO, but almost every data sheet I've seen emphasises the need for good ventilation.by David J - General
It only helps a little... still very slow even when working at $fn = 20.by David J - OpenSCAD
QuoteReplace My f5 is often quick, the f6 is boring slow. I am considering designing a cap on the f6 key, to prevent it being pressed by accident :-( My renders are so complex that canceling the f6 will often take as long as finishing it :-( Ahh - I think we're talking about different things - you're saying that F6 takes ages to complete. Same for me, but what I'm talking about is moving the iby David J - OpenSCAD
Concurrent processing would be nice... but, while I'm waiting for that (), I find that the Ctrl-numerical (e.g. Ctrl-0, Ctrl-9, etc.) keys help to get quick changes of viewpoint as they're almost instantaneous. Note: for me, it's the F5 render that's agonisingly slow - the F6 render is quick and easy.by David J - OpenSCAD
I also had a few oddities when first using this new release... after homing everything and loading the transformation file the print would start somewhere around X180:Y20 instead of X100:Y100 as usual. I hadn't raised this before now as I cannot reproduce it - it happened a few times, since when I've run G29 S0 a few times, printed a few objects, and everything has behaving normally (fingers crosby David J - Duet
And in the meantime... I'm making the model simpler!by David J - OpenSCAD
I'm having a problem when previewing complex objects - any movement or rotation takes a very long time to complete (sometimes minutes) and it's getting on my nerves! I have a fairly powerful (8-core) AMD CPU in my Linux Mint 18.1 64-bit machine, but a fairly ordinary graphics card. The system's CPU monitor shows that one CPU core is at 100% when redrawing is taking place, so it doesn't seem toby David J - OpenSCAD
QuoteDjDemonD I think if you have a printing surface with even (and good) reflectivity to IR then it works very well. Definitely beats inductive and capacitive sensors. If using spray of some sort this will affect the precision in some parts of the bed. My print bed is 3mm glass with black card underneath, with hairspray on the glass. The probe works nicely.by David J - General
Over the past week or so I've been trying to sort out a Z homing height problem on my Duet-equipped CoreXY printer (now sorted by a change to gcode and, hopefully, by an additional fix with new firmware). Yesterday, while testing the gcode changes, I realised that there was something that could have caused all sorts of pain - I illuminate my bed with a pair of LED strips that are actually vehiclby David J - General
Final update: Adding M561 as I described above seems to have fixed my problem completely - yesterday I printed some large pieces that went to the edges of the bed and all came out perfectly. I shall now download version 1.17c and see how I get on with that - should I try it with M561 in the startup gcode, or out?by David J - Duet
Sorry - I was a bit slow there! (see above)by David J - CoreXY Machines
Quotemrorange26 Is it easy to setup a Duet for a corexy printer. Absolutely painless - follow the guidance on dc42's website (just one or two commands in the config file) and you're away. Link to RepRap wiki guidanceby David J - CoreXY Machines
David, I had a quick look at my start-up G-codes, which are as follows: * I have a macro that runs M561 followed by G29 S0, which gets run at the start of a printing session (if I think it's appropriate). * My startup G-code is: G28 ; home all axes ;G32 ; auto-levelling G29 S1 ; use the bed mesh map G1 X10 Y10 Z20 ; go to the front left side, raise & await next move Note that G32by David J - Duet
Thanks David, I will have to review the sequence of events I've set up. I'll have a go at that tomorrow.by David J - Duet
Final update: I sorted the bed levelling mechanism (now 3-point suspension), levelled everything up as best I could, and tried again - and now I get a good print across the bed. However, while this is a good result, it doesn't really answer the original problem as I suspect that my printer will now give me a decent print without invoking any bed levelling! The issue of over-correcting the errorby David J - Duet
David - any views on what I reported in my last post? I haven't yet tried to go back to 1.14 as it's a lot easier to go forward a version than back... I am now in the process of sorting the bed levelling though, so can't do any more testing until that's finished.by David J - Duet
The problem comes when you have to decide whether the 'A' motor is plugged into the 'X' or 'Y' socket on the controller board, and whether the 'B' motor goes into the 'Y' or 'X' socket. It's even worse with deltas!by David J - CoreXY Machines
What David (dc42) said above - I had the X and Y motors swapped. It's not obvious in a CoreXY printer... it's a shame they're called "X" and "Y" as their action doesn't really match their name.by David J - CoreXY Machines
Quotestephenrc There's a set of arrows at one corner of the grid, red, green, blue. They start at the origin point. I know what you're saying - it's only a trivial point anyway, so I'm not going to get emotional about it! I think that part of my problem is that when the grid is first displayed the arrows are in the 'far corner' of the image (top-right) instead of the usual lower-left, meaningby David J - Duet
Quick update: I haven't tried 1.14 yet, but I have clarified my problem - the system seems to be over-compensating after running G32. I'll start by admitting that my bed isn't level - but it's not far off. If I get the X100:Y100 nozzle height correct it will be too low at X0:Y200 (almost touching the bed) and too high at X200:Y0. After running G32 it's too high at X0:Y200 and too low (touchingby David J - Duet
Re-reading what I've written - perhaps I haven't made myself clear... The best thing I can do is give an example from the Repetier-Host application: The little dot in one corner of the grid indicates unambiguously the location of the X0:Y0 origin. Something like this in the bed image would be ideal.by David J - Duet
I've just tried another test: 1. Heated everything up to working temps 2. Homed X, Y and Z 3. Checked and adjusted nozzle height at X100 Y100 Z0 - just gripping a piece of paper. 4. Moved Z axis to max height and back to 0 several times, then rechecked afterwards - still OK. 5. Ran G32, then checked nozzle height at X100 Y100 Z0 - nozzle too high, paper slips through (probably get 2 sheets in thby David J - Duet
PDBeal: I might have another go with just G32, which is what I used to use before the upgrade. I had cleaned the glass before testing, and given it a fresh coat of hairspray (my usual technique, so no change before and after upgrade).by David J - Duet
Quotedc42 I doubt that it has anything to do with the firmware upgrade, but you could always go back to the old firmware if you want to check. My best guesses are that your print bed is no longer stable, or your Z axis is no longer moving smoothly. The Z axis was fine up until I upgraded a couple of weeks ago. I'll give it a once-over just in case, though. I might try going back to 1.14, justby David J - Duet