Forum Replies Created
-
AuthorPosts
-
ZootalawsMemberZootalawsMember
The motion control should aim to get all three axes converging at the same point in time. It uses the feed rate to determine the speed of convergence.
If, for example, your Z has to move 50mm, your A 10mm and your C 5mm, Z will move at the maximum feedrate, with A and C calculated to meet it at the appropriate feed rate to achieve this.
If your C has to move 270 degrees, your A 340 degrees and your Z 0.5mm, all axes will start moving at the same time, but your Z will be moving very slowly in relation to your other two axes.
You also need to factor in the type of motion control planning that TinyG implements, compared to other systems like GRBL. The S-curves of increasing/decreasing acceleration that the TinyG implements is very different from other systems, which makes for very complicated 3-axis movements in accelerate, sustain, decelerate motion.
Like a 3D helix created in real-time to ensure a point is reached in concert.
Unless this is resulting in an incorrect cut, I’m not sure why you should care about the individual rate of movement of each axis.
I must say, I’m a bit confused about what exactly is going wrong.
ZootalawsMemberWhat are your $aam and $cam settings?
You can move rotational axes in two modes: standard (degrees) and radius (linear).
In standard mode, you tell it how many degrees, in radial mode, how far to move.
Are all axes changing rate or just Z? What’s your feed rate maximum set to? What’s your travel minimum, travel maximum set to for your rotating axes?
“Velocity max and feed rate are in degrees per minute and behave as per RS274 NGC v3 feed rate definitions”
NIST doc RS274: https://ws680.nist.gov/publication/get_pdf.cfm?pub_id=823374
A feed rate of 1000 would give you 16.66 degrees/second or ~21 seconds for a full rotation.
ZootalawsMemberEarthing problem
ZootalawsMemberWithout knowing anything about your configuration, type of stop switch, etc.
Could it be that it’s being triggered by induction, movement or similar?
An easy test on such a small piece is to disconnect your stops and manually zero, then run your gcode again. (Unscrew the terminals at the TinyG)
I don’t use CNCjs – there are better senders.
ZootalawsMemberYou’re welcome.
ZootalawsMemberWhat version of firmware are you running?
What does $A and $B and $C tell you?
Have you set the rotary mode? ($aam=3, $bam=3, $cam=3)
ZootalawsMemberIf you connect your vfd pwm inputs to the pwm + – on the TinyG, you can control the speed of your spindle using the TinyG.
Without knowing what vfd you have, impossible to give you more information than that
ZootalawsMemberJust connect + to pwm, – to gnd
ZootalawsMemberI use an OrangePi Zero Plus (about $20 with case, another couple of cents or so for a 12v > 5v step-down) running serial port json server with chilipeppr as my wireless interface. On the same Pi I have Laserweb/CNCWeb host and octoprint, but it took a little fettling.
I use TinyG/G2 with laser and CNC router and it is solid.
If I was going to use external drivers, I would use a Due with G2Core and appropriate shield, rather than a TinyG
- This reply was modified 6 years, 3 months ago by Zootalaws.
ZootalawsMemberEasily.
But that’s not the right question.
It’s not a matter of ‘can it’, it’s a matter of ‘how fast can it’.
With a slow enough feed, it will easily cope with hardwood and aluminium, it you might want it to run faster.
I run 340oz steppers and it works fine.
ZootalawsMemberFirstly, good job at placing your expensive electronic device on an earthed metal conductor. Bonus points for magic smoke!
Second, have you adjusted the drivers power? Have you connected that stepper to a different axis? What happened when you did that?
ZootalawsMemberNice little setup.
ZootalawsMemberI just json it from a stock file.
ZootalawsMemberNo, I meant $defa=1
In my experience, when you get weird results, it’s a good idea to go back to defaults and try with basic settings applied (motor def, direction, etc.).
-
AuthorPosts