Defined Printer Limits
I keep getting the following message when I try and start a print.
'According to your defined printer limits, this print will not fit inside your printer. Print Anyway?'
I can choose to print anyway and it works fine. This bug started after my update to 85.2.
'According to your defined printer limits, this print will not fit inside your printer. Print Anyway?'
I can choose to print anyway and it works fine. This bug started after my update to 85.2.
Comments
@nosize
Ignore next print moves for object size calculation. This is interesting if you make a extrusion at a fixed position. Then the server will include that into the size and that may lead teh rendere to show a much too small object.
@size
Stops the @nosize command from neglecting size computation. Never forget this if you use @nosize. They should always come as a pair.
;@nosize
and after this outside extrusion add
;@nosize
so it then can start with gcode rendering. Everything inside @nosize does not get rendered.
Would it be possible to add an option (Either per printer or per server) to disable this warning?
showing the computed dimension of the gcode.
I also re-entered a new printer profile in Cura and then I noticed that the old profile would systematically place the prints outside the print area. The new print profile would place them correctly on the board and therefore there was no more warnings.
I conclusion, it was combination of bad settings both in the slicer and repetier's prints settings.
Old profile:
New profile:
;FLAVOR:Marlin
cd /var/lib/Repetier-Server/printer/Felix/models/
Replace Felix with your printer slug. Then run ls to show files. Take the one you are interestid in and cat content of the gin filecat name.gin
At the end you will see something like
xMax: 112.56400299072266
xMin: 0
yMax: 112.56400299072266
yMin: 0
zMax: 4.599999904632568
zMin: 0
Then you know what the real dimension is according to server. That must be covered by the min/max dimensions in general printer configuration.
It is possible that you have a extrusion outside. My prusa config for example will do that at y = -3 so I had to allow that even I do not want to print there. Alternatively you can omit these parts using
@nosize
Ignore next print moves for object size calculation. This is interesting if you make a extrusion at a fixed position. Then the server will include that into the size and that may lead teh rendere to show a much too small object.
@size
Stops the @nosize command from neglecting size computation. Never forget this if you use @nosize. They should always come as a pair.
Do this (if you're purge line is G1 Y-3.0 F1000.0 ; go outside printing area ):
So i haven't printed anything in a while and was on Repetier Server 0.91.2. I now upgraded to the latest version 0.92.1 and today i wanted to print some things and for each of my uploaded GCODES i now get the Security Question about the printer size.
1. My printer profile in Repetier Server has not changed from 0.91.2 to now and has the correct print bed size settings.
2. My S3D and CURA profiles are also all the same since 0.91.2 and i have not made any changes to print bed sizes in my profiles nor in the startup scripts which do have a purge line in them.
3. The startup script has a purge line however it is not going outside the specified print bed dimension:
G1 X0.0 Y15.0 F3000.0 ; Move the nozzle to bottom left corner
G1 Z0 ; Move nozzle to print height
G1 X0.1 Y20 F5000.0 ; move to start-line position
G1 X0.1 Y200.0 F1500.0 E15 ; draw 1st line
G1 X0.4 Y200.0 F5000.0 ; move to side a little
G1 X0.4 Y20 F1500.0 E30 ; draw 2nd line
So realistically there should be no reason for me to get this error message.
On linux you find it in /var/lib/Repetier-Server/printer/<printer slug>/models
Interesiting part is this:
xMax: 117.88700103759766
xMaxMove: 115.697998046875
xMin: 83.34300231933594
xMinMove: 0
yMax: 128.48399353027344
yMaxMove: 210
yMin: 71.63999938964844
yMinMove: 73.0479965209961
zMax: 15.949999809265137
zMin: 0
The move limits are new in 0.92 so might not exist for old gcodes.
I also checked the corresponding .gin file which shows the following info at the end.
From what i can tell the yMAXMove indicates a movement that would be out of bounds for the printer so i guess this would be the reason for the message however based on the slicer settings and the printer settings in repetier server and also the 2D preview this value should not even be possible. To me this seems like an error in this new feature somehow?
Also if you upload same file multiple times is it always same yMaxMove for same gcode? If not it would be a server problem with uninitialized variable. If always the same it comes from a command in gcode.
Upload 1: yMaxMove: 348.64501953125
Upload 2: yMaxMove: 348.64501953125
When i look in the source gcode there is no mention anywhere of this value. So its not comming from the GCODE and repeated uploads generate the same yMaxMove value in the gin file.