Simplify3D User Forum

+0, or is it -0?

It's a trivial mental calculation to divide by 60, isn't it?

Baron:

A cnc is much slower and has much bigger workarea? there it might be better judging speed in minutes. But i myself want to measure speed in seconds, because we have so small workarea, so mm/sec is what i want to know. not minutes.
My machine does not take a minut to move from one side to another, it takes seconds or much less.

AndersE wrote:Baron:

A cnc is much slower and has much bigger workarea? there it might be better judging speed in minutes. But i myself want to measure speed in seconds, because we have so small workarea, so mm/sec is what i want to know. not minutes.
My machine does not take a minut to move from one side to another, it takes seconds or much less.

AndersE,

What baron said is correct. It doesn't matter how long it takes your machine to move from left to right or all around. The speeds understood by the microcontroller in your printer natively uses mm/min.
GCodes sent to the microcontrollers use the F variable which is speed in mm/min. Check this link:
http://reprap.org/wiki/G-code

So s3d actually uses speeds the firmware natively understands, whereas software using mm/sec make a back end conversion most likely.

+1
I don't care what g-code uses. That is irrelevant. I am used to seeing mm/sec so I should be able to select the program to display in those units.

+1

mm/s <---- should be the default (besides with this unit parameter numbers are smaller and easier to remember 30 mm/s vs 1800 mm/min.)

kdpainter wrote: I don't care what g-code uses. That is irrelevant. I am used to seeing mm/sec so I should be able to select the program to display in those units.

I think this is why the US still uses imperial units

+1 make mm/s and mm/min selectable for user presentation.

Hi,

I have a big problem with mm/min.

The value in mm/s is quiet simple for me.

Could you make it adjustable?

Regards
Stephan

+1

The G-code is in mm/minute. Which means all the commands under the scripts tab will be using mm/minute. It would be a much more confusing system if all of the tabs in the FFF window had mm/second and then the scripts tab used mm/minute. The current system is uniform as is and therefore much more user friendly, despite the fact that I've used mm/sec in the past with other programs.