New maker select + when I stop a job on host it will start where last job stopped

TT_Vert

it appears this maker select + uses Marlin sadly. When I start a job after cancelling a job at repetier-host it will start right where the last job left off as the home position for X (Any maybe Y). I have G28 in my starting GCODE and it works when I enter it manually but it doesn't seem to run my starting gcode. If I do an emergency stop it'll reboot printer and I think that does allow it to start in correct spot. Also is the reason I cannot see any of the print info on display of the plus like I do the maker select v2 because it is using marlin instead of repetier?

Thanks
Dave

Repetier

Do you print from sd card or directly? If directly over server or from host directly. I thjink you print over server so you need the homing in the servers start gcode, not in host. Better would be if it is in your slicers gcode. Each slicer should start with homing first anyway.

TT_Vert

I print from host.the gcode is still where it had been work my other printer (in cura)

TT_Vert

Did it again to me today. Printed from host, had to cancel job from host due to an issue w/ print and then when I started it over if I homed X from the printer it thought where the print left off was home. I started a new print from host and it still thought home was where it stopped last print. If I manually homed w/ G28 in host it as fine but not when I printed the file from host. G28 is in my start gcode and always works otherwise.
Dave

Repetier

Maybe the G28 is written wrong for your firmware? Host will send everything it considers gcode. You can see it in the log if that command was send. If it was send it is a firmware thing. If it doe snot get send copy the gcode lines to see if it shows a reason to not be send.

Older server versions had problems if there was no space before comment but host has no problems known.

TT_Vert

Where would the log be? I don't see much on the gui console and I didn't see any logs in appdata or program files folders (Windows).

Also seems it doesn't like the M107 either as the print cooling fan is always on. The repetier FW maker select V2 was perfect in all aspects. This marlin FW, not so much.

Dave

Repetier

If you enable logging in preferences->general it is repetier.log in host work directory.

TT_Vert

Ok here is the log. I started the job. I then canceled the job about 20 seconds into the print by clicking . The extruder was about mid axis on X when I stopped the job. I then went back to host and clicked print again and it started on the same X axis it ended on thinking it was home I assume. Even after re slicing and printing a complete new job the extruder crashes unless I power off the printer.

Dave

Repetier

No log. Also when positing log note the time entry where it happens for fast searching.

TT_Vert

No idea how that happened. Here is the log again I assume it's around line 1660 10:29:46

I still don't see it attached. I see the log after i upload it to your site but when I submit it is gone.

Here it is in my dropbox.
https://www.dropbox.com/s/rdowz1qtd2c99pe/repetier.log?dl=0<br/>

Repetier

That is not the written file log. Here the commands send are missing. Also the local log only contains last 2000 lines. I see a lot of ok where I could guess it contained a G28 but without seeing it I can not say.

You can also just try your self homing twice with G28 like in the gcode you send. If it happens only once the firmware just skipps homing for some unknown reason.

TT_Vert

Ok can you explain what you need then? This is the log generated by enabling what you told me to enable. Do i need to somehow change logging level to show what you want to see? I'll try to cancel a job and send a G28 to see if it homes where it should on next print or if it starts where last was cancelled.

Repetier

Looks like the log but it is missing the send commands. So I guess you are not printing with host but with repetier-server. In that case you need to check the server logs. But server will overwrite old log if you print same file twice. But we are interested in the second call anyway where you say G28 does not cause homing. So that is no problem.

All I saw was

echo:enqueing "G28 Z0"

but no line doing it for x and y direction.

TT_Vert

I am initiating all prints via host, none via server. I have no repetier.log file on my server (pi) Looking at the log session option in host it says "it will contain all communication even if disabled in log view". Oddly my log view has commands enabled and all it states is what layer i'm on, not the actual commands sent to printer. is that normal or part of the issue here?

Dave

TT_Vert

FYI this seems to occur for others as well. Maybe a marlin FW issue?

https://github.com/andrivet/ADVi3pp-Marlin/issues/15<br/>

TT_Vert

Also I reinstalled host and now all commands are showing properly in real-time log so I have to assume they'll show in repetier.log when the time comes to log this error. I have a long list of prints to finish before I can cancel a print to log this problem. With that said it seems this is a Marlin FW issue (See link above) which you probably have no ability to resolve anyway correct? BTW, is there a way to display layer # or layer x/xxx complete using M117? I know my i3 showed it but the i3 plus just cycles the ETE and ETA, not mentioning layer #. It definitely is showing them in the real-time host log "Printing layer 50 of 64"

Thanks
Dave

Repetier

Yes, we can not resolve firmware bugs. As I already thought host is sending it and firmware ignoring.

Layer is only shown if you print through repetier-server and have it enabled to cycle through all. Host as printer daemon will only show ETA/ETE.

TT_Vert

Is that a feature that can be requested or is it difficult to implement it? Clearly it is aware of the layer and is able to send ETA, ETE already would it be hard for host to send that data along via M117 commands? Oddly, I closed host when I went to bed last night mid-print and it was showing the gcode it executed at bottom of screen in log, now all it shows upon opening this AM is just "printing layer xxx of xxx" even w/ commands radio button enabled. I don't get why this changes out of nowhere?

Dave

TT_Vert

Ok I'm seriously starting to question my own insanity but I'm not going nuts and I have pics to prove it this time. I started a job on server this time, it showed a few lines of gcode commands and then just stopped in host.. Does it buffer them and just send a group all at once perhaps?

TT_Vert

Repetier said:

Layer is only shown if you print through repetier-server and have it enabled to cycle through all. Host as printer daemon will only show ETA/ETE.

I also want to follow up on this. Perhaps this is a bug but I started a job from repetier-server and the ONLY way it'll display layer is if I select the layer option. If I select cycle it only shows ETA/ETA.

Dave