Printer Overrides Temp Setting from Gcode file??

Hi everyone,

So I am still new to the 3d printing world, but I feel as I am getting the basics down. My Prusa I3 from Gadgets3D is running great and turning out some great quality prints. I print with Sainsmart 1.75mm PLA set to 230C. I know that sounds high, but the results are fantastic.

I use Cura to slice all my files and generate the Gcode. I set the initial layer and subsequent layers at 230. When I load it into the printer it automatically overrides the temp setting to 215. I have to use the LCD screen to manually update the temp. I tried using other slicing software too, but the printer always defaults to 215 and I have to manually adjust it.

I have Ramps 1.4, Marlin, and the 2560 board installed.

I'm guessing this is an issue with the Marlin software but I don't know for sure. Thanks in advance!

Edited 1 time(s). Last edit at 03/12/2014 07:47AM by trdcelica.

Post your g-code at www.pastebin.com and link it here.

Sorry for the late reply. That website said the gcode is too large to save.

Not sure if this is any help, but here is the section before the printing starts.

;Generated with Cura_SteamEngine 13.12
M109 T0 S230.000000
T0
;Sliced at: Tue 18-03-2014 10:42:13
;Basic settings: Layer height: 0.2 Walls: 1 Fill: 50
;Print time: #P_TIME#
;Filament used: #F_AMNT#m #F_WGHT#g
;Filament cost: #F_COST#
;M190 S0 ;Uncomment to add your own bed temperature line
;M109 S230 ;Uncomment to add your own temperature line
G1 Z10 F50 ; lift nozzle
G28 ; home all axes
M109 S215
G1 F128
G92 E0 ;zero the extruded length
G1 F200 E3 ;extrude 3mm of feed stock
G92 E0 ;zero the extruded length again
G1 F9000
;Put printing message on LCD screen
M117 Printing...


No idea why the printer over rides it to 215, But it does this for all slicing software I have tried.

Actually, in looking at the Gcode file I just pasted I see this: M109 S215

Is it save to assume that is what it happening? May be a silly question, but how would I fix that?

Update - Cura just came out with an update I got this morning and it fixed this issue. Talk about crazy timing... thanks though!