Hopefully the runaway problem is also fixed. Now that the $tr commands have "taken" I will continue with my testing. Finally found that hitting the reset button was the trick Think a power-down / power-up sequence did work. Would not actually transfer to the motors. Tried to change the settings but the settings would not actually apply.Įchoing the setting would give the correct new value, but the new value Checked the $tr settings and found that they had reverted to Then found that the z and y axis were moving much too fast, and x axis Include the avrdude "-e" parameter or it would not work.
#Coolterm tinyg upgrade#
The "easy" firmware upgrade did not work. So I decided to upgrade firmware to 440.16. Like 1000 cut commands would beįine and then you would get one random cut where it would go all the wayĪcross the workspace even past the hard limit, and cutting a big ugly line Issues with runaway cutting using CoolTerm. I purchased the board around 3 months ago. Parameters (using CoolTerm), then you must actually hit the reset button. Power-down / power-up sequence is NOT sufficient.
#Coolterm tinyg windows#
However, the tgupdater or "easy update" is not working in windows It fixes the reset problem you describedĪbove. If not, I will put up another post.Ĥ40.17 has been pushed to master. These runaway cuts, it is a real problem but hopefully it will now be fixed. There are no commands given to move outside the cutting area. I have checked and double checked my cut file and the cuts are correct. With CoolTerm or with tinyg? Probably need to look for a CoolTerm alternative, just so I can rule it out as a possible source of problems. It is not always clear where the source of the runaway problem would be. Finally found that hitting the reset button was the trick to get the $tr settings to apply. But for the $tr settings, it did not work. For some of the settings, I think a power-down / power-up sequence did work. Echoing the setting would give the correct new value, but the new value would not actually transfer to the motors. Tried to change the settings but the settings would not actually apply. Checked the $tr settings and found that they had reverted to certain defaults which were wrong. Then found that the z and y axis were moving much too fast, and x axis much too slow. Had to include the avrdude "-e" parameter or it would not work. Like 1000 cut commands would be fine and then you would get one random cut where it would go all the way across the workspace even past the hard limit, and cutting a big ugly line into your project. I was having intermittent issues with runaway cutting using CoolTerm. After having sent your parameters (using CoolTerm), then you must actually hit the reset button. I would like to also emphasize that a power-down / power-up sequence is NOT sufficient.
0 kommentar(er)
