Repetier Host 2.0.1 - CuraEngine seems to ignore 'Start' and 'End' gcode settings
In RepetierHost 1.6, I had my CuraEngine slicer settings set to add custom start and end gcode (to do a hotend purge, set up for volumetric extrusion, etc).
Now, with RepetierHost 2.0, it seems to ignore these settings, and the sliced file always starts with:
;Generated with Cura_SteamEngine 14.09
Now, with RepetierHost 2.0, it seems to ignore these settings, and the sliced file always starts with:
;Generated with Cura_SteamEngine 14.09
M109 S210 ;Heatup to 210C
G21 ;metric values
G90 ;absolute positioning
G28 ;Home
G1 Z15.0 F300 ;move the platform down 15mm
G92 E0 ;zero the extruded length
G1 F200 E5 ;extrude 5mm of feed stock
G92 E0 ;zero the extruded length again
.. instead of my custom GCode.
Any ideas? Known issue?
.. instead of my custom GCode.
Any ideas? Known issue?
Comments
From the ReptierHost log:
07:33:16.097 : CuraEngine command:/home/jmcmullan/Desktop/3DP/RepetierHost-2.0.1/plugins/CuraEngine/CuraEngine -p -v -c "/home/jmcmullan/.local/share/RepetierHost/cura.ini" -s posx=0 -s posy=0 -o "/home/jmcmullan/.local/share/RepetierHost/composition.gcode" "/home/jmcmullan/.local/share/RepetierHost/composition0.stl" "-"
/home/jmcmullan/.local/share/RepetierHost/cura.ini:
md5sum of the CuraEngine plugins:
$ md5sum plugins/CuraEngine/CuraEngine64
Removing 'CuraEngine' 19126e... and making it a symlink to CuraEngine64:
$ ln -sf CuraEngine64 plugins/CuraEngine/CuraEngine
solved my issues! I can now print with my custom G code.
Thanks for have me check my logs - I wouldn't have guessed this.
Looks like an old version of CuraEngine was in my plugins directory.
I got the same issue with Host version 2.0.1 on linux and with curaengine: not only start and end gcode where ignore, but all settings (printer settings and dimension, nozzle size, filament temp, ...).
In my plugins/CuraEngine directory, the 3 executable (CuraEngine, CuraEngine32 and CuraEngine64) all have different checksum. I can't tell to which one "CuraEngine" correspond...
Like jmcmullan, I moved away "CuraEngine" and create a new on as a symlink against "CuraEngine64".
I confirmed it solves the problem.
But it's strange, and I had no issues with 2.0.0.
So did you run configureFirst.sh after unpacking?