tinyg [mm] err: Gcode feedrate error

Home › Forums › TinyG › TinyG Support › tinyg [mm] err: Gcode feedrate error

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • September 10, 2014 at 7:01 am #6746
    bonetti
    Member

    Hi all,

    I have the following error, trying to send g1y0 gCode bloc/line:
    tinyg [mm] err: Gcode feedrate error: g1y0

    I tried this using my personal tinyG configuration properties ($variables), and using the default factory configuration, via $defa=1 command.

    Previously, I executed any g0 command and the rapid motion runs ok, without problems

    I’m sending Gcode files programmaticaly, from an Atmega1284p microController with an Adruino based program, which sends gCode lines via Serial port using the “Serial.println(“gcode”);” command, with a 100 miliseconds + time between commands and checking planner queue (qv=2). I also see what tinyG is responding thanks to a serial capture program (RealTerm).

    So I can verify that the sending system runs ok. G1 command is the only command that doesn’t work by the moment. I executed g0, g4, g20, properties etc successfully

    These are TinyG System properties:
    $fb: Firmware Build 380.08
    $fv: Firmware version 0.96
    $hv: Hardware version 8.00

    Thanks a lot for your help! I whish some day I will help you too

    September 10, 2014 at 10:08 am #6747
    bonetti
    Member

    Edit: Same problem with g2 and g3 command 🙁

    September 10, 2014 at 10:27 am #6748
    bonetti
    Member

    Solved! I miss the “fvalue” at the end of each g1,g2,g3 command

    Wrong command example: g1x5
    Right command example: g1x5f4

    Thanks anyway!

    September 10, 2014 at 10:36 am #6749
    cmcgrath5035
    Moderator

    I believe you need only set feed rate once unless you want to change it.

    Try :

    F4
g1x5
g1x10

    Or

    g1x5f4
g1x10
    September 17, 2014 at 6:04 am #6763
    bonetti
    Member

    Thanks cmcgrath, that’s it!

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.