Having trouble with new printer using v 1.04 and Repetier Host. OK w/ factory Marlin using R. Host
I assembled a I3 clone for a friend. It is identical to mine, except with a single extruder. A USB print worked with R. Host and the original Marlin FW. I installed Repetier FW 1.04 and I can't seem to get it to start a print using USB. R. Host gives several file error messages and the job kills before it does anything. One thing notable is that when the print is started, the Z axis raises 10 or 20 mm and then stops. Everything seems to be OK with manual control and running from an SD card. I'm about ready to back up to 0.92 unless this symptom is familiar to anyone.
Comments
Bed needs to go to 55°C and 2 minutes later a reset happens. Did you reset it and if so why or is that the problem you mean? After a reset host of course stops printing.
Did it just not get the temperature or did the heater cause power problems? Heated beds sometimes have less resistance then they should and use sometimes too much current.
In any case it is important to see full communication. You should even enable echo so you see which commands got executed and not only send. Then you know which command is causing the problem. As a test send same command directly from manual console and see if same thing happens.
At the first connect in log you see
Info:External Reset
that is ok as host resets printer on connect. After the further start I do not see a reason which I'd expect.
is the sequence before the restart. So one of the commands does cause this. So send them manually and see at what command it exactly happens. Bed was not up so it would need to stop at M190 S55 or that even causes it also heating before was good. But I see no further temperatures and M190 reports them automatically, so it could also be M107 or one of the 4 commands before. M107 would also a good guess if fan is set to wrong pin, e.g. reset pin, but pin 7 is the official fan pin as it looks.
Some boards use a different port for uploading firmware. Then they go into dfu mode and windows shows this as different port. If that is what you see it is ok.
You can also in host set sd card to not present to prevent any file related gcodes.
The error you see comes from SDCard.cpp from thsi line
Com::printFLN(Com::tErrorWritingToFile);
but that case only happens if you tell host to upload a file for printing. It gets called from commands.cpp
void Commands::commandLoop() {//while(true) {
#ifdef DEBUG_PRINT
debugWaitLoop = 1;
#endif
if(!Printer::isBlockingReceive()) {
GCode::readFromSerial();
GCode *code = GCode::peekCurrentCommand();
//UI_SLOW; // do longer timed user interface action
UI_MEDIUM; // do check encoder
if(code) {
#if SDSUPPORT
if(sd.savetosd) {
if(!(code->hasM() && code->M == 29)) // still writing to file
sd.writeCommand(code);
else
sd.finishWrite();
#if ECHO_ON_EXECUTE
code->echoCommand();
#endif
} else
Change
if(sd.savetosd) {toif(false & sd.savetosd) {and it should not happen any more but you can not upload files to sd card over host then. So only a temporal fix.Global variables use 5481 bytes (66%) of dynamic memory, leaving 2711 bytes for local variables. Maximum is 8192 bytes.