Movement speed coloring mm/s

[renceww3]

Running the most up to date version of Simplify3D in my OSX, i have been running into the problem that in preview mode the entire part in an uniform color when the coloring is set to movement Speed.
I have changed my preference to mm/s, and the coloring range is from 15mm/s to 1666.6 mm/s, I know I do not have the vastest printer out there but my CoreXY does obviously not come even close to that kind of speeds.

Is there a way to change the coloring range so i can make out which paths are printed faster than others?
If not, could this be added/ updated to a more reasonable coloring range?

Cheers

[brian442]

I think the range already represents the smallest and largest F-values in your file. So if you're getting a really large max value in the chart, it probably means you have a really large F-value in the file.

So open your gcode file in a text editor and look for large F-values. It's possible you entered a speed incorrectly somewhere.

[MHC]

I think the range already represents the smallest and largest F-values in your file. So if you're getting a really large max value in the chart, it probably means you have a really large F-value in the file.

So open your gcode file in a text editor and look for large F-values. It's possible you entered a speed incorrectly somewhere.

Thanks for the hint. I had the same question. I found that the start script had the following line:

Code: Select all

G1 X-120 Y-70 Z30 F9000 ; move to wait position off table

The 9000 translates to 150mm/sec. I changed that to a value of 4200 (70mm/sec) and now the color scheme scales from 0mm/sec to 70mm/s

[gearsawe]

Kind of have this problem. It counts non print moves is this list as well. so my 150mm/s moves are always the factor the makes the max value and my max print speed is 30mm/s. The prints are just bark blue to a light blue.

[dkightley]

Kind of have this problem.

Sort of lose-lose situation for you that doesn't have an answer....unless another non-productive flag is added to modify the behaviour of the software.

My way of thinking is that I know why the range appears larger than is needed for printable paths, so there must be a non-printable path that is fast. Hide the fact...and one day I might forget and miss something.

[gearsawe]

so if I uncheck the "Tavel moves" visibility then the scale should update for what is visible? no?