Extents issue without initial G0 moves

Hi,

I am facing a display issue under Axis on the preview when loading a Gcode file. Usually Gcode files will start with a first move as a G0, but I 'd rather use a G1 for the first move to be able to control the feed rate of this first move. Unfortunatly, this seems to induce a weird computation on the extents of the geometry of the file and a move is displayed from the 0 location of the machine.

Which means that when I load my file, it is not directly focused on the geometry as it would be with the G0 move. The difference is illustrated with the two attached files:
-withG0.png is with a initial G0 move, when loading the file, the preview is focused direcly on the geometry on a nice way
-withG1.png is with an initial G1 move, when loading the file, the extents show the 0 0 location and the preview is not zoomed on the aera of interest

Adding a false G0 relative motion as given below, at the begining before the initial move does not make any change to the preview.
G91
G0 X0 Y0 Z0
G90

Thank you

Nicolas

Hi,

not sure what a locking rotary is.

Nicolas

Hi,

so is that a bug for the preview and should I report it somewhere?

Hi,

In fact, I was not using any initial G0 moves as the associated rapid velocity for this first move was considered as too fast. Morevoer I did not want to have to adjust everytime I launch axis the rapid override slider, especially if I wanted to have it to a precise given value, then had to adjust it back to another value for the rest of a running code. Therefore I was using G1 move at the begining which was fine but affected by the preview issue.

So instead I linked a pin motion.analog-out.0 to the halui.rapid-override.value and made in every Gcode I generate the first move as:
M68 E0 Q0.5 (decrease rapid value to 0.5 of maximum speed)
G0 X Y
M68 E0 Q1 (decrease rapid value to 0.5 of maximum speed)
It is a way to solve my initial issue (first move too fast) not being affected by the preview problem.

However for ungrounded program using G91 within a code from the begining, the preview does not start from the actual machine location and the preview issue is still there. Hopefully it will be solved in the next version.

Nicolas