Rostock hanging at start of job

[TN Yankee]

Hello, all. First post, but I've been lurking for the past month or so. I've been quite happy with S3D so far, but haven't used it or my printer a lot lately due to time commitments.

I've been testing PCTPE, and making simple test cubes while tweaking various parameters. All of a sudden, I can't get any S3D jobs to print - they all hang very early in the code, before the hot end even drops down to the plate. I've looked at the gcode, but I'm not seeing anything odd.

1) Running S3D 3.0.2, in LinuxMint 17.2
2) Printer is SeeMeCNC Rostock MAX v2, Rambo & OEM Repetier firmware
3) Doesn't matter if I print via USB, or SD card from the LCD controller
4) I get a response of "fail open" if I try to run from SD card via S3D
5) Exported S3D gcode, and run from RepetierHost via USB (on a separate computer with separate USB cable) fails identically
6) A near-identical test cube job (from same STL) generated & run from RepetierHost (on separate computer) runs fine
7) The RH-generated gcode runs fine from SD card, via the LCD controller
8) I have manually sent each command and gotten further than below, but it did freeze after I got impatient and apparently sent too many commands at once
9) In all other aspects, S3D & the interface to the printer appear to be functioning properly, until the freeze. At that point, I use the disconnect/connect button to re-initialize
10) There is nothing in the starting script other than G28
11) The hot-end homes, but never moves again, though the first XYZ coordinates are shown in the Machine Control Position Readout
12) Both bed & hot-end temperatures are already stable before the job begins, so there shouldn't be any pausing for temperature changes

Is there something out of place here? Below are the lines from the comm window for a run I did yesterday. Attached is a PDF comparing the S3D & RH gcode files. Please ignore the coordinate differences between below & the PDF, as they were from different runs, but identical behavior.

SENT: G90
SENT: M82
SENT: M106 S0
SENT: M140 S40
SENT: M190 S40
RECEIVED: ok 0
RECEIVED: ok 0
RECEIVED: ok 0
RECEIVED: ok 0
RECEIVED: ok 0
SENT: M104 S240 T0
SENT: M109 S240 T0
RECEIVED: ok 0
RECEIVED: TargetExtr0:240
RECEIVED: ok 0
SENT: G28
SENT: G92 E0
SENT: G1 E-2.0000 F6600
SENT: G1 Z0.480 F1200
SENT: T0
RECEIVED: TargetExtr0:240
RECEIVED: ok 0
RECEIVED: ok 0
SENT: G1 X24.600 Y21.776 F9000
RECEIVED: ok 0
SENT: M105
RECEIVED: ok 0
SENT: G1 Z0.180 F1200
RECEIVED: ok 0
SENT: G1 E0.0000 F1980
RECEIVED: ok 0
SENT: G92 E0 <<<HANGS HERE


Many thanks to any help!

Mike

[andrewk72]

All of the gcode commands look correct, however, the printer stopped responding at the end. It looks like S3D sent the command correctly, but it wasn't getting any response. That's going to cause it to stop printing if the printer won't send anything back.

[TN Yankee]

Thanks for the reply. I had sent two files that were failing for me, to a friend with the same printer & S3D, and both printed fine for him.

I re-flashed the firmware this evening, and restored the same EEPROM values, and it seems to have corrected it - for now, at least.