Possible bad position updates

Home Forums TinyG TinyG Support Possible bad position updates

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #6288
    perfectphase
    Member

    Hi, While messing with different offsets I’ve noticed something strange

    I’m moving the machine around, changing to G55 then forcing a move in machine absolute, in G53, but the position that is reported is reported as absolute rather than G55 for the duration of the move, without reporting as change in “coor”.

    Also, after the move is complete a message “prep_null encountered” is reported.

    The script to reproduce is

    {“r”:{“fv”:0.970,”fb”:435.07,”hp”:1,”hv”:8,”id”:”2U2971-YKY”,”msg”:”SYSTEM READY”},”f”:[1,0,0,5141]}
    {“qr”:28,”qi”:1,”qo”:1}
    {“gc”:”g0x10y10″}
    {“r”:{},”f”:[1,0,18,77]}
    {“sr”:{“line”:0,”posx”:0.000,”posy”:0.000,”posz”:0.000,”posa”:0.000,”feed”:0.00,”vel”:0.01,”unit”:1,”coor”:1,”dist”:0,”frmo”:1,”momo”:0,”stat”:5}}
    {“qr”:27,”qi”:1,”qo”:0}
    {“sr”:{“posx”:0.005,”posy”:0.005,”vel”:16.59}}
    {“sr”:{“posx”:0.062,”posy”:0.062,”vel”:91.50}}
    {“sr”:{“posx”:0.257,”posy”:0.257,”vel”:244.37}}
    {“sr”:{“posx”:0.642,”posy”:0.642,”vel”:439.51}}
    {“sr”:{“posx”:1.295,”posy”:1.295,”vel”:656.85}}
    {“sr”:{“posx”:2.137,”posy”:2.137,”vel”:840.79}}
    {“sr”:{“posx”:3.198,”posy”:3.198,”vel”:952.75}}
    {“sr”:{“posx”:4.353,”posy”:4.353,”vel”:997.21}}
    {“sr”:{“posx”:5.470,”posy”:5.470,”vel”:999.20}}
    {“sr”:{“posx”:6.632,”posy”:6.632,”vel”:967.28}}
    {“sr”:{“posx”:7.663,”posy”:7.663,”vel”:863.07}}
    {“sr”:{“posx”:8.586,”posy”:8.586,”vel”:697.69}}
    {“sr”:{“posx”:9.276,”posy”:9.276,”vel”:483.46}}
    {“sr”:{“posx”:9.696,”posy”:9.696,”vel”:282.51}}
    {“sr”:{“posx”:9.920,”posy”:9.920,”vel”:116.31}}
    {“sr”:{“posx”:9.990,”posy”:9.990,”vel”:26.61}}
    {“sr”:{“posx”:10.000,”posy”:10.000,”vel”:0.32}}
    {“sr”:{“posx”:10.000,”posy”:10.000,”vel”:0.00,”stat”:3}}
    {“qr”:28,”qi”:0,”qo”:1}
    {“gc”:”g10l2p2x10y10″}
    {“r”:{},”f”:[1,0,23,103]}
    {“gc”:”g55″}
    {“r”:{},”f”:[1,0,13,72]}
    {“sr”:{“posx”:0.000,”posy”:0.000,”coor”:2}}
    {“mpo”:””}
    {“r”:{“mpo”:{“x”:10.000,”y”:10.000,”z”:0.000,”a”:0.000,”b”:0.000,”c”:0.000}},”f”:[1,0,11,7353]}
    {“gc”:”g53x0y0″}
    {“r”:{},”f”:[1,0,17,76]}
    {“sr”:{“posx”:10.000,”posy”:10.000,”vel”:0.01,”stat”:5}}
    {“qr”:27,”qi”:1,”qo”:0}
    {“sr”:{“posx”:9.996,”posy”:9.996,”vel”:12.61}}
    {“sr”:{“posx”:9.943,”posy”:9.943,”vel”:85.79}}
    {“sr”:{“posx”:9.771,”posy”:9.771,”vel”:226.11}}
    {“sr”:{“posx”:9.384,”posy”:9.384,”vel”:428.59}}
    {“sr”:{“posx”:8.744,”posy”:8.744,”vel”:646.41}}
    {“sr”:{“posx”:7.912,”posy”:7.912,”vel”:825.05}}
    {“sr”:{“posx”:6.858,”posy”:6.858,”vel”:948.63}}
    {“sr”:{“posx”:5.764,”posy”:5.764,”vel”:995.57}}
    {“sr”:{“posx”:4.588,”posy”:4.588,”vel”:999.47}}
    {“sr”:{“posx”:3.425,”posy”:3.425,”vel”:970.43}}
    {“sr”:{“posx”:2.389,”posy”:2.389,”vel”:877.00}}
    {“sr”:{“posx”:1.455,”posy”:1.455,”vel”:707.65}}
    {“sr”:{“posx”:0.781,”posy”:0.781,”vel”:505.51}}
    {“sr”:{“posx”:0.320,”posy”:0.320,”vel”:292.35}}
    {“sr”:{“posx”:0.087,”posy”:0.087,”vel”:123.00}}
    {“sr”:{“posx”:0.011,”posy”:0.011,”vel”:29.57}}
    {“sr”:{“posx”:0.000,”posy”:0.000,”vel”:0.53}}
    prep_null encountered
    {“sr”:{“posx”:-10.000,”posy”:-10.000,”vel”:0.00,”stat”:3}}
    {“qr”:28,”qi”:0,”qo”:1}

    Cheers,

    Stephen.

    • This topic was modified 10 years, 4 months ago by perfectphase.
    #6301
    perfectphase
    Member

    Hi, just thought I’d post a slightly simpler example, this is on 435.10

    http://pastebin.com/BDkMdSX0

    I reset the board to defaults and reset. Lines 6 & 9 set an offset. Perform a simple move in line 12 and get a status update in 15.
    If you then switch to g55 (line 16), you do not get a status report with the updated coor or position, and again nothing when you switch back. If you issue status requests after each set the reported values are correct.
    Interesting thing is if you then repeat the above g55, g54 switch (line 29) you do get status reports published.

    Sorry If this all sounds rather OCD, I know I’m on an EDGE build and you have bigger fish to fry, but I’ve been writing my own UI for TinyG (for fun) and have noticed this when my UI does not update after switching offsets, easily fixed by always sending a sr after each update, but thought I’d mention it.

    The ‘prep_null encountered’ issue seems to be related to setting an offset with G10 rather than $g55x, then preforming a move directly afterwards.

    Cheers,

    Stephen.

    • This reply was modified 10 years, 4 months ago by perfectphase.
    #6303
    alden
    Member

    Not OCD. Looks like you are using stock shapeoko settings. Ill try to reprocess this when I get back to the shop.

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