Manual Feed Rate Changes when print starts V1.54

I have 2 delta printers. One uses v0.91 firmware and  the other uses v0.92  firmware. When printing with the printer that uses the v0.92 firmware, the  feed rate control on the Host manual control tab changes from whatever I preset it to back to 100% when the print job starts. Once the job has started I must  to change the setting back to what I had set prior to starting the job.

When I use the printer that has v9.01 firmware installed, this does not happen. The value  always stays where I manually set it prior to the start of the print job. Is there a setting that I have  incorrectly configured somewhere ? I have cloned the Slic3r slicer settings from the first printer so they should be set up to slice identically.

Comments

  • I checked the code I found

    void Extruder::markAllUnjammed()
    {
        for(fast8_t i = 0; i < NUM_EXTRUDER; i++)
        {
            extruder[i].tempControl.setJammed(false);
            extruder[i].tempControl.setSlowedDown(false);
            extruder[i].resetJamSteps();
        }
        if(Printer::feedrateMultiply == JAM_SLOWDOWN_TO)
            Commands::changeFeedrateMultiply(100);

    which is the only part changing speed multiplier to 100. And this will only happen if it was set to JAM_SLOWDOWN_TO = 70 by default. So does it happen also with other values?

    I also tried myself and it did not change the multiplier with 0.92. The only way for it to change is having M220 in your gcode or if it comes from firmware the firmware needs to return something like

    18:47:08.631 : SpeedMultiply:128

    (needs ACK enabled to see it)). So you should log to file and see if one of both happens and which commands were involved there.
  • Here is a log. I have manually set the Feedrate to 85% (highlighted in red). As soon as the print job starts, the rate resets itself to 100 %. The version of the firmware is actually 0.92.2 if that helps


    Log:






    09:21:45.249 : N2599 M105 *48



    09:21:48.260 : N2600 M105 *51



    09:21:48.665 : N2601 M111 S15 *64



    09:21:48.665 : Echo:N2601 M111  S15



    09:21:51.317 : N2602 M105 *49



    09:21:51.317 : Echo:N2602 M105



    09:21:54.375 : N2603 M105 *48



    09:21:54.375 : Echo:N2603 M105



    09:21:55.170 : N2604 M220 S85 *77



    09:21:55.170 : Echo:N2604 M220  S85



    09:21:57.432 : N2605 M105 *54



    09:21:57.432 : Echo:N2605 M105



    09:21:57.651 : N2606 M117 ETE 00s *17



    09:21:57.666 : Echo:N2606 M117 ETE 00s



    09:21:58.041 : N2607 G28 *0



    09:21:58.041 : N2608 G1 Z5 F5000 *24



    09:22:01.816 : X:0.00 Y:0.00 Z:74.269 E:0.0000



    09:22:01.816 : Echo:N2607 G28



    09:22:01.832 : Echo:N2608 G1  Z5.00
    F5000.00



    09:22:01.832 : N2609 M105 *58



    09:22:01.832 : N2610 G21 *15



    09:22:01.832 : Echo:N2609 M105



    09:22:01.832 : N2611 G90 *4



    09:22:01.832 : Echo:N2610 G21



    09:22:01.832 : N2612 M82 *14



    09:22:01.847 : Echo:N2611 G90



    09:22:01.847 : Echo:N2612 M82



    09:22:01.847 : N2613 G92 E0 *81



    09:22:01.847 : N2614 G1 E-1 F3600 *35



    09:22:01.847 : Echo:N2613 G92 
    E0.0000



    09:22:01.847 : N2615 G92 E0 *87



    09:22:01.847 : Echo:N2614 G1 
    E-1.0000 F3600.00



    09:22:01.847 : N2616 G1 Z0.2 F7800 *4



    09:22:01.863 : Echo:N2615 G92 
    E0.0000



    09:22:01.863 : N2617 G1 X-22.047 Y-15.521 F7800 *83



    09:22:01.863 : Echo:N2616 G1  Z0.20
    F7800.00



    09:22:01.863 : N2618 G1 E1.1 F3600 *29



    09:22:01.879 : Echo:N2617 G1  X-22.05
    Y-15.52 F7800.00



    09:22:01.879 : Printing layer 1 of 40



    09:22:01.879 : N2619 G1 X-21.324 Y-16.548 E1.11765 F900 *44



    09:22:01.879 : Echo:N2618 G1  E1.1000
    F3600.00



    09:22:01.879 : N2620 G1 X-20.774 Y-17.234 E1.13 *66



    09:22:01.879 : Echo:N2619 G1  X-21.32
    Y-16.55 E1.1176 F900.00



    09:22:01.879 : N2621 G1 X-19.082 Y-19.09 E1.1653 *118




     





  • The log is incomplete. It does not contain ACK messages which are important here. We see that the host never sends a 100% speed multiplier so it is not the host changing it. Firmware sends changes to host so host will update if you set multiplier on printer lcd. That would be contained in the ACK messages.

    Also are you printing over the host or through the server? If through server the server could add commands also I'm quite sure it does not reset multiplier.
  • I am printing through host 1..54.

    Here is the log with the ACK turned on . You can see where I set the speed to 85%. You can also see where the speed is reset to 100 % .  Where is that coming from?  It is not in the G Code. There is no starting script..

    log2:


    07:34:11.455 : T:23.23 /0 @:0
    07:34:12.453 : wait
    07:34:13.451 : wait
    07:34:14.450 : wait
    07:34:14.512 : N178 M105 *9
    07:34:14.512 : ok 178
    07:34:14.512 : T:23.23 /0 @:0
    07:34:14.902 : N179 M220 S80 *119
    07:34:14.902 : ok 179
    07:34:14.902 : SpeedMultiply:80
    07:34:15.905 : wait
    07:34:16.909 : wait
    07:34:17.580 : N180 M105 *14
    07:34:17.580 : ok 180
    07:34:17.580 : T:23.23 /0 @:0
    07:34:18.578 : wait
    07:34:19.577 : wait
    07:34:20.575 : wait
    07:34:20.637 : N181 M105 *15
    07:34:20.637 : ok 181
    07:34:20.637 : T:23.33 /0 @:0
    07:34:21.636 : wait
    07:34:22.634 : wait
    07:34:23.633 : wait
    07:34:23.695 : N182 M105 *12
    07:34:23.695 : ok 182
    07:34:23.695 : T:23.33 /0 @:0
    07:34:23.945 : N183 M220 S85 *119
    07:34:23.945 : ok 183
    07:34:23.945 : SpeedMultiply:85
    07:34:24.943 : wait
    07:34:25.946 : wait
    07:34:26.741 : N184 M105 *10
    07:34:26.741 : ok 184
    07:34:26.741 : T:23.33 /0 @:0
    07:34:27.506 : N185 M117 ETE 00s *47
    07:34:27.506 : ok 185
    07:34:27.802 : N186 G28 *60
    07:34:27.802 : ok 186
    07:34:27.802 : N187 G1 Z5 F5000 *42
    07:34:31.640 : SpeedMultiply:100
    07:34:31.640 : X:0.00 Y:0.00 Z:74.269 E:1.9694
    07:34:31.640 : ok 187
    07:34:31.640 : N188 M105 *6
    07:34:31.640 : ok 188
    07:34:31.640 : N189 G21 *58
    07:34:31.640 : T:23.33 /0 @:0
    07:34:31.655 : ok 189
    07:34:31.655 : N190 G90 *56
    07:34:31.655 : ok 190
    07:34:31.655 : N191 M82 *48
    07:34:31.655 : ok 191
    07:34:31.655 : N192 G92 E0 *109
    07:34:31.655 : ok 192
    07:34:31.655 : N193 G1 E-1 F3600 *25
    07:34:31.687 : ok 193
    07:34:31.687 : N194 G92 E0 *107
    07:34:31.687 : ok 194
    07:34:31.687 : N195 G1 Z0.2 F7800 *58
    07:34:31.702 : ok 195
    07:34:31.702 : N196 G1 X-22.047 Y-15.521 F7800 *111
    07:34:31.702 : ok 196
    07:34:31.702 : N197 G1 E1.1 F3600 *47
    07:34:31.718 : ok 197
    07:34:31.718 : Printing layer 1 of 40
    07:34:31.718 : N198 G1 X-21.324 Y-16.548 E1.11765 F900 *16
    07:34:31.718 : ok 198
    07:34:31.718 : N199 G1 X-20.774 Y-17.234 E1.13 *117
    07:34:31.718 : ok 199
    07:34:31.718 : N200 G1 X-19.082 Y-19.09 E1.1653 *67
    07:34:31.718 : ok 200
    07:34:31.718 : N201 G1 X-18.45 Y-19.702 E1.17766 *116
    07:34:31.733 : ok 201
    07:34:31.733 : N202 G1 X-16.539 Y-21.332 E1.21295 *71
    07:34:31.733 : ok 202
    07:34:31.733 : N203 G1 X-15.836 Y-21.859 E1.22531 *75
    07:34:31.749 : ok 203
    07:34:31.749 : N204 G1 X-13.735 Y-23.236 E1.26061 *67
    07:34:31.749 : ok 204
    07:34:31.749 : N205 G1 X-12.971 Y-23.671 E1.27297 *64
    07:34:31.749 : ok 205
    07:34:31.749 : N206 G1 X-10.715 Y-24.775 E1.30826 *73
    07:34:31.765 : ok 206
    07:34:31.765 : N207 G1 X-9.902 Y-25.11 E1.32062 *70
    07:34:31.765 : ok 207
    07:34:31.765 : N208 G1 X-7.525 Y-25.922 E1.35591 *121
    07:34:31.765 : ok 208
    07:34:31.765 : N209 G1 X-6.677 Y-26.153 E1.36827 *115
    07:34:31.780 : ok 209
    07:34:31.780 : N210 G1 X-4.217 Y-26.661 E1.40357 *112
    07:34:31.780 : ok 210
    07:34:31.780 : N211 G1 X-3.346 Y-26.784 E1.41592 *119
    07:34:33.231 : ok 211
    07:34:33.231 : N212 M117 ETE 45m 41s *107
    07:34:33.559 : ok 212
    07:34:33.559 : N213 M105 *7
    07:34:33.559 : ok 213
    07:34:33.559 : N214 G1 X-0.842 Y-26.979 E1.45122 *121
    07:34:33.559 : T:23.33 /0 @:0
    07:34:33.574 : ok 214
    07:34:33.574 : N215 G1 X0.079 Y-26.99 E1.46416 *99
    07:34:34.323 : ok 215
    07:34:34.323 : N216 G1 X2.546 Y-26.872 E1.49887 F900 *2
    07:34:34.417 : ok 216
    07:34:34.417 : N217 G1 X3.42 Y-26.775 E1.51123 *106
    07:34:34.463 : ok 217
    07:34:34.463 : N218 G1 X5.894 Y-26.341 E1.54653 *86
    07:34:34.635 : ok 218
    07:34:34.635 : N219 G1 X6.749 Y-26.135 E1.55888 *83
    07:34:34.697 : ok 219
    07:34:34.697 : N220 G1 X0 Y0 F4800 *99
    07:34:34.869 : ok 220
    07:34:34.869 : N221 G1 Z100 F1000 *37
    07:34:34.916 : ok 221
    07:34:34.916 : N222 M104 T0 S0 *3
    07:34:34.931 : X:0.00 Y:0.00 Z:0.200 E:1.5510
    07:34:34.931 : ok 222
    07:34:34.931 : N223 M140 S0 *70
    07:34:37.412 : TargetExtr0:0
    07:34:37.412 : ok 223
    07:34:37.412 : N224 G1 X0 Y0 F4800 *103
    07:34:37.412 : ok 224
    07:34:37.412 : N225 G1 Z60 F1000 *22
    07:34:37.427 : ok 225
    07:34:37.427 : N226 M84 *57
    07:34:37.427 : ok 226
    07:34:37.427 : N227 M105 *0
    07:34:38.972 : N228 M105 *15

    Here is the start of the G Code file.


     generated by Slic3r 1.2.9 on 2015-08-23 at 07:29:45

    ; external perimeters extrusion width = 0.20mm
    ; perimeters extrusion width = 0.24mm
    ; infill extrusion width = 0.24mm
    ; solid infill extrusion width = 0.24mm
    ; top infill extrusion width = 0.24mm

    G28 ; home all axes
    G1 Z5 F5000 ; lift nozzle
    G21 ; set units to millimeters
    G90 ; use absolute coordinates
    M82 ; use absolute distances for extrusion
    G92 E0
    G1 E-1.00000 F3600.00000
    G92 E0
    G1 Z0.200 F7800.000
    G1 X-22.047 Y-15.521 F7800.000
    G1 E1.10000 F3600.00000
    G1 X-21.324 Y-16.548 E1.11765 F900.000
    G1 X-20.774 Y-17.234 E1.13000
    G1 X-19.082 Y-19.090 E1.16530
    G1 X-18.450 Y-19.702 E1.17766
    G1 X-16.539 Y-21.332 E1.21295
    G1 X-15.836 Y-21.859 E1.22



  • Ok, I see it happening and from timing I have to guess it is G28 doing it, also current 0.92.4 would not do it. Can you update to latest 0.92.4 to be sure you are using the current code. Not sure if we had this in G28 at some time - at least now it is not there any more.

    You should also test before if it is homing. Just set multiplier and home manually. That should reset multiplier already if I'm right.
  • Yes, you are correct. Homing does set the multiplier back to 100%. I will upgrade the firmware to 0.924.

    Thank You.

Sign In or Register to comment.