Cura and Octoprint on MPSV2

[Sailor 0]

It seems when Cura creates the GCode to be sent to Octoprint one line destroys the process: "N18 G1 Z15.0 F{travel_speed}*49"  I get an error in format error.  If I remove the {travel_speed}*49 and replace it with say 50 so that it says F50, all is good and the print continues.

I cannot seem to find where I can modify the script so that the {travel_speed}*49 does not become part of the gcode.

a portion of the data sent to Octoprint follows;

Recv: ok
Recv: Error:Format error
Recv: 
Send: N23 M105*22
Recv: Resend:18
Recv: ok
Recv: skip 19
Recv: ok
Send: N18 G1 Z15.0 F{travel_speed}*49
Recv: skip 20
Recv: ok
Send: N19 G92 E0*127
Recv: skip 21
Recv: ok
Recv: skip 22
Recv: ok
Recv: skip 23
Recv: ok
Send: N20 G1 X10 Y10*27
Send: N21 G28 Z0*106
Recv: Error:Format error
Recv: 
Recv: Resend:18
Recv: ok
Send: N22 G1 Z0.4*72
Send: N23 M105*22
Recv: skip 19
Recv: ok
Send: N18 G1 Z15.0 F{travel_speed}*49
Send: N19 G92 E0*127

 

Any assistance will be appreciated

[ahoeben 1,948]

Use {speed_travel} in your start gcode instead of {travel_speed}

Edited August 3, 2018 by ahoeben
Typo

[Sailor 0]

I will have to check that out, this is the first time I am using the Cura 3.1.1, only been printing a week, was using the Cura that came with my printer IIIP.  So much to learn so little time to do it.

[Sailor 0]

G1 Z15.0 F{travel_speed}*49 is in the start gcode, but I do not see where travel_speed is defined or set.

For now, I just changed my {travel_speed} to F50 in the start code, can always modify it later once I understand where the variable is defined.  I know or understand just enough programming to squeak by.

[ahoeben 1,948]

> Use {speed_travel} in your start gcode instead of {travel_speed}

 

{travel_speed} does not work with newer Cura versions. {speed_travel} does.

[Sailor 0]

Ok, I changed it and that line is no longer a culprit. 

 

I am getting a lot of checksum errors, is this normal?

[ahoeben 1,948]

No, checksum errors should not happen. They indicate connection issues between the computer running octoprint and the printer. Nothing Cura can do about that.

[Sailor 0]

I had a heck of a time getting my printer to connect with Octoprint, so there may be some communication problems that still exist.  The system just requests a resend and the fault for that line goes away, but a new one may show up later.  I am going to try and move the Raspberry Pi 3 b to a different location which may help with its reception.  I will let you know as soon as I get a chance to do so.