Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start and end scripts for different printers? #19

Open
moyesboy opened this issue Nov 7, 2018 · 10 comments
Open

Start and end scripts for different printers? #19

moyesboy opened this issue Nov 7, 2018 · 10 comments
Labels
help wanted The developers need help from the community to solve this.

Comments

@moyesboy
Copy link

moyesboy commented Nov 7, 2018

I have high hopes to eventually print using cura on my work flashforge creator pro printers where I currently use S3D and I fail to match the quality of what I get of my wanhao at home.
I'm struggling to find start and finish scripts that work for the flashforge creator pro.
My searches for info find lots of people finding the printer begins and then doesnt heat up, few seem to get as far as the print starting.
Is there somewhere to find some start and finish scripts that are known to work for particular printers?
I found some posted for the flashforge creator pro a while ago by ghostkeeper but I couldnt get a print using them either.
I think an issue might be the flashforge is using extruder 0 and extruder 1 and cura is calling them 1 and 2. I'm trying to use extruder 2 so maybe it tries to heat a non existent extruder and stops because it never heats up.

@Ghostkeeper
Copy link
Owner

I'm pretty sure that the extruder naming is not an issue here. The output of Cura is still T0 and T1, regardless of what the extruder names are (1 and 2 or Left and Right, doesn't matter).

I don't know where you found any Flashforge script posted by me, but I don't have a Flashforge so if I posted it, I didn't test it! I might have found it somewhere or posted it in name of someone else?

If you got it to work with S3D, maybe you could find the start-up sequence that they are using to start a print and use that?

@moyesboy
Copy link
Author

Ah yes it was not your start and finish codes, you were the next comment here: Ultimaker/Cura#3091

But tracking down start finish codes that work is proving difficult, and the ones I found are rather out of date for current cura version. I try again using info from here: http://markwal.github.io/programming/2016/02/18/ffcp-start-and-end-gcode.html together with info gathered from the comments... but its all very dated.

@Ghostkeeper Ghostkeeper added the help wanted The developers need help from the community to solve this. label Nov 15, 2018
@FireflyJar
Copy link

I am too trying to get Cura 3.6 to work with FlashForge Creator Pro. got the X3GWriter plug in and using the 'Makerbot' G-code flavor. I think we just need to figure out the start/end scripts. I tried others I found posted with no luck but I was trying to get the Left nozzle to work. But I do know depending on the software some refers nozzles as T0 or T1 and others T1 or T2, so looks like Cura is using 0/1, Left is T1 and right is T0. I will play with it more and post back here.

@moyesboy
Copy link
Author

moyesboy commented Dec 6, 2018

I have S3d but it seems to create a whole load of redundant g code at the start of its file, and it confuses me. Do let me know if you get it to work!

@JKJameson
Copy link

JKJameson commented Dec 8, 2018

I got it working on my Flashforge Creator Pro with the following;

Edit printer config at %AppData%\Roaming\cura\3.6\definition_changes\Flashforge+Creator+Pro_settings.inst.cfg and add this line to the [metadata] section: machine_x3g_variant = r1d

Start G-code

M73 P0
M107 ; turn off fan
G90 ; absolute coordinates

G130 X118 Y118 A118 B118 ; set stepper motor Vref to defaults
; let the Z stepper vref stay at eeprom level (probably 40)
;
; home and recall eeprom home position
T0 ; home on the right nozzle
G28 X Y Z ; home all axes at homing speed
G92 X0 Y0 Z0 A0 B0 ; set all coords to 0 for now
G1 Z5 F500 ; move Z 5mm away so we can carefully hit the limit switch
G161 Z F100 ; home Z slowly
M132 X Y Z ; recall stored home offsets for XYZ axes
;
; wait for heat up
G1 X110 Y-72 Z30 F3300 ; move to waiting position
; set temperatures and assert Vref
M140 S{print_bed_temperature} T0
M134 T0 ; stabilize bed temperature
M104 S{print_temperature} T0
M133 T0 ; stabilize right extruder temperature
M116 ; wait for temps

End G-code

M73 P100 ; end build progress
M140 S0 ; set bed temperature to 0
M104 S0 T0 ; set extruder temperature to 0
M104 S0 T1 ; set other extruder temperature to 0
G1 Z145 F1100 ; send the build plate to the bottom
T0 ; Next job assumes T0 is the current tool
G28 X Y F2500 ; home X and Y axes
M18 ; disable all stepper motors
M70 P5 (Print Complete)
M72 P1 ; Play Ta-Da song

@FireflyJar
Copy link

I have S3d but it seems to create a whole load of redundant g code at the start of its file, and it confuses me. Do let me know if you get it to work!

S3d works fine for me, didn't do the dual print yet, machine profiles are saved in registry so there is no way for me to send a file, but can send you screen shots. following is for FFCP dual on Simplify3D

ffcp s3d profile

; **** Replicator 1 dual start.gcode ****
M73 P0 ; enable build progress
G162 X Y F3000 ; home XY maximum
G161 Z F1200 ; home Z minimum
G92 Z-5 ; set Z to -5
G1 Z0 ; move Z to 0
G161 Z F100 ; home Z slowly
M132 X Y Z A B ; recall home offsets
M135 T0 ; load right extruder offsets
G1 X150 Y-70 Z30 F9000 ; move to wait position right hand side of the table
G130 X20 Y20 Z20 A20 B20 ; lower stepper Vrefs while heating
M126 S[fan_speed_pwm]
M140 S[bed0_temperature] T0
M134 T0 ; stabilize bed temperature
M104 S[extruder0_temperature] T0
M133 T0 ; stabilize right extruder temperature
G130 X127 Y127 Z40 A127 B127 ; default stepper Vrefs
G92 A0 B0 ; zero extruders
G1 Z0.4 ; position nozzle
G1 X110 Y-70 E25 F300 ; purge nozzle
G1 X120 Y-70 Z0.15 F1200 ; slow wipe
G1 X110 Y-70 Z0.5 F1200 ; lift
G92 A0 B0 ; zero extruders
M73 P1 ;@Body (notify GPX body has started)
; **** end of start.gcode ****

; **** Replicator 1 dual end.gcode ****
M73 P100 ; end build progress
G1 Z150 F1000 ; send Z axis to bottom of machine
M140 S0 T0 ; cool down HBP
M104 S0 T0 ; cool down right extruder
M104 S0 T1 ; cool down left extruder
M127 ; stop blower fan
G162 X Y F3000 ; home XY maximum
M18 ; disable stepper
M72 P1 ; play Ta-Da song
; **** end of end.gcode ****

@FireflyJar
Copy link

FireflyJar commented Dec 8, 2018

I got it working on my Flashforge Creator Pro with the following;

Edit printer config at %AppData%\Roaming\cura\3.6\definition_changes\Flashforge+Creator+Pro_settings.inst.cfg and add this line to the [metadata] section: machine_x3g_variant = r2

I tried this and at first I thought it was not working, but I waited and watched it, was moving so slow I almost couldn't see it moving, just hearing the buzz, after almost a minute it suddenly moved and spit out a blob and starting the first layer of the test cube. I think the priming code is bad.
so maybe other codes I tried were doing the same I just aborted the print before it got to finish the priming.
. . . Looking into it . . .
there is no priming code in start script, so I have no idea what's going on.

@JKJameson
Copy link

So it should actually be machine_x3g_variant = r1d
The code from here in Cura works really well for me: http://markwal.github.io/programming/2016/02/18/ffcp-start-and-end-gcode.html

@FireflyJar
Copy link

So it should actually be machine_x3g_variant = r1d
The code from here in Cura works really well for me: http://markwal.github.io/programming/2016/02/18/ffcp-start-and-end-gcode.html

yea, I tried it, it doesn't like it.
I am using the latest Cura 3.6, I confirmed I have it set to reprap and machine_x3g_variant = r1d.

@FireflyJar
Copy link

check out https://markwal.github.io/GpxUi/commandline.html ,
I have to try 'machine_x3g_variant = fcp' when I get home.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted The developers need help from the community to solve this.
Projects
None yet
Development

No branches or pull requests

4 participants