<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>speed recognition</title>
        <description> Hello Everyone.

Sorry for the n00by question, here it is:

I am confident in using slicing tools like slic3r. They give you the possibility to set velocities (i.e. velocity on the perimeters, on the infill ... [manual.slic3r.org] )

As a result, when I generate the G-Code, I have this kind of output: 

[...previous lines...]
G1 Z147.200 F7800.000
G1 Z149.400 F7800.000
M107
M104 S0 ; turn off temperature
G28 X0  ; home X axis
M84     ; disable motors

; avoid_crossing_perimeters = 1
; bed_size = 200,200
; bed_temperature = 0
[cut]
; first_layer_speed = 10
; first_layer_temperature = 205
[cut]
; bridge_speed = 40
; external_perimeter_speed = 30
; infill_speed = 40
[etc]

The question is:

How this firmware extract the &quot;speed&quot; information when needed ?
I expected some firmware instructions (like M220: Set speed factor override percentage) in the G-CODE when passing i.e. from infill to perimeters... but this is not true !
so how the firmware &quot;decides&quot; when we are on a perimeter or in a infill and how does it set corresponding velocities ? 

Similar consideration can be done for accelerations.

[this is because I am writing a custom firmware]

Thanks a lot,
Paolo</description>
        <link>https://reprap.org/forum/read.php?267,568049,568049#msg-568049</link>
        <lastBuildDate>Thu, 12 Mar 2026 16:05:11 -0400</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://reprap.org/forum/read.php?267,568049,568134#msg-568134</guid>
            <title>Re: speed recognition</title>
            <link>https://reprap.org/forum/read.php?267,568049,568134#msg-568134</link>
            <description><![CDATA[ Ah ok, I answer to myself:<br />
<br />
That info is contained in F parameters of the G0/G1 instructions (also if the terminology "feedrate" can be disguising :S [<a href="http://reprap.org/wiki/G-code#G0_.26_G1:_Move" target="_blank"  rel="nofollow">reprap.org</a>] )<br />
<br />
This generates new questions in me, but this is matter for another section of these forums.<br />
<br />
cya]]></description>
            <dc:creator>emdcp</dc:creator>
            <category>Repetier</category>
            <pubDate>Thu, 08 Oct 2015 09:53:47 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?267,568049,568049#msg-568049</guid>
            <title>speed recognition</title>
            <link>https://reprap.org/forum/read.php?267,568049,568049#msg-568049</link>
            <description><![CDATA[ Hello Everyone.<br />
<br />
Sorry for the n00by question, here it is:<br />
<br />
I am confident in using slicing tools like slic3r. They give you the possibility to set velocities (i.e. velocity on the perimeters, on the infill ... [<a href="http://manual.slic3r.org/expert-mode/speed" target="_blank"  rel="nofollow">manual.slic3r.org</a>] )<br />
<br />
As a result, when I generate the G-Code, I have this kind of output: <br />
<br />
[...previous lines...]<br />
G1 Z147.200 F7800.000<br />
G1 Z149.400 F7800.000<br />
M107<br />
M104 S0 ; turn off temperature<br />
G28 X0  ; home X axis<br />
M84     ; disable motors<br />
<br />
; avoid_crossing_perimeters = 1<br />
; bed_size = 200,200<br />
; bed_temperature = 0<br />
[cut]<br />
; first_layer_speed = 10<br />
; first_layer_temperature = 205<br />
[cut]<br />
; bridge_speed = 40<br />
; external_perimeter_speed = 30<br />
; infill_speed = 40<br />
[etc]<br />
<br />
The question is:<br />
<br />
How this firmware extract the "speed" information when needed ?<br />
I expected some firmware instructions (like M220: Set speed factor override percentage) in the G-CODE when passing i.e. from infill to perimeters... but this is not true !<br />
so how the firmware "decides" when we are on a perimeter or in a infill and how does it set corresponding velocities ? <br />
<br />
Similar consideration can be done for accelerations.<br />
<br />
[this is because I am writing a custom firmware]<br />
<br />
Thanks a lot,<br />
Paolo]]></description>
            <dc:creator>emdcp</dc:creator>
            <category>Repetier</category>
            <pubDate>Thu, 08 Oct 2015 05:55:29 -0400</pubDate>
        </item>
    </channel>
</rss>
