Forum Replies Created
-
AuthorPosts
-
October 13, 2013 at 9:27 am in reply to: Could Jerk be causing my extended ShapeOko to miss steps? #4760MakerboostMember
I tried lowering my $xjm and $yjm to 100.000, but it still skipped on the same lines.
I lowered my $xjd and $yjd to 0.01, and it didn’t slow down in the offending corners like it did on every other junction.
Could there be a mistake in the G-code?- This reply was modified 11 years, 1 month ago by Makerboost.
MakerboostMemberThank you for the clearification and the helpful tips!
MakerboostMemberI’ve got a v8 board and I’ve had lots of problems with noise.
I realized that it was mostly stuff I could fix like shielding and keeping signal cables away from stepper motor/cables and spindle cable. Put some ferrite cores on most of the wires.
Now I’ve run problem free for a few days when I before couldn’t even run a single job without random stops.I had an issue where the TinyG would skip or make arcs very tiny, and then just traverse to the next point causing it to dig into the material at high speeds.
I flashed it with the newest firmware, and now it runs fine again.MakerboostMemberI think I read somewhere on this forum that the TinyG doesn’t always give a response back.
I’d be interested in knowing this too actually.
MakerboostMemberI would recommend reading the ShapeOko Wiki for a good first-steps introduction.
I’ve got a ShapeOko with TinyG, and I’ve finally gotten it to work well. I’ve made a lot of mistakes, but have learned so much.
The most important lesson is proper shielding of stepper wires and limit signals, proper grounding of the machine, and reducing the noice from the spindle.Let us know if there’s a specific thing you’d like to know more about 😉
MakerboostMemberJust wanted to let you know that I’ve been running fine for a while with Coolterm, but I can’t try it out in tgFX until it recognizes the new firmware version.
MakerboostMemberI’ve got the same problem with tgFX after I updated my TinyG’s firmware to latest version. tgFX just can’t recognize the new version.
Also, I understand that tgFX doesn’t use XON/XOFF like a normal terminal client, but controls TinyG differently. This has caused my TinyG’s $ex value to revert to 0 every time I start up tgFX.I’m now using Coolterm, and it works, but it’s not ideal since I’ve gotten used to the visual feedback.
MakerboostMemberRan it 3 times, all without problems.
4th time I cut my piece, came out fine.I still have to run more tests, but it seems like the firmware flashing helped. Too bad about tgFX, I really liked that UI.
MakerboostMemberFlashed the new 380.05 (0.96) firmware, can’t connect with tgFX any longer. Stuck at “Getting TinyG Firmware Build Version….”
Connected with CoolTerm, set up all correct values, ran the g-code file without any problems.
Going to run it 10 more times before I trust it.MakerboostMemberDisconnected all cables, soldered the limit grounds to common wire that I connected to the TinyG. Put ferrite beads on all 5v cables.
Found stepper motor cable that wasn’t inserted correctly into screw terminal. It was underneath instead of inside the fixture. Fixed.
Connected and tried the g-code file once more, but it failed at the same place as before. Around line 40-45.
MakerboostMemberNo change. After running for a couple of minutes, it buried itself into the material with a sudden traverse. Seems like it just skipped a bunch of G-code steps.
Tried a new fresh computer, fresh install of tgFX, newest FTDI drivers with the XON-XOFF bugfix, and it’s even worse.
MakerboostMemberI noticed I was using the 32bit version of tgFX on my Windows 7 x64 machine. I have installed the latest 64bit version, so I tried that instead.
The UI is very laggy, but the program works.
I also tried adjusting the pots up a little on every axis to see if that made a difference.
Will let you know how it goes.
-
AuthorPosts