Forum Replies Created
-
AuthorPosts
-
ZootalawsMember
You would be better off to use a 12V supply for the laser. It’s probably cheaper than a DC-DC transformer.
The PWM output will be fine to use to control your laser, but you will need to have a different set of operating PWM parameters than you would for a spindle. Your LED laser (I presume) will be expecting a different range than your spindle.
This may help: https://jtechphotonics.com/?page_id=6798
- This reply was modified 2 years, 5 months ago by Zootalaws.
ZootalawsMemberIt’s the same as wiring any 6-wire to an aA4988
This covers it.
ZootalawsMemberNeed to make the CNC move as fast as in the below video link. Can someone help me do it?
I don’t understand the question.
What’s stopping you moving as fast as that machine?
What have you tried and what hasn’t worked?
I want to run like Hussein Bolt. Can someone help me do it?
If you don’t describe your problem, what you’ve done so far, and why yo’ve been unsuccessful, how do you expect someone that knows nothing about your machine to tell you what to do?
$XVM=5000 tells the machine what the maximum velocity should be when executing G0 moves. Why isn’t your machine traversing at that rate? What is happening? Are the TinyG stepper drivers big enough to drive the machine at that rate?
You’re asking a tiny little solid state stepper driver to drive what looks like at least 10kg of hardware at 5 metres a second. 18 km/h. Faster than I can walk and almost the maximum I can run.
I’ve got some pretty hefty machines and nothing I have runs at that rate.
I have a machine with hybrid NEMA32 stepper/servos running at 50V that can just reach that rate, using an advanced DSP controller that is about 20-50x faster than a TinyG
I’m not sure you have defined your needs properly if the TinyG was the answer to your requirement to go 5M/sec.
You certainly haven’t described your issue enough.
ZootalawsMemberWhatever.
ZootalawsMemberAll axes can be homed.
The docs use ‘x’ as the example, but xyz and abc are supported.
ZootalawsMemberYou don’t need to create a UI – there’s plenty out there to use.
Do you want to dedicate a computer to the job, or use a microcontroller or SBC like an ESP32 or Raspberry Pi?
If it was me, I’d buy a cheap Orange Pi clone and run some sort of GCode sender, like UGS: https://winder.github.io/ugs_website/
Load your Raspberry OS, load UGS, connect, send.
Doesn’t get much easier than that.
I would question the use of a TinyG for such a trivial task. A $10 Arduino shield would do the same job.
- This reply was modified 4 years, 7 months ago by Zootalaws.
ZootalawsMemberedit: can’t find the G2 support forum…
Wossappened?
- This reply was modified 4 years, 8 months ago by Zootalaws.
ZootalawsMemberIt’s all in the BOM on the github.
ZootalawsMemberZootalawsMemberTo prove it’s your F360 code, write a really simple G02/G03 arc cut
And create exactly the same thing in F360 – just a simple circle of the same dimensions
ZootalawsMemberYou can go further and make it wireless using ESP32 or Bluetooth.
Works great.
ZootalawsMemberZootalawsMemberThe 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
-
AuthorPosts