Well done and thanks for posting the solution. Just the sort of small thing that can really frustrate you.by MCcarman - General
Sounds like the issue with the temperature file. The config.H file calls a temperature file for your sensor This file will probably have one of the values in the wrong order. By that I mean one row is misplaced. This causes the interpolation to be wrong and you get this big hang around 83 degrees and then a rapid rise above about 93. The file is a text file with a list of 2 values. I think the 1sby MCcarman - General
I don't think the relative positioning is an issue and changing means all co-ordinates are now changed. Though I am not familiar with marlin. If you stay with absolute positioning then sending a G92 E0 will zero the extruder. So put that in start code or send it before any other extruder commands. If this was a new build we would probably be saying the motor was wired the wrong way. Don't forgetby MCcarman - General
Its hard to see from the picture but is the shift occurring on the first layer that is trying to print the unsupported ribs sticking out the sides (at an angle). No idea why this would cause an issue just looking to see if matches some geometry or operation change that might indicate its a slicing/Gcode issue. If you print the same part again do you get the exact same issue.by MCcarman - General
Printing slower may help. As DD says its an extrusion issue. At the corners the system is actually stationary for a moment but the extruder is still motoring. Also the second side is trying to be extruded over the last side. What size nozzle are you using? The larger the nozzle the worst the issue is likely to be. When designing parts try to avoid sharp corners. Even a small radius on the cornerby MCcarman - Printing
I can't see the pictures. If its OK manually then take a look at the Gcode and slicing settings. A simple sanity check would be to go through the layers in repetier etc and check the zvalue at your 5mm step change layer. How you get the code wrong is another question. Is the STL file correct? You are either missing layers or the layer height is wrong.by MCcarman - Printing
Just wondering why Slicer is showing 3 perimeters and cura 2. So this may be down to what settings you are using in each program.by MCcarman - Printing
Hi ManiPi. Can you tell us how you are creating and sending commands. 1. Cura => Host software =>Printer 2. Cura => Host software => SDcard => Printer 3. Cura => SDcard => Printer I believe you can set the AUTOHOME in Gcode in Cura and in host (start code) and is run using LCD option on the printer. So 1 and 2 above can have it twice in Gcode. Extruding to much? Others shouby MCcarman - General
Might be usefull to explain how you changed the fan wiring. Also if this is happening after 45mins have you considered heat issues on the controller/driver board.by MCcarman - Printing
Have a look in the delta printer section. Bed alignment is more complex than XY machines as it involves having the correct arm lengths and tower positions. You will find similar issues there.by MCcarman - Printing
thanks james - good info. I think some of these factors are historical but remain good rules of thumb. The slicer maths probably starts to become a bit inaccurate with certain combinations of parameters as does the machine limits. The other rule is to limit layer height to 0.8 of diameter. Again a sensible number to avoid extreme combinations. I suspect it avoids specifying wide widths and largeby MCcarman - Printing
Not an expert but no one has responded so:- In you picture you put the min Y to 58 which is less than 59 so would hit the end stop. Not clear if the sketch is the size of the bed or the travel range. Why is your Ymax for the scan area only 260? If you have 290 available to print then set the maxY to 280 for scanning.by MCcarman - General
Thanks Tinchus. I wondered why the 0.68 was quoted as I always assumed 0.48 when designing my parts. I assume you meant you can print detail down to 0.4mm. I would have thought that anything less than that requires under extruding which would give unpredictable results. Can you help explain how this width calculation works as its often shown in the Gcode files on this site which implies its theby MCcarman - Printing
Hmm. 1 and 3 are almost the same so you would have to check the detailed spec on the parts. The displays are different so get opinion on that, check heated bed spec and what PSU is supplied. No 2 has the X rails horizontal but no printed parts. This means the hot end/extruder arrangement is different. I don't think this is a common arrangement and given the amount of comments about this area youby MCcarman - Prusa i3 and variants
I would have thought you will also have issues due to the size of the fins. What size nozzle are you using? 0.4mm is a typical size which the slicer calculates as a real width of around 0.68mm. If your fin width is only 0.75 we hope your slicer realises and just prints a single run at the 0.68mm. However it has to stop at the end (outside of the fin) which inevitably causes a blob (because the noby MCcarman - Printing
Not sure where I got the 35mm from. Brain fade I guess. Speculation here. It may be a calculation problem in the firmware. Your maths seems OK. But the probe point is set the same as the max travel. Just wondering if this is causing the issue. You are stopping short by the offset amount in the opposite direction. Try probing at 394 to see if its the travel limit. Try probing at 363/364 to see ifby MCcarman - General
What does "stopping short" mean. Don't forget that you are trying to make the carriage got to where the sensor will align to the auto tune position. So if the sensor is offset X+35mm (from the nozzle) but you defined the tune position as 32 mm the nozzle will be at -3. However the end stop switch will trigger at 0 so you wont get to the tune position. Lowest left position will be the same as theby MCcarman - General
Any chance of pictures of your machine? Make sure the Z lead screws are not constrained at the top. Check the Z guide rods are parallel. Do you have separate drivers for the motors or are they wired in series or in parallel.by MCcarman - General
Looking at the errors they are all incomplete instructions. I can't offer help but perhaps someone who knows more on the communication side can help. Whether this is interference in the comms, a buffer size mismatch, comms speed (SD card speed) issue. If its loosing part of the commands you may get one where it misses a decimal and you end up with a travel over 10 times larger than required. Asby MCcarman - General
just to add to what DD said:- The 0.45 is assuming you have 0 in the z offset in your slicer. Normal practice is to set the Z offset to the paper thickness so you get the correct layer thickness. This is a negative value (- 0.1). And it only affects the first layer since all the other layers will increase Z as per your layer height specified.by MCcarman - General
If memory serves, :- Not sure about perimeters but in Slic3r you can partition the model and apply different infill's. I think you can use different z heights for the layers as well You will have to search the web to find some info. You have to be in slic3r, import the model, draw a box/volume over the area you want different and specify the appropriate parameters. Then slice and save the code. Iby MCcarman - General
The counter balance mass will only reduce the force in Z. However in X and Y the issue is inertial due to mass x or y velocity. In these directions the counter weight will not be of benefit and may make it worse as there is a z force due to the cord being at an angle (when not central) that creates inertia with the counter weight = worse than just the carriage on its own. The advantage you have iby MCcarman - CoreXY Machines
Possibly play in one of the drive mechanisms. This would happen if it always printed in the same path direction (clockwise for instance). So when it moves left it doesn't go far enough left and when it goes right it doesn't go far enough right. If you print fast so there is inertia it can tend to be too far instead of too little.by MCcarman - Printing
Im not sure I can help much but the GCODE comments are confusing as they don't have codes with them. You have a M104 code to set the temperature but there is no M116 to wait for the temperature to be reached - even though the comment is there. Since you have extrusion I assume you preheated the extruder before running the code. I would change this for peace of mind. I can't see anything in the coby MCcarman - Printing
In your video the drive gear isn't actually rotating its just oscillating back and forward. That usually indicates insufficient current to drive the motor. Check/adjust the current by tweaking the drive settings on the control board. I wouldn't say you can hear grinding but you can hear motors "buzzing" when they are under current. If you can I would shorten your Bowden tube. The longer the tubeby MCcarman - Prusa i3 and variants
Novel. You would have thought it was that the z guides are not square to the Y but you have checked that. Worth another look with fresh eyes - ensure its the guides that are square and your not checking drive screws. Are you using auto levelling? Is the bed level ? A picture of the machine may help.by MCcarman - Printing
What does "edited the gcode" mean? 8 secs sounds like it is just doing the moves you listed. Did you slice a model and then edit the gcode ? Look at the preview to see what the GCODE movements are - I suspect there is nothing. The movements you describe are typicaly in the startup and shutdown code in both the host options and in the slicer. So with no model sliced that is all you will get if youby MCcarman - Printing
Check how much/how easy it is to move the bed on the levelling springs. If the adjuster screw load is low the bed gets nearer to just resting on the springs so a Y motion can move the whole bed as far as the adjusting screw shaft to hole clearance allows. This may not seem much but can be visible. This can be made worse by increasing the bed weight (you added glass) and having only a small compreby MCcarman - General
This is a fairly common inclusion in slicer start code. It should not be an issue as it will be followed by the printing command that specifies the correct Z height for the print.by MCcarman - Printing