Error while exporting g-code "Failed to execute script"

[Portia-Lin]

Hello. Your project could probably help me a lot. I use a FlashForge Guider II printer. I don't really like how the standard FlashPrint slicer builds support. It seems like that function works crookedly and is not adjustable by parameters. In OrcaSliser I found a profile for Guider IIS. In my opinion, they shouldn't be much different and I would like to try printing the generated G-code for IIS on my Guider II. But I get an error when exporting g-code

I followed the instructions and I don't understand what's wrong. Is it possible to fix this error? Thank you

[grahamraines]

Hi, I am also using a guider IIS printer an am having exactly the same issue.

[urself25]

Hello. Your project could probably help me a lot. I use a FlashForge Guider II printer. I don't really like how the standard FlashPrint slicer builds support. It seems like that function works crookedly and is not adjustable by parameters. In OrcaSliser I found a profile for Guider IIS. In my opinion, they shouldn't be much different and I would like to try printing the generated G-code for IIS on my Guider II. But I get an error when exporting g-code
I followed the instructions and I don't understand what's wrong. Is it possible to fix this error? Thank you

Have you made any changes to the python file? If so can you post the code here? Also, can you upload a copy of the gcode file?

Hi, I am also using a guider IIS printer an am having exactly the same issue.

Same for you.

[grahamraines]

No changes to the python file.
Wont let me upload a copy of the gcode as it states it is a non supported file

[midnight-creator]

I have a similar error for Flashforge Artemis

Here's a snippet of my gcode: > ; machine_max_junction_deviation = 0.01 > ; machine_max_speed_e = 30,30 > ; machine_max_speed_x = 150,150 > ; machine_max_speed_y = 150,150 > ; machine_max_speed_z = 20,20 > ; machine_min_extruding_rate = 0,0

the script seems to fail at ; machine_max_speed_x =

I'm working on adding Flashforge artemis to OrcaSlicer. I'm not sure why it's listed twice in the gcode: https://github.com/midnight-creator/OrcaSlicer/blob/main/resources/profiles/Flashforge/machine/fdm_artemis_common.json#L25

[randomguy048]

I am using an Adventurer 4. Seems like the errors are the same.

[fakna-computerknabe]

I also encountered this problem/error with my Flashforge Adventurer 3. I searched the G-code for the mentioned “150,150” and found that it appears in the line “; machine_max_speed_y = 150,150” as the source of the problem. I think the issue is that Orca enters two speeds here, though I’m not sure why. If you delete the trailing “,150” you can use the .EXE to convert the G-code file to GX. Using Gemini, I created a batch file that first corrects this line and then passes the G-code file to the .EXE. Just place this file in the same folder as the .EXE.

Orca_Fix.bat:

@echo off
powershell -Command "(Get-Content '%1') -replace 'machine_max_speed_x = 150,150', 'machine_max_speed_x = 150' | Set-Content '%1'"
"C:\3D-print\Orca_Gcode_to_GX\Orca_Gcode_to_GX.exe" "%1"

Als Post-Processing-Script muss dann entsprechend die Batch anstatt der EXE angegeben werden like:
"C:\3D-print\Orca_Gcode_to_GX\Orca_Fix.bat"

@Portia-Lin
You need to find the line with 200 (not 150) and change the batch values to “200,200” and “200” accordingly!

@midnight-creator
You can use the code as is.

I hope this is helpful to some of you.

[fakna-computerknabe]

One more quick tip: To avoid having to rename the finished file, you can change the file extension directly to .gx in Orca:

[midnight-creator]

@fakna-computerknabe thanks!
I forked the code, modified the dual extruder script to be flexible for single and double, fixed this problem, and added a couple of other things: https://github.com/midnight-creator/Orca_Gcode_to_Gx/blob/main/Orca_Gcode_to_Gx_DualExt.py

I'm sure it could be formatted better