• The Plug Track functions are experimental and still being developed. Some of the earlier pages of this topic are now out-of-date.

    Some pages of this topic include contributions from members who are creating and posting their own CAD designs for 3D printing and laser-cutting. Do not confuse them with Templot's own exported CAD files.

Messing with FB

AndyB

Member
Thread starter
These are regular PLA prints with a blast of grey primer. They represent wide clips for turnouts on 12" timbers. The timbers are very thin - only three 0.15 mm layers. I do that just to speed up the prints as I'm only really interested in the clips at the moment but it might be possible to glue thin printed timbers with clips on plywood or other timbers.

PhotoGrey.JPG
 
_______________
message ref: 4230
Location
Sandbach, Cheshire
Info
Builder of Finescale Signals in 2mm scale to 7mm scale, Trackwork, Turnouts and Layouts.
I have re-measured the code 82 with possibly a better tool and comes out at 0.99mm, as regards the foot, not easy to measure but seems to be 0.33mm
 
_______________
message ref: 4237

AndyB

Member
Thread starter
I have re-measured the code 82 with possibly a better tool and comes out at 0.99mm, as regards the foot, not easy to measure but seems to be 0.33mm

Hi Stephen,

Is that Peco Code 82?
Is 0.99mm the width of the rail head?

The Proto87 Code 70 rail I'm using is:

.0725" tall (Code 72.5)
Base width 0.0681" (1.73mm)
Base height 0.38mm approximately
Head width 0.0337" (0.86mm)

I used a micrometer for the measurements in inches. Based on the rails I have the widths are maxima.

Andy
 
_______________
message ref: 4241

AndyB

Member
Thread starter
I should point out that to get that amount of detail I did modify my printer to increase the X-Y resolution. I replaced the steppers with ones that take twice as many steps per revolution and I also used smaller drive cogs for the toothed belts. The extruder nozzle diameter is 0.2 mm which is probably close to the lowest practical limit.

The small nozzle helps a lot with detail but it can also substantially increase the time it takes to produce a print, particularly while printing timbers and sleepers. However, I've been able to speed-up printing timbers and sleepers quite a bit, even with such a small nozzle.

I've been printing a test panel consisting of six 00 sleepers 1.2 mm deep and adjusting various parameters in Slic3r (the slicing program I use) and I've managed to get it down to just over six minutes, or one minute per sleeper. That's without chairs/baseplates of course but they take a much smaller percentage of the total time and there's not much that can be done to make them print faster.
 
_______________
message ref: 4394

AndyB

Member
Thread starter
I'm not sure if this is a problem with my slicer or my printer. I think it's really caused by ambiguity in the protocol but my prints don't quite complete. The last few moves don't happen before the job terminates leaving a small "hole" in the top layer. It's because some G codes are buffered and some take effect immediately.

Rather than mess around with the G code my workaround is to add a very small sacrificial bump in my STL model that's one layer higher than everything else.
 
_______________
message ref: 4401

Martin Wynne

Admin
Location
West of the Severn UK
Info
.
Enjoy using Templot?
Thanks.

Please do not send requests for help direct to me via email.

Post your questions on the forum where everyone can see them and add
helpful replies.
Rather than mess around with the G code my workaround is to add a very small sacrificial bump in my STL model that's one layer higher than everything else.
@AndyB

Hi Andy,

Your slicer probably includes an editable script for the printer which is appended to the end of each job. If you insert a M400 command, it should cause the printer to wait in a loop until all printing moves are finished. If there is already a M400 in the ending script, try adding a second one to stop the buffering -- see discussion in the online forums.

Or attach your gcode file here, and we might be able to spot the problem.

cheers,

Martin.
 
_______________
message ref: 4402

AndyB

Member
Thread starter
@AndyB

Hi Andy,

Your slicer probably includes an editable script for the printer which is appended to the end of each job. If you insert a M400 command, it should cause the printer to wait in a loop until all printing moves are finished. If there is already a M400 in the ending script, try adding a second one to stop the buffering -- see discussion in the online forums.

Or attach your gcode file here, and we might be able to spot the problem.

cheers,

Martin.
Thanks Martin.
Yes, I know about the M400 fix but I would actually have to edit the G-code produced by the slicer. My workaround is a one-time fix for any model I create (or maybe I should call it a "hack") :)
Cheers,
Andy
 
_______________
message ref: 4419

Martin Wynne

Admin
Location
West of the Severn UK
Info
.
Enjoy using Templot?
Thanks.

Please do not send requests for help direct to me via email.

Post your questions on the forum where everyone can see them and add
helpful replies.
Thanks Martin.
Yes, I know about the M400 fix but I would actually have to edit the G-code produced by the slicer. My workaround is a one-time fix for any model I create (or maybe I should call it a "hack") :)
Cheers,
Andy
@AndyB

Hi Andy,

If you edit the end code script in the slicer it will be a one-time fix. The end code is appended to every gcode file:

end_gcode.png


You can set a different end script for each of your printers. Also the start code.

cheers,

Martin.
 
_______________
message ref: 4420

AndyB

Member
Thread starter
Hi Martin,

Yes, I know about the start and end scripts and I do use them.

The problem is there is a race condition. The printer buffers some commands (like the normal print moves) but not all commands. The slicer puts a G92 at the end of the G-code and G92 is not buffered. That means it can take effect before the printer has finished printing the final layer.

Adding a M400 before the G92 fixes the problem. Putting it after the G92 doesn't so I'd have to edit the G-code every time the slicer generated a new version. I suppose I could change the slicer code or the printer's firmware but it's a lot simpler just to add the bump to the model :D

Cheers,
Andy
 
_______________
message ref: 4421
Top