Heated Bed problems - CTC Replicator Clone


#1

What is the problem?
When sending g-code from cura to the printer, all the bed temperatures are set to 60. Once the print starts, it shows pre-heating, gets to 60 and then the pre heat temperature jumps to 130, and cannot be overrridden until the print starts.
What did you already try to solve it?
I've checked all the settings in Cura, and in the printer, I can see nothing to show 130

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)
Latest version of Octoprint, CTC Dual with sailfish firmare
G-Code below shows the jump to 130

Recv:  T:58 /0 B:63 /60 T0:58 /0 T1:31 /0 @:0 B@:0
Recv: ok
Send: N5 M140 S69*95
Recv: ok
Send: N6 M104 S210*96
Recv: ok
Send: N7 M109 S210*108
Recv: ok
Send: N8 M82*17
Recv: ok
Send: N9 M73 P0*94
Recv: ok
Send: N10 G162 X Y F2000(home XY axes maximum)*48
Recv:  T:57 /210 B:62 /130 T0:57 /210 T1:32 /0 @:0 B@:0
Recv: ok

Help?


#2

Er, what is this? I'm seeing an M140 command with a temperature of 69C followed by *95* or perhaps you highlighted in bold a trailing "95" after the M140 S69...? I see "dual" as in "CTC Dual" but there can't be two bed heaters.

And then again, there's that M104 S210 *96* and again with the M109 a shadow value of "108".


#3

I believe the N5 and the 95 (should be *95) are the line number and the checksum added by Octoprint. For some reason, only some of the * are showing up in this listing. If they aren't getting sent to the printer, then I'd expect the printer to complain about a checksum error.

Of course, I know nothing about Sailfish firmware so I could be completely wrong here.


#4

I'm sure this odd "95" is caused while the lines are posted as normal text instead as code.
So the markup formats text included in * italic.
Here an example from a just started print:

Send: N0 M110 N0125
Recv: ok
Send: N1 G21
27
Recv: ok
Send: N2 M10739
Recv: ok
Send: N3 M140 S50
83
Recv: ok
Send: N4 M104 S21098
Recv: ok
Send: N5 G28
22

Send: N0 M110 N0*125
Recv: ok
Send: N1 G21*27
Recv: ok
Send: N2 M107*39
Recv: ok
Send: N3 M140 S50*83
Recv: ok
Send: N4 M104 S210*98
Recv: ok
Send: N5 G28*22

#5

So we're looking at this:

...which is the same as:

Recv: T:58 /0 B:63 /60 T0:58 /0 T1:31 /0 @:0 B@:0
Send: M140 S69          # Set Bed Temperature (non-blocking)
Send: M104 S210         # Set Extruder Temperature (non-blocking)
Send: M109 S210         # Set Extruder Temperature and Wait (blocking)
Send: M82               # Set extruder to absolute mode
Send: M73 P0            # Set build percentage
Send: G162 X Y F2000    # Home X/Y axes to max in each case
Recv: T:57 /210 B:62 /130 T0:57 /210 T1:32 /0 @:0 B@:0

I'm not really seeing an M190, for what it's worth. I don't think this is OctoPrint; it feels like the firmware (Marlin, perhaps).


#6

Just out of curiosity, which version of Cura are you using to slice it ?

I'm asking because I've had some odd temperature things happen with 3.3.1 on my Marlin firmware, and I'm wondering if there's some sort of issue or conflict between Marlin and Cura 3.3.1


#7

Just for the record, @b-morgan and @BerndJM are correct, the spurious 95 is a formatting issue and actually just the checksum. I've fixed the formatting in the OP.

Always use the "paste code" button:

image

(or manually inserted ``` code fences) to keep that from happening.