1,68km, LOL. So doing it the simple way would work so far as register size is concerned, but I think the main motion of the paper needs to be one directional, hence the idea of using either stepped or a composite motion. Any thoughts on what the best general approach would be?
Latest posts made by markdashabout
-
RE: What are the Maximum Dimentions that Duet gcode can handle?
-
RE: S-Curve/ sinusoidal , Jerk +acceleration
Did you say higher pint speeds?
-
What are the Maximum Dimentions that Duet gcode can handle?
I have a general question. And I have a rather obscure application in mind.
What I'd like to know is what are the maximum numbers that can be used in a gcode command.
The application is laser cutting of a piano roll. At the moment the hardware to do this does not exists. A maximum piano roll is 350ft but you still need to cut individual holes in the paper within 0.1mm or less. If we were working in inches, then 5000 inches should cover it and of course this is easily represented as a floating point number. But there are other issues and registers, so the question is what are the real life limits here and what would be the best way to handle this.
I was very interested to see that the Duet board can handle many different geometries. One easy way to do this (which avoids very large numbers) is to paginate it and cut one page at a time, then roll through the next 10 inches (or whatever) and cut that. But it does introduce the possibilities of discontinuity at the page edges.
Another way to handle this would be to have 2 X axis, one that increases perhaps linearly over time from 0 to 3000 inches and the other which has more limited movement so that when you say move to x=1000.2543 inches and X1 is already at 978 inches the X2 motor would move to an absolute position on the carrriage at 22.2543 inches. In this scenario an existing problem is how to keep the X2 parameter within the limited phisical range of the carriage, perhaps if it got near the edges the X1 feed rate could be sped up or slowed down depending on the average X2 position.
Thoughts anyone?