Using Tinyg with UGS classic and I'm unable to get the machine status to track work and machine positions.
When I orginally setup TinyG with UGS it did track positions but now it is not longer tracking. UGS support suggested I flash the latest firmware (https://github.com/synthetos/tinyg) and I successfully did, this didn't solve issue. Additionally UGS support indicated I may want to try to change the "firmware values".
Any input is greatly appreciated.
Thanks
It would be helpful if you could be a bit more specific on what you call "UGS did track positions..". Are you referring to the display of the tinyG streaming status messages?
Keep in mind I am not super familiar with UGS but understand it to be slightly more enhanced than CootTerm but less display oriented than Chilipeppr or cnc.js
A $$ parameter dump would be useful here, as it answers a bunch of setup questions. Best way to send the $$ dump is to copy the screen to a text file, upload that file to a cloud drive (gdrive, dropbox, etc) and provide a URL for that file.
Here is the work/machine position I need to work with tinyG
https://drive.google.com/file/d/1BffVLdAjP8fNdcXm2JMX22ac6YjL639L/view?usp=sharing
The work/machine position worked when I initially integrated the tinyG. However, it stopped tracking at some point since then and most recently I successfully flashed the latest firmware on github. Are there firmware values that should be changed?
**** Connected to COM7 @ 115200 baud ****
[ready] {"r":{"fv":0.970,"fb":440.20,"hp":1,"hv":8,"id":"3Y2462-PKY","msg":"SYSTEM READY"},"f":[1,0,0,5879]}
>>> {ej:1}
>>> {sr:{posx:t, posy:t, posz:t, mpox:t, mpoy:t, mpoz:t, plan:t, vel:t, unit:t, stat:t, dist:t, frmo:t, coor:t}}
>>> {jv:4}
>>> {qv:0}
>>> {sv:1}
>>> {sr:n}
{"r":{"ej":1},"f":[1,0,7,2003]}
{"r":{"sr":{"posx":0.000,"posy":0.000,"posz":0.000,"mpox":0.000,"mpoy":0.000,"mpoz":0.000,"plan":0,"vel":0.00,"unit":1,"stat":1,"dist":0,"frmo":1,"coor":1}},"f":[1,0,109,1782]}
{"r":{"jv":4},"f":[1,0,7,7333]}
{"r":{"qv":0},"f":[1,0,7,8353]}
{"r":{"err":"{s"},"f":[1,111,3,5694]}
[ready] {"r":{"fv":0.970,"fb":440.20,"hp":1,"hv":8,"id":"3Y2462-PKY","msg":"SYSTEM READY"},"f":[1,0,0,5879]}
>>> {ej:1}
>>> {sr:{posx:t, posy:t, posz:t, mpox:t, mpoy:t, mpoz:t, plan:t, vel:t, unit:t, stat:t, dist:t, frmo:t, coor:t}}
>>> {jv:4}
>>> {qv:0}
>>> {sv:1}
>>> {sr:n}
{"r":{"ej":1},"f":[1,0,7,2003]}
{"r":{"sr":{"posx":0.000,"posy":0.000,"posz":0.000,"mpox":0.000,"mpoy":0.000,"mpoz":0.000,"plan":0,"vel":0.00,"unit":1,"stat":1,"dist":0,"frmo":1,"coor":1}},"f":[1,0,109,1782]}
{"r":{"jv":4},"f":[1,0,7,7333]}
{"r":{"qv":0},"f":[1,0,7,8353]}
{"r":{"err":"{s"},"f":[1,111,3,5694]}
>>> G21G91G1Y0.06F100
>>> G90 G21
{"r":{},"f":[1,0,18,77]}
{"r":{},"f":[1,0,8,4401]}
Here is the work/machine position while actively toggling
https://drive.google.com/file/d/1erEIU8N-w6on2RsvZ9a_btznlRC-5kI8/view?usp=sharing
Any input is appreciated
I could not read the most recent file, just sent an access request.
A Parameter dump ($$ output) might help here.
>>> $$ output
[ready] {"r":{"fv":0.970,"fb":440.20,"hp":1,"hv":8,"id":"3Y2462-PKY","msg":"SYSTEM READY"},"f":[1,0,0,5879]}
>>> {ej:1}
>>> {sr:{posx:t, posy:t, posz:t, mpox:t, mpoy:t, mpoz:t, plan:t, vel:t, unit:t, stat:t, dist:t, frmo:t, coor:t}}
>>> {jv:4}
>>> {qv:0}
>>> {sv:1}
>>> {sr:n}
{"r":{"ej":1},"f":[1,0,7,2003]}
{"r":{"sr":{"posx":0.000,"posy":0.000,"posz":0.000,"mpox":0.000,"mpoy":0.000,"mpoz":0.000,"plan":0,"vel":0.00,"unit":1,"stat":1,"dist":0,"frmo":1,"coor":1}},"f":[1,0,109,1782]}
{"r":{"jv":4},"f":[1,0,7,7333]}
{"r":{"qv":0},"f":[1,0,7,8353]}
{"r":{"sv":0},"f":[1,0,4,1598]}
>>> G21G91G1X-0.06F100
>>> G90 G21
{"r":{},"f":[1,0,19,78]}
{"r":{},"f":[1,0,8,4401]}
Reply #11997
has an open link use that one instead.
Thanks
I am still not sure I understand what you mean by "stopped tracking".
From what I can see in the above, you are now running FW. 440.20
I'll assume you were prior on something earlier (?)
Is you issue that the machine is moving, but the reported values are locked at 0.00?
Is your flow control setting, $ex, consistent with what UGS requires?
Yes, my issue is that the machine is moving, but the reported values are locked at 0.00. Any ideas what might cause this?
Very odd indeed. I am no UGS expert, but looking at the various windows it appears that other numeric values are being returned in status reports.
Difficult to figure out how you might have gotten into this state.
A suggestion would be to send a $defa=1 command
This will reset the entire parameter EEPROM, including some hidden stuff that on occasion gets corrupted.
You will have to re-enter any parameters that you might have customized
That worked!
Thank you for your help!
A frequent cause of EEPROM corruption has been attempts to 'script' sending parameters to tinyG in bulk.
Enter parameter changes manually via the console, one at a time.
Back to TinyG Support or the forum archive.