Forum Replies Created
-
AuthorPosts
-
perfectphaseMember
That’s awesome, thanks. I’m traveling at the moment, will have a play when I get home.
perfectphaseMemberHi, just thought I’d post a slightly simpler example, this is on 435.10
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.
perfectphaseMemberHi all, thanks for taking the time to respond.
I have updated to 435.10. Still locks up, here is a modified sequence that causes a problem
http://pastebin.com/0HwGTazR
http://pastebin.com/BzCuAa2HA dump of my config is http://pastebin.com/zbXCnZ6Y
I’ve also noticed I’m getting ‘prep_null encountered’ quite a bit, for example
Hope that helps a bit.
Thanks
Stephen.
P.S. I notice from the startup and commits that the defaults have been changed so $defa in 435.10 loads the defaults for the Shapeoko 375mm rather than the “Default settings for release” profile.
perfectphaseMemberHi, think I’ve worked it out, its
G10 P2 L2 X100 Y100
Cheers,
Stephen.
-
AuthorPosts