I'm testing out Mattercontrol 1.1.3 (On OSX) with a Flashforge CreatorX.
I added my custom gcode that starts the extruders/temperatures etc. If I export the file as gcode, I see my custom gode at the start of the file.
; generated by Slic3r 1.0.0RC1 on 2014-10-10 at 10:04:46
; layer_height = 0.15
; perimeters = 3
; top_solid_layers = 5
; bottom_solid_layers = 2
; fill_density = 0.23
; perimeter_speed = 40
; infill_speed = 60
; travel_speed = 90
; nozzle_diameter = 0.4
; filament_diameter = 1.74
; extrusion_multiplier = 0.96
; perimeters extrusion width = 0.40mm
; infill extrusion width = 0.40mm
; solid infill extrusion width = 0.40mm
; top infill extrusion width = 0.45mm
; support material extrusion width = 0.40mm
; first layer extrusion width = 0.45mm
M127 ; disable fan
M103
M73 P0
G21
G90
M140 S100
G162 X Y F2500
G161 Z F1100
G92 Z-5
G1 Z0.0
G161 Z F100
M132 X Y Z A B
G1 X-110.5 Y-72 Z50 F3300.0
G130 X20 Y20 A20 B20
M134 T0
M104 S250
M133 T0
G130 X127 Y127 A127 B127
M108 T0
M135 T0
G0 X-113 Y-72
G0 Z0
G92 E0
G1 E6 F300
G92 E0
G1 X-110 Y-65 F300
G1 Z0.6
M73 P0 ; update progress
... snip rest of gcode
You can see I'm heating up the bed first, then waiting and then heating up the extruder.
Now if I run gpx manually on this file:
gpx -m r1d -g test.gcode test.x3g
Then try to print the resulting test.x3g, I see the start routine run as expected.
If instead, I export as x3g from the export screen, the extruders move to the waiting postion but immediately the extruder starts heating up and the bed temperature is turned off.
So somehow the x3g generation isn't quite the same as the gcode generation (to it's detriment.)
Thanks for looking.
I'm testing out Mattercontrol 1.1.3 (On OSX) with a Flashforge CreatorX.
I added my custom gcode that starts the extruders/temperatures etc. If I export the file as gcode, I see my custom gode at the start of the file.
You can see I'm heating up the bed first, then waiting and then heating up the extruder. Now if I run gpx manually on this file:
Then try to print the resulting test.x3g, I see the start routine run as expected.
If instead, I export as x3g from the export screen, the extruders move to the waiting postion but immediately the extruder starts heating up and the bed temperature is turned off.
So somehow the x3g generation isn't quite the same as the gcode generation (to it's detriment.) Thanks for looking.