Forum Replies Created
-
AuthorPosts
-
aldenMember
The best way to get 5 steppers at this point is to use the (experimental) G2 code branch on an Arduino Due. The ARM version has the horsepower to properly drive 5 or 6 axes. The code is compatible with the Synthetos gShield to drive the first 3 axes, then you must come up with 2 more drivers. You could jumper in another gShield, or use some pololus or Easydrivers or something like that.
It means you are in for a bit more build on your own. Also the G2 code base is still experimental, but it’s getting pretty good (if I can say so myself).
aldenMemberIf you isolate the questionable axis and just drive a motor does it have these problems? I’m at a loss on this one. I wonder if it’s a driver problem.
aldenMemberI had a thought. What if the Y axes actually move different distances. Perhaps the belts are under different tension and are stretched differently. An experiment would be to disable one of the Y motors and run a move and measure it. Then do the other one and see if you have the exact same travel. Just a thought that occurred to me when I was tightening up my Shapeoko2.
aldenMemberIt sounds like it might be a driver problem. Are the currents set the same, and do you notice any difference if you change them? Also, does it vary with speed – like G1 f100 through G1 f1000 through G0?
aldenMemberTry this again in millimeters (G21). 400 Inches per minute is pretty fast! Or try a move at F15 if you stay in inches mode. Also, check your X axis settings. $x. It sounds like you have the maximum velocity and maximum feedrate settings too high for your motor. The motor will spin during acceleration, then stall, then spin again during deceleration.
- This reply was modified 10 years, 2 months ago by alden.
aldenMemberNot a bad question. Yes, this setup should work on anything that has up to about a 10 nanosecond rise time requirement. Plenty fast for the PWM channel!
aldenMemberI don’t have a breadboard recommendation. There might be some out there. I’d probably just get a DIP version of the chip and breadboard it. You can get 5v off the board – check the schematics. The 125/126 have 4 buffers, so you can do all the pins it you need to.
aldenMemberThe v8 outputs are about 3v to 3.2v from the 3.3v processor. On the v9 (not yet released) we have provided a way to generate 5v outputs, but that doesn’t help you much on the v8. There are 3 ways I can think of to drive the SSR from a v8:
1. Use an external level shifter. The 74LS125 or 126 are good chips for this. Tie the Vcc to 5v and drive the input from the 3v signal. Make sure the enable is set hi or lo depending on which chip you are using.
2. Find an SSR that actually meets its 3v spec. Seems to be easier said than done.
3. Cheat the TinyG board by voiding the warranty. It’s possible to drive the on-board components at up to 3.6v (MCU and stepper drivers). If you change out the voltage setting resistors on the switching regulator you can fiddle with the voltage to – say – 3.5v. This might provide enough lift in the outputs to actually drive a marginal relay. I don’t recommend this – it’s very dicey. One slip and you fry the entire board. But it’s possible
I think option 1 is the best.
- This reply was modified 10 years, 2 months ago by alden.
aldenMemberTemporary fix for the homing issue is in place. See github issue:
https://github.com/synthetos/TinyG/issues/97aldenMemberJuKu – I have opened an issue on Github for $me / $md – let’s move the discussion there if we may:
https://github.com/synthetos/TinyG/issues/98
In short, it’s working for me. I wonder what’s different in your commands and/or setup.
aldenMemberThanks. The issue is on Github here:
https://github.com/synthetos/TinyG/issues/99
I’ve continued the discussion there.
aldenMemberGlad it worked. We have an item to update the wiki with special instructions for Shapeoko2
aldenMemberJuKu – 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.
aldenMemberI think you have to temporarily change over to NO for G38.2. This should probably be logged as an issue on github. Do you remember where you read that NO and NC are OK? I dpn’t recall this, and if it;s out there I’d like to correct it. — Thanks.
aldenMemberFor starters the travel per revolution on motors 1, 2 and 3 is set for the Shapeoko1 which had smaller wheels. (We need to update the wiki with a page especially for the Shapeoko2)
I believe the Shapeoko2 has 20 teeth pre revolution at 2mm per tooth. So the $_tr value should be 40. I’m not sure that will account for all the difference you are seeing, though. Set the value and try lines of defined length, like 100mm. I can’t see anything else incorrect in your settings.
The settings don’t list the firmware revision or build. What $fv and $fb are you running?
-
AuthorPosts