I opened this thread to open discussion on any issues people are having with the latest edge builds - firmware build 435.xx series / firmware version 0.97
We think this is a pretty clean build, but it (always) deserves more testing and field experience. When it shakes out it will be promoted to the master branch.
I was out of town this weekend, but tested it now when I came home: Both versions .07 and .08 fix the feedrate issues. No hasted circles, no clunking noises (I believe the clunk was when it tried to drive the motor too fast).
Now for the tests that grath asked, with versions 435.06 and .08:
Test 1
(machine freshly reset and at 0/0/0)
G0 X0.8 (06: X motor does not move; 08: X moves to X0.8)
G0 X1 (06: X moves to physical X1; 08: X moves to X1)
G0 X0 (06: X moves to physical X0; 08: X moves to X0).
Test 2
(machine freshly reset and at 0/0/0)
G0 X0.8 (06: no move; 08: X moves to X0.8)
G1 Z-1 F100 (06: Z axis moves ok, X axis moves to X0.8; 08: Z OK, X does not move)
Thanks for the testing. I am continuing to run tests on this. I plan to push these to edge early this coming week assuming there are no other issues that show up. Please let me know how it goes. Thanks again.
PS - with standard shapeoko settings the G0 movement should work down to about 0.02mm
I have completed some initial testing on various 2.5d and 3D milling jobs including a lot of Arcs and Z-axis movement and this build ran flawlessly. The Only issue I had was self induced, I forgot to save my settings before flashing the tinyG but got it all configured just took a little more time :).
JuKu - thanks for the heads up. I'll post these as github Issues and look into them. I may need to come back to you for settings or other information if I cannot reproduce these.
Please post anything else you find - or just put it up as an Issue directly.
Found it. Older version of the firmware did obey $me/$md even when $_pm was set to 0. I am using a settings dump that load my settings to TinyG after firmware update; that had individual motor power managements turned off, which still allowed global power management. Sorry for the false alarm. (I updated Github also.)
This topic is from the original forum (August 2014). Your reply starts a new discussion linked to it.