[SOLVED] print_job request failed with status: 500

AstroPrint Cloud Service Troubleshooting
#1

Hi, several times this morning my print job just suddenly stops out of no where. The only indication I can find of a problem is this in the astrobox.log file;

astroprint.cloud - ERROR - print_job request failed with status: 500

This error is particularly a concern for me because when the print job stops, the heat bed and extruder and still maintaining the melting point of the plastic (190C extruder / 50C heatbed) for hours right on top of where the print material was extruded, melting plastic and having a concern for a cause of fire.

Any help would be appreciated on fixing this issue. I know I’m giving little diagnostic information up front, however if you tell me where to look I can retrieve the information for you.

I’ve started the serial debug log and am waiting for another print to fail to see if I can capture more information. I’m using Repetier Firmware 0.92.9 (latest GitHub as of today).

1 Like
#2

I forgot to mention that this only happens when I use the “Cloud Print” feature, starting a print from http://astroprint.com … if I print the file locally on the Raspberry Pi astrobox, this doesn’t happen.

2 Likes
#3

Thanks for the report, We’re going to investigate this

1 Like
#4

Thanks so much for the report, this should be fixed now. Please confirm when you have a chance!

1 Like
#5

Hi, not sure if its related or not. Anyway, it happened again a couple of minutes ago. Here is the serial.log output;

2016-06-05 01:03:09,994 - SERIAL - DEBUG - Recv: ok 8029
2016-06-05 01:03:09,999 - SERIAL - DEBUG - Send: N8032 G1 X104.094 Y109.477 E1158.07940*104
2016-06-05 01:03:10,063 - SERIAL - DEBUG - Recv: ok 8030
2016-06-05 01:03:10,068 - SERIAL - DEBUG - Send: N8033 G1 X103.831 Y109.905 E1158.10028*96
2016-06-05 01:03:10,081 - SERIAL - DEBUG - Recv: Error:Wrong checksum
2016-06-05 01:03:10,087 - SERIAL - DEBUG - Recv:
2016-06-05 01:03:10,094 - SERIAL - DEBUG - Recv: Resend:8031
2016-06-05 01:03:10,098 - SERIAL - DEBUG - Send: N8031 G1 X104.291 Y109.000 E1158.05794*109
2016-06-05 01:03:10,103 - SERIAL - DEBUG - Recv: ok
2016-06-05 01:03:10,108 - SERIAL - DEBUG - Send: N8032 G1 X104.094 Y109.477 E1158.07940*104
2016-06-05 01:03:10,118 - SERIAL - DEBUG - Recv: skip 8033
2016-06-05 01:03:10,123 - SERIAL - DEBUG - Recv: ok
2016-06-05 01:03:10,127 - SERIAL - DEBUG - Send: N8033 G1 X103.831 Y109.905 E1158.10028*96
2016-06-05 01:03:10,134 - SERIAL - DEBUG - Recv: ok 8031
2016-06-05 01:03:10,138 - SERIAL - DEBUG - Send: N8034 G1 X103.497 Y110.296 E1158.12166*103
2016-06-05 01:03:10,146 - SERIAL - DEBUG - Recv: ok 8032
2016-06-05 01:03:10,150 - SERIAL - DEBUG - Send: N8035 G1 X103.108 Y110.629 E1158.14295*108
2016-06-05 01:03:10,218 - SERIAL - DEBUG - Recv: ok 8033
2016-06-05 01:03:10,222 - SERIAL - DEBUG - Send: N8036 G1 X102.675 Y110.893 E1158.16403*103
2016-06-05 01:03:10,405 - SERIAL - DEBUG - Recv: ok 8034
2016-06-05 01:03:10,410 - SERIAL - DEBUG - Send: N8037 M105*27
2016-06-05 01:03:10,481 - SERIAL - DEBUG - Recv:
2016-06-05 01:03:10,489 - SERIAL - DEBUG - Recv: Resend:8035
2016-06-05 01:03:10,493 - SERIAL - DEBUG - Send: N8035 G1 X103.108 Y110.629 E1158.14295*108
2016-06-05 01:03:10,499 - SERIAL - DEBUG - Recv: ok
2016-06-05 01:03:10,503 - SERIAL - DEBUG - Send: N8036 G1 X102.675 Y110.893 E1158.16403*103
2016-06-05 01:03:10,513 - SERIAL - DEBUG - Recv: Error:Format error
2016-06-05 01:03:10,516 - SERIAL - DEBUG - Changing monitoring state from 'Printing' to 'Error: Format error
#6

This is unrelated to AstroPrint. You’re getting two errors:

Error:Wrong checksum

The way we calculate checksums is according to the GCODE specs and have done it the same way for a very long time. This error though seems to be recoverable.

The next error is more severe as the AstroBox doesn’t know what to do with it and simple stops the print.

Recv: Error:Format error

I can’t find information about this error here at all: http://reprap.org/wiki/G-code

My guess, honestly is that is a problem in the latest Repetier firmware. Are you using official releases of taking code from HEAD which might be unstable?

#7

Hi, thanks Daniel. I’m using the latest checkout from the Master Branch of Repetier Firmware.

Octopi doesn’t drop the connection on receiving “Error:Format error” and resends the line (the request to resend the line happens after the “Changing Monitor State” actually).

#8

I guess this could easily be fixed by adding in;

or 'Format error' in line \

In marlin/comm.py file somewhere around line 1020? Looks like Repetier Host just ignores the error.

#9

Thanks for the info and suggestion. I have added to our Issue list and it will get fixed: