Topics created by titanhusker

What exactly does the M98 error say? You may need to enclose the path to your macro in double quotes. M98 P"0:/macros/my macro.g"

If you add parameter F2 to your M563 P0 ... tool definition command, then when the tool is active the fan commands generated by the slicer will control fan 2.

@Emily I have had that happen to, but this is a new spool. A couple of times when I have ran into a moisture issue, or so I suspected, I baked them for a little. Drying them out helped, I try and do a better job of properly storing filament now.

@phaedrux & @dc42 - Ha, SMH.....seriously sometimes it is obvious and another set of eyes can make you see the problem. I overlooked the small stuff, I changed one line and it is perfectly centered,

M208 X300 Y200 Z300 S0 ; Set axis maxima

@titanhusker said in Not printing correctly. Any ideas?:

@dc42 - I will try and post the config.g file as quick as I can, I am headed into surgery at the moment. Meanwhile just as a precaution, is there a link for me to download firmware 1.17e in case it is just easier for me to revert back. I can’t seem to find it anywhere.

https://github.com/dc42/RepRapFirmware/tree/a863bd9d6e7e48738c8dda6c7d55600f551fc545/Release

Not sure what happened, but I reloaded the firmware because I thought I found a 1.17 copy, turned out it was 1.15b, so I went back to 1.19.2 and this time I only changed the WiFi Server to 1.93 instead of 1.21 and presto, everything is working again. I won't pretend that was the intention, but I'll take it. Thank you for your help. I did however go in and clean all of the macros up, the original writer of them had them somewhat very vanilla. I found a tutorial, I believe you wrote, that explained it in very great detail, so I copied many of your examples and reworked them for my setup.

You are correct sir, and that was a mistype, I actually meant 552, the original author of the config files did not have a Network file in place, all good now on that. I downgraded the Wifi Server back to 1.93 and it resolved almost all of the issues, with the firmware and the macros, not sure if I had something incompatible going on.

I was also experiencing this (IIUC) and the culprit was an uneven heat spread on the bed. I had the bed temperature set to 73°C for the first layer and 55°C for the rest. At around the fourth layer corners would begin to curl up. I felt the temperature at different points on the bed with my fingers and found out that there were stark contrasts in temperature between points only 2cm apart.

A workaround for me was to heat the bed to 90°C, and start printing when it cooled down to about 80°C. I figured this would help the bed area further from the center to contain heat better and thus prevent larger temperature differences per distance from occurring. During printing of the first layer of a larger print the temperature would set to 73°C. After repeating the routine before each print, three 1.5h print jobs completed neatly with good bed adhesion and no detaching.

If you have only 1 extruder you can add T0 to the end of your config.g to select it when the machine powers up. This avoids a "no tool selected" problem. If you have multiple tools then it's a bit more complicated.

Mac with S3D… put this in your Scripts/Additional terminal commands for post processing section.

You will need to update the IP address to your Duet. When you save the gcode (it doesnt matter where), it will at the same time upload to the duet and start printing right away. Be sure you check your printer before printing, Its easy to forget a print or maybe even just a skirt is still there. You can turn off your computer after it finishes uploading. The gcode is completely on the Duet. You will not be able to control the printer from S3D at this point, you will need to use the web interface.

curl --data-binary "@[output_filepath]" -X POST [http://192.168.5.26/rr_upload?name=gcodes](http://192.168.5.26/rr_upload?name=gcodes)[output_filename].gcode
curl -G http://192.168.5.26/rr_gcode –data-urlencode "gcode=M32 [output_filename].gcode"

EDIT: This might have problems with certain characters in the filenames. I had a failed upload with a space in the filename. I havent had time to play with that yet.

Glad to hear you got it working!

I added my config-override.g to the same folder on Drive. It only includes the results of the PID autotuning so nothing very interesting.
I see your other problem was already answered in the other thread, you just need to set some tool as active. I have it in my Slic3r start code, but I guess it could just as well be in the end of config.g.