No Motion output after g2core upgrade.

Home › Forums › TinyG › TinyG Support › No Motion output after g2core upgrade.

Tagged: , , , , ,

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • June 20, 2018 at 8:40 pm #11021
    marv2097
    Member

    Hi,

    After upgrading g2core on the Due, the same gcode file that did work well now doesn’t create any motion output..

    I’m new to tinyg and looking to control a plasma table. To get started I flashed the binary from http://synthetos.github.io/g2/ to the Due and used ChiliPeppr to control it. The Binary was named “Due+gShield edge 078.03”.

    Using linux as my dev machine I cloned the git master branch, complied and loaded this onto the Due, this connects in ChiliPeppr and shows the following build details:

    [fb]  firmware build             100.26
[fbs] firmware build "100.26-10-g1ff7"
[fbc] firmware config "settings_default.h"
[fv]  firmware version            0.99
[hp]  hardware platform           3.00
[hv]  hardware version            0.00

    The problem comes when I try to run the same gcode as before. It appears to send the gcode to the due but reports its been executed in 00:00:00 and no output is seen. The gcode is really simple to avoid this being an issue. It is only 15 lines and simulates fine but wont produce any output when its run.

    N1 (1001)
N2 (50MM SQUARE)
N3 G21 G90 G64 G40
N4 T0 M6
N5 G17
N6 M3 S1000
N7 G0 X0 Y0 Z10
N8 G1 Z-1 F400
N9 G1 X50 Y0
N10 G1 X50 Y50
N11 G1 X0 Y50
N12 G1 X0 Y0
N13 G0 Z15
N14 M5
N15 M30

    I have also tried loading the latest edge version 101.03 and this has the same result. I am using SPJS 1.95. Jogging also doesn’t work in the later versions.

    Has anyone any idea what I am doing wrong?

    Many Thanks
    Marv

    June 21, 2018 at 1:36 pm #11023
    marv2097
    Member

    I seem to have narrowed down the problem a little.. On edge ver 101.03 I seem to have issues getting any linear motion to work.

    G0 and G1 codes have no effect but G2 and G3 do. To test this I reset the due and issue A G1 code with from the Chilipeppr console, the response I get indicates no movement:

     G01 X50 F1000
{"r":{},"f":[1,0,14]}
{"sr":{"stat":3,"feed":1000,"momo":1}}

    However if I send a G2 code then i get movement and also pulses on the step pins.

     G02 I5 F1000
{"r":{},"f":[1,0,13]}
{"qr":4}
{"sr":{"posx":0.46233,"posy":2.07757,"vel":845.81,"stat":5,"momo":2,"mpox":0.47137,"mpoy":2.09634}}
{"qr":7}
{"sr":{"posx":3.20353,"posy":4.65577,"vel":841.57,"mpox":3.20353,"mpoy":4.65577}}
{"qr":12}
{"sr":{"posx":6.47414,"posy":4.76734,"vel":824.09,"mpox":6.47414,"mpoy":4.76734}}
{"qr":17}
{"sr":{"posx":9.37074,"posy":2.40753,"vel":885.66,"mpox":9.37074,"mpoy":2.40753}}
{"qr":22}
{"sr":{"posx":9.92472,"posy":-0.82455,"vel":786.12,"mpox":9.92472,"mpoy":-0.82455}}
{"qr":27}
{"sr":{"posx":8.02448,"posy":-3.97016,"vel":951.86,"mpox":8.02448,"mpoy":-3.97016}}
{"qr":32}
{"sr":{"posx":4.80239,"posy":-4.99383,"vel":760.89,"mpox":4.80239,"mpoy":-4.99383}}
{"qr":37}
{"sr":{"posx":1.5633,"posy":-3.61922,"vel":1000,"mpox":1.5633,"mpoy":-3.61922}}
{"qr":42}
{"qr":47}
{"sr":{"posx":0.03265,"posy":-0.50854,"vel":653.04,"mpox":0.03265,"mpoy":-0.50854}}
{"sr":{"posx":0,"posy":0,"vel":0,"stat":3,"mpox":0,"mpoy":0}}

    Is this a bug or could I have some config related issue that could cause this?

    June 24, 2018 at 8:41 am #11028
    cmcgrath5035
    Moderator

    When you built 101.03, did you build for DUE-gShield?
    BTW, there as a pre-built version here https://github.com/synthetos/g2/releases/download/101.03/g2core-gShield-101.03.bin

    Check that the Motors are enabled, I believe that they are disabled by the default settings.h.

    This does sort of sound like a config issue

    June 25, 2018 at 7:39 am #11030
    marv2097
    Member

    Thanks cmcgrath, yes used the following MAKE command:

    `make PLATFORM=DUE BOARD=gShield’

    I will try the pre-built binary and see if its any different. At the moment im not using a shield, just taking step/dir from the relevant pins.

    What I dont understand is that with the same config/setup i get movement for any G02 and G03 codes but not for G00 or G01. It just skips past them like its not processing them. Even when in the same file it will skip the linear moves but arc’s work fine.

    At the moment I dont have any way to debug the HW but if there is any other commands I can run on there to get more info then let me know.

    Cheers

    June 25, 2018 at 10:10 am #11031
    marv2097
    Member

    Ok so I tried the downloaded. binary and get the same results.

    I have also managed to get a G01 code to work if I directly send it using minicom. So I suspect somewhere an issue with either Chilipeppr or SPJS is more likely than the g2core based on what im seeing. More testing needed i think but I am getting closer.

    June 25, 2018 at 7:40 pm #11034
    cmcgrath5035
    Moderator

    Good luck, many Chilipeppr users are using G2core, perhaps look at their Group chats.

    October 3, 2018 at 5:42 am #11131
    mgrl
    Member

    hi!

    had the same issue (g1/g0 not working, g2 working) with the version g2core-gShield-101.03.bin loaded and flashed from here https://github.com/synthetos/g2/releases/tag/101.03

    I compiled my own version for gShield-Configuration with win7 64bit in atmel studio 7 – now it works as expected.

    Was happy I found this topic, since I didn’t know what I did wrong – it seems nothing?

    October 4, 2018 at 5:58 pm #11134
    cmcgrath5035
    Moderator

    Do you have a diff tool in Win10 land?
    I’m curious to know if the file you built and the 101.03 you loaded are the same.

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